HomeMy WebLinkAbout063732-PM1 - Construction-Related - Contract - Mercantile Partners, L.P. and Bob Moore Construction Inc.Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E1256FORT WORTHCONTRACTFORTHE CONSTRUCTION OFMEACHAM BOULEVARD AT MERCANTILE DMVEIPRC Record No. IPRC24-0018City Project No. 105417FID No. 30114-0200431-105417-E07685X-FUe No. X-XXXXXFile No. K-3228IVtattie Parker Jesus "Jay" ChapaMayor City ManagerChris HarderDirector, Water DepartmentLauren PrieurDirector, Transportation and Public Works DepartmentPrepared forThe City of Fort WorthJuly 2025WestwoodWESTWOOD PROFESSIOANL SERVICES, INC.500 WEST 7™ STREETFORT WORTH, TX 76102TBPELSFirm #10074301Firm #117 56E 250 TE 250 PROFESSIONAL ENGI
N
E
ERLICENSED S
T
ATE OF TEXASKOLE T. WEBER1203168/16/20248/20/2025CSC No. 63732-PM1
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 00 00STANDARD CONSTRUCTION SPECIFICATION DOCUMENTSPage 1 of 5SECTION 00 00 10TABLE OF CONTENTSDEVELOPER AWARDED PROJECTSDivision 00 - General ConditionsLast Revised00 11 130021 130041 0000 42 430013 130015 110045 120015 1300 45 2600^15^1000 52 4300 61 2500621300 62 1400621900 72 0000 73 000073 10Invitation to BiddersInstructions to BiddersBid FormProposal Form Unit PriceBid BondBidders Prequalification'-sPrequalification StatementBidder Prequalification ApplicatiefiContractor Compliance with Workers' Compensation LawMinority Business Enterprise GoalAgreementCertificate of InsurancePerformance BondPayment BondMaintenance BondGeneral ConditionsSupplementary ConditionsStandard City Conditions of the Construction Contract for DeveloperAwarded Projects03/20/202003/20/202004/02/201405/22/2019(M ,02/20110/1,02/20 M09/01/201503/09/202004/02/201408/21/201806/16/201607/01/201101/31/201201/31/201201/31/201211/15/201707/01/201101/10/2013Division 0101 11 0001 25 000131 1901 312001 323301 33000135 1301 45 2301 500001 55260157 1301 600001 66 0001 700001 712301 74 2301771901 782301 7839General RequirementsSummary of WorkSubstitution ProceduresPreconstmction MeetingProject MeetingsPreconstmction VideoSubmittalsSpecial Project ProceduresTesting and Inspection ServicesTemporary Facilities and ControlsStreet Use Permit and Modifications to Traffic ControlStorm Water Pollution Prevention PlanProduct RequirementsProduct Storage and Handling RequirementsMobilization and RemobilizationConstruction StakingCleaningCloseout RequirementsOperation and Maintenance DataProject Record DocumentsLast Revised12/20/201208/30/201308/30/201307/01/201108/30/201308/30/201308/30/201303/20/202007/01/201107/01/201107/01/201103/20/202004/07/201404/07/201404/07/201404/07/201404/07/201404/07/201404/07/2014CITY OF FORT WORTHSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTSRevised March 8, 2024Meacham Boulevard at Mercantile DriveCPN:10S4n
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 00 00STANDARD CONSTRUCTION SPECIFICATION DOCUMENTSPage 2 of 5Technical Specifications which have been modified by the Engineer specifically for thisProject; hard copies are included in the Project's Contract DocumentsNONETechnical Specifications listed below are included for this Project by reference and can beviewed/downloaded from the City's website at:http://fortworthtexas.gov/tpw/contractors/Division 02 -0241 1302^1 110241 15existing ConditionsSelective Site DemolitionUtility Removal/AbandonmentPaving RemovalLast Revised12/20/201212/20/201202/02/2016Division 03 - ConcreteDivision 26 - Electrical03 30 0003 34 1303 34 1603 80 00Cast-In-Place ConcreteControlled Low Strength Material (CLSM)Concrete Base Material for Trench RepairModifications to Existing Concrete Structures12/20/201212/20/201212/20/201212/20/201226 05 0026 05 1026 05 3326 05 d326 05 50Common Work Results for ElectricalDemolition for Electrical SystemsRacewaya and Boxes for Electrical SystemsUnderground Ducta and Raceways for Electrical SystemsCommunications Multi Duct Conduit11/22/201312/20/201212/20/201207/01/201102/26/2016Division 31 -31 10003123 1631 23 23312/100312500313600313700EarthworkSite ClearingUnclassified ExcavationEmbankmentsErosion and Sediment ControlGabions12/20/201201/28/201301/28/201301/28/201312/20/201212/20/201212/20/2012Division 32 -3201 173201 1832012932 11 2332 11 2932113332 113732121632 12 7332 13 1332 13 20exterior ImprovementsPermanent Asphalt Paving Pi-epatfTemporary Asphalt Paving Repay--Concrete Paving RepairFlexible Base CoursesLime Treated Base CoursesCement Treated Base CoursesLiquid Treated Soil StabilizerAsphalt PavingAsphalt Paving Crack SealantsConcrete PavingConcrete Sidewalks, Driveways and Barrier Free Ramps12/20/201212/20/201212/20/201212/20/201212/20/201212/20/201208/21/201512/20/201212/20/201212/20/201206/05/2018CITY OF FORT WORTHSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTSRevised March 8, 2024Meacham Boulevard at Mercantile DriveCPN:105417
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 00 00STANDARD CONSTRUCTION SPECIFICATION DOCUMENTSPage 3 of 532 13 73Concrete Pavmg Joint Sealants12/20/201232 U 16Brick Unit Paving12/20/2012321613Concrete Curb and Gutters and Valley Gutters10/05/201632 17 23Payment Markings11/22/201332 17 25Curb Address Painting11/01/20133231 13Chain Fences and Gates12/20/2012•^6Wire Fences and Gates12/20/2012323129Wood Fences and Gates12/20/20123232 13Cast in Place Concrete Pi-etaining Walls06/05/20183291 19Topsoil Placement and Finishing of Parkways12/20/2012329213Hydro Mulching, Seeding, and Sodding12/20/20123293^3Trees and Shrubs12/20/2012Division 33 - Utilities-W40-Sewer and Manholc Testing12/20/20123301 31Closed Circuit Television (CCTV) Inspection03/03/201633 03 10Bypass Pumping of Existing Sewer Systems12/20/201233 Od 10Joint Bonding and Electrical Isolation12/20/2012330/1 11Corrosion Control Test Stations12/20/2012330^ 12Magneoium Anode Cathodic Protection System12/20/201233 0^ 30Temporary Water Services~y —vv'Ttwioci. VIL'CUCleaning and Acceptance Testing of Water MainsS^£StVlT,07/01/20110440.uumiiy. unu J'VUUUULUIIUICleaning of Sewer Mains'02/06/2013015012/20/201;33 05 10Utility Trench Excavation, Embedment, and Backfill12/12/201633 05 12Water Line Lowering12/20/201233 05 13Frame, Cover and Grade Rings - Cast Iron01 /22/20163305 13.10Frame, Cover and Grade Rings —Composite01/22/201633 05 14Adjusting Manholes, Inlets, Valve Boxes, and Other Structures to12/20/201233 05 16Concrete Water Vaults12/20/20123305 17Concrete Collars12/20/2012-95-^0Auger Boring12/20/2012330521Tunnel Liner Plate12/20/201233 05 22Steel Casing Pipe12/20/2012-95-^Hand Tunneling12/20/201233 05 2^1Installation of Carrier Pipe in Casing or Tunnel Liner Plate06/19/201;33 05 26Utility Marlcers/Locators12/20/2012-95-^0-Location of Existing Utilities12/20/201244-^5-Bolts, Nuts, and Gaskcts12/20/201233 11 10Ductile Iron Pipe12/20/201233 11 11Ductile Iron Fittings12/20/201233 11 12Polyvinyl Chloride (PVC) Pressure Pipe11/16/201833 11 13d.oncrete Pressure Pipe, Bar Wrapped, Steel Cylinder Type12/20/20124^-44Buried Steel Pipe and Fittings12/20/201233 1210Water Services 1 inch to 2 inch02/11/201733 12 11Large Water Metera12/20/20124Q-WPi-csilient Seated Gate Valve12/20/201233 1221AWWA Paibber Seated Butterfly Valvoa12/20/2012CITY OF FORT WORTHSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTSRevised March 8, 2024Meacliam Boulevard at Mercantile DriveCPN:W54H
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 00 00STANDARD CONSTRUCTION SPECIFICATION DOCUMENTSPage 4 of 533 1225Connection to Existing Water Mains02/06/201;33 1230Combination Air Valve Assemblies for Potable Water Systems12/20/201233 12^0Fire Hydrants01/03/201133 1250Water Sample Stations12/20/201233 12 60Standard Blow off Valve Aascmbly06/19/20133331 12Cured in Place Pipe (C-ff^12/20/20123331 13Fiberglaos Reinforced Pipe for Gravity Sanitary Sewers12/20/20123331 15High Density Polyethylene (HDPE) Pipe for Sanitaiy Sewer12/20/20123331 20Polyvinyl Chloridc (PVC) Gravity Sanitaiy Sewer Pipe06/19/2013333121Polyvinyl Chloridc (PVC) CloGcd Profile Gravity Sanitaiy Sewer12/20/20123331 22Sanitary Scwor Slip LiniHg12/20/2012-^-^Sanitary Sewer Pipe Enlargement12/20/2012333150Sanitary Sewer Service Connections and Service Line0/1/26/201;^-wCombination Air Valve for Sanitary Sewer Force Mains12/20/2012333910r-^ast in Place Concrete Manholes12/20/2012wPrecaot Concrete Manholes12/20/2012333930Fiberglass Manhetes12/20/20123339^10Wastewater Access Chamber (WAC)12/20/201233 39 60Epoxy Liners for Sanitary Sewer Structures12/20/201233^11 10Reinforced Concrete Storm Sewer Pipc/Culverts07/01/2011-4^-44High Density Polyethylene (HDPE) Pipe for Storm Drain12/20/201233/11 12R.cinforced Polyothlcno (SP.PE) Pipe11/13/2015-46-90iubdrainagc12/20/201233^1601Slotted Storm Drains07/01/2011331602Trench Drains07/01/201133/19 10Cast in Place Manholes and Junction Boxes12/20/20124920Curb and Drop Inlets12/20/2012-49-4QStorm Drainage Headwalls and Wingwallo07/01/2011Division 34 -3441 103441 10.013441 10.023441 10.033^1 ^11 1131 ^11 133^ ^1 1531 ^11 16344120344120.013^1 1120.0231 ^1 20.033441 3031 ,11 503471 13FransportationTraffic SignalsAttachment A - Controller CabinetAttachment B - Controller SpecificationAttachment C - Software SpecificationTemporary Traffic SignalsRemoving Traffic SignalsRectangular Puipid Flashing BcaeeBPedestrian Hybrid SignalRoadway Illumination AssembliesArterial LED Roadway LuminairesFreeway LED P^oadway LuminairesPresidential LED P^oadway LuminairesAluminum SignsSingle Mode Fiber Optic GabteTraffic Control10/12/201512/18/201502/201201/201211 /22/201312/20/201211/22/201311/22/201312/20/201206/15/201506/15/201506/15/201511/12/201302/26/201611/22/2013CITY OF FORT WORTHSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTSRevised March 8, 2024Meacham Boulevard at Mercantile DriveCPN: 105417
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 00 00STANDARD CONSTRUCTION SPECIFICATION DOCUMENTSPage 5 of 5AppendixGC ^1.01 —Availability of LandsGC /1.02 —Subsurface and Physical ConditionsGC /\.0/\ —Underground FacilitiesGC •1.06 —Hazardous Environmental Condition at SiteGC 6.06.D —Minority and Women Owned Business Enteiprise ComplianceGC 6.07 —Wage R-ateaGC 6.09 —Permita and UtilitiesGC 6.2^1 —NondiscriminationGR-01 60 00 Product RequirementsEND OF SECTIONCITY OF FORT WORTH Meacham Boulevard at Mercantile DriveSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTS CPN: 10541 7Revised March 8, 2024
SECTION 00 42 43Developer Awarded Projects - PROPOSAL FORM,P.BtD PROPOSAIUNIT PRICE BIDBidder's ApplicationProject Item Inf&misuonBidlistlteiNo.1234567DescnptionUNIT B: PAVING(213.0503 BARRIER FREE RAMP, TfrPE M.l1213.0504 BARRIER FREE RAMP, TVPE M-2t213.0505 BARRIER FREE RAM?, T/PE M-31213.0510 BARRiER FREE RAMP, T^PE C-3)999.0001 STAMPED CONCRCTE (4"i>999.0002 IN LET PROTECTION1999.0003 TREE PROTECTIONSpecification SwkNo,IPROVEMENTS3213 2032 13 2032 13 2032 13 2099 99 9999 99 9999 99 99Unit ofMeasweEAEAEAEA5YEAEABidQiuntity1241448741TOTAL UNIT B: PAVING IMPROVEMENT;1234567891011121314151617181920212223242527282930313233343536373839404142434445464748495051525354UNIT C: TRAFFIC SIGNALS AND STRIPINGS1441.1001 FURNISH/iNSTALL 3-SECT SIGNAL HEAD ASSEMBLE[441.1002 FURNISH/1NSTALI 4-SECT SIGNAL HEAD ASSEMBL'i1441.1031 FURN1SH/1NSTALL AUDIBLE PEDESTRIAN PUSHBUTTON>TATiONS441.1209 FURNiSH/tHSTALL BBU SYSTEM EXT MOUNTEC1441.1215 FURNISH/tNSTALL HYBRID DETECTION DE\/iCE[441.1220 FURNISH/1NSTALL MODEL 711 PREEMPTiOH DCTECFOR1441.1224 FURNtSH/iNSTALL PfiEEMPTION U8LE[441.1250 FURNISH/INSTALL PTZ CAMERA1441.1260 FURN1SH/IN STALL CATS ETHERNET CABLE1441.13115/C 14 AWG MUITI.CONDUCTOR CABIE1441.1312 7/C 14 AWG MULThCONDUCTOR UBLi1441.1314 10/C 14 AWG MUITI.CONDUCTOR CABLE1441.1315 20/C 14 AWG MULTI-CONOUCTOfi CABLE1441.1322 3/C 14 AWG MULTI.CONDUCTOR UBLE[441.1408 NO 6 INSULATED ELEC CONDF1441.1410 NO 10 INSULATED ELEC CONOF1441.1414 NO 8 8ARE ELEC CONOF1441.1502 FURNISH/INSTALl GROUND BOX TCPE B, W/APFtO^1441.1503 FURNISH/iNSTALl GROUND BOX T/PE D. W/APRO^1441.1603 FURN5SH/1NSTALI 10'-20' FED POLE ASSMBU1441.1613 FURNSSH/1NSTALL TYPE 43 SiGNAL POLf!441.1615FURN!SH/INSTALLTt'PE45S!GNALPOL(!441.1624 FURNISH/INSTALL MAST ARM 40'-481441.1625 FURNtSH/INSTALL MAST ARM S2'-601441.1701 TV 1 SIGNAL FOUNDATiC^,441.1705 Tt' 5 SIGNAL FOUNDATION.441.1709 FED POLE (10-14') SPREAD FOOTING FOUNDATIOI^;441.1715 SIGNAL CABINET FOUNDATION - 3521 & BBl;441.1725 FURNiSH/IHSTALL ATC SIGNAL CONTROLIEP1441.1741 FURNiSH/INSTALL 3521 CONTROLLER CABINET ASSEM91Y441.4001 FURN1SH/INSTALLAIUM SiGN MAST ARM MOUH1.441.4002 FURNISH/iNSTALLALUM SiGN GROUND MOUNT TXDOTTD.441.4108 REMOVE SIGN PANELAND POS1:60S.om FURNISH/1NSTALL EIEC SERV PEDESTM:605,3011 2" CONDT PVC SCH 40 {T:605.3012 2" CONOT PVC 5CH 40 (8;605.3021 3° CONDT PVC SCH 40 fT60S.3022 3° CONDT PVC SCH 40 (8:605.3032 4B CONDT PVCSCH 40 (B;123.0101 UNCLASSIFIED EXCAVATION BY PLAN170.0100 Mobilization217.0103 6° BRK PVMT MARKING HAS (W:217.0201 8" SLD PVMT MARKING HAS (W;217.0501 24° SLD PVMT MARKING HAE (W;217.0502 PREFORMED THERMOPlASTfC COMTRAST MARKINGS -4- CROSSWALK217.1002 LANE LEGEND ARRC?217.1004 LANE LEGEND ONLY217.1016 PREFORMED THERMOPLASTIC CONTRAST MARKINGS -EGEND YIELD SYMBOL217.2103 REFL RAISED MARKER T/ 1!-A-^217.2104 REFL RAISED MARKER T/ H-C-R217.4301 REMOVE 4" PVMT MARKING217.4306 REMOVE 24" PVMT MARKING217.4307 REMOVE RAISED MARKER34 411034 411034 411034411034 41.1034 411034 411034 411034 411034 411034 411034411034.3434343434.343434.3434.3434343434110110110nonono1101101.ItIIiI10333333334411034 411034413034 41 3034 41 3026050026 05 3326053326 05 3326 05 3326 05 3331231601700032 17 2332 17 2332 17 2332 17 2332 17 2332172332 17 2332 17 2332 17 2332172332 17 2332 17 23EAEAEAEAEAEALFEALFLFIFLFLFLFIFIFIFEAEAEAEAEAEAEAEAEAEAEAEAEAEAEAEAEALFLFLFLFLFCTLSIFLFIFLFEAEAEAEAEAIFIFEA104814411101124096903sos8951SAQ601710135015413133111119641625535145440190821200462745500664040167203873TOTAL UNIT C: STREET LIGHTS AND SIGNSWddfiUnit Price$18,791.1^$22,471.7:$18,798.Si$19,215.^$576.8;$476.061$1,413.3;ProposalBiJ Value$225.493.6!$89,886.8;$18.798.5i$76,860.5;$280,916.2]$1.904.2.!$1,413.3;S695.273.39$2,65S.5'$2,908.4;$1,251.16]$14,877.00)$18,492.11$7,975.5f$4.4f$1., 190. K$4.4fS6.11$6.3<$6.7;$7.4<$4.4S$3.91$1.70|$3.54|$1,864.09!$2,203.2i$5,772.2;$14,6&4.2($16,016.5i$21,183.3E$25,073.7Gl$22,315.SO|$10,413.9($S,794.5I$6,322.73$8.160.0;$20,1-13.46$24.889.2;$907.501$1,099.4:$148.77$16,141.5'$18.57$52.0:$20.3'$61.001$?3.0($111.S8|$66,838.7;?2.go|$3.9E$17.43$40.6^$53i.a1$570.53$106.^$8.70|$8.70j$2.01$8.23]$145.5;$26.5S5.4C$11.633,8C$10,009.2i$14,877.(X:$73,968.4;$31,902.2^$4,950.6C$1,190.1£$5,530.40S586.5E$5,725.03$6,126.85$6,658.8C$8,1S8.0CS234.6C$2.907.(X;$4,779.0C$1,864.05$11,016.40$23,089.13$H>664.2£$48,049.7^S21,183.3£$75,221.10$66,946.5C$10.413.90$5.794.59$6,322.73$8,160.03$20,143.46$24,889.23$8,167.50$6,596,46$595.08$16,141.55$11,606.25$27.857.45$2,949.30$26.840.00$13,881.40$9,149.56$66,838.72$580.00$1,829.52$12,977.90$20,305.00$3,191.10$3,423.18$4,254.80$348.00$1.452.90$40.20$312.74$10,623.69$803,543.95lummaryUNIT B: PAVING IMPROVEMENTSUNIT C: TRAFFIC SIGNALS AND STRIPINGSTcI Co:tion 1B!((695.273.39$803,543.95$1,498,817.34This Bid is submitted by the entity named below:BIDDER: Bob Moure ConstructionAuAlWtTITLE; El'ScilBiCTt&t'roMt.UDATE: 6/5/2025 | 15:57:16 COTEND OF SECTION20I5W35 BiJPrapMl
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E1256004512DAP PREQUALIFICATION STATEMENTPage 1 oflSECTION 00 45 12DAP - PREQUALIFICATION STATEMENTEach Bidder is required to complete the information below by identifying the prequalified contractorsand/or subcontractors whom they intend to utilize for the major work type(s) listed. In the "Major WorkTYEG" box_m'ovide the complete maior work type and actual description as provided by the WaterDepartment for water and sewer and TPW for naying.Major Work TypePaving ImprovementsStreet Lights and SignsContractor/Subcontractor Company NameBCR, LLCRoad Solutions LLCPrequalificationExpiration DateDecember 8,2026December 11,2026The undersigned hereby certifies that the contractors and/or subcontractors described in the table aboveare currently prequalified for the work types listed.BIDDER:Bob Moore Construction3611 William D Tate AveGrapevine, TX 76051BY: Mark Duvall / —DocuSIgned by:f^y^ PiA^itt•80310C02617C407...(Signature)TITLE: Executive Vice PresidentDATE: 8/5/2025 | 10:18:05 CDTEND OF SECTIONCIT/ OF FORT WORTHSTANDARD CONSTRUCTION PREQUALIFICATION STATEMENT- DEVELOPER AWARDED PROJECTSForm Version September 1, 2015
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 45 26 - 1CONTRACTOR COMPLIANCE WITH WORKER'S COMPENSATION LAW1 of 1101112131415161718192021222324252627282930313233343536373839SECTION 00 45 26CONTRACTOR COMPLIANCE WITH WORKER'S COMPENSATION LAWPursuant to Texas Labor Code Section 406.096(a), as amended, Contractor certifies that itprovides worker's compensation insurance coverage for all of its employees employed on CityProject No. CPN 105417. Contractor further certifies that, pursuant to Texas Labor Code, Section406.096(b), as amended, it will provide to City its subcontractor's certificates of compliance withworker's compensation coverage.CONTRACTOR:Bob Moore Construction Inc.Company3611 William D. TateAddressGrapevine, TexasAve.76051By: Mark DuvallSignature:(Please Print)'DocuSigned by:Aw^ Dw^ii•80310C92517C407...City/State/ZipTHE STATE OF TEXASCOUNTY OF TARRANTTitle: Executive Vice President(Please Print)§§BEFORE ME, the undersigned authority, on this day personally appeared' • __, known to me to be the person whose name issubscribed to the foregoing instrument, and acknowledged to me that he/she executed the same asthe act and deed of _; _. ' ' . for the purposes andconsideration therein expressed and in the capacity therein stated.GIVEN UNDER MY HAND AND SEAL OF OFFICE this_, 20_.day ofNotary Public in and for the State of TexasEND OF SECTIONDEBRAKAY MOORENotary Public, State of TexasMy Comm.Exp. 11/08/2025Notary ID 574100-3CITY OF FORT WORTHSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTSRevised April 2, 2014Meacham Boulevard at Mercantile DriveCPN 105417
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 52 43 - 1Developer Awarded Project Agreement1 of41 SECTION 00 52 432 AGREEMENT3 THIS AGREEMENT, authorized on _is made by and between the Developer,4 (Insert Full Legal Name of Developer), authorized to do business in Texas ("Developer") , and5 _ Bob Moore Construction Inc. , authorized to do6 business in Texas, acting by and through its duly authorized representative, ("Contractor"),7 Developer and Contractor, in consideration of the mutual covenants hereinafter set forth, agree as8 follows:9 Article 1. WORK10 Contractor shall complete all Work as specified or indicated in the Contract Documents for the11 Project identified herein.12 Article 2. PROJECT13 The project for which the Work under the Contract Documents may be the whole or only a part is14 generally described as follows:15 Meacham Boulevard at Mercantile Drive16 CPN 10541717 Article 3. CONTRACT TIME18 3.1 Time is of the essence.19 All time limits for Milestones, if any, and Final Acceptance as stated in the Contract20 Documents are of the essence to this Contract.21 3.2 Final Acceptance.22 The Work will be complete for Final Acceptance within {120} calendar days after the date23 when the Contract Time commences to run as provided in Paragraph 12.04 of the Standard24 City Conditions of the Construction Contract for Developer Awarded Projects.25 3.3 Liquidated damages26 Contractor recognizes that time is of the essence of this Agreement and that Developer will27 suffer financial loss if the Work is not completed within the times specified in Paragraph28 3.2 above, plus any extension thereof allowed in accordance with Article 10 of the Standard29 City Conditions of the Construction Contract for Developer Awarded Projects. The30 Contractor also recognizes the delays, expense and difficulties involved in proving in a31 legal proceeding the actual loss suffered by the Developer if the Work is not completed on32 time. Accordingly, instead of requiring any such proof. Contractor agrees that as liquidated33 damages for delay (but not as a penalty). Contractor shall pay Developer N/A Dollars34 ($N/A) for each day that expires after the time specified in Paragraph 3.2 for Final35 Acceptance until the City issues the Final Letter of Acceptance.CITY OF FORT WORTH Meacham Boulevard at Mercantile DriveSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTS - DEVELOPER AWARDED PROJECTS CPN 10541 7Revised June 16,20168/19/2025
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 52 43 - 2Developer Awarded Project AgreementPage 2 of 436 Article 4. CONTRACT PRICE37 Developer agrees to pay Contractor for performance of the Work in accordance with the Contract38 Documents an amount in current funds of Dollars39 ($ 1,498,817.34 _).40 Article 5. CONTRACT DOCUMENTS41 5.1 CONTENTS:42 A. The Contract Documents which comprise the entire agreement between Developer and43 Contractor concerning the Work consist of the following:44 1. This Agreement.45 2. Attachments to this Agreement:46 a. Bid Form (As provided by Developer)47 1) Proposal Form (DAP Version)48 2) Prequalification Statement49 3) State and Federal documents (project specific)50 b. Insurance ACORD Form(s)51 c. Payment Bond (DAP Version)52 d. Performance Bond (DAP Version)53 e. Maintenance Bond (DAP Version)54 f. Power of Attorney for the Bonds55 g. Worker's Compensation Affidavit56 h. MBE and/orSBE Commitment Fonn (If required)57 3. Standard City General Conditions of the Construction Contract for Developer5 8 Awarded Proj ects .59 4. Supplementary Conditions.60 5. Specifications specifically made a part of the Contract Documents by attachment or,61 if not attached, as incorporated by reference and described in the Table of Contents62 of the Project's Contract Documents.63 6. Drawings.64 7. Addenda.65 8. Documentation submitted by Contractor prior to Notice of Award.66 9. The following which may be delivered or issued after the Effective Date of the67 Agreement and, if issued, become an incorporated part of the Contract Documents:68 a. Notice to Proceed.69 b. Field Orders.70 c. Change Orders.71 d. Letter of Final Acceptance.7273CITY OF FORT WORTH Meacham Boulevard at Mercantile DriveSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTS - DEVELOPER AWARDED PROJECTS CPN 10541 7Revised June 16,2016One million, four hundred ninety-eight thousand, eight hundred seventeen & 34/100
Docusign Envelope ID: 202AC2CA-DE8E-4BF2-99AO-5A1EFB5E125600 52 43 - 3Developer Awarded Project AgreementPage 3 of 474 Article 6. INDEMNIFICATION75 6.1 Contractor covenants and agrees to indemnify, hold harmless and defend, at its own76 expense, the city, its officers, servants and employees, from and against any and all77 claims arising out of, or alleged to arise out of, the work and services to be performed78 by the contractor, its officers, agents, employees, subcontractors, licenses or invitees79 under this contract. This indemnification provision is specifically intended to operate80 and be effective even if it is alleged or proven that all or some of the damages being81 sought were caused, in whole or in part, by any act^ omission or negligence of the city.82 This indemnity provision is intended to include, without limitation, indemnity for costs,83 expenses and legal fees incurred by the city in defending against such claims and causes84 of actions.8586 6.2 Contractor covenants and agrees to indemnify and hold harmless, at its own expense,87 the city, its officers, servants and employees, from and against any and all loss, damage88 or destruction of property of the city, arising out of, or alleged to arise out of, the work89 and services to be performed by the contractor, its officers, agents, employees,90 subcontractors, licensees or invitees under this contract. This indemnification provision91 is specifically intended to operate and be effective even if it is alleged or proven that all92 or some of the damages being sought were caused, in whole or in part, by any act,93 omission or negligence of the city.9495 Article 7. MISCELLANEOUS96 7.1 Terms.97 Terms used in this Agreement are defined in Article 1 of the Standard City Conditions of the98 Construction Contract for Developer Awarded Projects.99 7.2 Assignment of Contract.100 This Agreement, including all of the Contract Documents may not be assigned by the101 Contractor without the advanced express written consent of the Developer.102 7.3 Successors and Assigns.103 Developer and Contractor each binds itself, its partners, successors, assigns and legal104 representatives to the other party hereto, in respect to all covenants, agreements and105 obligations contained in the Contract Documents.106 7.4 Severability.107 Any provision or part of the Contract Documents held to be unconstitutional, void or108 unenforceable by a court of competent jurisdiction shall be deemed stricken, and all109 remaining provisions shall continue to be valid and binding upon DEVELOPER and110 CONTRACTOR.Ill 7.5 Governing Law and Venue.112 This Agreement, including all of the Contract Documents is performable in the State of113 Texas. Venue shall be Tarrant County, Texas, or the United States District Court for the114 Northern District of Texas, Fort Worth Division.CITY OF FORT WORTH Meacham Boulevard at Mercantile DriveSTANDARD CONSTRUCTION SPECIFICATION DOCUMENTS - DEVELOPER AWARDED PROJECTS CPN 10541 7Revised June 16,2016
Dpcusign Enveiope ID: 202RC2CA-�E8E-46F2-99A0-5A1EF85E1256
OOS2d3-4
Develaper Awardcd Projcct Agreei�ic��t
Page A of 4
IIS
I 16 7.6 Autho�ity to Sign.
t 17 Contractor shall attach evidence of aut�xoriry to sign Agreement, if other than duly authoi7zed
118 signatory of tlie Contractor.
119
120 IN WiTNESS WHEREO�, Developer ar►d Contractor have executed this Agreement in rnuftiple
I21 counterparts.
�22
123 This Agreernent is effective as of tkze iast data signed by the Parties ("Effective Date").
124
Contractor:
Bob Moore Canstruction Inc.
By' �DoeuSEpnad by:
��'Lc�� �u��,
�,��a��;.�
(�` �gnatui•e�...
Mark Du�all
(Printed Narne)
!25
Title: Executive Vice President
COrilpan}i N8iri6: Bob Moore Construction InC.
Address:
3�� 1 WiNiam D Tate A�e.
ciry/scate/Zip: Gra�evine, TX 76051
8/5/2025 � 1 Q:18:05 CDT
Dacc
Develope :
� , rz.,.� �- �
BY: .- - �' ��
�l (Signal
��'iAN �nlD�r1�'�9
(Printed Na�ne)
Title: ��1 '���
Company name:
Address:
'L�� R�}C�M �! .�lD
Ciry/State/Zip: �� �/U/�p�731 � ����
Date
��t�.z �
C11'Y OF FORT 1VORTF{ hlevchanr Rnulevmd af Alerca�rlile t7rive
STANDARD C�NSTRIfCTIOiV SPGCIFICATION DOCUMGNTS DEVEi.OFER AWAEtDED PRdJECTS CPN 105417
Revised June 16,2016
19th August 25
D08213-2
PERFORMANCE BOND
Page 2 of 3
L extensinn of the Ca�Itract� th�l i�3ay be granted on the part af the Deveioper and/a• City, then this
2 obligation shall be and become null and void, othe���vise ko remain in fu[� force and effect.
3 PROVID�D FURTH��:,R, that iFany legal action i�e filed on this Bor�d, �eiu�e s[lali lie in
4 Tarrant County, Te�as or the United States District Court for t17e Northern District of TeYas, Fort
S i�01'�h DIViS[OE1.
b "I'l�is bond is made �nc! exectited in con�pliance 4vitk� tlie provisior�s of Chapter 2253 of the
7 Texas Government Code, as ame�zd�d, and �I1 [iaE�ilities on this bond shall be determined in
8 accordar�ce with the provisions of said statue.
9 YN W�TNESS WHER�QF, the Principak and tkle Su�•ety ha�e SIGNED and SEALED
10 titis instrument E�y duly auti�orized agents and officers on this tlae � F�� day of
� � Pv (� ST . 2p 2� .
l2
13
l4
l5
16
17
18
19 ATTEST:
aa
,
2, � � � _� : y��l���
22
23 {Principal) 5ecretaiy
24
2S
2G
z� ��=�r�,� � ������ l� -�__
28 Witness as to P�•incip�►1
PRINCiPAL:
Bob Moore Construction, Inc.
I'-'`P�- �- D���.�-
BY: � �T �/ "�
5ignature
�n r�! �� �I�'� �� 1�x�� � �
�
Name aiid Title
Address: 36� 1 William D. Tate Av�nu�
Gra�e�ine, �X 76059
CITY OF FORT WORTH Meacham 8oulevard at Mercantrle Dnve
STANDARD CITY CONDITIONS - DEVELOP�R AWAR�ED PROJECTS CPN i054i7
Revised January 31, 2Q12
006213-3
PERFORMANCE BOND
Page 3 of 3
1
2
3
4
$
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
?;
24
��. .1
Jessi Turner
Witness as to Surety
SURETY: Travelers Casulaty & Surety Company of America
BY: r ���i'��.��� _._ .
, v -
Slgllcltll
Payton Blanchard, Attorney-in-Fact
Name and Title
Address: One Tower Square
Hartford, CT 06183
Telephone Number $60-277-0111
*Note: If signed by an officer of the Surety Company, there must be on file a certified exri�act
from the by-laws showing that this person has authority to sign such obligation. If
Surety's physical address is different from its mailing address, both must be provided.
The date of the bond shall not be prior to the date the Contract is awarded.
CITY OF FORT WORTH
STANDARD CITY CONDITIONS - DEVELOPER AWARDED PROJECTS
Revised January 31, 2012
Meacham Boulevard at Mercantile Drive
CPN 105417
�
TRAVELERSJ
Travelers Casualty and Surety Company of America
Travelers Casualty and Surety Company
St. Paul Fire and Marine Insurance Company
POWER OF ATTORNEY
KNOW ALL MEN BY THESE PRESENTS: That Travelers Casualty and Surety Company of America, Travelers Casualty and Surety Company, and St.
Paul Fire and Marine Insurance Company are corporations duly organized under the laws of the State of Connecticut (herein collectively called the
"Companies"), and that the Companies do hereby make, constitute and appoint Payton Blanchard of FORT WORTH ,
Texas , their true and lawful Attorney-in-Fact to sign, execute, seal and acknowledge any and all bonds, recognizances,
conditionai undertakings and other writings obligatory in the nature thereof on behalf of the Companies in their business of guaranteeing the
fidelity of persons, guaranteeing the performance of contracts and executing or guaranteeing bonds and undertakings required or permitted in any
actions or proceedings allowed by law.
IN WITNESS WHEREOF, the Companies have caused this instrument to be signed, and their corporate seals to be hereto affixed, this 17th day of January,
2019.
��W'4�11f7/.� JP�t� ANO �
y d �
� 4t 4'p� � * �
� �� Q � �� n � ���
g • � W C � u� �
•'� ��bi ��a` � *
. � $'
State of Connecticut
City of Hartford ss.
By: ,
Robert L. Rane , enior Vice President
On this the 17th day of January, 2019, before me personally appeared Robert L. Raney, who acknowledged himself to be the Senior Vice President
of Travelers Casualty and Surety Company of America, Travelers Casualty and Surety Company, and St. Paul Fire and Marine Insurance Company, and
that he, as such, being authorized so to do, executed the foregoing instrument for the purposes therein contained by signing on behalf of said
Companies by himself as a duly authorized officer.
IN WITNESS WHEREOF, I hereunto set my hand and official seal.
My Commission expires the 30th day of June, 2021
JJee+tF,FP yoW",,b /n/
� T N01AAY � ' ��ii,v�(h �/����_�
•* �,� ;1
P�'�`�� Anna P. Nowik, Notary Public
.���
This Power of Attorney is granted under and by the authority of the following resolutions adopted by the Boards of Directors of Travelers Casuaity and
Surety Company of America, Travelers Casualty and Surety Company, and St. Paul Fire and Marine Insurance Company, which resolutions are now in full
force and effect, reading as follows:
RESOLVED, that the Chairman, the President, any Vice Chairman, any Executive Vice President, any Senior Vice President, any Vice President, any
Second Vice President, the Treasurer, any Assistant Treasurer, the Corporate Secretary or any Assistant Secretary may appoint Attorneys-in-Fact and
Agents to act for and on behalf of the Company and may give such appointee such authority as his or her certificate of authority may prescribe to sign
with the Company's name and seal with the Company's seal bonds, recognizances, contracts of indemnity, and other writings obligatory in the nature of a
bond, recognizance, or conditional undertaking, and any of said officers or the Board of Directors at any time may remove any such appointee and revoke
the power given him or her; and it is
FURTHER RESOLVED, that the Chairman, the President, any Vice Chairman, any Executive Vice President, any Senior Vice President or any Vice
President may delegate all or any part of the foregoing authority to one or more officers or employees of this Company, provided that each such
delegation is in writing and a copy thereof is filed in the office of the Secretary; and it is
FURTHER RESOLVED, that any bond, recognizance, contract of indemnity, or writing obligatory in the nature of a bond, recognizance, or conditional
undertaking shall be valid and binding upon the Company when (a) signed by the President, any Vice Chairman, any Executive Vice President, any
Senior Vice President or any Vice President, any Second Vice President, the Treasurer, any Assistant Treasurer, the Corporate Secretary or any
Assistant Secretary and duly attested and sealed with the Company's seal by a Secretary or Assistant Secretary; or (b) duly executed (under seal, if
required) by one or more Attorneys-in-Fact and Agents pursuant to the power prescribed in his or her certificate or their certificates of authority or by one
or more Company officers pursuant to a written delegation of authority; and it is
FURTHER RESOLVED, that the signature of each of the following officers: President, any Executive Vice President, any Senior Vice President, any Vice
President, any Assistant Vice President, any Secretary, any Assistant Secretary, and the seal of the Company may be affixed by facsimile to any Power of
Attorney or to any certificate relating thereto appointing Resident Vice Presidents, Resident Assistant Secretaries or Attorneys-in-Fact for purposes only of
executing and attesting bonds and undertakings and other writings obligatory in the nature thereof, and any such Power of Attorney or certificate bearing
such facsimile signature or facsimile seal shall be valid and binding upon the Company and any such power so executed and certified by such facsimile
signature and facsimile seal shall be valid and binding on the Company in the future with respect to any bond or understanding to which it is attached.
I, Kevin E. Hughes, the undersigned, Assistant Secretary of Travelers Casualty and Surety Company of America, Travelers Casualty and Surety
Company, and St. Paui Fire and Marine Insurance Company, do hereby certify that the above and foregoing is a true and correct copy of the Power of
Attorney executed by sa:� Gcmpa� ies, which remains in full force and effect.
Dated this day oF
�„^5~yyR J'�tY 4Yp �f
y��ir � , J � * �
�+$ (/ur `�
A ��."Ol�iOt� E, y �CONN.�' t � �
\ ;� / o fGl �
� �..�.� `�/ a� � 1�
S bt np *�
�� �
Kevin E. Hughes, Assi�retary
To ve�ify the authenticity of this Power ofAttorney, p/ease ca// us at 1-800-411-3880.
P/ease refer to the above-named Attorney-in-Pact and the detai/s of the bond to which this Power ofAttorney is attached.
19th August 25
00 62 14 - 2
PAYIv1GV'r [30ND
Pagc 3 of 2
1
?
3
4
5
b
7
8
9
1�
1[
12
13
i4
IS
Tl�is �ond is made �i�d executed iRl compliar►ce witl� the provisio�as ot Cl�apter 2253
ot tEie Te�as Governn�ent Coc�e, as amended, and �II liabilities oii tliis bond s1�all i�e
dete���nEned in accordance witl� t[le provisions of said statute,
IN WITN�SS WH�R�OF, the P�•i�fcip�l and Surety have each SIGNED
and SEALED this instrument by dt�ly autharized agents and officers on this
tl�e Iqt�` day of pv GuS�" , 20 ��
ATT�ST:
,;,��%�,���_� �Yjf���.:-�
(Pri��cipal) Secreta�•y
'��.!✓'rG<- �rfr'`. �:'(� \' �� �'-
Witness as ta Principal
ATT�ST:
I v�v �
(St�r y) Secretary , ,lessica Turner
.�
/ � ��
N' �
�Vlh] S �5 tp Stla'ety Wilfiam Blanchard
PRINCIPAL:
Bob Moore Conskruc#ion, Inc.
BY: r�D �
�
S�gnah�•e
�kL�-- Qufn1�� EJ f
Name and Title
Address: 3811 William D. Tate A�enue
Grapevine, TX 76059
SURETY:
Travelers Casulaty & Sureiy Company of Arr�erica
�
BY: � �/�.�i%� ' .
igna e � " ' : .
, , ,. �,�:
Payton Blanchard, Aitorney-in-Fact ' ,
Nanie atzd Tit�e ' ' '
A(i[�Cess: One Tower Square
Hartforcf, CT 06183
Telephone Ntin�ber: sso-277-0� � �
Note: IFsigned Uy an officer of the Surety, there i��ust be on �le a certified e:ctract fi•om the bylaws
showing #hat this �lel'SOIl 1]flS 1l1iI74Clij� i0 Sl�l] SLICiI o�ligatio�i. lf Sucety's pl�ysical address is
differe�st froni its mailing address, botEt must be provided.
The d�t� of tl�e liond shall »ot be priar to tlae date the Contract is �wardecE.
�rrn o� s�cTxoN
C[TY OF PORT WOIt"�'Nl ,llenclanna Boulevarcf a1 �Llercarilile Dt•ive
STAND.ARD CCTY COND[�1'10N5 -� D�:VELOPGR AWARRGD PROJL'C'fS Cin� Pi•ojecf No. 105�l17
Revised lanuary 31, 2012
Travelers Casualty and Surety Company of America
�� Travelers Casualty and Surety Company
TRAVELERS � St. Paul Fire and Marine Insurance Company
POWER OF ATTORNEY
KNOW ALL MEN BY THESE PRESENTS: That Travelers Casualty and Surety Company of America, Travelers Casualty and Surety Company, and St.
Paul Fire and Marine Insurance Company are corporations duly organized under the laws of the State of Connecticut (herein collectively called the
"Companies"), and that the Companies do hereby make, constitute and appoint Payton Blanchard of FORT WORTH ,
Texas , their true and lawful Attorney-in-Fact to sign, execute, seal and acknowledge any and all bonds, recognizances,
conditional undertakings and other writings obligatory in the nature thereof on behalf of the Companies in their business of guaranteeing the
fidelity of persons, guaranteeing the performance of contracts and executing or guaranteeing bonds and undertakings required or permitted in any
actions or proceedings allowed by law.
IN WITNESS WHEREOF, the Companies have caused this instrument to be signed, and their corporate seals to be hereto affixed, this 17th day of January,
2019.
,..,
�V��r qJ� TV a�yp@` -,_ �
``� � 9 ��*�
��C�NtR 2 W �
4 � s �r' �
� � i � � �
� • � 'r`1 . '��a `s #
State of Connecticut
City of Hartford ss.
/
By: ,
Robert L. Rane , enior Vice President
On this the 17th day of January, 2019, before me personally appeared Robert L. Raney, who acknowledged himself to be the Senior Vice President
of Travelers Casualty and Surety Company of America, Travelers Casualty and Surety Company, and St. Paul Fire and Marine Insurance Company, and
that he, as such, being authorized so to do, executed the foregoing instrument for the purposes therein contained by signing on behalf of said
Companies by himself as a duly authorized officer.
IN WITNESS WHEREOF, I hereunto set my hand and official seal
My Commission expires the 30th day of June, 2021
��PP �o��+ /�I �^��i�I�/G
� �
NOTAAY }i �
k 4i� �� �(
P�a`�� " Anna P. Nowik, Notary Public
`b•x„E„�'�'�
This Power of Attorney is granted under and by the authority of the following resolutions adopted by the Boards of Directors of Travelers Casualty and
Surety Company of America, Travelers Casualty and Surety Company, and St. Paul Fire and Marine Insurance Company, which resolutions are now in full
force and effect, reading as follows:
RESOLVED, that the Chairman, the President, any Vice Chairman, any Executive Vice President, any Senior Vice President, any Vice President, any
Second Vice President, the Treasurer, any Assistant Treasurer, the Corporate Secretary or any Assistant Secretary may appoint Attorneys-in-Fact and
Agents to act for and on behalf of the Company and may give such appointee such authority as his or her certificate of authority may prescribe to sign
with the Company's name and seal with the Company's seal bonds, recognizances, contracts of indemnity, and other writings obligatory in the nature of a
bond, recognizance, or conditional undertaking, and any of said officers or the Board of Directors at any time may remove any such appointee and revoke
the power given him or her; and it is
FURTHER RESOLVED, that the Chairman, the President, any Vice Chairman, any Executive Vice President, any Senior Vice President or any Vice
President may delegate all or any part of the foregoing authority to one or more officers or employees of this Company, provided that each such
delegation is in writing and a copy thereof is filed in the office of the Secretary; and it is
FURTHER RESOLVED, that any bond, recognizance, contract of indemnity, or writing obligatory in the nature of a bond, recognizance, or conditional
undertaking shall be valid and binding upon the Company when (a) signed by the President, any Vice Chairman, any Executive Vice President, any
Senior Vice President or any Vice President, any Second Vice President, the Treasurer, any Assistant Treasurer, the Corporate Secretary or any
Assistant Secretary and duly attested and sealed with the Company's seal by a Secretary or Assistant Secretary; or (b) duly executed (under seal, if
required) by one or more Attorneys-in-Fact and Agents pursuant to the power prescribed in his or her certificate or their certificates of authority or by one
or more Company officers pursuant to a written delegation of authority; and it is
FURTHER RESOLVED, that the signature of each of the following officers: President, any Executive Vice President, any Senior Vice President, any Vice
President, any Assistant Vice President, any Secretary, any Assistant Secretary, and the seal of the Company may be affixed by facsimile to any Power of
Attorney or to any certificate relating thereto appointing Resident Vice Presidents, Resident Assistant Secretaries or Attorneys-in-Fact for purposes only of
executing and attesting bonds and undertakings and other writings obligatory in the nature thereof, and any such Power of Attorney or certificate bearing
such facsimile signature or facsimile seal shall be valid and binding upon the Company and any such power so executed and certified by such facsimile
signature and facsimile seal shall be valid and binding on the Company in the future with respect to any bond or understanding to which it is attached.
I, Kevin E. Hughes, the undersigned, Assistant Secretary of Travelers Casualty and Surety Company of America, Travelers Casualty and Surety
Company, and St. Paul Fire and Marine Insurance Company, do hereby certify that the above and foregoing is a true and correct copy of the Power of
Attorney executed by said Companies, which remains in full force and effect.
Dated this day cf ,
r��W yyA(� Q�� �Y 4!:p � ��
� J L �
s�tr'�� �_ � �' *
3, w�s�onwj � . ww,�ro, < �' oaeoµet
?yf�.+� W ca�N. o '�, � �
;
a� f
• �- Y+ �� IQ
w �
Kevin E. Hughes, Assi�retary
ia ve�ify the authenticity of this Power ofAtto�ney, p/ease ca// us at 1-800-421-3880,
P/�ase �efe: tc rhe above-named Attorney-in-Fact and the detai/s of the bond to which this Power ofAitorney is attached.
19th August
25
006219-2
MAINTENANCE BOND
Page 2 of 4
1 Work, including any Work resulting from a duly authorized Change Order
2 (collectively herein, the "Work") as provided for in said Contract and
3 designated as Meacham Boulevard at Mercantile Drive ; and
4 WHEREAS, Principal binds itself to use such materials and to so construct the
S Work in accordance with the plans, specifications and Contract Documents that the
6 Work is and will remain free from defects in materials or workmanship for and during
7 the period of two (2) years after the date of Final Acceptance of the Work by the City
8 ("Maintenance Period"); and
9 WHEREAS, Principal binds itself to repair or reconstruct the Work in whole or in
10 part upon receiving notice from the Developer and/or City of the need thereof at any
11 time within the Maintenance Period.
12 NOW THEREFORE, the condition of this obligation is such that if Principal shall
13 remedy any defective Work, for which timely notice was provided by Developer or City,
14 to a completion satisfactory to the City, then this obligation shall become null and void;
15 otherwise to remain in full force and effect
16
17
18
19
20
21
22
23
24
25
PROVIDED, HOWEVER, if Principal shall fail so to repair or reconstruct any
timely noticed defective Work, it is agreed that the Developer or City may cause any and
all such defective Work to be repaired and/or reconstructed with all associated costs
thereof being borne by the Principal and the Surety under this Maintenance Bond; and
PROVIDED FURTHER, that if any legal action be filed on this Bond, venue shall lie in
Tarrant County, Texas or the United States District Court for the Northern District of
Texas, Fort Worth Division; and
PROVIDED FURTHER, that this obligation shall be continuous in nature and
successive recoveries may be had hereon for successive breaches.
CITY OF FORT WORTH
STANDARD CITY CONDITIONS — DEVELOPER AWARDED PROJECTS
Revised lanuary 31, 2012
Meacham eoulevard at Mercantile Drive
City Project No. 105417
ooszi9-�
MAINTENANCE SOND
Page 3 of 4
1 IN WITNESS WHEREOF, ti�e Principal and t�e Surety have SEGNED and SEALED
2 this instrument by duly authorized agents and officers on this the ��r� day of_
3 A(� G� S� , 20�?�.
4
5
6
�
8
9
1�
��
12
13
14
15
�.6
17
18
19
2fl
21
22
23
24
25
26
27
2$
29
�a
31
32
ATTEST• � �.
� � l.� � �.� � 1 � �r t �c��l �-�
(Principal) Secretary
�� t'�-?1% Cc �� I���') C.� r' E'_-
Wfiness as to Principal
ATTEST:
(Sur tyj Secretary , Jessica 7urner
� j� ��= �
/�l
c
WItI1G55 �S t0 5U1"e�y � Wilfiam 6l2nchard
CI1Y OF FDR7 W�RTH
57AN�ARD CITY CDNPiTfOfVS — QEVELOPER AWARDED PROJEC75
Revised January 31, 20J.2
PRINCIPAL:
Bob Moare Construction, lnc.
Mj`�� p1,�V� �` � _
BY: i}�VL-� ��
Signature
l r'�� l�l/- �� �� ���� �11 �-�-�� �� ��/ r�
Name and Title
A(�CIfe55: 3619 William D. Tale Avenue, Grapevine, TX 76051
5U RE7Y:
Travelers Casulaty & Sure[y Company of Americ�
� n •: . .... � .
B � '-�•� ' ' � -- � .
Y: �� .
Si ature .
Payian Blanchard, Attarney-in-Faci
Name and Ti�Ee
ACICI I'e55: One Tower Square,
Hartfard, CT 06183
Telephane Number; aso-2��-0���
Mieacham Boulevard at Mercantile Drive
City Project No. 105417
0
006219-4
MAINTENANCE BOND
Page 4 of 4
1 *Note: If signed by an officer of the Surety Company, there must be on file a certified
2 extract from the by-laws showing that this person has authority to sign such
3 obligation. If Surety's physical address is different from its mailing address,
4 both must be provided.
5
6 The date of the bond shall not be prior to the date the Contract is awarded.
7
END OF SECTION
CITY OF FORT WORTH Meacham Boulevard at Mercantile Drive
STANDARD CITY CONDITIONS — DEVELOPER AWARDED PROJECTS City P�oject No. 105417
Revised January 31, 2012
Travelers Casualty and Surety Company of America
�I Travelers Casualty and Surety Company
TRAVELERS .J St. Paul Fire and Marine Insurance Company
POWER OF ATTORNEY
KNOW ALL MEN BY THESE PRESENTS: That Travelers Casualty and Surety Company of America, Travelers Casualty and Surety Company, and St.
Paul Fire and Marine Insurance Company are corporations duly organized under the laws of the State of Connecticut (herein collectively called the
"Companies"), and that the Companies do hereby make, constitute and appoint Payton Blanchard of FORT WORTH ,
Texas , their true and lawful Attorney-in-Fact to sign, execute, seal and acknowledge any and all bonds, recognizances,
conditional undertakings and other writings obligatory in the nature thereof on behalf of the Companies in their business of guaranteeing the
fidelity of persons, guaranteeing the performance of contracts and executing or guaranteeing bonds and undertakings required or permitted in any
actions or proceedings allowed by law.
IN WITNESS WHEREOF, the Companies have caused this instrument to be signed, and their corporate seals to be hereto affixed, this 17th day of January,
2019.
Y
�,`yF��f)p� bJPtvµom ��
�.l F�flif(� i uP G9K �� * �
�t � HA(iTFOHD� �qQ�l�
r�� ��' � W CONN o � � �
W �
e � �'S �y1 • n�,as fr *
State of Connecticut
City of Hartford ss.
By: .
Robert L. Rane , enior Vice President
On this the 17th day of January, 2019, before me personally appeared Robert L. Raney, who acknowledged himself to be the Senior Vice President
of Travelers Casualty and Surety Company of America, Travelers Casualty and Surety Company, and St. Paul Fire and Marine Insurance Company, and
that he, as such, being authorized so to do, executed the foregoing instrument for the purposes therein contained by signing on behalf of said
Companies by himself as a duly authorized officer.
IN WITNESS WHEREOF, I hereunto set my hand and official seal.
My Commission expires the 30th day of June, 2021
��SPP��oh�' i '//J �yA
* � ��'�i�/%� Y /������
i NOTSAY *3
* b+�
P�1z`�c Anna P. Nowik, Notary Public
tx��'a
This Power of Attorney is granted under and by the authority of the following resolutions adopted by the Boards of Directors of Travelers Casualty and
Surety Company of America, Travelers Casualty and Surety Company, and St. Paul Fire and Marine Insurance Company, which resolutions are now in full
force and effect, reading as follows:
RESOLVED, that the Chairman, the President, any Vice Chairman, any Executive Vice President, any Senior Vice President, any Vice President, any
Second Vice President, the Treasurer, any Assistant Treasurer, the Corporate Secretary or any Assistant Secretary may appoint Attorneys-in-Fact and
Agents to act for and on behalf of the Company and may give such appointee such authority as his or her certificate of authority may prescribe to sign
with the Company's name and seal with the Company's seal bonds, recognizances, contracts of indemnity, and other writings obligatory in the nature of a
bond, recognizance, or conditional undertaking, and any of said officers or the Board of Directors at any time may remove any such appointee and revoke
the power given him or her; and it is
FURTHER RESOLVED, that the Chairman, the President, any Vice Chairman, any Executive Vice President, any Senior Vice President or any Vice
President may delegate all or any part of the foregoing authority to one or more officers or employees of this Company, provided that each such
delegation is in writing and a copy thereof is filed in the office of the Secretary; and it is
FURTHER RESOLVED, that any bond, recognizance, contract of indemnity, or writing obligatory in the nature of a bond, recognizance, or conditional
undertaking shail be valid and binding upon the Company when (a) signed by the President, any Vice Chairman, any Executive Vice President, any
Senior Vice President or any Vice President, any Second Vice President, the Treasurer, any Assistant Treasurer, the Corporate Secretary or any
Assistant Secretary and duly attested and sealed with the Company's seal by a Secretary or Assistant Secretary; or (b) duly executed (under seal, if
required) by one or more Attorneys-in-Fact and Agents pursuant to the power prescribed in his or her certificate or their certificates of authority or by one
or more Company officers pursuant to a written delegation of authority; and it is
FURTHER RESOLVED, that the signature of each of the following officers: President, any Executive Vice President, any Senior Vice President, any Vice
President, any Assistant Vice President, any Secretary, any Assistant Secretary, and the seal of the Company may be affixed by facsimile to any Power of
Attorney or to any certificate relating thereto appointing Resident Vice Presidents, Resident Assistant Secretaries or Attorneys-in-Fact for purposes only of
executing and attesting bonds and undertakings and other writings obligatory in the nature thereof, and any such Power of Attorney or certificate bearing
such facsimile signature or facsimile seal shall be valid and binding upon the Company and any such power so executed and certified by such facsimile
signature and facsimile seal shall be valid and binding on the Company in the future with respect to any bond or understanding to which it is attached.
I, Kevin E. Hughes, the undersigned, Assistant Secretary of Travelers Casualty and Surety Company of America, Travelers Casualty and Surety
Company, and St. Paul Fire and Marine Insurance Company, do hereby certify that the above and foregoing is a true and correct copy of the Power of
Attorney executed by said Companies, which remains in full force and effect.
Dated this d�y ot ,
I`.h"W(�yC 9Jr�tv q��Q _�!rt
� \M•'
�'S'� E j�<? G � y�� �'
�T fliiiFOF� ��, 1 s WViTFOAD� + y Q�AfI
� A CONtA � � ��'` CONN. e �,. � �
d
�� • ,� df . '�a° f� *
K ���� �
� Kevin E. Hughes, Assi�retary
Tu verify the authenticity of this Powe� ofAtto�ney, p/ease ca// us at 1-800-421-3880,
P/ease refer tn the above-named Attorney-in-Fact and the detai/s of the bond to which this Power ofAltorney is attached.
IMPORTANT NOTICE
To obtain information or make a complaint:
You may call Travelers Casualty and Surety Company of America and its affiliates'
toll-free telephone number for information or to make a complaint at:
1-800-328-2189
You may contact the Texas Department of Insurance to obtain information on
companies, coverages, rights or complaints at:
1-800-252-3439
You may write the Texas Department of Insurance:
P. O. Box 149104
Austin, TX 78714-9104
Fax: (512) 475-1771
Web: http://www.tdi.state.Uc.us
E-mail: ConsumerProtection(c�tdi.state.tx.us
PREMIUM OR CLAIM DISPUTES:
Should you have a dispute concerning your premium or about a claim you should
contact your Agent or Travelers first. If the dispute is not resolved, you may contact the
Texas Department of Insurance.
ATTACH THIS NOTICE TO YOUR BOND:
This notice is for information only and does not become a part or condition of the
attached document and is given to comply with Texas legal and regulatory requirements.
(PN-042-B) Ed.10.18.07
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
STANDARD CITY CONDITIONS
OF THE CONSTRUCTION CONTRACT
FOR DEVELOPER AWARDED PROJECTS
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
STANDARD CITY CONDITIONS OF THE
CONSTRUCTION CONTRACT
FOR DEVELOPER AWARDED PROJECTS
TABLE OF CONTENTS
Page
Article 1 – Definitions and Terminology .......................................................................................................... 1
1.01 Defined Terms ............................................................................................................................... 1
1.02 Terminology .................................................................................................................................. 5
Article 2 – Preliminary Matters ......................................................................................................................... 6
2.01 Before Starting Construction ........................................................................................................ 6
2.02 Preconstruction Conference .......................................................................................................... 6
2.03 Public Meeting .............................................................................................................................. 6
Article 3 – Contract Documents and Amending ............................................................................................... 6
3.01 Reference Standards ..................................................................................................................... 6
3.02 Amending and Supplementing Contract Documents .................................................................. 6
Article 4 – Bonds and Insurance ....................................................................................................................... 7
4.01 Licensed Sureties and Insurers ..................................................................................................... 7
4.02 Performance, Payment, and Maintenance Bonds ........................................................................ 7
4.03 Certificates of Insurance ............................................................................................................... 7
4.04 Contractor’s Insurance .................................................................................................................. 9
4.05 Acceptance of Bonds and Insurance; Option to Replace ........................................................... 12
Article 5 – Contractor’s Responsibilities ........................................................................................................ 12
5.01 Supervision and Superintendent ................................................................................................. 12
5.02 Labor; Working Hours ................................................................................................................ 13
5.03 Services, Materials, and Equipment ........................................................................................... 13
5.04 Project Schedule .......................................................................................................................... 14
5.05 Substitutes and “Or-Equals” ....................................................................................................... 14
5.06 Pre-Qualification of Bidders (Prime Contractors and Subcontractors) ..................................... 16
5.07 Concerning Subcontractors, Suppliers, and Others ................................................................... 16
5.08 Wage Rates.................................................................................................................................. 18
5.09 Patent Fees and Royalties ........................................................................................................... 19
5.10 Laws and Regulations ................................................................................................................. 19
5.11 Use of Site and Other Areas ....................................................................................................... 19
5.12 Record Documents ...................................................................................................................... 20
5.13 Safety and Protection .................................................................................................................. 21
5.14 Safety Representative ................................................................................................................. 21
5.15 Hazard Communication Programs ............................................................................................. 22
5.16 Submittals .................................................................................................................................... 22
5.17 Contractor’s General Warranty and Guarantee .......................................................................... 23
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
5.18 Indemnification ........................................................................................................................... 24
5.19 Delegation of Professional Design Services .............................................................................. 24
5.20 Right to Audit: ............................................................................................................................ 25
5.21 Nondiscrimination....................................................................................................................... 25
Article 6 – Other Work at the Site ................................................................................................................... 26
6.01 Related Work at Site ................................................................................................................... 26
Article 7 – City’s Responsibilities................................................................................................................... 26
7.01 Inspections, Tests, and Approvals .............................................................................................. 26
7.02 Limitations on City’s Responsibilities ....................................................................................... 26
7.03 Compliance with Safety Program ............................................................................................... 27
Article 8 – City’s Observation Status During Construction ........................................................................... 27
8.01 City’s Project Representative ..................................................................................................... 27
8.02 Authorized Variations in Work .................................................................................................. 27
8.03 Rejecting Defective Work .......................................................................................................... 27
8.04 Determinations for Work Performed .......................................................................................... 28
Article 9 – Changes in the Work ..................................................................................................................... 28
9.01 Authorized Changes in the Work ............................................................................................... 28
9.02 Notification to Surety .................................................................................................................. 28
Article 10 – Change of Contract Price; Change of Contract Time ................................................................ 28
10.01 Change of Contract Price ............................................................................................................ 28
10.02 Change of Contract Time............................................................................................................ 28
10.03 Delays .......................................................................................................................................... 28
Article 11 – Tests and Inspections; Correction, Removal or Acceptance of Defective Work ...................... 29
11.01 Notice of Defects ........................................................................................................................ 29
11.02 Access to Work ........................................................................................................................... 29
11.03 Tests and Inspections .................................................................................................................. 29
11.04 Uncovering Work ....................................................................................................................... 30
11.05 City May Stop the Work ............................................................................................................. 30
11.06 Correction or Removal of Defective Work ................................................................................ 30
11.07 Correction Period ........................................................................................................................ 30
11.08 City May Correct Defective Work ............................................................................................. 31
Article 12 – Completion .................................................................................................................................. 32
12.01 Contractor’s Warranty of Title ................................................................................................... 32
12.02 Partial Utilization ........................................................................................................................ 32
12.03 Final Inspection ........................................................................................................................... 32
12.04 Final Acceptance ......................................................................................................................... 33
Article 13 – Suspension of Work .................................................................................................................... 33
13.01 City May Suspend Work ............................................................................................................ 33
Article 14 – Miscellaneous .............................................................................................................................. 34
14.01 Giving Notice .............................................................................................................................. 34
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
14.02 Computation of Times ................................................................................................................ 34
14.03 Cumulative Remedies ................................................................................................................. 34
14.04 Survival of Obligations ............................................................................................................... 35
14.05 Headings ...................................................................................................................................... 35
00 73 10- 1
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 1 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
ARTICLE 1 – DEFINITIONS AND TERMINOLOGY
1.01 Defined Terms
A. Wherever used in these General Conditions or in other Contract Documents, the terms listed
below have the meanings indicated which are applicable to both the singular and plural thereof,
and words denoting gender shall include the masculine, feminine and neuter. Said terms are
generally capitalized or written in italics, but not always. When used in a context consistent with
the definition of a listed-defined term, the term shall have a meaning as defined below whether
capitalized or italicized or otherwise. In addition to terms specifically defined, terms with initial
capital letters in the Contract Documents include references to identified articles and paragraphs,
and the titles of other documents or forms.
1. Agreement - The written instrument which is evidence of the agreement between Developer
and Contractor covering the Work
2. Asbestos—Any material that contains more than one percent asbestos and is friable or is
releasing asbestos fibers into the air above current action levels established by the United
States Occupational Safety and Health Administration.
3. Business Day – A business day is defined as a day that the City conducts normal business,
generally Monday through Friday, except for federal or state holidays observed by the City.
4. Buzzsaw – City’s on-line, electronic document management and collaboration system.
5. Calendar Day – A day consisting of 24 hours measured from midnight to the next midnight.
6. City— The City of Fort Worth, Texas, a Texas home-rule municipal corporation, acting by,
its governing body through its City Manager, his designee, or agents authorized pursuant to
its duly authorized charter on his behalf.
7. Community Facilities Agreement (CFA) -–A Contract between the Developer and the City
for the Construction of one or more following public facilities within the City public right-of-
way or easement: Water, Sanitary Sewer, Street, Storm Drain, Street Light, and Street Signs.
A CFA may include private facilities within the right-of-way dedicated as private right-of-
way or easement on a recorded plat.
8. Contract—The entire and integrated written document incorporating the Contract
Documents between the Developer, Contractor, and/or City concerning the Work. The
Contract supersedes prior negotiations, representations, or agreements, whether written or
oral.
9. Contract Documents—Those items that make up the contract and which must include the
Agreement, and it’s attachments such as standard construction specifications, standard City
Conditions, other general conditions of the Developer, including:
a. An Agreement
00 73 10- 2
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 2 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
b. Attachments to the Agreement
i. Bid Form
ii. Vendor Compliance with State Law Non-Resident Bidder
iii. Prequalification Statement
c. Current Prevailing Wage Rates Table (if required by City)
d. Insurance Accord Form
e. Payment Bond
f. Performance Bond
g. Maintenance Bond
h. Power of Attorney for Bonds
i. Workers Compensation Affidavit
j. MWBE Commitment Form( If required by City)
k. General Conditions
l. Supplementary Conditions
m. The Standard City Conditions
n. Specifications specifically made part of the Contract Documents by attachment, if
not attached, as incorporated by reference and described in the Table of Contents of
the Project’s Contract Documents
o. Drawings
p. Documentation submitted by contractor prior to Notice of Award.
q. The following which may be delivered or issued after the effective date if the
Agreement and, if issued become an incorporated part of the Contract Documents
i. Notice to Proceed
ii. Field Orders
iii. Change Orders
iv. Letters of Final Acceptance
r. Approved Submittals, other Contractor submittals, and the reports and drawings of
subsurface and physical conditions are not Contract Documents.
10. Contractor—The individual or entity with whom Developer has entered into the Agreement.
11. Day or day – A day, unless otherwise defined, shall mean a Calendar Day.
12. Developer – An individual or entity that desires to make certain improvements within the
City of Fort Worth
13. Drawings—That part of the Contract Documents prepared or approved by Engineer which
graphically shows the scope, extent, and character of the Work to be performed by
Contractor. Submittals are not Drawings as so defined.
14. Engineer—The licensed professional engineer or engineering firm registered in the State of
Texas performing professional services for the Developer.
15. Final Acceptance – The written notice given by the City to the Developer and/or Contractor
that the Work specified in the Contract Documents has been completed to the satisfaction of
the City.
00 73 10- 3
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 3 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
16. Final Inspection – Inspection carried out by the City to verify that the Contractor has
completed the Work, and each and every part or appurtenance thereof, fully, entirely, and in
conformance with the Contract Documents.
17. General Requirements—A part of the Contract Documents between the Developer and a
Contractor.
18. Laws and Regulations—Any and all applicable laws, rules, regulations, ordinances, codes,
and orders of any and all governmental bodies, agencies, authorities, and courts having
jurisdiction.
19. Liens—Charges, security interests, or encumbrances upon Project funds, real property, or
personal property.
20. Milestone—A principal event specified in the Contract Documents relating to an
intermediate Contract Time prior to Final Acceptance of the Work.
21. Non-Participating Change Order—A document, which is prepared for and reviewed by the
City, which is signed by Contractor, and Developer, and authorizes an addition, deletion, or
revision in the Work or an adjustment in the Contract Price or the Contract Time, issued on
or after the Effective Date of the Agreement.
22. Participating Change Order—A document, which is prepared for and approved by the City,
which is signed by Contractor, Developer, and City and authorizes an addition, deletion, or
revision in the Work or an adjustment in the Contract Price or the Contract Time, issued on
or after the Effective Date of the Agreement.
23. Plans – See definition of Drawings.
24. Project Schedule—A schedule, prepared and maintained by Contractor, in accordance with
the General Requirements, describing the sequence and duration of the activities comprising
the Contractor’s plan to accomplish the Work within the Contract Time.
25. Project—The Work to be performed under the Contract Documents.
26. Project Representative—The authorized representative of the City who will be assigned to
the Site.
27. Public Meeting – An announced meeting conducted by the Developer to facilitate public
participation and to assist the public in gaining an informed view of the Project.
28. Regular Working Hours – Hours beginning at 7:00 a.m. and ending at 6:00 p.m., Monday
thru Friday (excluding legal holidays).
29. Samples—Physical examples of materials, equipment, or workmanship that are
representative of some portion of the Work and which establish the standards by which such
portion of the Work will be judged.
00 73 10- 4
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 4 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
30. Schedule of Submittals—A schedule, prepared and maintained by Contractor, of required
submittals and the time requirements to support scheduled performance of related
construction activities.
31. Site—Lands or areas indicated in the Contract Documents as being furnished by City or
Developer upon which the Work is to be performed, including rights-of-way, permits, and
easements for access thereto, and such other lands furnished by City or Developer which are
designated for the use of Contractor.
32. Specifications—That part of the Contract Documents consisting of written requirements for
materials, equipment, systems, standards and workmanship as applied to the Work, and
certain administrative requirements and procedural matters applicable thereto.
Specifications may be specifically made a part of the Contract Documents by attachment or,
if not attached, may be incorporated by reference as indicated in the Table of Contents
(Division 00 00 00) of each Project.
33. Standard City Conditions – That part of the Contract Documents setting forth requirements
of the City.
34. Subcontractor—An individual or entity having a direct contract with Contractor or with any
other Subcontractor for the performance of a part of the Work at the Site.
35. Submittals—All drawings, diagrams, illustrations, schedules, and other data or information
which are specifically prepared or assembled by or for Contractor and submitted by
Contractor to illustrate some portion of the Work.
36. Superintendent – The representative of the Contractor who is available at all times and able
to receive instructions from the City and/or Developer and to act for the Contractor.
37. Supplementary Conditions—That part of the Contract Documents which amends or
supplements the General Conditions.
38. Supplier—A manufacturer, fabricator, supplier, distributor, materialman, or vendor having
a direct contract with Contractor or with any Subcontractor to furnish materials or
equipment to be incorporated in the Work by Contractor or Subcontractor.
39. Underground Facilities—All underground pipelines, conduits, ducts, cables, wires,
manholes, vaults, tanks, tunnels, or other such facilities or attachments, and any
encasements containing such facilities, including but not limited to, those that convey
electricity, gases, steam, liquid petroleum products, telephone or other communications,
cable television, water, wastewater, storm water, other liquids or chemicals, or traffic or
other control systems.
40. Weekend Working Hours – Hours beginning at 9:00 a.m. and ending at 5:00 p.m., Saturday,
Sunday or legal holiday, as approved in advance by the City.
00 73 10- 5
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 5 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
41. Work—The entire construction or the various separately identifiable parts thereof required
to be provided under the Contract Documents. Work includes and is the result of performing
or providing all labor, services, and documentation necessary to produce such construction
including any Participating Change Order, Non-Participating Change Order, or Field
Order, and furnishing, installing, and incorporating all materials and equipment into such
construction, all as required by the Contract Documents.
42. Working Day – A working day is defined as a day, not including Saturdays, Sundays, or
legal holidays authorized by the City for contract purposes, in which weather or other
conditions not under the control of the Contractor will permit the performance of the
principal unit of work underway for a continuous period of not less than 7 hours between 7
a.m. and 6 p.m.
1.02 Terminology
A. The words and terms discussed in Paragraph 1.02.B through D are not defined but, when used in
the Bidding Requirements or Contract Documents, have the indicated meaning.
B. Defective:
1. The word “defective,” when modifying the word “Work,” refers to Work that is
unsatisfactory, faulty, or deficient in that it:
a. does not conform to the Contract Documents; or
b. does not meet the requirements of any applicable inspection, reference standard, test, or
approval referred to in the Contract Documents; or
c. has been damaged prior to City’s written acceptance.
C. Furnish, Install, Perform, Provide:
1. The word “Furnish” or the word “Install” or the word “Perform” or the word “Provide” or
the word “Supply,” or any combination or similar directive or usage thereof, shall mean
furnishing and incorporating in the Work including all necessary labor, materials, equipment,
and everything necessary to perform the Work indicated, unless specifically limited in the
context used.
D. Unless stated otherwise in the Contract Documents, words or phrases that have a well-known
technical or construction industry or trade meaning are used in the Contract Documents in
accordance with such recognized meaning.
00 73 10- 6
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 6 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
ARTICLE 2 – PRELIMINARY MATTERS
2.01 Before Starting Construction
Baseline Schedules: Submit to City in accordance with the Contract Documents, and prior to starting
the Work. New schedules will be submitted to City when Participating Change Orders or Non-
Participating Change Orders occur.
2.02 Preconstruction Conference
Before any Work at the Site is started, the Contractor shall attend a Preconstruction Conference as
specified in the Contract Documents.
2.03 Public Meeting
Contractor may not mobilize any equipment, materials or resources to the Site prior to Contractor
attending the Public Meeting as scheduled by the City.
ARTICLE 3 – CONTRACT DOCUMENTS AND AMENDING
3.01 Reference Standards
A. Standards, Specifications, Codes, Laws, and Regulations
1. Reference to standards, specifications, manuals, or codes of any technical society,
organization, or association, or to Laws or Regulations, whether such reference be specific or
by implication, shall mean the standard, specification, manual, code, or Laws or Regulations
in effect at the time of opening of Bids (or on the Effective Date of the Agreement if there
were no Bids), except as may be otherwise specifically stated in the Contract Documents.
2. No provision or instruction shall be effective to assign to City, or any of its officers,
directors, members, partners, employees, agents, consultants, or subcontractors, any duty or
authority to supervise or direct the performance of the Work or any duty or authority to
undertake responsibility inconsistent with the provisions of the Contract Documents.
3.02 Amending and Supplementing Contract Documents
A. The Contract Documents may be amended to provide for additions, deletions, and revisions in
the Work or to modify the terms and conditions thereof by a Participating Change Order or a
Non-Participating Change Order.
B. The requirements of the Contract Documents may be supplemented, and minor variations and
deviations in the Work not involving a change in Contract Price or Contract Time, may be
authorized, by one or more of the following ways:
1. A Field Order;
00 73 10- 7
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 7 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
1. City’s or Engineer’s review of a Submittal (subject to the provisions of Paragraph 5.16.C); or
2. City’s written interpretation or clarification.
ARTICLE 4 – BONDS AND INSURANCE
4.01 Licensed Sureties and Insurers
All bonds and insurance required by the Contract Documents to be purchased and maintained by
Contractor shall be obtained from surety or insurance companies that are duly licensed or authorized
in the State of Texas to issue bonds or insurance policies for the limits and coverage so required.
Such surety and insurance companies shall also meet such additional requirements and qualifications
as may be provided Section 4.04.
4.02 Performance, Payment, and Maintenance Bonds
A. Contractor shall furnish performance and payment bonds in the name of Developer and City, in
accordance with Texas Government Code Chapter 2253 or successor statute, each in an amount
equal to the Contract Price as security for the faithful performance and payment of all of
Contractor’s obligations under the Contract Documents.
B. Contractor shall furnish maintenance bonds in the name of Developer and City in an amount
equal to the Contract Price as security to protect the City against any defects in any portion of the
Work described in the Contract Documents. Maintenance bonds shall remain in effect for two
(2) years after the date of Final Acceptance by the City.
C. All bonds shall be in the form prescribed by the Contract Documents except as provided
otherwise by Laws or Regulations, and shall be executed by such sureties as are named in the list
of “Companies Holding Certificates of Authority as Acceptable Sureties on Federal Bonds and
as Acceptable Reinsuring Companies” as published in Circular 570 (amended) by the Financial
Management Service, Surety Bond Branch, U.S. Department of the Treasury. All bonds signed
by an agent or attorney-in-fact must be accompanied by a sealed and dated power of attorney
which shall show that it is effective on the date the agent or attorney-in-fact signed each bond.
D. If the surety on any bond furnished by Contractor is declared bankrupt or becomes insolvent or
its right to do business is terminated in the State of Texas or it ceases to meet the requirements of
Paragraph 4.02.C, Contractor shall promptly notify City and shall, within 30 days after the event
giving rise to such notification, provide another bond and surety, both of which shall comply
with the requirements of Paragraphs 4.01 and 4.02.C.
4.03 Certificates of Insurance
Contractor shall deliver to Developer and City, with copies to each additional insured and loss payee
identified in these Standard City Conditions certificates of insurance (and other evidence of
insurance requested by City or any other additional insured) which Contractor is required to
purchase and maintain.
00 73 10- 8
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 8 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
1. The certificate of insurance shall document the City, an as “Additional Insured” on all
liability policies.
2. The Contractor’s general liability insurance shall include a, “per project” or “per location”,
endorsement, which shall be identified in the certificate of insurance provided to the City.
3. The certificate shall be signed by an agent authorized to bind coverage on behalf of the
insured, be complete in its entirety, and show complete insurance carrier names as listed in
the current A.M. Best Property & Casualty Guide
4. The insurers for all policies must be licensed and/or approved to do business in the State of
Texas. Except for workers’ compensation, all insurers must have a minimum rating of A-:
VII in the current A. M. Best Key Rating Guide or have reasonably equivalent financial
strength and solvency to the satisfaction of Risk Management. If the rating is below that
required, written approval of City is required.
5. All applicable policies shall include a Waiver of Subrogation (Rights of Recovery) in favor
of the City. In addition, the Contractor agrees to waive all rights of subrogation against the
Engineer (if applicable), and each additional insured identified in these Standard City
Conditions. Failure of the City to demand such certificates or other evidence of full
compliance with the insurance requirements or failure of the City to identify a deficiency
from evidence that is provided shall not be construed as a waiver of Contractor’s obligation
to maintain such lines of insurance coverage.
6. If insurance policies are not written for specified coverage limits, an Umbrella or Excess
Liability insurance for any differences is required. Excess Liability shall follow form of the
primary coverage.
7. Unless otherwise stated, all required insurance shall be written on the “occurrence basis”. If
coverage is underwritten on a claims-made basis, the retroactive date shall be coincident with
or prior to the date of the effective date of the agreement and the certificate of insurance shall
state that the coverage is claims-made and the retroactive date. The insurance coverage shall
be maintained for the duration of the Contract and for three (3) years following Final
Acceptance provided under the Contract Documents or for the warranty period, whichever is
longer. An annual certificate of insurance submitted to the City shall evidence such
insurance coverage.
8. Policies shall have no exclusions by endorsements, which, neither nullify or amend, the
required lines of coverage, nor decrease the limits of said coverage unless such endorsements
are approved in writing by the City. In the event a Contract has been bid or executed and the
exclusions are determined to be unacceptable or the City desires additional insurance
coverage, and the City desires the contractor/engineer to obtain such coverage, the contract
price shall be adjusted by the cost of the premium for such additional coverage plus 10%.
9. Any self-insured retention (SIR), in excess of $25,000.00, affecting required insurance
coverage shall be approved by the City in regards to asset value and stockholders' equity. In
00 73 10- 9
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 9 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
lieu of traditional insurance, alternative coverage maintained through insurance pools or risk
retention groups, must also be approved by City.
10. Any deductible in excess of $5,000.00, for any policy that does not provide coverage on a
first-dollar basis, must be acceptable to and approved by the City.
11. City, at its sole discretion, reserves the right to review the insurance requirements and to
make reasonable adjustments to insurance coverage’s and their limits when deemed
necessary and prudent by the City based upon changes in statutory law, court decision or the
claims history of the industry as well as of the contracting party to the City. The City shall
be required to provide prior notice of 90 days, and the insurance adjustments shall be
incorporated into the Work by Change Order.
12. City shall be entitled, upon written request and without expense, to receive copies of policies
and endorsements thereto and may make any reasonable requests for deletion or revision or
modifications of particular policy terms, conditions, limitations, or exclusions necessary to
conform the policy and endorsements to the requirements of the Contract. Deletions,
revisions, or modifications shall not be required where policy provisions are established by
law or regulations binding upon either party or the underwriter on any such policies.
13. City shall not be responsible for the direct payment of insurance premium costs for
Contractor’s insurance.
4.04 Contractor’s Insurance
A. Workers Compensation and Employers’ Liability. Contractor shall purchase and maintain such
insurance coverage with limits consistent with statutory benefits outlined in the Texas Workers’
Compensation Act (Texas Labor Code, Ch. 406, as amended), and minimum limits for
Employers’ Liability as is appropriate for the Work being performed and as will provide
protection from claims set forth below which may arise out of or result from Contractor’s
performance of the Work and Contractor’s other obligations under the Contract Documents,
whether it is to be performed by Contractor, any Subcontractor or Supplier, or by anyone directly
or indirectly employed by any of them to perform any of the Work, or by anyone for whose acts
any of them may be liable:
1. claims under workers’ compensation, disability benefits, and other similar employee benefit
acts;
2. claims for damages because of bodily injury, occupational sickness or disease, or death of
Contractor’s employees.
3. The limits of liability for the insurance shall provide the following coverages for not less
than the following amounts or greater where required by Laws and Regulations
a. Statutory limits
b. Employer's liability
00 73 10- 10
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 10 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
1) $100,000 each accident/occurrence
2) $100,000 Disease - each employee
3) $500,000 Disease - policy limit
B. Commercial General Liability. Coverage shall include but not be limited to covering liability
(bodily injury or property damage) arising from: premises/operations, independent contractors,
products/completed operations, personal injury, and liability under an insured contract. Insurance
shall be provided on an occurrence basis, and as comprehensive as the current Insurance
Services Office (ISO) policy. This insurance shall apply as primary insurance with respect to
any other insurance or self-insurance programs afforded to the City. The Commercial General
Liability policy, shall have no exclusions by endorsements that would alter of nullify
premises/operations, products/completed operations, contractual, personal injury, or advertising
injury, which are normally contained with the policy, unless the City approves such exclusions
in writing.
1. For construction projects that present a substantial completed operation exposure, the City
may require the contractor to maintain completed operations coverage for a minimum of no
less than three (3) years following the completion of the project
2. Contractor's Liability Insurance under this Section which shall be on a per project basis
covering the Contractor with minimum limits of:
a. $1,000,000 each occurrence
b. $2,000,000 aggregate limit
3. The policy must have an endorsement (Amendment – Aggregate Limits of Insurance)
making the General Aggregate Limits apply separately to each job site.
4. The Commercial General Liability Insurance policies shall provide “X”, “C”, and “U”
coverage’s. Verification of such coverage must be shown in the Remarks Article of the
Certificate of Insurance.
C. Automobile Liability. A commercial business auto policy shall provide coverage on “any auto”,
defined as autos owned, hired and non-owned and provide indemnity for claims for damages
because bodily injury or death of any person and or property damage arising out of the work,
maintenance or use of any motor vehicle by the Contractor, any Subcontractor or Supplier, or by
anyone directly or indirectly employed by any of them to perform any of the Work, or by anyone
for whose acts any of them may be liable.
1. Automobile Liability, Contractor’s Liability Insurance under this Section, which shall be in
an amount not less than the following amounts:
a. Automobile Liability - a commercial business policy shall provide coverage on "Any
Auto", defined as autos owned, hired and non-owned.
00 73 10- 11
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 11 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
1) $1,000,000 each accident on a combined single limit basis. Split limits are
acceptable if limits are at least:
2) $250,000 Bodily Injury per person
3) $500,000 Bodily Injury per accident /
4) $100,000 Property Damage
D. Railroad Protective Liability. If any of the work or any warranty work is within the limits of
railroad right-of-way, the Contractor shall comply with the following requirements:
1. The Contractor’s construction activities will require its employees, agents, subcontractors,
equipment, and material deliveries to cross railroad properties and tracks owned and
operated by: ____________________________________________________________
Write the name of the railroad company. (If none, then write none)
2. The Contractor shall conduct its operations on railroad properties in such a manner as not to
interfere with, hinder, or obstruct the railroad company in any manner whatsoever in the use
or operation of its/their trains or other property. Such operations on railroad properties may
require that Contractor to execute a “Right of Entry Agreement” with the particular railroad
company or companies involved, and to this end the Contractor should satisfy itself as to the
requirements of each railroad company and be prepared to execute the right-of-entry (if any)
required by a railroad company. The requirements specified herein likewise relate to the
Contractor’s use of private and/or construction access roads crossing said railroad company’s
properties.
3. The Contractual Liability coverage required by Paragraph 5.04D of the General Conditions
shall provide coverage for not less than the following amounts, issued by companies
satisfactory to the City and to the Railroad Company for a term that continues for so long as
the Contractor’s operations and work cross, occupy, or touch railroad property:
a. General Aggregate: _____________________________________
Enter limits provided by Railroad Company (If none, write none)
b. Each Occurrence: : _____________________________________
Enter limits provided by Railroad Company (If none, write none)
4. With respect to the above outlined insurance requirements, the following shall govern:
a. Where a single railroad company is involved, the Contractor shall provide one insurance
policy in the name of the railroad company. However, if more than one grade separation
or at-grade crossing is affected by the Project at entirely separate locations on the line or
lines of the same railroad company, separate coverage may be required, each in the
amount stated above.
b. Where more than one railroad company is operating on the same right-of-way or where
several railroad companies are involved and operated on their own separate rights-of-
N/A
N/A
N/A
00 73 10- 12
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 12 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
way, the Contractor may be required to provide separate insurance policies in the name
of each railroad company.
c. If, in addition to a grade separation or an at-grade crossing, other work or activity is
proposed on a railroad company’s right-of-way at a location entirely separate from the
grade separation or at-grade crossing, insurance coverage for this work must be included
in the policy covering the grade separation.
d. If no grade separation is involved but other work is proposed on a railroad company’s
right-of-way, all such other work may be covered in a single policy for that railroad, even
though the work may be at two or more separate locations.
5. No work or activities on a railroad company’s property to be performed by the Contractor
shall be commenced until the Contractor has furnished the City with an original policy or
policies of the insurance for each railroad company named, as required above. All such
insurance must be approved by the City and each affected Railroad Company prior to the
Contractor’s beginning work.
6. The insurance specified above must be carried until all Work to be performed on the railroad
right-of-way has been completed and the grade crossing, if any, is no longer used by the
Contractor. In addition, insurance must be carried during all maintenance and/or repair work
performed in the railroad right-of-way. Such insurance must name the railroad company as
the insured, together with any tenant or lessee of the railroad company operating over tracks
involved in the Project.
E. Notification of Policy Cancellation: Contractor shall immediately notify City upon cancellation
or other loss of insurance coverage. Contractor shall stop work until replacement insurance has
been procured. There shall be no time credit for days not worked pursuant to this section.
4.05 Acceptance of Bonds and Insurance; Option to Replace
If City has any objection to the coverage afforded by or other provisions of the bonds or insurance
required to be purchased and maintained by the Contractor in accordance with Article 5 on the basis
of non-conformance with the Contract Documents, the Developer and City shall so notify the
Contractor in writing within 10 Business Days after receipt of the certificates (or other evidence
requested). Contractor shall provide to the City such additional information in respect of insurance
provided as the Developer or City may reasonably request. If Contractor does not purchase or
maintain all of the bonds and insurance required by the Contract Documents, the Developer or City
shall notify the Contractor in writing of such failure prior to the start of the Work, or of such failure
to maintain prior to any change in the required coverage.
ARTICLE 5 – CONTRACTOR’S RESPONSIBILITIES
5.01 Supervision and Superintendent
A. Contractor shall supervise, inspect, and direct the Work competently and efficiently, devoting
such attention thereto and applying such skills and expertise as may be necessary to perform the
00 73 10- 13
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 13 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
Work in accordance with the Contract Documents. Contractor shall be solely responsible for the
means, methods, techniques, sequences, and procedures of construction.
B. At all times during the progress of the Work, Contractor shall assign a competent, English-
speaking, Superintendent who shall not be replaced without written notice to City. The
Superintendent will be Contractor’s representative at the Site and shall have authority to act on
behalf of Contractor. All communication given to or received from the Superintendent shall be
binding on Contractor.
C. Contractor shall notify the City 24 hours prior to moving areas during the sequence of
construction.
5.02 Labor; Working Hours
A. Contractor shall provide competent, suitably qualified personnel to perform construction as
required by the Contract Documents. Contractor shall at all times maintain good discipline and
order at the Site.
B. Except as otherwise required for the safety or protection of persons or the Work or property at
the Site or adjacent thereto, and except as otherwise stated in the Contract Documents, all Work
at the Site shall be performed during Regular Working Hours. Contractor will not permit the
performance of Work beyond Regular Working Hours or for Weekend Working Hours without
City’s written consent (which will not be unreasonably withheld). Written request (by letter or
electronic communication) to perform Work:
1. for beyond Regular Working Hours request must be made by noon at least two (2) Business
Days prior
2. for Weekend Working Hours request must be made by noon of the preceding Thursday
3. for legal holidays request must be made by noon two Business Days prior to the legal
holiday.
5.03 Services, Materials, and Equipment
A. Unless otherwise specified in the Contract Documents, Contractor shall provide and assume full
responsibility for all services, materials, equipment, labor, transportation, construction
equipment and machinery, tools, appliances, fuel, power, light, heat, telephone, water, sanitary
facilities, temporary facilities, and all other facilities and incidentals necessary for the
performance, Contractor required testing, start-up, and completion of the Work.
B. All materials and equipment incorporated into the Work shall be as specified or, if not specified,
shall be of good quality and new, except as otherwise provided in the Contract Documents. All
special warranties and guarantees required by the Specifications shall expressly run to the benefit
of City. If required by City, Contractor shall furnish satisfactory evidence (including reports of
required tests) as to the source, kind, and quality of materials and equipment.
00 73 10- 14
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 14 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
C. All materials and equipment to be incorporated into the Work shall be stored, applied, installed,
connected, erected, protected, used, cleaned, and conditioned in accordance with instructions of
the applicable Supplier, except as otherwise may be provided in the Contract Documents.
5.04 Project Schedule
A. Contractor shall adhere to the Project Schedule established in accordance with Paragraph 2.01
and the General Requirements as it may be adjusted from time to time as provided below.
1. Contractor shall submit to City for acceptance (to the extent indicated in Paragraph 2.01 and
the General Requirements) proposed adjustments in the Project Schedule.
2. Proposed adjustments in the Project Schedule that will change the Contract Time shall be
submitted in accordance with the requirements of Article 9. Adjustments in Contract Time
for projects with City participation shall be made by participating change orders.
5.05 Substitutes and “Or-Equals”
A. Whenever an item of material or equipment is specified or described in the Contract Documents
by using the name of a proprietary item or the name of a particular Supplier, the specification or
description is intended to establish the type, function, appearance, and quality required. Unless
the specification or description contains or is followed by words reading that no like, equivalent,
or “or-equal” item or no substitution is permitted, other items of material or equipment of other
Suppliers may be submitted to City for review under the circumstances described below.
1. “Or-Equal” Items: If in City’s sole discretion an item of material or equipment proposed by
Contractor is functionally equal to that named and sufficiently similar so that no change in
related Work will be required, it may be considered by City as an “or-equal” item, in which
case review and approval of the proposed item may, in City’s sole discretion, be
accomplished without compliance with some or all of the requirements for approval of
proposed substitute items. For the purposes of this Paragraph 5.05.A.1, a proposed item of
material or equipment will be considered functionally equal to an item so named if:
a. City determines that:
1) it is at least equal in materials of construction, quality, durability, appearance,
strength, and design characteristics;
2) it will reliably perform at least equally well the function and achieve the results
imposed by the design concept of the completed Project as a functioning whole; and
3) it has a proven record of performance and availability of responsive service; and
b. Contractor certifies that, if approved and incorporated into the Work:
1) there will be no increase in cost to the City or increase in Contract Time; and
00 73 10- 15
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 15 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
2) it will conform substantially to the detailed requirements of the item named in the
Contract Documents.
2. Substitute Items:
a. If in City’s sole discretion an item of material or equipment proposed by Contractor does
not qualify as an “or-equal” item under Paragraph 5.05.A.1, it may be submitted as a
proposed substitute item.
b. Contractor shall submit sufficient information as provided below to allow City to
determine if the item of material or equipment proposed is essentially equivalent to that
named and an acceptable substitute therefor. Requests for review of proposed substitute
items of material or equipment will not be accepted by City from anyone other than
Contractor.
c. Contractor shall make written application to City for review of a proposed substitute item
of material or equipment that Contractor seeks to furnish or use. The application shall
comply with Section 01 25 00 and:
1) shall certify that the proposed substitute item will:
i. perform adequately the functions and achieve the results called for by the general
design;
ii. be similar in substance to that specified;
iii. be suited to the same use as that specified; and
2) will state:
i. the extent, if any, to which the use of the proposed substitute item will prejudice
Contractor’s achievement of final completion on time;
ii. whether use of the proposed substitute item in the Work will require a change in
any of the Contract Documents (or in the provisions of any other direct contract
with City for other work on the Project) to adapt the design to the proposed
substitute item;
iii. whether incorporation or use of the proposed substitute item in connection with
the Work is subject to payment of any license fee or royalty; and
3) will identify:
i. all variations of the proposed substitute item from that specified;
ii. available engineering, sales, maintenance, repair, and replacement services; and
00 73 10- 16
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 16 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
4) shall contain an itemized estimate of all costs or credits that will result directly or
indirectly from use of such substitute item, including costs of redesign and Damage
Claims of other contractors affected by any resulting change.
B. Substitute Construction Methods or Procedures: If a specific means, method, technique,
sequence, or procedure of construction is expressly required by the Contract Documents,
Contractor may furnish or utilize a substitute means, method, technique, sequence, or procedure
of construction approved by City. Contractor shall submit sufficient information to allow City, in
City’s sole discretion, to determine that the substitute proposed is equivalent to that expressly
called for by the Contract Documents. Contractor shall make written application to City for
review in the same manner as those provided in Paragraph 5.05.A.2.
C. City’s Evaluation: City will be allowed a reasonable time within which to evaluate each
proposal or submittal made pursuant to Paragraphs 5.05.A and 5.05.B. City may require
Contractor to furnish additional data about the proposed substitute. City will be the sole judge of
acceptability. No “or-equal” or substitute will be ordered, installed or utilized until City’s review
is complete, which will be evidenced by a Change Order in the case of a substitute and an
accepted Submittal for an “or-equal.” City will advise Contractor in writing of its determination.
D. Special Guarantee: City may require Contractor to furnish at Contractor’s expense a special
performance guarantee, warranty, or other surety with respect to any substitute. Contractor shall
indemnify and hold harmless City and anyone directly or indirectly employed by them from and
against any and all claims, damages, losses and expenses (including attorneys fees) arising out
of the use of substituted materials or equipment.
E. City’s Cost Reimbursement: City will record City’s costs in evaluating a substitute proposed or
submitted by Contractor pursuant to Paragraphs 5.05.A.2 and 5.05.B. Whether or not City
approves a substitute so proposed or submitted by Contractor, Contractor may be required to
reimburse City for evaluating each such proposed substitute. Contractor may also be required to
reimburse City for the charges for making changes in the Contract Documents.
F. Contractor’s Expense: Contractor shall provide all data in support of any proposed substitute or
“or-equal” at Contractor’s expense.
G. Substitute Reimbursement: Costs (savings or charges) attributable to acceptance of a substitute
shall be incorporated to the Contract by Participating Change Order.
5.06 Pre-Qualification of Bidders (Prime Contractors and Subcontractors)
A. The Contractor and any subcontractors are required to be prequalified for the work types
requiring pre-qualification
5.07 Concerning Subcontractors, Suppliers, and Others
A. Minority and Women Owned Business Enterprise Compliance:
00 73 10- 17
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 17 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
Required for this Contract.
(Check this box if there is any City Participation)
Not Required for this Contract.
It is City policy to ensure the full and equitable participation by Minority and Women Business
Enterprises (MWBE) in the procurement of goods and services on a contractual basis. If the
Contract Documents provide for a MWBE goal, Contractor is required to comply with the intent
of the City’s MWBE Ordinance (as amended) by the following:
1. Contractor shall, upon request by City, provide complete and accurate information regarding
actual work performed by a MWBE on the Contract and payment therefor.
2. Contractor will not make additions, deletions, or substitutions of accepted MWBE without
written consent of the City. Any unjustified change or deletion shall be a material breach of
Contract and may result in debarment in accordance with the procedures outlined in the
Ordinance.
3. Contractor shall, upon request by City, allow an audit and/or examination of any books,
records, or files in the possession of the Contractor that will substantiate the actual work
performed by an MWBE. Material misrepresentation of any nature will be grounds for
termination of the Contract. Any such misrepresentation may be grounds for disqualification
of Contractor to bid on future contracts with the City for a period of not less than three years.
B. Contractor shall be fully responsible to City for all acts and omissions of the Subcontractors,
Suppliers, and other individuals or entities performing or furnishing any of the Work just as
Contractor is responsible for Contractor’s own acts and omissions. Nothing in the Contract
Documents:
1. shall create for the benefit of any such Subcontractor, Supplier, or other individual or entity
any contractual relationship between City and any such Subcontractor, Supplier or other
individual or entity; nor
2. shall create any obligation on the part of City to pay or to see to the payment of any moneys
due any such Subcontractor, Supplier, or other individual or entity except as may otherwise
be required by Laws and Regulations.
C. Contractor shall be solely responsible for scheduling and coordinating the Work of
Subcontractors, Suppliers, and other individuals or entities performing or furnishing any of the
Work under a direct or indirect contract with Contractor.
D. All Subcontractors, Suppliers, and such other individuals or entities performing or furnishing
any of the Work shall communicate with City through Contractor.
E. All Work performed for Contractor by a Subcontractor or Supplier will be pursuant to an
appropriate agreement between Contractor and the Subcontractor or Supplier which specifically
binds the Subcontractor or Supplier to the applicable terms and conditions of these Contract
x
00 73 10- 18
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 18 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
Documents, Contractor shall provide City contract numbers and reference numbers to the
Subcontractors and/or Suppliers.
5.08 Wage Rates
Required for this Contract.
Not Required for this Contract.
A. Duty to pay Prevailing Wage Rates. The Contractor shall comply with all requirements of
Chapter 2258, Texas Government Code (as amended), including the payment of not less than the
rates determined by the City Council of the City of Fort Worth to be the prevailing wage rates in
accordance with Chapter 2258. Such prevailing wage rates are included in these Contract
Documents.
B. Penalty for Violation. A Contractor or any Subcontractor who does not pay the prevailing wage
shall, upon demand made by the City, pay to the City $60 for each worker employed for each
calendar day or part of the day that the worker is paid less than the prevailing wage rates
stipulated in these contract documents. This penalty shall be retained by the City to offset its
administrative costs, pursuant to Texas Government Code 2258.023.
C. Complaints of Violations and City Determination of Good Cause. On receipt of information,
including a complaint by a worker, concerning an alleged violation of 2258.023, Texas
Government Code, by a Contractor or Subcontractor, the City shall make an initial
determination, before the 31st day after the date the City receives the information, as to whether
good cause exists to believe that the violation occurred. The City shall notify in writing the
Contractor or Subcontractor and any affected worker of its initial determination. Upon the
City’s determination that there is good cause to believe the Contractor or Subcontractor has
violated Chapter 2258, the City shall retain the full amounts claimed by the claimant or
claimants as the difference between wages paid and wages due under the prevailing wage rates,
such amounts being subtracted from successive progress payments pending a final determination
of the violation.
D. Arbitration Required if Violation Not Resolved. An issue relating to an alleged violation of
Section 2258.023, Texas Government Code, including a penalty owed to the City or an affected
worker, shall be submitted to binding arbitration in accordance with the Texas General
Arbitration Act (Article 224 et seq., Revised Statutes) if the Contractor or Subcontractor and any
affected worker does not resolve the issue by agreement before the 15th day after the date the
City makes its initial determination pursuant to Paragraph C above. If the persons required to
arbitrate under this section do not agree on an arbitrator before the 11th day after the date that
arbitration is required, a district court shall appoint an arbitrator on the petition of any of the
persons. The City is not a party in the arbitration. The decision and award of the arbitrator is
final and binding on all parties and may be enforced in any court of competent jurisdiction.
E. Records to be Maintained. The Contractor and each Subcontractor shall, for a period of three (3)
years following the date of acceptance of the work, maintain records that show (i) the name and
x
00 73 10- 19
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 19 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
occupation of each worker employed by the Contractor in the construction of the Work provided
for in this Contract; and (ii) the actual per diem wages paid to each worker. The records shall be
open at all reasonable hours for inspection by the City. The provisions of Paragraph 6.23, Right
to Audit, shall pertain to this inspection.
F. Progress Payments. With each progress payment or payroll period, whichever is less, the
Contractor shall submit an affidavit stating that the Contractor has complied with the
requirements of Chapter 2258, Texas Government Code.
G. Posting of Wage Rates. The Contractor shall post prevailing wage rates in a conspicuous place at
all times.
H. Subcontractor Compliance. The Contractor shall include in its subcontracts and/or shall
otherwise require all of its Subcontractors to comply with Paragraphs A through G above.
5.09 Patent Fees and Royalties
A. To the fullest extent permitted by Laws and Regulations, Contractor shall indemnify and hold
harmless City, from and against all claims, costs, losses, and damages (including but not limited
to all fees and charges of engineers, architects, attorneys, and other professionals and all court
or arbitration or other dispute resolution costs) arising out of or relating to any infringement of
patent rights or copyrights incident to the use in the performance of the Work or resulting from
the incorporation in the Work of any invention, design, process, product, or device not specified
in the Contract Documents.
5.10 Laws and Regulations
A. Contractor shall give all notices required by and shall comply with all Laws and Regulations
applicable to the performance of the Work. Except where otherwise expressly required by
applicable Laws and Regulations, the City shall not be responsible for monitoring Contractor’s
compliance with any Laws or Regulations.
B. If Contractor performs any Work knowing or having reason to know that it is contrary to Laws
or Regulations, Contractor shall bear all claims, costs, losses, and damages (including but not
limited to all fees and charges of engineers, architects, attorneys, and other professionals and all
court or arbitration or other dispute resolution costs) arising out of or relating to such Work.
However, it shall not be Contractor’s responsibility to make certain that the Specifications and
Drawings are in accordance with Laws and Regulations, but this shall not relieve Contractor of
Contractor’s obligations under Paragraph 3.01.
5.11 Use of Site and Other Areas
A. Limitation on Use of Site and Other Areas:
1. Contractor shall confine construction equipment, the storage of materials and equipment, and
the operations of workers to the Site and other areas permitted by Laws and Regulations, and
shall not unreasonably encumber the Site and other areas with construction equipment or
00 73 10- 20
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 20 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
other materials or equipment. Contractor shall assume full responsibility for any damage to
any such land or area, or to the owner or occupant thereof, or of any adjacent land or areas
resulting from the performance of the Work.
2. At any time when, in the judgment of the City, the Contractor has obstructed or closed or is
carrying on operations in a portion of a street, right-of-way, or easement greater than is
necessary for proper execution of the Work, the City may require the Contractor to finish the
section on which operations are in progress before work is commenced on any additional
area of the Site.
3. Should any Damage Claim be made by any such owner or occupant because of the
performance of the Work, Contractor shall promptly attempt to resolve the Damage Claim.
4. Pursuant to Paragraph 5.18, Contractor shall indemnify and hold harmless City, from and
against all claims, costs, losses, and damages arising out of or relating to any claim or
action, legal or equitable, brought by any such owner or occupant against City.
B. Removal of Debris During Performance of the Work: During the progress of the Work
Contractor shall keep the Site and other areas free from accumulations of waste materials,
rubbish, and other debris. Removal and disposal of such waste materials, rubbish, and other
debris shall conform to applicable Laws and Regulations.
C. Site Maintenance Cleaning: 24 hours after written notice is given to the Contractor that the
clean-up on the job site is proceeding in a manner unsatisfactory to the City or Developer, if the
Contractor fails to correct the unsatisfactory procedure, the City may take such direct action as
the City deems appropriate to correct the clean-up deficiencies cited to the Contractor in the
written notice (by letter or electronic communication), and shall be entitled to recover its cost in
doing so. The City may withhold Final Acceptance until clean-up is complete and cost are
recovered.
D. Final Site Cleaning: Prior to Final Acceptance of the Work Contractor shall clean the Site and
the Work and make it ready for utilization by City or adjacent property owner. At the completion
of the Work Contractor shall remove from the Site all tools, appliances, construction equipment
and machinery, and surplus materials and shall restore to original condition or better all property
disturbed by the Work.
E. Loading Structures: Contractor shall not load nor permit any part of any structure to be loaded
in any manner that will endanger the structure, nor shall Contractor subject any part of the Work
or adjacent property to stresses or pressures that will endanger it.
5.12 Record Documents
A. Contractor shall maintain in a safe place at the Site or in a place designated by the Contractor
and approved by the City, one (1) record copy of all Drawings, Specifications, Addenda, Change
Orders, Field Orders, and written interpretations and clarifications in good order and annotated
to show changes made during construction. These record documents together with all approved
00 73 10- 21
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 21 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
Samples and a counterpart of all accepted Submittals will be available to City for reference.
Upon completion of the Work, these record documents, any operation and maintenance manuals,
and Submittals will be delivered to City prior to Final Inspection. Contractor shall include
accurate locations for buried and imbedded items.
5.13 Safety and Protection
A. Contractor shall be solely responsible for initiating, maintaining and supervising all safety
precautions and programs in connection with the Work. Such responsibility does not relieve
Subcontractors of their responsibility for the safety of persons or property in the performance of
their work, nor for compliance with applicable safety Laws and Regulations. Contractor shall
take all necessary precautions for the safety of, and shall provide the necessary protection to
prevent damage, injury or loss to:
1. all persons on the Site or who may be affected by the Work;
2. all the Work and materials and equipment to be incorporated therein, whether in storage on
or off the Site; and
3. other property at the Site or adjacent thereto, including trees, shrubs, lawns, walks,
pavements, roadways, structures, utilities, and Underground Facilities not designated for
removal, relocation, or replacement in the course of construction.
B. Contractor shall comply with all applicable Laws and Regulations relating to the safety of
persons or property, or to the protection of persons or property from damage, injury, or loss; and
shall erect and maintain all necessary safeguards for such safety and protection. Contractor shall
notify owners of adjacent property and of Underground Facilities and other utility owners when
prosecution of the Work may affect them, and shall cooperate with them in the protection,
removal, relocation, and replacement of their property.
C. Contractor shall comply with the applicable requirements of City’s safety programs, if any.
D. Contractor shall inform City of the specific requirements of Contractor’s safety program, if any,
with which City’s employees and representatives must comply while at the Site.
E. All damage, injury, or loss to any property referred to in Paragraph 5.13.A.2 or 5.13.A.3 caused,
directly or indirectly, in whole or in part, by Contractor, any Subcontractor, Supplier, or any
other individual or entity directly or indirectly employed by any of them to perform any of the
Work, or anyone for whose acts any of them may be liable, shall be remedied by Contractor.
F. Contractor’s duties and responsibilities for safety and for protection of the Work shall continue
until such time as all the Work is completed and City has accepted the Work.
5.14 Safety Representative
Contractor shall inform City in writing of Contractor’s designated safety representative at the Site.
00 73 10- 22
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 22 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
5.15 Hazard Communication Programs
Contractor shall be responsible for coordinating any exchange of material safety data sheets or other
hazard communication information required to be made available to or exchanged between or
among employers in accordance with Laws or Regulations.
5.16 Submittals
A. Contractor shall submit required Submittals to City for review and acceptance. Each submittal
will be identified as required by City.
1. Submit number of copies specified in the General Requirements.
2. Data shown on the Submittals will be complete with respect to quantities, dimensions,
specified performance and design criteria, materials, and similar data to show City the
services, materials, and equipment Contractor proposes to provide and to enable City to
review the information for the limited purposes required by Paragraph 5.16.C.
3. Submittals submitted as herein provided by Contractor and reviewed by City for
conformance with the design concept shall be executed in conformity with the Contract
Documents unless otherwise required by City.
4. When Submittals are submitted for the purpose of showing the installation in greater detail,
their review shall not excuse Contractor from requirements shown on the Drawings and
Specifications.
5. For-Information-Only submittals upon which the City is not expected to conduct review or
take responsive action may be so identified in the Contract Documents.
6. Submit required number of Samples specified in the Specifications.
7. Clearly identify each Sample as to material, Supplier, pertinent data such as catalog numbers,
the use for which intended and other data as City may require to enable City to review the
submittal for the limited purposes required by Paragraph 5.16.C.
B. Where a Submittal is required by the Contract Documents or the Schedule of Submittals, any
related Work performed prior to City’s review and acceptance of the pertinent submittal will be
at the sole expense and responsibility of Contractor.
C. City’s Review:
1. City will provide timely review of required Submittals in accordance with the Schedule of
Submittals acceptable to City. City’s review and acceptance will be only to determine if the
items covered by the submittals will, after installation or incorporation in the Work, conform
to the information given in the Contract Documents and be compatible with the design
concept of the completed Project as a functioning whole as indicated by the Contract
Documents.
00 73 10- 23
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 23 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
2. City’s review and acceptance will not extend to means, methods, techniques, sequences, or
procedures of construction (except where a particular means, method, technique, sequence,
or procedure of construction is specifically and expressly called for by the Contract
Documents) or to safety precautions or programs incident thereto. The review and
acceptance of a separate item as such will not indicate approval of the assembly in which the
item functions.
3. City’s review and acceptance shall not relieve Contractor from responsibility for any
variation from the requirements of the Contract Documents unless Contractor has complied
with the requirements of Section 01 33 00 and City has given written acceptance of each
such variation by specific written notation thereof incorporated in or accompanying the
Submittal. City’s review and acceptance shall not relieve Contractor from responsibility for
complying with the requirements of the Contract Documents.
5.17 Contractor’s General Warranty and Guarantee
A. Contractor warrants and guarantees to City that all Work will be in accordance with the Contract
Documents and will not be defective. City and its officers, directors, members, partners,
employees, agents, consultants, and subcontractors shall be entitled to rely on representation of
Contractor’s warranty and guarantee.
B. Contractor’s warranty and guarantee hereunder excludes defects or damage caused by:
1. abuse, modification, or improper maintenance or operation by persons other than Contractor,
Subcontractors, Suppliers, or any other individual or entity for whom Contractor is
responsible; or
2. normal wear and tear under normal usage.
C. Contractor’s obligation to perform and complete the Work in accordance with the Contract
Documents shall be absolute. None of the following will constitute an acceptance of Work that is
not in accordance with the Contract Documents or a release of Contractor’s obligation to
perform the Work in accordance with the Contract Documents:
1. observations by City;
2. recommendation or payment by City or Developer of any progress or final payment;
3. the issuance of a certificate of Final Acceptance by City or any payment related thereto by
City;
4. use or occupancy of the Work or any part thereof by City;
5. any review and acceptance of a Submittal by City;
6. any inspection, test, or approval by others; or
00 73 10- 24
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 24 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
7. any correction of defective Work by City.
D. The Contractor shall remedy any defects or damages in the Work and pay for any damage to
other work or property resulting therefrom which shall appear within a period of two (2) years
from the date of Final Acceptance of the Work unless a longer period is specified and shall
furnish a good and sufficient maintenance bond, complying with the requirements of Article
4.02.B. The City will give notice of observed defects with reasonable promptness.
5.18 Indemnification
A. Contractor covenants and agrees to indemnify, hold harmless and defend, at its own expense, the
City, its officers, servants and employees, from and against any and all claims arising out of, or
alleged to arise out of, the work and services to be performed by the Contractor, its officers,
agents, employees, subcontractors, licenses or invitees under this Contract. THIS
INDEMNIFICATION PROVISION IS SPECIFICALLY INTENDED TO OPERATE
AND BE EFFECTIVE EVEN IF IT IS ALLEGED OR PROVEN THAT ALL OR SOME
OF THE DAMAGES BEING SOUGHT WERE CAUSED, IN WHOLE OR IN PART, BY
ANY ACT, OMISSION OR NEGLIGENCE OF THE CITY. This indemnity provision is
intended to include, without limitation, indemnity for costs, expenses and legal fees incurred by
the City in defending against such claims and causes of actions.
B. Contractor covenants and agrees to indemnify and hold harmless, at its own expense, the City, its
officers, servants and employees, from and against any and all loss, damage or destruction of
property of the City, arising out of, or alleged to arise out of, the work and services to be
performed by the Contractor, its officers, agents, employees, subcontractors, licensees or invitees
under this Contract. THIS INDEMNIFICATION PROVISION IS SPECIFICALLY
INTENDED TO OPERATE AND BE EFFECTIVE EVEN IF IT IS ALLEGED OR
PROVEN THAT ALL OR SOME OF THE DAMAGES BEING SOUGHT WERE
CAUSED, IN WHOLE OR IN PART, BY ANY ACT, OMISSION OR NEGLIGENCE OF
THE CITY.
5.19 Delegation of Professional Design Services
A. Contractor will not be required to provide professional design services unless such services are
specifically required by the Contract Documents for a portion of the Work or unless such
services are required to carry out Contractor’s responsibilities for construction means, methods,
techniques, sequences and procedures.
B. If professional design services or certifications by a design professional related to systems,
materials or equipment are specifically required of Contractor by the Contract Documents, City
will specify all performance and design criteria that such services must satisfy. Contractor shall
cause such services or certifications to be provided by a properly licensed professional, whose
signature and seal shall appear on all drawings, calculations, specifications, certifications, and
Submittals prepared by such professional. Submittals related to the Work designed or certified
by such professional, if prepared by others, shall bear such professional’s written approval when
submitted to City.
00 73 10- 25
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 25 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
C. City shall be entitled to rely upon the adequacy, accuracy and completeness of the services,
certifications or approvals performed by such design professionals, provided City has specified
to Contractor performance and design criteria that such services must satisfy.
D. Pursuant to this Paragraph 5.19, City’s review and acceptance of design calculations and design
drawings will be only for the limited purpose of checking for conformance with performance
and design criteria given and the design concept expressed in the Contract Documents. City’s
review and acceptance of Submittals (except design calculations and design drawings) will be
only for the purpose stated in Paragraph 5.16.C.
5.20 Right to Audit:
A. The City reserves the right to audit all projects utilizing City funds
B. The Contractor agrees that the City shall, until the expiration of three (3) years after final
payment under this Contract, have access to and the right to examine and photocopy any directly
pertinent books, documents, papers, and records of the Contractor involving transactions relating
to this Contract. Contractor agrees that the City shall have access during Regular Working Hours
to all necessary Contractor facilities and shall be provided adequate and appropriate work space
in order to conduct audits in compliance with the provisions of this Paragraph. The City shall
give Contractor reasonable advance notice of intended audits.
C. Contractor further agrees to include in all its subcontracts hereunder a provision to the effect that
the subcontractor agrees that the City shall, until the expiration of three (3) years after final
payment under this Contract, have access to and the right to examine and photocopy any directly
pertinent books, documents, papers, and records of such Subcontractor, involving transactions to
the subcontract, and further, that City shall have access during Regular Working Hours to all
Subcontractor facilities, and shall be provided adequate and appropriate work space in order to
conduct audits in compliance with the provisions of this Paragraph. The City shall give
Subcontractor reasonable advance notice of intended audits.
D. Contractor and Subcontractor agree to photocopy such documents as may be requested by the
City. The City agrees to reimburse Contractor for the cost of the copies as follows at the rate
published in the Texas Administrative Code in effect as of the time copying is performed.
5.21 Nondiscrimination
A. The City is responsible for operating Public Transportation Programs and implementing transit-
related projects, which are funded in part with Federal financial assistance awarded by the U.S.
Department of Transportation and the Federal Transit Administration (FTA), without
discriminating against any person in the United States on the basis of race, color, or national
origin.
B. Title VI, Civil Rights Act of 1964 as amended: Contractor shall comply with the requirements of
the Act and the Regulations as further defined in the Supplementary Conditions for any project
receiving Federal assistance.
00 73 10- 26
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 26 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
ARTICLE 6 – OTHER WORK AT THE SITE
6.01 Related Work at Site
A. City may perform other work related to the Project at the Site with City’s employees, or other
City contractors, or through other direct contracts therefor, or have other work performed by
utility owners. If such other work is not noted in the Contract Documents, then written notice
thereof will be given to Contractor prior to starting any such other work; and
B. Contractor shall afford each other contractor who is a party to such a direct contract, each utility
owner, and City, if City is performing other work with City’s employees or other City
contractors, proper and safe access to the Site, provide a reasonable opportunity for the
introduction and storage of materials and equipment and the execution of such other work, and
properly coordinate the Work with theirs. Contractor shall do all cutting, fitting, and patching of
the Work that may be required to properly connect or otherwise make its several parts come
together and properly integrate with such other work. Contractor shall not endanger any work of
others by cutting, excavating, or otherwise altering such work; provided, however, that
Contractor may cut or alter others' work with the written consent of City and the others whose
work will be affected.
C. If the proper execution or results of any part of Contractor’s Work depends upon work
performed by others under this Article 7, Contractor shall inspect such other work and promptly
report to City in writing any delays, defects, or deficiencies in such other work that render it
unavailable or unsuitable for the proper execution and results of Contractor’s Work. Contractor’s
failure to so report will constitute an acceptance of such other work as fit and proper for
integration with Contractor’s Work except for latent defects in the work provided by others.
ARTICLE 7 – CITY’S RESPONSIBILITIES
7.01 Inspections, Tests, and Approvals
City’s responsibility with respect to certain inspections, tests, and approvals is set forth in Paragraph
11.03.
7.02 Limitations on City’s Responsibilities
A. The City shall not supervise, direct, or have control or authority over, nor be responsible for,
Contractor’s means, methods, techniques, sequences, or procedures of construction, or the safety
precautions and programs incident thereto, or for any failure of Contractor to comply with Laws
and Regulations applicable to the performance of the Work. City will not be responsible for
Contractor’s failure to perform the Work in accordance with the Contract Documents.
B. City will notify the Contractor of applicable safety plans pursuant to Paragraph 5.13.
00 73 10- 27
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 27 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
7.03 Compliance with Safety Program
While at the Site, City’s employees and representatives shall comply with the specific applicable
requirements of Contractor’s safety programs of which City has been informed pursuant to
Paragraph 5.13.
ARTICLE 8 – CITY’S OBSERVATION STATUS DURING CONSTRUCTION
8.01 City’s Project Representative
City will provide one or more Project Representative(s) during the construction period. The duties
and responsibilities and the limitations of authority of City’s representative during construction are
set forth in the Contract Documents.
A. City’s Project Representative will make visits to the Site at intervals appropriate to the various
stages of construction as City deems necessary in order to observe the progress that has been
made and the quality of the various aspects of Contractor’s executed Work. Based on
information obtained during such visits and observations, City’s Project Representative will
determine, in general, if the Work is proceeding in accordance with the Contract Documents.
City’s Project Representative will not be required to make exhaustive or continuous inspections
on the Site to check the quality or quantity of the Work. City’s Project Representative’s efforts
will be directed toward providing City a greater degree of confidence that the completed Work
will conform generally to the Contract Documents.
B. City’s Project Representative’s visits and observations are subject to all the limitations on
authority and responsibility in the Contract Documents.
8.02 Authorized Variations in Work
City’s Project Representative may authorize minor variations in the Work from the requirements of
the Contract Documents which do not involve an adjustment in the Contract Price or the Contract
Time and are compatible with the design concept of the completed Project as a functioning whole as
indicated by the Contract Documents. These may be accomplished by a Field Order and will be
binding on City Developer, and also on Contractor, who shall perform the Work involved promptly.
8.03 Rejecting Defective Work
City will have authority to reject Work which City’s Project Representative believes to be defective,
or will not produce a completed Project that conforms to the Contract Documents or that will
prejudice the integrity of the design concept of the completed Project as a functioning whole as
indicated by the Contract Documents. City will have authority to conduct special inspection or
testing of the Work as provided in Article 11, whether or not the Work is fabricated, installed, or
completed.
00 73 10- 28
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 28 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
8.04 Determinations for Work Performed
Contractor will determine the actual quantities and classifications of Work performed. City’s Project
Representative will review with Contractor the preliminary determinations on such matters before
rendering a written recommendation. City’s written decision will be final (except as modified to
reflect changed factual conditions or more accurate data).
ARTICLE 9 – CHANGES IN THE WORK
9.01 Authorized Changes in the Work
A. Without invalidating the Contract and without notice to any surety, City may, at any time or
from time to time, order Extra Work. Upon notice of such Extra Work, Contractor shall
promptly proceed with the Work involved which will be performed under the applicable
conditions of the Contract Documents (except as otherwise specifically provided). Extra Work
shall be memorialized by a Participating Change Order which may or may not precede an order
of Extra work.
B. For minor changes of Work not requiring changes to Contract Time or Contract Price on a
project with City participation, a Field Order may be issued by the City.
9.02 Notification to Surety
If the provisions of any bond require notice to be given to a surety of any change affecting the
general scope of the Work or the provisions of the Contract Documents (including, but not limited
to, Contract Price or Contract Time), the giving of any such notice will be Contractor’s
responsibility. The amount of each applicable bond will be adjusted by the Contractor to reflect the
effect of any such change.
ARTICLE 10 – CHANGE OF CONTRACT PRICE; CHANGE OF CONTRACT TIME
10.01 Change of Contract Price
A. The Contract Price may only be changed by a Participating Change Order for projects with City
participation.
10.02 Change of Contract Time
A. The Contract Time may only be changed by a Participating Change Order for projects with City
participation.
10.03 Delays
A. If Contractor is delayed, City shall not be liable to Contractor for any claims, costs, losses, or
damages (including but not limited to all fees and charges of engineers, architects, attorneys, and
other professionals and all court or arbitration or other dispute resolution costs) sustained by
Contractor on or in connection with any other project or anticipated project.
00 73 10- 29
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 29 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
ARTICLE 11 – TESTS AND INSPECTIONS; CORRECTION, REMOVAL OR ACCEPTANCE OF
DEFECTIVE WORK
11.01 Notice of Defects
Notice of all defective Work of which City has actual knowledge will be given to Contractor.
Defective Work may be rejected, corrected, or accepted as provided in this Article 13.
11.02 Access to Work
City, independent testing laboratories, and governmental agencies with jurisdictional interests will
have access to the Site and the Work at reasonable times for their observation, inspection, and
testing. Contractor shall provide them proper and safe conditions for such access and advise them of
Contractor’s safety procedures and programs so that they may comply therewith as applicable.
11.03 Tests and Inspections
A. Contractor shall give City timely notice of readiness of the Work for all required inspections,
tests, or approvals and shall cooperate with inspection and testing personnel to facilitate required
inspections or tests.
B. If Contract Documents, Laws or Regulations of any public body having jurisdiction require any
of the Work (or part thereof) to be inspected, tested, or approved, Contractor shall assume full
responsibility for arranging and obtaining such independent inspections, tests, retests or
approvals, pay all costs in connection therewith, and furnish City the required certificates of
inspection or approval; excepting, however, those fees specifically identified in the
Supplementary Conditions or any Texas Department of Licensure and Regulation (TDLR)
inspections, which shall be paid as described in the Supplementary Conditions.
C. Contractor shall be responsible for arranging and obtaining and shall pay all costs in connection
with any inspections, tests, re-tests, or approvals required for City’s acceptance of materials or
equipment to be incorporated in the Work; or acceptance of materials, mix designs, or equipment
submitted for approval prior to Contractor’s purchase thereof for incorporation in the Work.
Such inspections, tests, re-tests, or approvals shall be performed by organizations approved by
City.
D. City may arrange for the services of an independent testing laboratory (“Testing Lab”) to
perform any inspections or tests (“Testing”) for any part of the Work, as determined solely by
City.
1. City will coordinate such Testing to the extent possible, with Contractor;
2. Should any Testing under this Section 11.03 D result in a “fail”, “did not pass” or other
similar negative result, the Contractor shall be responsible for paying for any and all retests.
Contractor’s cancellation without cause of City initiated Testing shall be deemed a negative
result and require a retest.
00 73 10- 30
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 30 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
3. Any amounts owed for any retest under this Section 11.03 D shall be paid directly to the
Testing Lab by Contractor. City will forward all invoices for retests to
Developer/Contractor.
4. If Contractor fails to pay the Testing Lab, City will not issue a letter of Final Acceptance
until the Testing Lab is Paid
E. If any Work (or the work of others) that is to be inspected, tested, or approved is covered by
Contractor without written concurrence of City, Contractor shall, if requested by City, uncover
such Work for observation.
11.04 Uncovering Work
A. If any Work is covered contrary to the Contract Documents or specific instructions by the City, it
must, if requested by City, be uncovered for City’s observation and replaced at Contractor’s
expense.
11.05 City May Stop the Work
If the Work is defective, or Contractor fails to supply sufficient skilled workers or suitable materials
or equipment, or fails to perform the Work in such a way that the completed Work will conform to
the Contract Documents, City may order Contractor to stop the Work, or any portion thereof, until
the cause for such order has been eliminated; however, this right of City to stop the Work shall not
give rise to any duty on the part of City to exercise this right for the benefit of Contractor, any
Subcontractor, any Supplier, any other individual or entity, or any surety for, or employee or agent
of any of them.
11.06 Correction or Removal of Defective Work
A. Promptly after receipt of written notice, Contractor shall correct all defective Work pursuant to
an acceptable schedule, whether or not fabricated, installed, or completed, or, if the Work has
been rejected by City, remove it from the Project and replace it with Work that is not defective.
Contractor shall pay all claims, costs, additional testing, losses, and damages (including but not
limited to all fees and charges of engineers, architects, attorneys, and other professionals and all
court or arbitration or other dispute resolution costs) arising out of or relating to such correction
or removal (including but not limited to all costs of repair or replacement of work of others).
Failure to require the removal of any defective Work shall not constitute acceptance of such
Work.
B. When correcting defective Work under the terms of this Paragraph 11.06 or Paragraph 11.07,
Contractor shall take no action that would void or otherwise impair City’s special warranty and
guarantee, if any, on said Work.
11.07 Correction Period
A. If within two (2) years after the date of Final Acceptance (or such longer period of time as may
be prescribed by the terms of any applicable special guarantee required by the Contract
00 73 10- 31
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 31 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
Documents), any Work is found to be defective, or if the repair of any damages to the land or
areas made available for Contractor’s use by City or permitted by Laws and Regulations as
contemplated in Paragraph 5.10.A is found to be defective, Contractor shall promptly, without
cost to City and in accordance with City’s written instructions:
1. repair such defective land or areas; or
2. correct such defective Work; or
3. if the defective Work has been rejected by City, remove it from the Project and replace it
with Work that is not defective, and
4. satisfactorily correct or repair or remove and replace any damage to other Work, to the work
of others or other land or areas resulting therefrom.
B. If Contractor does not promptly comply with the terms of City’s written instructions, or in an
emergency where delay would cause serious risk of loss or damage, City may have the defective
Work corrected or repaired or may have the rejected Work removed and replaced. All claims,
costs, losses, and damages (including but not limited to all fees and charges of engineers,
architects, attorneys, and other professionals and all court or other dispute resolution costs)
arising out of or relating to such correction or repair or such removal and replacement (including
but not limited to all costs of repair or replacement of work of others) will be paid by Contractor.
C. Where defective Work (and damage to other Work resulting therefrom) has been corrected or
removed and replaced under this Paragraph 11.07, the correction period hereunder with respect
to such Work may be required to be extended for an additional period of one year after the end
of the initial correction period. City shall provide 30 days written notice to Contractor and
Developer should such additional warranty coverage be required. Contractor’s obligations under
this Paragraph 11.07 are in addition to any other obligation or warranty. The provisions of this
Paragraph 11.07 shall not be construed as a substitute for, or a waiver of, the provisions of any
applicable statute of limitation or repose.
11.08 City May Correct Defective Work
A. If Contractor fails within a reasonable time after written notice from City to correct defective
Work, or to remove and replace rejected Work as required by City in accordance with Paragraph
11.06.A, or if Contractor fails to perform the Work in accordance with the Contract Documents,
or if Contractor fails to comply with any other provision of the Contract Documents, City may,
after seven (7) days written notice to Contractor and the Developer, correct, or remedy any such
deficiency.
B. In exercising the rights and remedies under this Paragraph 11.09, City shall proceed
expeditiously. In connection with such corrective or remedial action, City may exclude
Contractor from all or part of the Site, take possession of all or part of the Work and suspend
Contractor’s services related thereto, and incorporate in the Work all materials and equipment
incorporated in the Work, stored at the Site or for which City has paid Contractor but which are
00 73 10- 32
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 32 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
stored elsewhere. Contractor shall allow City, City’s representatives, agents, consultants,
employees, and City’s other contractors, access to the Site to enable City to exercise the rights
and remedies under this Paragraph.
C. All claims, costs, losses, and damages (including but not limited to all fees and charges of
engineers, architects, attorneys, and other professionals and all court or other dispute resolution
costs) incurred or sustained by City in exercising the rights and remedies under this Paragraph
13.09 will be charged against Contractor, and a Change Order will be issued incorporating the
necessary revisions in the Contract Documents with respect to the Work; and City shall be
entitled to an appropriate decrease in the Contract Price.
D. Contractor shall not be allowed an extension of the Contract Time because of any delay in the
performance of the Work attributable to the exercise of City’s rights and remedies under this
Paragraph 11.09.
ARTICLE 12 – COMPLETION
12.01 Contractor’s Warranty of Title
Contractor warrants and guarantees that title to all Work, materials, and equipment covered by any
Application for Payment will pass to City no later than the time of Final Acceptance and shall be
free and clear of all Liens.
12.02 Partial Utilization
A. Prior to Final Acceptance of all the Work, City may use or occupy any substantially completed
part of the Work which has specifically been identified in the Contract Documents, or which
City, determines constitutes a separately functioning and usable part of the Work that can be
used by City for its intended purpose without significant interference with Contractor’s
performance of the remainder of the Work. City at any time may notify Contractor in writing to
permit City to use or occupy any such part of the Work which City determines to be ready for its
intended use, subject to the following conditions:
1. Contractor at any time may notify City in writing that Contractor considers any such part of
the Work ready for its intended use.
2. Within a reasonable time after notification as enumerated in Paragraph 14.05.A.1, City and
Contractor shall make an inspection of that part of the Work to determine its status of
completion. If City does not consider that part of the Work to be substantially complete, City
will notify Contractor in writing giving the reasons therefor.
3. Partial Utilization will not constitute Final Acceptance by City.
12.03 Final Inspection
A. Upon written notice from Contractor that the entire Work is complete in accordance with the
Contract Documents:
00 73 10- 33
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 33 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
1. within 10 days, City will schedule a Final Inspection with Contractor.
2. City will notify Contractor in writing of all particulars in which this inspection reveals that
the Work is incomplete or defective. Contractor shall immediately take such measures as are
necessary to complete such Work or remedy such deficiencies.
12.04 Final Acceptance
A. Upon completion by Contractor to City’s satisfaction, of any additional Work identified in the
Final Inspection, City will issue to Contractor a letter of Final Acceptance upon the satisfaction
of the following:
1. All documentation called for in the Contract Documents, including but not limited to the
evidence of insurance required by Paragraph 5.03;
2. consent of the surety, if any, to Final Acceptance;
3. a list of all pending or released Damage Claims against City that Contractor believes are
unsettled; and
4. affidavits of payments and complete and legally effective releases or waivers (satisfactory to
City) of all Lien rights arising out of or Liens filed in connection with the Work.
5. after all Damage Claims have been resolved:
a. directly by the Contractor or;
b. Contractor provides evidence that the Damage Claim has been reported to Contractor’s
insurance provider for resolution.
6. Issuing Final Acceptance by the City shall not relieve the Contractor of any guarantees or
other requirements of the Contract Documents which specifically continue thereafter.
ARTICLE 13 – SUSPENSION OF WORK
13.01 City May Suspend Work
A. At any time and without cause, City may suspend the Work or any portion thereof by written
notice to Contractor and which may fix the date on which Work will be resumed. Contractor
shall resume the Work on the date so fixed. During temporary suspension of the Work covered
by these Contract Documents, for any reason, the City will stop contract time on City
participation projects.
B. Should the Contractor not be able to complete a portion of the Project due to causes beyond the
control of and without the fault or negligence of the Contractor, and should it be determined by
mutual consent of the Contractor and City that a solution to allow construction to proceed is not
00 73 10- 34
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 34 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
available within a reasonable period of time, Contractor may request an extension in Contract
Time, directly attributable to any such suspension.
C. If it should become necessary to suspend the Work for an indefinite period, the Contractor shall
store all materials in such a manner that they will not obstruct or impede the public unnecessarily
nor become damaged in any way, and he shall take every precaution to prevent damage or
deterioration of the work performed; he shall provide suitable drainage about the work, and erect
temporary structures where necessary.
ARTICLE 14 – MISCELLANEOUS
14.01 Giving Notice
A. Whenever any provision of the Contract Documents requires the giving of written notice, it will
be deemed to have been validly given if:
1. delivered in person to the individual or to a member of the firm or to an officer of the
corporation for whom it is intended; or
2. delivered at or sent by registered or certified mail, postage prepaid, to the last business
address known to the giver of the notice.
B. Business address changes must be promptly made in writing to the other party.
C. Whenever the Contract Documents specifies giving notice by electronic means such electronic
notice shall be deemed sufficient upon confirmation of receipt by the receiving party.
14.02 Computation of Times
When any period of time is referred to in the Contract Documents by days, it will be computed to
exclude the first and include the last day of such period. If the last day of any such period falls on a
Saturday or Sunday or on a day made a legal holiday the next Working Day shall become the last
day of the period.
14.03 Cumulative Remedies
The duties and obligations imposed by these General Conditions and the rights and remedies
available hereunder to the parties hereto are in addition to, and are not to be construed in any way as
a limitation of, any rights and remedies available to any or all of them which are otherwise imposed
or available by Laws or Regulations, by special warranty or guarantee, or by other provisions of the
Contract Documents. The provisions of this Paragraph will be as effective as if repeated specifically
in the Contract Documents in connection with each particular duty, obligation, right, and remedy to
which they apply.
00 73 10- 35
Standard City Conditions Of The Construction Contract For Developer Awarded Projects
Page 35 of 35
CITY OF FORT WORTH
STANDARD CITY CONDITIONS – DEVELOPER AWARDED PROJECTS
Revised: January 10, 2013
14.04 Survival of Obligations
All representations, indemnifications, warranties, and guarantees made in, required by, or given in
accordance with the Contract Documents, as well as all continuing obligations indicated in the
Contract Documents, will survive final payment, completion, and acceptance of the Work or
termination or completion of the Contract or termination of the services of Contractor.
14.05 Headings
Article and paragraph headings are inserted for convenience only and do not constitute parts of these
General Conditions.
01 11 00 - 1
DAP SUMMARY OF WORK
Page 1 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised December 20, 2012
1 SECTION 01 11 00
2 SUMMARY OF WORK
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Summary of Work to be performed in accordance with the Contract Documents
7 B. Deviations from this City of Fort Worth Standard Specification
8 1. None.
9 C. Related Specification Sections include, but are not necessarily limited to:
10 1. Division 0 - Bidding Requirements, Contract Forms, and Conditions of the Contract
11 2. Division 1 - General Requirements
12 1.2 PRICE AND PAYMENT PROCEDURES
13 A. Measurement and Payment
14 1. Work associated with this Item is considered subsidiary to the various items bid.
15 No separate payment will be allowed for this Item.
16 1.3 REFERENCES [NOT USED]
17 1.4 ADMINISTRATIVE REQUIREMENTS
18 A. Work Covered by Contract Documents
19 1. Work is to include furnishing all labor, materials, and equipment, and performing
20 all Work necessary for this construction project as detailed in the Drawings and
21 Specifications.
22 B. Subsidiary Work
23 1. Any and all Work specifically governed by documentary requirements for the
24 project, such as conditions imposed by the Drawings or Contract Documents in
25 which no specific item for bid has been provided for in the Proposal and the item is
26 not a typical unit bid item included on the standard bid item list, then the item shall
27 be considered as a subsidiary item of Work, the cost of which shall be included in
28 the price bid in the Proposal for various bid items.
29 C. Use of Premises
30 1. Coordinate uses of premises under direction of the City.
31 2. Assume full responsibility for protection and safekeeping of materials and
32 equipment stored on the Site.
33 3. Use and occupy only portions of the public streets and alleys, or other public places
34 or other rights-of-way as provided for in the ordinances of the City, as shown in the
35 Contract Documents, or as may be specifically authorized in writing by the City.
36 a. A reasonable amount of tools, materials, and equipment for construction
37 purposes may be stored in such space, but no more than is necessary to avoid
38 delay in the construction operations.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 11 00 - 2
DAP SUMMARY OF WORK
Page 2 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised December 20, 2012
1 b. Excavated and waste materials shall be stored in such a way as not to interfere
2 with the use of spaces that may be designated to be left free and unobstructed
3 and so as not to inconvenience occupants of adjacent property.
4 c. If the street is occupied by railroad tracks, the Work shall be carried on in such
5 manner as not to interfere with the operation of the railroad.
6 1) All Work shall be in accordance with railroad requirements set forth in
7 Division 0 as well as the railroad permit.
8 D. Work within Easements
9 1. Do not enter upon private property for any purpose without having previously
10 obtained permission from the owner of such property.
11 2. Do not store equipment or material on private property unless and until the
12 specified approval of the property owner has been secured in writing by the
13 Contractor and a copy furnished to the City.
14 3. Unless specifically provided otherwise, clear all rights-of-way or easements of
15 obstructions which must be removed to make possible proper prosecution of the
16 Work as a part of the project construction operations.
17 4. Preserve and use every precaution to prevent damage to, all trees, shrubbery, plants,
18 lawns, fences, culverts, curbing, and all other types of structures or improvements,
19 to all water, sewer, and gas lines, to all conduits, overhead pole lines, or
20 appurtenances thereof, including the construction of temporary fences and to all
21 other public or private property adjacent to the Work.
22 5. Notify the proper representatives of the owners or occupants of the public or private
23 lands of interest in lands which might be affected by the Work.
24 a. Such notice shall be made at least 48 hours in advance of the beginning of the
25 Work.
26 b. Notices shall be applicable to both public and private utility companies and any
27 corporation, company, individual, or other, either as owners or occupants,
28 whose land or interest in land might be affected by the Work.
29 c. Be responsible for all damage or injury to property of any character resulting
30 from any act, omission, neglect, or misconduct in the manner or method or
31 execution of the Work, or at any time due to defective work, material, or
32 equipment.
33 6. Fence
34 a. Restore all fences encountered and removed during construction of the Project
35 to the original or a better than original condition.
36 b. Erect temporary fencing in place of the fencing removed whenever the Work is
37 not in progress and when the site is vacated overnight, and/or at all times to
38 provide site security.
39 c. The cost for all fence work within easements, including removal, temporary
40 closures and replacement, shall be subsidiary to the various items bid in the
41 project proposal, unless a bid item is specifically provided in the proposal.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 11 00 - 3
DAP SUMMARY OF WORK
Page 3 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised December 20, 2012
1 1.5 SUBMITTALS [NOT USED]
2 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
3 1.7 CLOSEOUT SUBMITTALS [NOT USED]
4 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
5 1.9 QUALITY ASSURANCE [NOT USED]
6 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
7 1.11 FIELD [SITE] CONDITIONS [NOT USED]
8 1.12 WARRANTY [NOT USED]
9 PART 2 - PRODUCTS [NOT USED]
10 PART 3 - EXECUTION [NOT USED]
11 END OF SECTION
12
Revision Log
DATE NAME SUMMARY OF CHANGE
13
Meacham Boulevard at Mercantile Drive
CPN 105417
01 25 00 - 1
DAP SUBSTITUTION PROCEDURES
Page 1 of 4
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised August 30, 2013
Birchman Office Space
CPN 105553
SECTION 01 25 00
SUBSTITUTION PROCEDURES
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. The procedure for requesting the approval of substitution of a product that is not
equivalent to a product which is specified by descriptive or performance criteria or
defined by reference to 1 or more of the following:
a. Name of manufacturer
b. Name of vendor
c. Trade name
d. Catalog number
2. Substitutions are not "or-equals".
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Work associated with this Item is considered subsidiary to the various items bid. No
separate payment will be allowed for this Item.
1.3 REFERENCES [NOT USED]
1.4 ADMINISTRATIVE REQUIREMENTS
A. Request for Substitution - General
1. Within 30 days after award of Contract (unless noted otherwise), the City will
consider formal requests from Contractor for substitution of products in place of
those specified.
2. Certain types of equipment and kinds of material are described in Specifications by
means of references to names of manufacturers and vendors, trade names, or catalog
numbers.
a. When this method of specifying is used, it is not intended to exclude from
consideration other products bearing other manufacturer's or vendor's names,
trade names, or catalog numbers, provided said products are "or-equals," as
determined by City.
3. Other types of equipment and kinds of material may be acceptable substitutions
under the following conditions:
a. Or-equals are unavailable due to strike, discontinued production of products
meeting specified requirements, or other factors beyond control of Contractor;
or,
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised August 30, 2013
Birchman Office Space
CPN 105553
01 25 00 - 2
DAP SUBSTITUTION PROCEDURES
Page 2 of 4
b. Contractor proposes a cost and/or time reduction incentive to the City.
1.5 SUBMITTALS
A. See Request for Substitution Form (attached)
B. Procedure for Requesting Substitution
1. Substitution shall be considered only:
a. After award of Contract
b. Under the conditions stated herein
2. Submit 3 copies of each written request for substitution, including:
a. Documentation
1) Complete data substantiating compliance of proposed substitution with
Contract Documents
2) Data relating to changes in construction schedule, when a reduction is
proposed
3) Data relating to changes in cost
b. For products
1) Product identification
a) Manufacturer's name
b) Telephone number and representative contact name
c) Specification Section or Drawing reference of originally specified
product, including discrete name or tag number assigned to original
product in the Contract Documents
2) Manufacturer's literature clearly marked to show compliance of proposed
product with Contract Documents
3) Itemized comparison of original and proposed product addressing product
characteristics including, but not necessarily limited to:
a) Size
b) Composition or materials of construction
c) Weight
d) Electrical or mechanical requirements
4) Product experience
a) Location of past projects utilizing product
b) Name and telephone number of persons associated with referenced
projects knowledgeable concerning proposed product
c) Available field data and reports associated with proposed product
5) Samples
a) Provide at request of City.
b) Samples become the property of the City.
c. For construction methods:
1) Detailed description of proposed method
2) Illustration drawings
C. Approval or Rejection
1. Written approval or rejection of substitution given by the City
2. City reserves the right to require proposed product to comply with color and pattern
of specified product if necessary to secure design intent.
3. In the event the substitution is approved, if a reduction in cost or time results, it will
be documented by Change Order.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised August 30, 2013
Birchman Office Space
CPN 105553
01 25 00 - 3
DAP SUBSTITUTION PROCEDURES
Page 3 of 4
4. Substitution will be rejected if:
a. Submittal is not through the Contractor with his stamp of approval
b. Request is not made in accordance with this Specification Section
c. In the Developer’s opinion, acceptance will require substantial revision of the
original design
d. In the City’s or Developer’s opinion, substitution will not perform adequately
the function consistent with the design intent
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE
A. In making request for substitution or in using an approved product, the Contractor
represents that the Contractor:
1. Has investigated proposed product, and has determined that it is adequate or
superior in all respects to that specified, and that it will perform function for which it
is intended
2. Will provide same guarantee for substitute item as for product specified
3. Will coordinate installation of accepted substitution into Work, to include building
modifications if necessary, making such changes as may be required for Work to be
complete in all respects
4. Waives all claims for additional costs related to substitution which subsequently
arise
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS [NOT USED]
PART 3 - EXECUTION [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised August 30, 2013
Birchman Office Space
CPN 105553
01 25 00 - 4
DAP SUBSTITUTION PROCEDURES
Page 4 of 4
EXHIBIT A
REQUEST FOR SUBSTITUTION FORM:
TO:
PROJECT: DATE:
We hereby submit for your consideration the following product instead of the specified item for
the above project:
SECTION PARAGRAPH SPECIFIED ITEM
Proposed Substitution:
Reason for Substitution:
Include complete information on changes to Drawings and/or Specifications which proposed
substitution will require for its proper installation.
Fill in Blanks Below:
A. Will the undersigned contractor pay for changes to the building design, including engineering
and detailing costs caused by the requested substitution?
B. What effect does substitution have on other trades?
C. Differences between proposed substitution and specified item?
D. Differences in product cost or product delivery time?
E. Manufacturer's guarantees of the proposed and specified items are:
Equal Better (explain on attachment)
The undersigned states that the function, appearance and quality are equivalent or superior to the
specified item.
Submitted By: For Use by City
Signature Recommended Recommended
as noted
Firm Not recommended Received late
Address By
Date
Date Remarks
Telephone
For Use by City:
Approved Rejected
City Date
Meacham Boulevard at Mercantile Drive
CPN 105417
01 31 19 - 1
DAP PRECONSTRUCTION MEETING
Page 1 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 SECTION 01 31 19
2 PRECONSTRUCTION MEETING
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Provisions for the preconstruction meeting to be held prior to the start of Work to
7 clarify construction contract administration procedures
8 B. Deviations from this City of Fort Worth Standard Specification
9 1. No construction schedule required unless requested by the City.
10 C. Related Specification Sections include, but are not necessarily limited to:
11 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
12 2. Division 1 – General Requirements
13 1.2 PRICE AND PAYMENT PROCEDURES
14 A. Measurement and Payment
15 1. Work associated with this Item is considered subsidiary to the various items bid.
16 No separate payment will be allowed for this Item.
17 1.3 REFERENCES [NOT USED]
18 1.4 ADMINISTRATIVE REQUIREMENTS
19 A. Coordination
20 1. Attend preconstruction meeting.
21 2. Representatives of Contractor, subcontractors and suppliers attending meetings
22 shall be qualified and authorized to act on behalf of the entity each represents.
23 3. Meeting administered by City may be tape recorded.
24 a. If recorded, tapes will be used to prepare minutes and retained by City for
25 future reference.
26 B. Preconstruction Meeting
27 1. A preconstruction meeting will be held within 14 days after the delivery of the
28 distribution package to the City.
29 a. The meeting will be scheduled and administered by the City.
30 2. The Project Representative will preside at the meeting, prepare the notes of the
31 meeting and distribute copies of same to all participants who so request by fully
32 completing the attendance form to be circulated at the beginning of the meeting.
33 3. Attendance shall include:
34 a. Developer and Consultant
35 b. Contractor's project manager
36 c. Contractor's superintendent
37 d. Any subcontractor or supplier representatives whom the Contractor may desire
38 to invite or the City may request
Meacham Boulevard at Mercantile Drive
CPN 105417
01 31 19 - 2
DAP PRECONSTRUCTION MEETING
Page 2 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 e. Other City representatives
2 f. Others as appropriate
3 4. Preliminary Agenda may include:
4 a. Introduction of Project Personnel
5 b. General Description of Project
6 c. Status of right-of-way, utility clearances, easements or other pertinent permits
7 d. Contractor’s work plan and schedule
8 e. Contract Time
9 f. Notice to Proceed
10 g. Construction Staking
11 h. Progress Payments
12 i. Extra Work and Change Order Procedures
13 j. Field Orders
14 k. Disposal Site Letter for Waste Material
15 l. Insurance Renewals
16 m. Payroll Certification
17 n. Material Certifications and Quality Control Testing
18 o. Public Safety and Convenience
19 p. Documentation of Pre-Construction Conditions
20 q. Weekend Work Notification
21 r. Legal Holidays
22 s. Trench Safety Plans
23 t. Confined Space Entry Standards
24 u. Coordination with the City’s representative for operations of existing water
25 systems
26 v. Storm Water Pollution Prevention Plan
27 w. Coordination with other Contractors
28 x. Early Warning System
29 y. Contractor Evaluation
30 z. Special Conditions applicable to the project
31 aa. Damages Claims
32 bb. Submittal Procedures
33 cc. Substitution Procedures
34 dd. Correspondence Routing
35 ee. Record Drawings
36 ff. Temporary construction facilities
37 gg. MBE/SBE procedures
38 hh. Final Acceptance
39 ii. Final Payment
40 jj. Questions or Comments
Meacham Boulevard at Mercantile Drive
CPN 105417
01 31 19 - 3
DAP PRECONSTRUCTION MEETING
Page 3 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 1.5 SUBMITTALS [NOT USED]
2 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
3 1.7 CLOSEOUT SUBMITTALS [NOT USED]
4 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
5 1.9 QUALITY ASSURANCE [NOT USED]
6 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
7 1.11 FIELD [SITE] CONDITIONS [NOT USED]
8 1.12 WARRANTY [NOT USED]
9 PART 2 - PRODUCTS [NOT USED]
10 PART 3 - EXECUTION [NOT USED]
11 END OF SECTION
12
Revision Log
DATE NAME SUMMARY OF CHANGE
13
Meacham Boulevard at Mercantile Drive
CPN 105417
01 32 33 - 1
DAP PRECONSTRUCTION VIDEO
Page 1 of 2
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised August 30, 2013
Birchman Office Space
CPN 105553
SECTION 01 32 33
PRECONSTRUCTION VIDEO
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Administrative and procedural requirements for:
a. Preconstruction Videos
B. Deviations from this City of Fort Worth Standard Specification
1. Though not mandatory, it is highly recommended on infill developer projects.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Work associated with this Item is considered subsidiary to the various items bid.
No separate payment will be allowed for this Item.
1.3 REFERENCES [NOT USED]
1.4 ADMINISTRATIVE REQUIREMENTS
A. Preconstruction Video
1. Produce a preconstruction video of the site/alignment, including all areas in the
vicinity of and to be affected by construction.
a. Provide digital copy of video upon request by the City.
2. Retain a copy of the preconstruction video until the end of the maintenance surety
period.
1.5 SUBMITTALS [NOT USED]
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS [NOT USED]
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised August 30, 2013
Birchman Office Space
CPN 105553
01 32 33 - 2
DAP PRECONSTRUCTION VIDEO
Page 2 of 2
PART 3 - EXECUTION [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 1
DAP SUBMITTALS
Page 1 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 SECTION 01 33 00
2 DAP SUBMITTALS
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. General methods and requirements of submissions applicable to the following
7 Work-related submittals:
8 a. Shop Drawings
9 b. Product Data (including Standard Product List submittals)
10 c. Samples
11 d. Mock Ups
12 B. Deviations from this City of Fort Worth Standard Specification
13 1. None.
14 C. Related Specification Sections include, but are not necessarily limited to:
15 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
16 2. Division 1 – General Requirements
17 1.2 PRICE AND PAYMENT PROCEDURES
18 A. Measurement and Payment
19 1. Work associated with this Item is considered subsidiary to the various items bid.
20 No separate payment will be allowed for this Item.
21 1.3 REFERENCES [NOT USED]
22 1.4 ADMINISTRATIVE REQUIREMENTS
23 A. Coordination
24 1. Notify the City in writing, at the time of submittal, of any deviations in the submittals
25 from the requirements of the Contract Documents.
26 2. Coordination of Submittal Times
27 a. Prepare, prioritize and transmit each submittal sufficiently in advance of
28 performing the related Work or other applicable activities, or within the time
29 specified in the individual Work Sections, of the Specifications.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 2
DAP SUBMITTALS
Page 2 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 b. Contractor is responsible such that the installation will not be delayed by
2 processing times including, but not limited to:
3 a) Disapproval and resubmittal (if required)
4 b) Coordination with other submittals
5 c) Testing
6 d) Purchasing
7 e) Fabrication
8 f) Delivery
9 g) Similar sequenced activities
10 c. No extension of time will be authorized because of the Contractor's failure to
11 transmit submittals sufficiently in advance of the Work.
12 d. Make submittals promptly in accordance with approved schedule, and in such
13 sequence as to cause no delay in the Work or in the work of any other
14 contractor.
15 B. Submittal Numbering
16 1. When submitting shop drawings or samples, utilize a 9-character submittal cross-
17 reference identification numbering system in the following manner:
18 a. Use the first 6 digits of the applicable Specification Section Number.
19 b. For the next 2 digits number use numbers 01-99 to sequentially number each
20 initial separate item or drawing submitted under each specific Section number.
21 c. Last use a letter, A-Z, indicating the resubmission of the same drawing (i.e.
22 A=2nd submission, B=3rd submission, C=4th submission, etc.). A typical
23 submittal number would be as follows:
24
25 03 30 00-08-B
26
27 1) 03 30 00 is the Specification Section for Concrete
28 2) 08 is the eighth initial submittal under this Specification Section
29 3) B is the third submission (second resubmission) of that particular shop
30 drawing
31 C. Contractor Certification
32 1. Review shop drawings, product data and samples, including those by
33 subcontractors, prior to submission to determine and verify the following:
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 3
DAP SUBMITTALS
Page 3 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 a. Field measurements
2 b. Field construction criteria
3 c. Catalog numbers and similar data
4 d. Conformance with the Contract Documents
5 2. Provide each shop drawing, sample and product data submitted by the Contractor
6 with a Certification Statement affixed including:
7 a. The Contractor's Company name
8 b. Signature of submittal reviewer
9 c. Certification Statement
10 1) “By this submittal, I hereby represent that I have determined and verified
11 field measurements, field construction criteria, materials, dimensions,
12 catalog numbers and similar data and I have checked and coordinated
13 each item with other applicable approved shop drawings."
14 D. Submittal Format
15 1. Fold shop drawings larger than 8 ½ inches x 11 inches to 8 ½ inches x 11inches.
16 2. Bind shop drawings and product data sheets together.
17 3. Order
18 a. Cover Sheet
19 1) Description of Packet
20 2) Contractor Certification
21 b. List of items / Table of Contents
22 c. Product Data /Shop Drawings/Samples /Calculations
23 E. Submittal Content
24 1. The date of submission and the dates of any previous submissions
25 2. The Project title and number
26 3. Contractor identification
27 4. The names of:
28 a. Contractor
29 b. Supplier
30 c. Manufacturer
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 4
DAP SUBMITTALS
Page 4 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 5. Identification of the product, with the Specification Section number, page and
2 paragraph(s)
3 6. Field dimensions, clearly identified as such
4 7. Relation to adjacent or critical features of the Work or materials
5 8. Applicable standards, such as ASTM or Federal Specification numbers
6 9. Identification by highlighting of deviations from Contract Documents
7 10. Identification by highlighting of revisions on resubmittals
8 11. An 8-inch x 3-inch blank space for Contractor and City stamps
9 F. Shop Drawings
10 1. As specified in individual Work Sections includes, but is not necessarily limited to:
11 a. Custom-prepared data such as fabrication and erection/installation (working)
12 drawings
13 b. Scheduled information
14 c. Setting diagrams
15 d. Actual shopwork manufacturing instructions
16 e. Custom templates
17 f. Special wiring diagrams
18 g. Coordination drawings
19 h. Individual system or equipment inspection and test reports including:
20 1) Performance curves and certifications
21 i. As applicable to the Work
22 2. Details
23 a. Relation of the various parts to the main members and lines of the structure
24 b. Where correct fabrication of the Work depends upon field measurements
25 1) Provide such measurements and note on the drawings prior to submitting
26 for approval.
27 G. Product Data
28 1. For submittals of product data for products included on the City’s Standard Product
29 List, clearly identify each item selected for use on the Project.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 5
DAP SUBMITTALS
Page 5 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 2. For submittals of product data for products not included on the City’s Standard
2 Product List, submittal data may include, but is not necessarily limited to:
3 a. Standard prepared data for manufactured products (sometimes referred to as
4 catalog data)
5 1) Such as the manufacturer's product specification and installation
6 instructions
7 2) Availability of colors and patterns
8 3) Manufacturer's printed statements of compliances and applicability
9 4) Roughing-in diagrams and templates
10 5) Catalog cuts
11 6) Product photographs
12 7) Standard wiring diagrams
13 8) Printed performance curves and operational-range diagrams
14 9) Production or quality control inspection and test reports and certifications
15 10) Mill reports
16 11) Product operating and maintenance instructions and recommended
17 spare-parts listing and printed product warranties
18 12) As applicable to the Work
19 H. Samples
20 1. As specified in individual Sections, include, but are not necessarily limited to:
21 a. Physical examples of the Work such as:
22 1) Sections of manufactured or fabricated Work
23 2) Small cuts or containers of materials
24 3) Complete units of repetitively used products color/texture/pattern swatches
25 and range sets
26 4) Specimens for coordination of visual effect
27 5) Graphic symbols and units of Work to be used by the City for independent
28 inspection and testing, as applicable to the Work
29 I. Do not start Work requiring a shop drawing, sample or product data nor any material to
30 be fabricated or installed prior to the approval or qualified approval of such item.
31 1. Fabrication performed, materials purchased or on-site construction accomplished
32 which does not conform to approved shop drawings and data is at the Contractor's
33 risk.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 6
DAP SUBMITTALS
Page 6 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 2. The City will not be liable for any expense or delay due to corrections or remedies
2 required to accomplish conformity.
3 3. Complete project Work, materials, fabrication, and installations in conformance with
4 approved shop drawings, applicable samples, and product data.
5 J. Submittal Distribution
6 1. Electronic Distribution
7 a. Confirm development of Project directory for electronic submittals to be
8 uploaded to City’s Buzzsaw site, or another external FTP site approved by the
9 City.
10 b. Shop Drawings
11 1) Upload submittal to designated project directory and notify appropriate City
12 representatives via email of submittal posting.
13 2) Hard Copies
14 a) 3 copies for all submittals
15 b) If Contractor requires more than 1 hard copy of Shop Drawings
16 returned, Contractor shall submit more than the number of copies listed
17 above.
18 c. Product Data
19 1) Upload submittal to designated project directory and notify appropriate City
20 representatives via email of submittal posting.
21 2) Hard Copies
22 a) 3 copies for all submittals
23 d. Samples
24 1) Distributed to the Project Representative
25 2. Hard Copy Distribution (if required in lieu of electronic distribution)
26 a. Shop Drawings
27 1) Distributed to the City
28 2) Copies
29 a) 8 copies for mechanical submittals
30 b) 7 copies for all other submittals
31 c) If Contractor requires more than 3 copies of Shop Drawings returned,
32 Contractor shall submit more than the number of copies listed above.
33 b. Product Data
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 7
DAP SUBMITTALS
Page 7 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 1) Distributed to the City
2 2) Copies
3 a) 4 copies
4 c. Samples
5 1) Distributed to the Project Representative
6 2) Copies
7 a) Submit the number stated in the respective Specification Sections.
8 3. Distribute reproductions of approved shop drawings and copies of approved
9 product data and samples, where required, to the job site file and elsewhere as
10 directed by the City.
11 a. Provide number of copies as directed by the City but not exceeding the number
12 previously specified.
13 K. Submittal Review
14 1. The review of shop drawings, data and samples will be for general conformance
15 with the design concept and Contract Documents. This is not to be construed as:
16 a. Permitting any departure from the Contract requirements
17 b. Relieving the Contractor of responsibility for any errors, including details,
18 dimensions, and materials
19 c. Approving departures from details furnished by the City, except as otherwise
20 provided herein
21 2. The review and approval of shop drawings, samples or product data by the City
22 does not relieve the Contractor from his/her responsibility with regard to the
23 fulfillment of the terms of the Contract.
24 a. All risks of error and omission are assumed by the Contractor, and the City will
25 have no responsibility therefore.
26 3. The Contractor remains responsible for details and accuracy, for coordinating the
27 Work with all other associated work and trades, for selecting fabrication processes,
28 for techniques of assembly and for performing Work in a safe manner.
29 4. If the shop drawings, data or samples as submitted describe variations and show a
30 departure from the Contract requirements which City finds to be in the interest of
31 the City and to be so minor as not to involve a change in Contract Price or time for
32 performance, the City may return the reviewed drawings without noting an
33 exception.
34 5. Submittals will be returned to the Contractor under 1 of the following codes:
35 a. Code 1
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 8
DAP SUBMITTALS
Page 8 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 1) "NO EXCEPTIONS TAKEN" is assigned when there are no notations or
2 comments on the submittal.
3 a) When returned under this code the Contractor may release the
4 equipment and/or material for manufacture.
5 b. Code 2
6 1) "EXCEPTIONS NOTED". This code is assigned when a confirmation of the
7 notations and comments IS NOT required by the Contractor.
8 a) The Contractor may release the equipment or material for manufacture;
9 however, all notations and comments must be incorporated into the
10 final product.
11 c. Code 3
12 1) "EXCEPTIONS NOTED/RESUBMIT". This combination of codes is
13 assigned when notations and comments are extensive enough to require a
14 resubmittal of the package.
15 a) The Contractor may release the equipment or material for manufacture;
16 however, all notations and comments must be incorporated into the
17 final product.
18 b) This resubmittal is to address all comments, omissions and
19 non-conforming items that were noted.
20 c) Resubmittal is to be received by the City within 15 Calendar Days of
21 the date of the City's transmittal requiring the resubmittal.
22 d. Code 4
23 1) "NOT APPROVED" is assigned when the submittal does not meet the
24 intent of the Contract Documents.
25 a) The Contractor must resubmit the entire package revised to bring the
26 submittal into conformance.
27 b) It may be necessary to resubmit using a different manufacturer/vendor
28 to meet the Contract Documents.
29 6. Resubmittals
30 a. Handled in the same manner as first submittals
31 1) Corrections other than requested by the City
32 2) Marked with revision triangle or other similar method
33 a) At Contractor’s risk if not marked
34 b. Submittals for each item will be reviewed no more than twice at the City’s
35 expense.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 9
DAP SUBMITTALS
Page 9 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 1) All subsequent reviews will be performed at times convenient to the City
2 and at the Contractor's expense, based on the City's or City
3 Representative’s then prevailing rates.
4 2) Provide Contractor reimbursement to the City within 30 Calendar Days for
5 all such fees invoiced by the City.
6 c. The need for more than 1 resubmission or any other delay in obtaining City's
7 review of submittals, will not entitle the Contractor to an extension of Contract
8 Time.
9 7. Partial Submittals
10 a. City reserves the right to not review submittals deemed partial, at the City’s
11 discretion.
12 b. Submittals deemed by the City to be not complete will be returned to the
13 Contractor, and will be considered "Not Approved" until resubmitted.
14 c. The City may at its option provide a list or mark the submittal directing the
15 Contractor to the areas that are incomplete.
16 8. If the Contractor considers any correction indicated on the shop drawings to
17 constitute a change to the Contract Documents, then written notice must be
18 provided thereof to the Developer at least 7 Calendar Days prior to release for
19 manufacture.
20 9. When the shop drawings have been completed to the satisfaction of the City, the
21 Contractor may carry out the construction in accordance therewith and no further
22 changes therein except upon written instructions from the City.
23 10. Each submittal, appropriately coded, will be returned within 30 Calendar Days
24 following receipt of submittal by the City.
25 L. Mock ups
26 1. Mock Up units as specified in individual Sections, include, but are not necessarily
27 limited to, complete units of the standard of acceptance for that type of Work to be
28 used on the Project. Remove at the completion of the Work or when directed.
29 M. Qualifications
30 1. If specifically required in other Sections of these Specifications, submit a P.E.
31 Certification for each item required.
32 N. Request for Information (RFI)
33 1. Contractor Request for additional information
34 a. Clarification or interpretation of the contract documents
35 b. When the Contractor believes there is a conflict between Contract Documents
Meacham Boulevard at Mercantile Drive
CPN 105417
01 33 00 - 10
DAP SUBMITTALS
Page 10 of 10
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised August 30, 2013
1 c. When the Contractor believes there is a conflict between the Drawings and
2 Specifications
3 1) Identify the conflict and request clarification
4 2. Sufficient information shall be attached to permit a written response without further
5 information.
6
7
8
9
10 1.5 SUBMITTALS [NOT USED]
11 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
12 1.7 CLOSEOUT SUBMITTALS [NOT USED]
13 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
14 1.9 QUALITY ASSURANCE [NOT USED]
15 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
16 1.11 FIELD [SITE] CONDITIONS [NOT USED]
17 1.12 WARRANTY [NOT USED]
18 PART 2 - PRODUCTS [NOT USED]
19 PART 3 - EXECUTION [NOT USED]
20 END OF SECTION
21
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 D. Johnson 1.4.K.8. Working Days modified to Calendar Days
22
Meacham Boulevard at Mercantile Drive
CPN 105417
01 35 13 - 1
DAP SPECIAL PROJECT PROCEDURES
Page 1 of 7
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS CPN 105553
Revised August, 30, 2013
1 SECTION 01 35 13
2 SPECIAL PROJECT PROCEDURES
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. The procedures for special project circumstances that includes, but is not limited to:
7 a. Coordination with the Texas Department of Transportation
8 b. Work near High Voltage Lines
9 c. Confined Space Entry Program
10 d. Air Pollution Watch Days
11 e. Use of Explosives, Drop Weight, Etc.
12 f. Water Department Notification
13 g. Public Notification Prior to Beginning Construction
14 h. Coordination with United States Army Corps of Engineers
15 i. Coordination within Railroad permits areas
16 j. Dust Control
17 k. Employee Parking
18 B. Deviations from this City of Fort Worth Standard Specification
19 1. None.
20 C. Related Specification Sections include, but are not necessarily limited to:
21 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
22 2. Division 1 – General Requirements
23 3. Section 33 12 25 – Connection to Existing Water Mains
24
25 1.2 REFERENCES
26 A. Reference Standards
27 1. Reference standards cited in this Specification refer to the current reference
28 standard published at the time of the latest revision date logged at the end of this
29 Specification, unless a date is specifically cited.
30 2. Health and Safety Code, Title 9. Safety, Subtitle A. Public Safety, Chapter 752.
31 High Voltage Overhead Lines.
32 3. North Central Texas Council of Governments (NCTCOG) – Clean Construction
33 Specification
34 1.3 ADMINISTRATIVE REQUIREMENTS
35 A. Coordination with the Texas Department of Transportation
36 1. When work in the right-of-way which is under the jurisdiction of the Texas
37 Department of Transportation (TxDOT):
38 a. Notify the Texas Department of Transportation prior to commencing any work
39 therein in accordance with the provisions of the permit
Meacham Boulevard at Mercantile Drive
CPN 105417
01 35 13 - 2
DAP SPECIAL PROJECT PROCEDURES
Page 2 of 7
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS CPN 105553
Revised August, 30, 2013
1 b. All work performed in the TxDOT right-of-way shall be performed in
2 compliance with and subject to approval from the Texas Department of
3 Transportation
4 B. Work near High Voltage Lines
5 1. Regulatory Requirements
6 a. All Work near High Voltage Lines (more than 600 volts measured between
7 conductors or between a conductor and the ground) shall be in accordance with
8 Health and Safety Code, Title 9, Subtitle A, Chapter 752.
9 2. Warning sign
10 a. Provide sign of sufficient size meeting all OSHA requirements.
11 3. Equipment operating within 10 feet of high voltage lines will require the following
12 safety features
13 a. Insulating cage-type of guard about the boom or arm
14 b. Insulator links on the lift hook connections for back hoes or dippers
15 c. Equipment must meet the safety requirements as set forth by OSHA and the
16 safety requirements of the owner of the high voltage lines
17 4. Work within 6 feet of high voltage electric lines
18 a. Notification shall be given to:
19 1) The power company (example: ONCOR)
20 a) Maintain an accurate log of all such calls to power company and record
21 action taken in each case.
22 b. Coordination with power company
23 1) After notification coordinate with the power company to:
24 a) Erect temporary mechanical barriers, de-energize the lines, or raise or
25 lower the lines
26 c. No personnel may work within 6 feet of a high voltage line before the above
27 requirements have been met.
28 C. Confined Space Entry Program
29 1. Provide and follow approved Confined Space Entry Program in accordance with
30 OSHA requirements.
31 2. Confined Spaces include:
32 a. Manholes
33 b. All other confined spaces in accordance with OSHA’s Permit Required for
34 Confined Spaces
35 D. Use of Explosives, Drop Weight, Etc.
36 1. When Contract Documents permit on the project the following will apply:
37 a. Public Notification
38 1) Submit notice to City and proof of adequate insurance coverage, 24 hours
39 prior to commencing.
40 2) Minimum 24 hour public notification in accordance with Section 01 31 13
41 E. Water Department Coordination
42 1. During the construction of this project, it will be necessary to deactivate, for a
43 period of time, existing lines. The Contractor shall be required to coordinate with
44 the Water Department to determine the best times for deactivating and activating
45 those lines.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 35 13 - 3
DAP SPECIAL PROJECT PROCEDURES
Page 3 of 7
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS CPN 105553
Revised August, 30, 2013
1 2. Coordinate any event that will require connecting to or the operation of an existing
2 City water line system with the City’s representative.
3 a. Coordination shall be in accordance with Section 33 12 25.
4 b. If needed, obtain a hydrant water meter from the Water Department for use
5 during the life of named project.
6 c. In the event that a water valve on an existing live system be turned off and on
7 to accommodate the construction of the project is required, coordinate this
8 activity through the appropriate City representative.
9 1) Do not operate water line valves of existing water system.
10 a) Failure to comply will render the Contractor in violation of Texas Penal
11 Code Title 7, Chapter 28.03 (Criminal Mischief) and the Contractor
12 will be prosecuted to the full extent of the law.
13 b) In addition, the Contractor will assume all liabilities and
14 responsibilities as a result of these actions.
15 F. Public Notification Prior to Beginning Construction
16 1. Prior to beginning construction on any block in the project, on a block by block
17 basis, prepare and deliver a notice or flyer of the pending construction to the front
18 door of each residence or business that will be impacted by construction. The notice
19 shall be prepared as follows:
20 a. Post notice or flyer 7 days prior to beginning any construction activity on each
21 block in the project area.
22 1) Prepare flyer on the Contractor’s letterhead and include the following
23 information:
24 a) Name of Project
25 b) City Project No (CPN)
26 c) Scope of Project (i.e. type of construction activity)
27 d) Actual construction duration within the block
28 e) Name of the contractor’s foreman and phone number
29 f) Name of the City’s inspector and phone number
30 g) City’s after-hours phone number
31 2) A sample of the ‘pre-construction notification’ flyer is attached as Exhibit
32 A.
33 3) Submit schedule showing the construction start and finish time for each
34 block of the project to the inspector.
35 4) Deliver flyer to the City Inspector for review prior to distribution.
36 b. No construction will be allowed to begin on any block until the flyer is
37 delivered to all residents of the block.
38 G. Public Notification of Temporary Water Service Interruption during Construction
39 1. In the event it becomes necessary to temporarily shut down water service to
40 residents or businesses during construction, prepare and deliver a notice or flyer of
41 the pending interruption to the front door of each affected resident.
42 2. Prepared notice as follows:
43 a. The notification or flyer shall be posted 24 hours prior to the temporary
44 interruption.
45 b. Prepare flyer on the contractor’s letterhead and include the following
46 information:
47 1) Name of the project
48 2) City Project Number
Meacham Boulevard at Mercantile Drive
CPN 105417
01 35 13 - 4
DAP SPECIAL PROJECT PROCEDURES
Page 4 of 7
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS CPN 105553
Revised August, 30, 2013
1 3) Date of the interruption of service
2 4) Period the interruption will take place
3 5) Name of the contractor’s foreman and phone number
4 6) Name of the City’s inspector and phone number
5 c. A sample of the temporary water service interruption notification is attached as
6 Exhibit B.
7 d. Deliver a copy of the temporary interruption notification to the City inspector
8 for review prior to being distributed.
9 e. No interruption of water service can occur until the flyer has been delivered to
10 all affected residents and businesses.
11 f. Electronic versions of the sample flyers can be obtained from the Project
12 Construction Inspector.
13 H. Coordination with United States Army Corps of Engineers (USACE)
14 1. At locations in the Project where construction activities occur in areas where
15 USACE permits are required, meet all requirements set forth in each designated
16 permit.
17 I. Coordination within Railroad Permit Areas
18 1. At locations in the project where construction activities occur in areas where
19 railroad permits are required, meet all requirements set forth in each designated
20 railroad permit. This includes, but is not limited to, provisions for:
21 a. Flagmen
22 b. Inspectors
23 c. Safety training
24 d. Additional insurance
25 e. Insurance certificates
26 f. Other employees required to protect the right-of-way and property of the
27 Railroad Company from damage arising out of and/or from the construction of
28 the project. Proper utility clearance procedures shall be used in accordance
29 with the permit guidelines.
30 2. Obtain any supplemental information needed to comply with the railroad’s
31 requirements.
32 J. Dust Control
33 1. Use acceptable measures to control dust at the Site.
34 a. If water is used to control dust, capture and properly dispose of waste water.
35 b. If wet saw cutting is performed, capture and properly dispose of slurry.
36 K. Employee Parking
37 1. Provide parking for employees at locations approved by the City.
38 L. {Coordination with North Central Texas Council of Governments (NCTCOG) Clean
39 Construction Specification [if required for the project]
40 1. Comply with equipment, operational, reporting and enforcement requirements set
41 forth in NCTCOG’s Clean Construction Specification.}
Meacham Boulevard at Mercantile Drive
CPN 105417
01 35 13 - 5
DAP SPECIAL PROJECT PROCEDURES
Page 5 of 7
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS CPN 105553
Revised August, 30, 2013
1 1.4 SUBMITTALS [NOT USED]
2 1.5 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
3 1.6 CLOSEOUT SUBMITTALS [NOT USED]
4 1.7 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
5 1.8 QUALITY ASSURANCE [NOT USED]
6 1.9 DELIVERY, STORAGE, AND HANDLING [NOT USED]
7 1.10 FIELD [SITE] CONDITIONS [NOT USED]
8 1.11 WARRANTY [NOT USED]
9 PART 2 - PRODUCTS [NOT USED]
10 PART 3 - EXECUTION [NOT USED]
11 END OF SECTION
12
Revision Log
DATE NAME SUMMARY OF CHANGE
8/31/2012 D. Johnson
1.3.B – Added requirement of compliance with Health and Safety Code, Title 9.
Safety, Subtitle A. Public Safety, Chapter 752. High Voltage Overhead Lines.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 35 13 - 6
DAP SPECIAL PROJECT PROCEDURES
Page 6 of 7
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS CPN 105553
Revised August, 30, 2013
1 EXHIBIT A
2 (To be printed on Contractor’s Letterhead)
3
4
5
6 Date:
7
8 CPN No.:
9 Project Name:
10 Mapsco Location:
11 Limits of Construction:
12
13
14
15
16
17 THIS IS TO INFORM YOU THAT UNDER A CONTRACT WITH THE CITY OF FORT
18 WORTH, OUR COMPANY WILL WORK ON UTILITY LINES ON OR AROUND YOUR
19 PROPERTY.
20
21 CONSTRUCTION WILL BEGIN APPROXIMATELY SEVEN DAYS FROM THE DATE
22 OF THIS NOTICE.
23
24 IF YOU HAVE QUESTIONS ABOUT ACCESS, SECURITY, SAFETY OR ANY OTHER
25 ISSUE, PLEASE CALL:
26
27
28 Mr. <CONTRACTOR’S SUPERINTENDENT> AT <TELEPHONE NO.>
29
30 OR
31
32 Mr. <CITY INSPECTOR> AT < TELEPHONE NO.>
33
34 AFTER 4:30 PM OR ON WEEKENDS, PLEASE CALL (817) 392 8306
35
36 PLEASE KEEP THIS FLYER HANDY WHEN YOU CALL
Meacham Boulevard at Mercantile Drive
CPN 105417
01 35 13 - 7
DAP SPECIAL PROJECT PROCEDURES
Page 7 of 7
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS CPN 105553
Revised August, 30, 2013
1 EXHIBIT B
2
3
4
Meacham Boulevard at Mercantile Drive
CPN 105417
01 45 23
DAP TESTING AND INSPECTION SERVICES
Page 1 of 2
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised March 20, 2020
Birchman Office Space
CPN 105553
SECTION 01 45 23
TESTING AND INSPECTION SERVICES
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Testing and inspection services procedures and coordination
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Work associated with this Item is considered subsidiary to the various Items bid.
No separate payment will be allowed for this Item.
a. Contractor is responsible for performing, coordinating, and payment of all
Quality Control testing.
b. City is responsible for performing and payment for first set of Quality
Assurance testing.
1) If the first Quality Assurance test performed by the City fails, the
Contractor is responsible for payment of subsequent Quality Assurance
testing until a passing test occurs.
a) Final acceptance will not be issued by City until all required payments
for testing by Contractor have been paid in full.
1.3 REFERENCES [NOT USED]
1.4 ADMINISTRATIVE REQUIREMENTS
A. Testing
1. Complete testing in accordance with the Contract Documents.
2. Coordination
a. When testing is required to be performed by the City, notify City, sufficiently
in advance, when testing is needed.
b. When testing is required to be completed by the Contractor, notify City,
sufficiently in advance, that testing will be performed.
3. Distribution of Testing Reports
a. Electronic Distribution
1) Confirm development of Project directory for electronic submittals to be
uploaded to the City’s document management system, or another form of
distribution approved by the City.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 45 23
DAP TESTING AND INSPECTION SERVICES
Page 2 of 2
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised March 20, 2020
Birchman Office Space
CPN 105553
2) Upload test reports to designated project directory and notify appropriate
City representatives via email of submittal posting.
3) Hard Copies
a) 1 copy for all submittals submitted to the Project Representative
b. Hard Copy Distribution (if required in lieu of electronic distribution)
1) Tests performed by City
a) Distribute 1 hard copy to the Contractor
2) Tests performed by the Contractor
a) Distribute 3 hard copies to City’s Project Representative
4. Provide City’s Project Representative with trip tickets for each delivered load of
Concrete or Lime material including the following information:
a. Name of pit
b. Date of delivery
c. Material delivered
B. Inspection
1. Inspection or lack of inspection does not relieve the Contractor from obligation to
perform work in accordance with the Contract Documents.
1.5 SUBMITTALS [NOT USED]
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS [NOT USED]
PART 3 - EXECUTION [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
03/20/2020 D.V. Magaña Removed reference to Buzzsaw and noted that electronic submittals be uploaded
through the City’s document management system.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 50 00 - 1
DAP TEMPORARY FACILITIES AND CONTROLS
Page 1 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised JULY 1, 2011
1 SECTION 01 50 00
2 TEMPORARY FACILITIES AND CONTROLS
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Provide temporary facilities and controls needed for the Work including, but not
7 necessarily limited to:
8 a. Temporary utilities
9 b. Sanitary facilities
10 c. Storage Sheds and Buildings
11 d. Dust control
12 e. Temporary fencing of the construction site
13 B. Deviations from this City of Fort Worth Standard Specification
14 1. None.
15 C. Related Specification Sections include, but are not necessarily limited to:
16 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
17 2. Division 1 – General Requirements
18 1.2 PRICE AND PAYMENT PROCEDURES
19 A. Measurement and Payment
20 1. Work associated with this Item is considered subsidiary to the various Items bid.
21 No separate payment will be allowed for this Item.
22 1.3 REFERENCES [NOT USED]
23 1.4 ADMINISTRATIVE REQUIREMENTS
24 A. Temporary Utilities
25 1. Obtaining Temporary Service
26 a. Make arrangements with utility service companies for temporary services.
27 b. Abide by rules and regulations of utility service companies or authorities
28 having jurisdiction.
29 c. Be responsible for utility service costs until Work is approved for Final
30 Acceptance.
31 1) Included are fuel, power, light, heat and other utility services necessary for
32 execution, completion, testing and initial operation of Work.
33 2. Water
34 a. Contractor to provide water required for and in connection with Work to be
35 performed and for specified tests of piping, equipment, devices or other use as
36 required for the completion of the Work.
37 b. Provide and maintain adequate supply of potable water for domestic
38 consumption by Contractor personnel and City’s Project Representatives.
39 c. Coordination
40 1) Contact City 1 week before water for construction is desired
Meacham Boulevard at Mercantile Drive
CPN 105417
01 50 00 - 2
DAP TEMPORARY FACILITIES AND CONTROLS
Page 2 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised JULY 1, 2011
1 d. Contractor Payment for Construction Water
2 1) Obtain construction water meter from City for payment as billed by City’s
3 established rates.
4 3. Electricity and Lighting
5 a. Provide and pay for electric powered service as required for Work, including
6 testing of Work.
7 1) Provide power for lighting, operation of equipment, or other use.
8 b. Electric power service includes temporary power service or generator to
9 maintain operations during scheduled shutdown.
10 4. Telephone
11 a. Provide emergency telephone service at Site for use by Contractor personnel
12 and others performing work or furnishing services at Site.
13 5. Temporary Heat and Ventilation
14 a. Provide temporary heat as necessary for protection or completion of Work.
15 b. Provide temporary heat and ventilation to assure safe working conditions.
16 B. Sanitary Facilities
17 1. Provide and maintain sanitary facilities for persons on Site.
18 a. Comply with regulations of State and local departments of health.
19 2. Enforce use of sanitary facilities by construction personnel at job site.
20 a. Enclose and anchor sanitary facilities.
21 b. No discharge will be allowed from these facilities.
22 c. Collect and store sewage and waste so as not to cause nuisance or health
23 problem.
24 d. Haul sewage and waste off-site at no less than weekly intervals and properly
25 dispose in accordance with applicable regulation.
26 3. Locate facilities near Work Site and keep clean and maintained throughout Project.
27 4. Remove facilities at completion of Project
28 C. Storage Sheds and Buildings
29 1. Provide adequately ventilated, watertight, weatherproof storage facilities with floor
30 above ground level for materials and equipment susceptible to weather damage.
31 2. Storage of materials not susceptible to weather damage may be on blocks off
32 ground.
33 3. Store materials in a neat and orderly manner.
34 a. Place materials and equipment to permit easy access for identification,
35 inspection and inventory.
36 4. Equip building with lockable doors and lighting, and provide electrical service for
37 equipment space heaters and heating or ventilation as necessary to provide storage
38 environments acceptable to specified manufacturers.
39 5. Fill and grade site for temporary structures to provide drainage away from
40 temporary and existing buildings.
41 6. Remove building from site prior to Final Acceptance.
42 D. Temporary Fencing
43 1. Provide and maintain for the duration or construction when required in contract
44 documents
45 E. Dust Control
Meacham Boulevard at Mercantile Drive
CPN 105417
01 50 00 - 3
DAP TEMPORARY FACILITIES AND CONTROLS
Page 3 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised JULY 1, 2011
1 1. Contractor is responsible for maintaining dust control through the duration of the
2 project.
3 a. Contractor remains on-call at all times
4 b. Must respond in a timely manner
5 F. Temporary Protection of Construction
6 1. Contractor or subcontractors are responsible for protecting Work from damage due
7 to weather.
8 1.5 SUBMITTALS [NOT USED]
9 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
10 1.7 CLOSEOUT SUBMITTALS [NOT USED]
11 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
12 1.9 QUALITY ASSURANCE [NOT USED]
13 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
14 1.11 FIELD [SITE] CONDITIONS [NOT USED]
15 1.12 WARRANTY [NOT USED]
16 PART 2 - PRODUCTS [NOT USED]
17 PART 3 - EXECUTION [NOT USED]
18 3.1 INSTALLERS [NOT USED]
19 3.2 EXAMINATION [NOT USED]
20 3.3 PREPARATION [NOT USED]
21 3.4 INSTALLATION
22 A. Temporary Facilities
23 1. Maintain all temporary facilities for duration of construction activities as needed.
24 3.5 [REPAIR] / [RESTORATION]
25 3.6 RE-INSTALLATION
26 3.7 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
27 3.8 SYSTEM STARTUP [NOT USED]
28 3.9 ADJUSTING [NOT USED]
29 3.10 CLEANING [NOT USED]
30 3.11 CLOSEOUT ACTIVITIES
31 A. Temporary Facilities
Meacham Boulevard at Mercantile Drive
CPN 105417
01 50 00 - 4
DAP TEMPORARY FACILITIES AND CONTROLS
Page 4 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised JULY 1, 2011
1 1. Remove all temporary facilities and restore area after completion of the Work, to a
2 condition equal to or better than prior to start of Work.
3 3.12 PROTECTION [NOT USED]
4 3.13 MAINTENANCE [NOT USED]
5 3.14 ATTACHMENTS [NOT USED]
6 END OF SECTION
7
Revision Log
DATE NAME SUMMARY OF CHANGE
8
Meacham Boulevard at Mercantile Drive
CPN 105417
01 55 26 - 1
DAP STREET USE PERMIT AND MODIFICATIONS TO TRAFFIC CONTROL
Page 1 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised July 1, 2011
1 SECTION 01 55 26
2 STREET USE PERMIT AND MODIFICATIONS TO TRAFFIC CONTROL
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Administrative procedures for:
7 a. Street Use Permit
8 b. Modification of approved traffic control
9 c. Removal of Street Signs
10 B. Deviations from this City of Fort Worth Standard Specification
11 1. None.
12 C. Related Specification Sections include, but are not necessarily limited to:
13 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
14 2. Division 1 – General Requirements
15 3. Section 34 71 13 – Traffic Control
16 1.2 PRICE AND PAYMENT PROCEDURES
17 A. Measurement and Payment
18 1. Work associated with this Item is considered subsidiary to the various Items bid.
19 No separate payment will be allowed for this Item.
20 1.3 REFERENCES
21 A.Reference Standards
22 1. Reference standards cited in this specification refer to the current reference standard
23 published at the time of the latest revision date logged at the end of this
24 specification, unless a date is specifically cited.
25 2. Texas Manual on Uniform Traffic Control Devices (TMUTCD).
26 1.4 ADMINISTRATIVE REQUIREMENTS
27 A. Traffic Control
28 1. General
29 a. When traffic control plans are included in the Drawings, provide Traffic
30 Control in accordance with Drawings and Section 34 71 13.
31 b. When traffic control plans are not included in the Drawings, prepare traffic
32 control plans in accordance with Section 34 71 13 and submit to City for
33 review.
34 1) Allow minimum 10 working days for review of proposed Traffic Control.
35 B. Street Use Permit
36 1. Prior to installation of Traffic Control, a City Street Use Permit is required.
37 a. To obtain Street Use Permit, submit Traffic Control Plans to City
38 Transportation and Public Works Department.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 55 26 - 2
DAP STREET USE PERMIT AND MODIFICATIONS TO TRAFFIC CONTROL
Page 2 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised July 1, 2011
1 1) Allow a minimum of 5 working days for permit review.
2 2) Contractor’s responsibility to coordinate review of Traffic Control plans for
3 Street Use Permit, such that construction is not delayed.
4 C. Modification to Approved Traffic Control
5 1. Prior to installation traffic control:
6 a. Submit revised traffic control plans to City Department Transportation and
7 Public Works Department.
8 1) Revise Traffic Control plans in accordance with Section 34 71 13.
9 2) Allow minimum 5 working days for review of revised Traffic Control.
10 3) It is the Contractor’s responsibility to coordinate review of Traffic Control
11 plans for Street Use Permit, such that construction is not delayed.
12 D. Removal of Street Sign
13 1. If it is determined that a street sign must be removed for construction, then contact
14 City Transportation and Public Works Department, Signs and Markings Division to
15 remove the sign.
16 E. Temporary Signage
17 1. In the case of regulatory signs, replace permanent sign with temporary sign meeting
18 requirements of the latest edition of the Texas Manual on Uniform Traffic Control
19 Devices (MUTCD).
20 2. Install temporary sign before the removal of permanent sign.
21 3. When construction is complete, to the extent that the permanent sign can be
22 reinstalled, contact the City Transportation and Public Works Department, Signs
23 and Markings Division, to reinstall the permanent sign.
24 F. Traffic Control Standards
25 1. Traffic Control Standards can be found on the City’s Buzzsaw website.
26 1.5 SUBMITTALS [NOT USED]
27 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
28 1.7 CLOSEOUT SUBMITTALS [NOT USED]
29 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
30 1.9 QUALITY ASSURANCE [NOT USED]
31 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
32 1.11 FIELD [SITE] CONDITIONS [NOT USED]
33 1.12 WARRANTY [NOT USED]
34 PART 2 - PRODUCTS [NOT USED]
35 PART 3 - EXECUTION [NOT USED]
36 END OF SECTION
Meacham Boulevard at Mercantile Drive
CPN 105417
01 55 26 - 3
DAP STREET USE PERMIT AND MODIFICATIONS TO TRAFFIC CONTROL
Page 3 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised July 1, 2011
1
Revision Log
DATE NAME SUMMARY OF CHANGE
2
Meacham Boulevard at Mercantile Drive
CPN 105417
01 57 13 - 1
DAP STORM WATER POLLUTION PREVENTION
Page 1 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised July 1, 2011
1 SECTION 01 57 13
2 STORM WATER POLLUTION PREVENTION
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Procedures for Storm Water Pollution Prevention Plans
7 B. Deviations from this City of Fort Worth Standard Specification
8 1. None.
9 C. Related Specification Sections include, but are not necessarily limited to:
10 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the
11 Contract
12 2. Division 1 – General Requirements
13 3. Section 31 25 00 – Erosion and Sediment Control
14 1.2 PRICE AND PAYMENT PROCEDURES
15 A. Measurement and Payment
16 1. Construction Activities resulting in less than 1 acre of disturbance
17 a. Work associated with this Item is considered subsidiary to the various Items
18 bid. No separate payment will be allowed for this Item.
19 2. Construction Activities resulting in greater than 1 acre of disturbance
20 a. Measurement and Payment shall be in accordance with Section 31 25 00.
21 1.3 REFERENCES
22 A. Abbreviations and Acronyms
23 1. Notice of Intent: NOI
24 2. Notice of Termination: NOT
25 3. Storm Water Pollution Prevention Plan: SWPPP
26 4. Texas Commission on Environmental Quality: TCEQ
27 5. Notice of Change: NOC
28 A.Reference Standards
29 1. Reference standards cited in this Specification refer to the current reference
30 standard published at the time of the latest revision date logged at the end of this
31 Specification, unless a date is specifically cited.
32 2. Integrated Storm Management (iSWM) Technical Manual for Construction
33 Controls
34 1.4 ADMINISTRATIVE REQUIREMENTS
35 A. General
36 1. Contractor is responsible for resolution and payment of any fines issued associated
37 with compliance to Stormwater Pollution Prevention Plan.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 57 13 - 2
DAP STORM WATER POLLUTION PREVENTION
Page 2 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised July 1, 2011
1 B. Construction Activities resulting in:
2 1. Less than 1 acre of disturbance
3 a. Provide erosion and sediment control in accordance with Section 31 25 00 and
4 Drawings.
5 2. 1 to less than 5 acres of disturbance
6 a. Texas Pollutant Discharge Elimination System (TPDES) General Construction
7 Permit is required
8 b. Complete SWPPP in accordance with TCEQ requirements
9 1) TCEQ Small Construction Site Notice Required under general permit
10 TXR150000
11 a) Sign and post at job site
12 b) Prior to Preconstruction Meeting, send 1 copy to City Department of
13 Transportation and Public Works, Environmental Division, (817) 392-
14 6088.
15 2) Provide erosion and sediment control in accordance with:
16 a) Section 31 25 00
17 b) The Drawings
18 c) TXR150000 General Permit
19 d) SWPPP
20 e) TCEQ requirements
21 3. 5 acres or more of Disturbance
22 a. Texas Pollutant Discharge Elimination System (TPDES) General Construction
23 Permit is required
24 b. Complete SWPPP in accordance with TCEQ requirements
25 1) Prepare a TCEQ NOI form and submit to TCEQ along with required fee
26 a) Sign and post at job site
27 b) Send copy to City Department of Transportation and Public Works,
28 Environmental Division, (817) 392-6088.
29 2) TCEQ Notice of Change required if making changes or updates to NOI
30 3) Provide erosion and sediment control in accordance with:
31 a) Section 31 25 00
32 b) The Drawings
33 c) TXR150000 General Permit
34 d) SWPPP
35 e) TCEQ requirements
36 4) Once the project has been completed and all the closeout requirements of
37 TCEQ have been met a TCEQ Notice of Termination can be submitted.
38 a) Send copy to City Department of Transportation and Public Works,
39 Environmental Division, (817) 392-6088.
40 1.5 SUBMITTALS
41 A. SWPPP
42 1. Submit in accordance with Section 01 33 00, except as stated herein.
43 a. Prior to the Preconstruction Meeting, submit a draft copy of SWPPP to the City
44 as follows:
45 1) 1 copy to the City Project Manager
46 a) City Project Manager will forward to the City Department of
47 Transportation and Public Works, Environmental Division for review
Meacham Boulevard at Mercantile Drive
CPN 105417
01 57 13 - 3
DAP STORM WATER POLLUTION PREVENTION
Page 3 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised July 1, 2011
1 B. Modified SWPPP
2 1. If the SWPPP is revised during construction, resubmit modified SWPPP to the City
3 in accordance with Section 01 33 00.
4 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
5 1.7 CLOSEOUT SUBMITTALS [NOT USED]
6 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
7 1.9 QUALITY ASSURANCE [NOT USED]
8 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
9 1.11 FIELD [SITE] CONDITIONS [NOT USED]
10 1.12 WARRANTY [NOT USED]
11 PART 2 - PRODUCTS [NOT USED]
12 PART 3 - EXECUTION [NOT USED]
13 END OF SECTION
14
Revision Log
DATE NAME SUMMARY OF CHANGE
15
Meacham Boulevard at Mercantile Drive
CPN 105417
01 60 00
DAP PRODUCT REQUIREMENTS
Page 1 of 2
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised March 20, 2020
Birchman Office Space
CPN 105553
SECTION 01 60 00
PRODUCT REQUIREMENTS
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. References for Product Requirements and City Standard Products List
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES [NOT USED]
1.3 REFERENCES [NOT USED]
1.4 ADMINISTRATIVE REQUIREMENTS
A list of City approved products for use is available through the City’s website at:
https://apps.fortworthtexas.gov/ProjectResources/ and following the directory
path: 02 - Construction Documents\Standard Products List
A. Only products specifically included on City’s Standard Product List in these Contract
Documents shall be allowed for use on the Project.
1. Any subsequently approved products will only be allowed for use upon specific
approval by the City.
B. Any specific product requirements in the Contract Documents supersede similar
products included on the City’s Standard Product List.
1. The City reserves the right to not allow products to be used for certain projects even
though the product is listed on the City’s Standard Product List.
C. Although a specific product is included on City’s Standard Product List, not all
products from that manufacturer are approved for use, including but not limited to, that
manufacturer’s standard product.
D. See Section 01 33 00 for submittal requirements of Product Data included on City’s
Standard Product List.
1.5 SUBMITTALS [NOT USED]
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
Meacham Boulevard at Mercantile Drive
CPN 105417
01 60 00
DAP PRODUCT REQUIREMENTS
Page 2 of 2
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised March 20, 2020
Birchman Office Space
CPN 105553
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS [NOT USED]
PART 3 - EXECUTION [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
10/12/12 D. Johnson Modified Location of City’s Standard Product List
4/7/2014 M.Domenech Revised for DAP application
03/20/2020 D.V. Magaña Removed reference to Buzzsaw and noted that the City approved products list is
accessible through the City’s website.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 66 00 - 1
DAP PRODUCT STORAGE AND HANDLING REQUIREMENTS
Page 1 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 SECTION 01 66 00
2 PRODUCT STORAGE AND HANDLING REQUIREMENTS
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Scheduling of product delivery
7 2. Packaging of products for delivery
8 3. Protection of products against damage from:
9 a. Handling
10 b. Exposure to elements or harsh environments
11 B. Deviations from this City of Fort Worth Standard Specification
12 1. None.
13 C. Related Specification Sections include, but are not necessarily limited to:
14 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
15 2. Division 1 – General Requirements
16 1.2 PRICE AND PAYMENT PROCEDURES
17 A. Measurement and Payment
18 1. Work associated with this Item is considered subsidiary to the various Items bid.
19 No separate payment will be allowed for this Item.
20 1.3 REFERENCES [NOT USED]
21 1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
22 1.5 SUBMITTALS [NOT USED]
23 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
24 1.7 CLOSEOUT SUBMITTALS [NOT USED]
25 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
26 1.9 QUALITY ASSURANCE [NOT USED]
27 1.10 DELIVERY AND HANDLING
28 A. Delivery Requirements
29 1. Schedule delivery of products or equipment as required to allow timely installation
30 and to avoid prolonged storage.
31 2. Provide appropriate personnel and equipment to receive deliveries.
32 3. Delivery trucks will not be permitted to wait extended periods of time on the Site
33 for personnel or equipment to receive the delivery.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 66 00 - 2
DAP PRODUCT STORAGE AND HANDLING REQUIREMENTS
Page 2 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 4. Deliver products or equipment in manufacturer's original unbroken cartons or other
2 containers designed and constructed to protect the contents from physical or
3 environmental damage.
4 5. Clearly and fully mark and identify as to manufacturer, item and installation
5 location.
6 6. Provide manufacturer's instructions for storage and handling.
7 B. Handling Requirements
8 1. Handle products or equipment in accordance with these Contract Documents and
9 manufacturer’s recommendations and instructions.
10 C. Storage Requirements
11 1. Store materials in accordance with manufacturer’s recommendations and
12 requirements of these Specifications.
13 2. Make necessary provisions for safe storage of materials and equipment.
14 a. Place loose soil materials and materials to be incorporated into Work to prevent
15 damage to any part of Work or existing facilities and to maintain free access at
16 all times to all parts of Work and to utility service company installations in
17 vicinity of Work.
18 3. Keep materials and equipment neatly and compactly stored in locations that will
19 cause minimum inconvenience to other contractors, public travel, adjoining owners,
20 tenants and occupants.
21 a. Arrange storage to provide easy access for inspection.
22 4. Restrict storage to areas available on construction site for storage of material and
23 equipment as shown on Drawings, or approved by City’s Project Representative.
24 5. Provide off-site storage and protection when on-site storage is not adequate.
25 a. Provide addresses of and access to off-site storage locations for inspection by
26 City’s Project Representative.
27 6. Do not use lawns, grass plots or other private property for storage purposes without
28 written permission of owner or other person in possession or control of premises.
29 7. Store in manufacturers’ unopened containers.
30 8. Neatly, safely and compactly stack materials delivered and stored along line of
31 Work to avoid inconvenience and damage to property owners and general public
32 and maintain at least 3 feet from fire hydrant.
33 9. Keep public and private driveways and street crossings open.
34 10. Repair or replace damaged lawns, sidewalks, streets or other improvements to
35 satisfaction of City’s Project Representative.
36 a. Total length which materials may be distributed along route of construction at
37 one time is 1,000 linear feet, unless otherwise approved in writing by City’s
38 Project Representative.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 66 00 - 3
DAP PRODUCT STORAGE AND HANDLING REQUIREMENTS
Page 3 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 1.11 FIELD [SITE] CONDITIONS [NOT USED]
2 1.12 WARRANTY [NOT USED]
3 PART 2 - PRODUCTS [NOT USED]
4 PART 3 - EXECUTION
5 3.1 INSTALLERS [NOT USED]
6 3.2 EXAMINATION [NOT USED]
7 3.3 PREPARATION [NOT USED]
8 3.4 ERECTION [NOT USED]
9 3.5 REPAIR / RESTORATION [NOT USED]
10 3.6 RE-INSTALLATION [NOT USED]
11 3.7 FIELD [OR] SITE QUALITY CONTROL
12 A. Tests and Inspections
13 1. Inspect all products or equipment delivered to the site prior to unloading.
14 B. Non-Conforming Work
15 1. Reject all products or equipment that are damaged, used or in any other way
16 unsatisfactory for use on the project.
17 3.8 SYSTEM STARTUP [NOT USED]
18 3.9 ADJUSTING [NOT USED]
19 3.10 CLEANING [NOT USED]
20 3.11 CLOSEOUT ACTIVITIES [NOT USED]
21 3.12 PROTECTION
22 A. Protect all products or equipment in accordance with manufacturer's written directions.
23 B. Store products or equipment in location to avoid physical damage to items while in
24 storage.
25 C. Protect equipment from exposure to elements and keep thoroughly dry if required by
26 the manufacturer.
27 3.13 MAINTENANCE [NOT USED]
28 3.14 ATTACHMENTS [NOT USED]
29 END OF SECTION
30
Meacham Boulevard at Mercantile Drive
CPN 105417
01 66 00 - 4
DAP PRODUCT STORAGE AND HANDLING REQUIREMENTS
Page 4 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
Revision Log
DATE NAME SUMMARY OF CHANGE
4/7/2014 M.Domenech Revised for DAP application
1
Meacham Boulevard at Mercantile Drive
CPN 105417
01 70 00 - 1
DAP MOBILIZATION AND REMOBILIZATION
Page 1 of 4
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
CPN 105553
SECTION 01 70 00
MOBILIZATION AND REMOBILIZATION
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Mobilization and Demobilization
a. Mobilization
1) Transportation of Contractor’s personnel, equipment, and operating supplies
to the Site
2) Establishment of necessary general facilities for the Contractor’s operation
at the Site
3) Premiums paid for performance and payment bonds
4) Transportation of Contractor’s personnel, equipment, and operating supplies
to another location within the designated Site
5) Relocation of necessary general facilities for the Contractor’s operation
from 1 location to another location on the Site.
b. Demobilization
1) Transportation of Contractor’s personnel, equipment, and operating supplies
away from the Site including disassembly
2) Site Clean-up
3) Removal of all buildings and/or other facilities assembled at the Site for this
Contract
c. Mobilization and Demobilization do not include activities for specific items of
work that are for which payment is provided elsewhere in the contract.
2. Remobilization
a. Remobilization for Suspension of Work specifically required in the Contract
Documents or as required by City includes:
1) Demobilization
a) Transportation of Contractor’s personnel, equipment, and operating
supplies from the Site including disassembly or temporarily securing
equipment, supplies, and other facilities as designated by the Contract
Documents necessary to suspend the Work.
b) Site Clean-up as designated in the Contract Documents
2) Remobilization
a) Transportation of Contractor’s personnel, equipment, and operating
supplies to the Site necessary to resume the Work.
b) Establishment of necessary general facilities for the Contractor’s
operation at the Site necessary to resume the Work.
3) No Payments will be made for:
a) Mobilization and Demobilization from one location to another on the
Site in the normal progress of performing the Work.
b) Stand-by or idle time
c) Lost profits
3. Mobilizations and Demobilization for Miscellaneous Projects
a. Mobilization and Demobilization
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
CPN 105553
01 70 00 - 2
DAP MOBILIZATION AND REMOBILIZATION
Page 2 of 4
1) Mobilization shall consist of the activities and cost on a Work Order basis
necessary for:
a) Transportation of Contractor’s personnel, equipment, and operating
supplies to the Site for the issued Work Order.
b) Establishment of necessary general facilities for the Contractor’s
operation at the Site for the issued Work Order
2) Demobilization shall consist of the activities and cost necessary for:
a) Transportation of Contractor’s personnel, equipment, and operating
supplies from the Site including disassembly for each issued Work
Order
b) Site Clean-up for each issued Work Order
c) Removal of all buildings or other facilities assembled at the Site for
each Work Oder
b. Mobilization and Demobilization do not include activities for specific items of
work for which payment is provided elsewhere in the contract.
4. Emergency Mobilizations and Demobilization for Miscellaneous Projects
a. A Mobilization for Miscellaneous Projects when directed by the City and the
mobilization occurs within 24 hours of the issuance of the Work Order.
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Mobilization and Demobilization
a. Measure
1) This Item is considered subsidiary to the various Items bid.
b. Payment
1) The work performed and materials furnished in accordance with this Item
are subsidiary to the various Items bid and no other compensation will be
allowed.
2. Remobilization for suspension of Work as specifically required in the Contract
Documents
a. Measurement
1) Measurement for this Item shall be per each remobilization performed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
and measured as provided under “Measurement” will be paid for at the unit
price per each “Specified Remobilization” in accordance with Contract
Documents.
c. The price shall include:
1) Demobilization as described in Section 1.1.A.2.a.1)
2) Remobilization as described in Section 1.1.A.2.a.2)
d. No payments will be made for standby, idle time, or lost profits associated this
Item.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
CPN 105553
01 70 00 - 3
DAP MOBILIZATION AND REMOBILIZATION
Page 3 of 4
3. Remobilization for suspension of Work as required by City
a. Measurement and Payment
1) This shall be submitted as a Contract Claim in accordance with Article 10
of Section 00 72 00.
2) No payments will be made for standby, idle time, or lost profits associated
with this Item.
4. Mobilizations and Demobilizations for Miscellaneous Projects
a. Measurement
1) Measurement for this Item shall be for each Mobilization and
Demobilization required by the Contract Documents
b. Payment
1) The Work performed and materials furnished in accordance with this Item
and measured as provided under “Measurement” will be paid for at the unit
price per each “Work Order Mobilization” in accordance with Contract
Documents. Demobilization shall be considered subsidiary to mobilization
and shall not be paid for separately.
c. The price shall include:
1) Mobilization as described in Section 1.1.A.3.a.1)
2) Demobilization as described in Section 1.1.A.3.a.2)
d. No payments will be made for standby, idle time, or lost profits associated this
Item.
5. Emergency Mobilizations and Demobilizations for Miscellaneous Projects
a. Measurement
1) Measurement for this Item shall be for each Mobilization and
Demobilization required by the Contract Documents
b. Payment
1) The Work performed and materials furnished in accordance with this Item
and measured as provided under “Measurement” will be paid for at the unit
price per each “Work Order Emergency Mobilization” in accordance with
Contract Documents. Demobilization shall be considered subsidiary to
mobilization and shall not be paid for separately.
c. The price shall include
1) Mobilization as described in Section 1.1.A.4.a)
2) Demobilization as described in Section 1.1.A.3.a.2)
d. No payments will be made for standby, idle time, or lost profits associated this
Item.
1.3 REFERENCES [NOT USED]
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 SUBMITTALS [NOT USED]
1.6 INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
CPN 105553
01 70 00 - 4
DAP MOBILIZATION AND REMOBILIZATION
Page 4 of 4
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS [NOT USED]
PART 3 - EXECUTION [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
4/7/2014 M.Domenech Revised for DAP application
Meacham Boulevard at Mercantile Drive
CPN 105417
01 71 23 - 1
CONSTRUCTION STAKING AND SURVEY
Page 1 of 8
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 14, 2018
SECTION 01 71 23
CONSTRUCTION STAKING AND SURVEY
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Requirements for construction staking and construction survey
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Construction Staking
a. Measurement
1) Measurement for this Item shall be by lump sum.
b. Payment
1) The work performed and the materials furnished in accordance with this
Item shall be paid for at the lump sum price bid for “Construction Staking”.
2) Payment for “Construction Staking” shall be made in partial payments
prorated by work completed compared to total work included in the lump
sum item.
c. The price bid shall include, but not be limited to the following:
1) Verification of control data provided by City.
2) Placement, maintenance and replacement of required stakes and markings
in the field.
3) Preparation and submittal of construction staking documentation in the
form of “cut sheets” using the City’s standard template.
2. Construction Survey
a. Measurement
1) This Item is considered subsidiary to the various Items bid.
b. Payment
1) The work performed and the materials furnished in accordance with this
Item are subsidiary to the various Items bid and no other compensation will be
allowed.
3. As-Built Survey
a. Measurement
1) Measurement for this Item shall be by lump sum.
b. Payment
1) The work performed and the materials furnished in accordance with this
Item shall be paid for at the lump sum price bid for “As-Built Survey”.
01 71 23 - 2
CONSTRUCTION STAKING AND SURVEY
Page 2 of 8
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 14, 2018
2) Payment for “Construction Staking” shall be made in partial payments
prorated by work completed compared to total work included in the lump sum
item.
c. The price bid shall include, but not be limited to the following::
1) Field measurements and survey shots to identify location of completed
facilities.
2) Documentation and submittal of as-built survey data onto contractor redline
plans and digital survey files.
1.3 REFERENCES
A. Definitions
1. Construction Survey - The survey measurements made prior to or while
construction is in progress to control elevation, horizontal position, dimensions and
configuration of structures/improvements included in the Project Drawings.
2. As-built Survey –The measurements made after the construction of the
improvement features are complete to provide position coordinates for the features
of a project.
3. Construction Staking – The placement of stakes and markings to provide offsets
and elevations to cut and fill in order to locate on the ground the designed
structures/improvements included in the Project Drawings. Construction staking
shall include staking easements and/or right of way if indicated on the plans.
4. Survey “Field Checks” – Measurements made after construction staking is
completed and before construction work begins to ensure that structures marked on
the ground are accurately located per Project Drawings.
B. Technical References
1. City of Fort Worth – Construction Staking Standards (available on City’s Buzzsaw
website) – 01 71 23.16.01_ Attachment A_Survey Staking Standards
2. City of Fort Worth - Standard Survey Data Collector Library (fxl) files (available
on City’s Buzzsaw website).
3. Texas Department of Transportation (TxDOT) Survey Manual, latest revision
4. Texas Society of Professional Land Surveyors (TSPS), Manual of Practice for Land
Surveying in the State of Texas, Category 5
1.4 ADMINISTRATIVE REQUIREMENTS
A. The Contractor’s selection of a surveyor must comply with Texas Government
Code 2254 (qualifications based selection) for this project.
1.5 SUBMITTALS
A. Submittals, if required, shall be in accordance with Section 01 33 00.
B. All submittals shall be received and reviewed by the City prior to delivery of work.
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
A. Field Quality Control Submittals
Meacham Boulevard at Mercantile Drive
CPN 105417
01 71 23 - 3
CONSTRUCTION STAKING AND SURVEY
Page 3 of 8
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 14, 2018
1. Documentation verifying accuracy of field engineering work, including coordinate
conversions if plans do not indicate grid or ground coordinates.
2. Submit “Cut-Sheets” conforming to the standard template provided by the City
(refer to 01 71 23.16.01 – Attachment A – Survey Staking Standards).
1.7 CLOSEOUT SUBMITTALS
B. As-built Redline Drawing Submittal
1. Submit As-Built Survey Redline Drawings documenting the locations/elevations of
constructed improvements signed and sealed by Registered Professional Land
Surveyor (RPLS) responsible for the work (refer to 01 71 23.16.01 – Attachment A
– Survey Staking Standards) .
2. Contractor shall submit the proposed as-built and completed redline drawing
submittal one (1) week prior to scheduling the project final inspection for City
review and comment. Revisions, if necessary, shall be made to the as-built redline
drawings and resubmitted to the City prior to scheduling the construction final
inspection.
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE
A. Construction Staking
1. Construction staking will be performed by the Contractor.
2. Coordination
a. Contact City’s Project Representative at least one week in advance notifying
the City of when Construction Staking is scheduled.
b. It is the Contractor’s responsibility to coordinate staking such that
construction activities are not delayed or negatively impacted.
3. General
a. Contractor is responsible for preserving and maintaining stakes. If City
surveyors are required to re-stake for any reason, the Contractor will be
responsible for costs to perform staking. If in the opinion of the City, a
sufficient number of stakes or markings have been lost, destroyed disturbed or
omitted that the contracted Work cannot take place then the Contractor will be
required to stake or re-stake the deficient areas.
B. Construction Survey
1. Construction Survey will be performed by the Contractor.
2. Coordination
a. Contractor to verify that horizontal and vertical control data established in the
design survey and required for construction survey is available and in place.
3. General
a. Construction survey will be performed in order to construct the work shown
on the Construction Drawings and specified in the Contract Documents.
b. For construction methods other than open cut, the Contractor shall perform
construction survey and verify control data including, but not limited to, the
following:
1) Verification that established benchmarks and control are accurate.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 71 23 - 4
CONSTRUCTION STAKING AND SURVEY
Page 4 of 8
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 14, 2018
2) Use of Benchmarks to furnish and maintain all reference lines and grades
for tunneling.
3) Use of line and grades to establish the location of the pipe.
4) Submit to the City copies of field notesused to establish all lines and
grades, if requested, and allow the City to check guidance system setup prior
to beginning each tunneling drive.
5) Provide access for the City, if requested, to verify the guidance system and
the line and grade of the carrier pipe.
6) The Contractor remains fully responsible for the accuracy of the work and
correction of it, as required.
7) Monitor line and grade continuously during construction.
8) Record deviation with respect to design line and grade once at each pipe
joint and submit daily records to the City.
9) If the installation does not meet the specified tolerances (as outlined in
Sections 33 05 23 and/or 33 05 24), immediately notify the City and correct
the installation in accordance with the Contract Documents.
C. As-Built Survey
1. Required As-Built Survey will be performed by the Contractor.
2. Coordination
a. Contractor is to coordinate with City to confirm which features require as-
built surveying.
b. It is the Contractor’s responsibility to coordinate the as-built survey and
required measurements for items that are to be buried such that construction
activities are not delayed or negatively impacted.
c. For sewer mains and water mains 12” and under in diameter, it is acceptable
to physically measure depth and mark the location during the progress of
construction and take as-built survey after the facility has been buried. The
Contractor is responsible for the quality control needed to ensure accuracy.
3. General
a. The Contractor shall provide as-built survey including the elevation and
location (and provide written documentation to the City) of construction
features during the progress of the construction including the following:
1) Water Lines
a) Top of pipe elevations and coordinates for waterlines at the following
locations:
(1) Minimum every 250 linear feet, including
(2) Horizontal and vertical points of inflection, curvature,
etc.
(3) Fire line tee
(4) Plugs, stub-outs, dead-end lines
(5) Casing pipe (each end) and all buried fittings
2) Sanitary Sewer
a) Top of pipe elevations and coordinates for force mains and siphon
sanitary sewer lines (non-gravity facilities) at the following locations:
(1) Minimum every 250 linear feet and any buried fittings
(2) Horizontal and vertical points of inflection, curvature,
etc.
3) Stormwater – Not Applicable
Meacham Boulevard at Mercantile Drive
CPN 105417
01 74 23 - 1
DAP CLEANING
Page 1 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 SECTION 01 74 23
2 CLEANING
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Intermediate and final cleaning for Work not including special cleaning of closed
7 systems specified elsewhere
8 B. Deviations from this City of Fort Worth Standard Specification
9 1. None.
10 C. Related Specification Sections include, but are not necessarily limited to:
11 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
12 2. Division 1 – General Requirements
13 3. Section 32 92 13 – Hydro-Mulching, Seeding and Sodding
14 1.2 PRICE AND PAYMENT PROCEDURES
15 A. Measurement and Payment
16 1. Work associated with this Item is considered subsidiary to the various Items bid.
17 No separate payment will be allowed for this Item.
18 1.3 REFERENCES [NOT USED]
19 1.4 ADMINISTRATIVE REQUIREMENTS
20 A. Scheduling
21 1. Schedule cleaning operations so that dust and other contaminants disturbed by
22 cleaning process will not fall on newly painted surfaces.
23 2. Schedule final cleaning upon completion of Work and immediately prior to final
24 inspection.
25 1.5 SUBMITTALS [NOT USED]
26 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
27 1.7 CLOSEOUT SUBMITTALS [NOT USED]
28 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
29 1.9 QUALITY ASSURANCE [NOT USED]
30 1.10 STORAGE, AND HANDLING
31 A. Storage and Handling Requirements
32 1. Store cleaning products and cleaning wastes in containers specifically designed for
33 those materials.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 74 23 - 2
DAP CLEANING
Page 2 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 1.11 FIELD [SITE] CONDITIONS [NOT USED]
2 1.12 WARRANTY [NOT USED]
3 PART 2 - PRODUCTS
4 2.1 OWNER-FURNISHED [OR] OWNER-SUPPLIEDPRODUCTS [NOT USED]
5 2.2 MATERIALS
6 A. Cleaning Agents
7 1. Compatible with surface being cleaned
8 2. New and uncontaminated
9 3. For manufactured surfaces
10 a. Material recommended by manufacturer
11 2.3 ACCESSORIES [NOT USED]
12 2.4 SOURCE QUALITY CONTROL [NOT USED]
13 PART 3 - EXECUTION
14 3.1 INSTALLERS [NOT USED]
15 3.2 EXAMINATION [NOT USED]
16 3.3 PREPARATION [NOT USED]
17 3.4 APPLICATION [NOT USED]
18 3.5 REPAIR / RESTORATION [NOT USED]
19 3.6 RE-INSTALLATION [NOT USED]
20 3.7 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
21 3.8 SYSTEM STARTUP [NOT USED]
22 3.9 ADJUSTING [NOT USED]
23 3.10 CLEANING
24 A. General
25 1. Prevent accumulation of wastes that create hazardous conditions.
26 2. Conduct cleaning and disposal operations to comply with laws and safety orders of
27 governing authorities.
28 3. Do not dispose of volatile wastes such as mineral spirits, oil or paint thinner in
29 storm or sanitary drains or sewers.
30 4. Dispose of degradable debris at an approved solid waste disposal site.
31 5. Dispose of nondegradable debris at an approved solid waste disposal site or in an
32 alternate manner approved by City and regulatory agencies.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 74 23 - 3
DAP CLEANING
Page 3 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 6. Handle materials in a controlled manner with as few handlings as possible.
2 7. Thoroughly clean, sweep, wash and polish all Work and equipment associated with
3 this project.
4 8. Remove all signs of temporary construction and activities incidental to construction
5 of required permanent Work.
6 9. If project is not cleaned to the satisfaction of the City, the City reserves the right to
7 have the cleaning completed at the expense of the Contractor.
8 10. Do not burn on-site.
9 B. Intermediate Cleaning during Construction
10 1. Keep Work areas clean so as not to hinder health, safety or convenience of
11 personnel in existing facility operations.
12 2. At maximum weekly intervals, dispose of waste materials, debris and rubbish.
13 3. Confine construction debris daily in strategically located container(s):
14 a. Cover to prevent blowing by wind
15 b. Store debris away from construction or operational activities
16 c. Haul from site at a minimum of once per week
17 4. Vacuum clean interior areas when ready to receive finish painting.
18 a. Continue vacuum cleaning on an as-needed basis, until Final Acceptance.
19 5. Prior to storm events, thoroughly clean site of all loose or unsecured items, which
20 may become airborne or transported by flowing water during the storm.
21 C. Exterior (Site or Right of Way) Final Cleaning
22 1. Remove trash and debris containers from site.
23 a. Re-seed areas disturbed by location of trash and debris containers in accordance
24 with Section 32 92 13.
25 2. Sweep roadway to remove all rocks, pieces of asphalt, concrete or any other object
26 that may hinder or disrupt the flow of traffic along the roadway.
27 3. Clean any interior areas including, but not limited to, vaults, manholes, structures,
28 junction boxes and inlets.
29 4. If no longer required for maintenance of erosion facilities, and upon approval by
30 City, remove erosion control from site.
31 5. Clean signs, lights, signals, etc.
32 3.11 CLOSEOUT ACTIVITIES [NOT USED]
33 3.12 PROTECTION [NOT USED]
34 3.13 MAINTENANCE [NOT USED]
35 3.14 ATTACHMENTS [NOT USED]
36
37
38
39
40
Meacham Boulevard at Mercantile Drive
CPN 105417
01 74 23 - 4
DAP CLEANING
Page 4 of 4
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 END OF SECTION
2
Revision Log
DATE NAME SUMMARY OF CHANGE
4/7/2014 M.Domenech Revised for DAP application
3
Meacham Boulevard at Mercantile Drive
CPN 105417
01 77 19 - 1
DAP CLOSEOUT REQUIREMENTS
Page 1 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 SECTION 01 77 19
2 CLOSEOUT REQUIREMENTS
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. The procedure for closing out a contract
7 B. Deviations from this City of Fort Worth Standard Specification
8 1. None.
9 C. Related Specification Sections include, but are not necessarily limited to:
10 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
11 2. Division 1 – General Requirements
12 1.2 PRICE AND PAYMENT PROCEDURES
13 A. Measurement and Payment
14 1. Work associated with this Item is considered subsidiary to the various Items bid.
15 No separate payment will be allowed for this Item.
16 1.3 REFERENCES [NOT USED]
17 1.4 ADMINISTRATIVE REQUIREMENTS
18 A. Guarantees, Bonds and Affidavits
19 1. No application for final payment will be accepted until all guarantees, bonds,
20 certificates, licenses and affidavits required for Work or equipment as specified are
21 satisfactorily filed with the City.
22 B. Release of Liens or Claims
23 1. No application for final payment will be accepted until satisfactory evidence of
24 release of liens has been submitted to the City.
25 1.5 SUBMITTALS
26 A. Submit all required documentation to City’s Project Representative.
Meacham Boulevard at Mercantile Drive
CPN 105417
01 77 19 - 2
DAP CLOSEOUT REQUIREMENTS
Page 2 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 1.6 INFORMATIONAL SUBMITTALS [NOT USED]
2 1.7 CLOSEOUT SUBMITTALS [NOT USED]
3 PART 2 - PRODUCTS [NOT USED]
4 PART 3 - EXECUTION
5 3.1 INSTALLERS [NOT USED]
6 3.2 EXAMINATION [NOT USED]
7 3.3 PREPARATION [NOT USED]
8 3.4 CLOSEOUT PROCEDURE
9 A. Prior to requesting Final Inspection, submit:
10 1. Project Record Documents in accordance with Section 01 78 39
11 2. Operation and Maintenance Data, if required, in accordance with Section 01 78 23
12 B. Prior to requesting Final Inspection, perform final cleaning in accordance with Section
13 01 74 23.
14 C. Final Inspection
15 1. After final cleaning, provide notice to the City Project Representative that the Work
16 is completed.
17 a. The City will make an initial Final Inspection with the Contractor present.
18 b. Upon completion of this inspection, the City will notify the Contractor, in
19 writing within 10 business days, of any particulars in which this inspection
20 reveals that the Work is defective or incomplete.
21 2. Upon receiving written notice from the City, immediately undertake the Work
22 required to remedy deficiencies and complete the Work to the satisfaction of the
23 City.
24 3. Upon completion of Work associated with the items listed in the City's written
25 notice, inform the City, that the required Work has been completed. Upon receipt
26 of this notice, the City, in the presence of the Contractor, will make a subsequent
27 Final Inspection of the project.
28 4. Provide all special accessories required to place each item of equipment in full
29 operation. These special accessory items include, but are not limited to:
30 a. Specified spare parts
31 b. Adequate oil and grease as required for the first lubrication of the equipment
32 c. Initial fill up of all chemical tanks and fuel tanks
33 d. Light bulbs
34 e. Fuses
35 f. Vault keys
36 g. Handwheels
37 h. Other expendable items as required for initial start-up and operation of all
38 equipment
39 D. Notice of Project Completion
Meacham Boulevard at Mercantile Drive
CPN 105417
01 77 19 - 3
DAP CLOSEOUT REQUIREMENTS
Page 3 of 3
CITY OF FORT WORTH Birchman Office Space
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – Developer Awarded Projects CPN 105553
Revised April 7, 2014
1 1. Once the City Project Representative finds the Work subsequent to Final Inspection
2 to be satisfactory, the City will issue a Notice of Project Completion (Green Sheet).
3 E. Supporting Documentation
4 1. Coordinate with the City Project Representative to complete the following
5 additional forms:
6 a. Final Payment Request
7 b. Statement of Contract Time
8 c. Affidavit of Payment and Release of Liens
9 d. Consent of Surety to Final Payment
10 e. Pipe Report (if required)
11 f. Contractor’s Evaluation of City
12 g. Performance Evaluation of Contractor
13 F. Letter of Final Acceptance
14 1. Upon review and acceptance of Notice of Project Completion and Supporting
15 Documentation, in accordance with General Conditions, City will issue Letter of
16 Final Acceptance and release the Final Payment Request for payment.
17 3.5 REPAIR / RESTORATION [NOT USED]
18 3.6 RE-INSTALLATION [NOT USED]
19 3.7 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
20 3.8 SYSTEM STARTUP [NOT USED]
21 3.9 ADJUSTING [NOT USED]
22 3.10 CLEANING [NOT USED]
23 3.11 CLOSEOUT ACTIVITIES [NOT USED]
24 3.12 PROTECTION [NOT USED]
25 3.13 MAINTENANCE [NOT USED]
26 3.14 ATTACHMENTS [NOT USED]
27 END OF SECTION
28
Revision Log
DATE NAME SUMMARY OF CHANGE
4/7/2014 M.Domenech Revised for DAP application
29
Meacham Boulevard at Mercantile Drive
CPN 105417
01 78 23 - 1
DAP OPERATION AND MAINTENANCE DATA
Page 1 of 5
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
SECTION 01 78 23
OPERATION AND MAINTENANCE DATA
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Product data and related information appropriate for City's maintenance and
operation of products furnished under Contract
2. Such products may include, but are not limited to:
a. Traffic Controllers
b. Irrigation Controllers (to be operated by the City)
c. Butterfly Valves
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Work associated with this Item is considered subsidiary to the various Items bid.
No separate payment will be allowed for this Item.
1.3 REFERENCES [NOT USED]
1.4 ADMINISTRATIVE REQUIREMENTS
A. Schedule
1. Submit manuals in final form to the City within 30 calendar days of product
shipment to the project site.
1.5 SUBMITTALS
A. Submittals shall be in accordance with Section 01 33 00. All submittals shall be
approved by the City prior to delivery.
1.6 INFORMATIONAL SUBMITTALS
A. Submittal Form
1. Prepare data in form of an instructional manual for use by City personnel.
2. Format
a. Size: 8 ½ inches x 11 inches
b. Paper
1) 40 pound minimum, white, for typed pages
2) Holes reinforced with plastic, cloth or metal
c. Text: Manufacturer’s printed data, or neatly typewritten
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
01 78 23 - 2
DAP OPERATION AND MAINTENANCE DATA
Page 2 of 5
d. Drawings
1) Provide reinforced punched binder tab, bind in with text
2) Reduce larger drawings and fold to size of text pages.
e. Provide fly-leaf for each separate product, or each piece of operating
equipment.
1) Provide typed description of product, and major component parts of
equipment.
2) Provide indexed tabs.
f. Cover
1) Identify each volume with typed or printed title "OPERATING AND
MAINTENANCE INSTRUCTIONS".
2) List:
a) Title of Project
b) Identity of separate structure as applicable
c) Identity of general subject matter covered in the manual
3. Binders
a. Commercial quality 3-ring binders with durable and cleanable plastic covers
b. When multiple binders are used, correlate the data into related consistent
groupings.
4. If available, provide an electronic form of the O&M Manual.
B. Manual Content
1. Neatly typewritten table of contents for each volume, arranged in systematic order
a. Contractor, name of responsible principal, address and telephone number
b. A list of each product required to be included, indexed to content of the volume
c. List, with each product:
1) The name, address and telephone number of the subcontractor or installer
2) A list of each product required to be included, indexed to content of the
volume
3) Identify area of responsibility of each
4) Local source of supply for parts and replacement
d. Identify each product by product name and other identifying symbols as set
forth in Contract Documents.
2. Product Data
a. Include only those sheets which are pertinent to the specific product.
b. Annotate each sheet to:
1) Clearly identify specific product or part installed
2) Clearly identify data applicable to installation
3) Delete references to inapplicable information
3. Drawings
a. Supplement product data with drawings as necessary to clearly illustrate:
1) Relations of component parts of equipment and systems
2) Control and flow diagrams
b. Coordinate drawings with information in Project Record Documents to assure
correct illustration of completed installation.
c. Do not use Project Record Drawings as maintenance drawings.
4. Written text, as required to supplement product data for the particular installation:
a. Organize in consistent format under separate headings for different procedures.
b. Provide logical sequence of instructions of each procedure.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
01 78 23 - 3
DAP OPERATION AND MAINTENANCE DATA
Page 3 of 5
5. Copy of each warranty, bond and service contract issued
a. Provide information sheet for City personnel giving:
1) Proper procedures in event of failure
2) Instances which might affect validity of warranties or bonds
C. Manual for Materials and Finishes
1. Submit 5 copies of complete manual in final form.
2. Content, for architectural products, applied materials and finishes:
a. Manufacturer's data, giving full information on products
1) Catalog number, size, composition
2) Color and texture designations
3) Information required for reordering special manufactured products
b. Instructions for care and maintenance
1) Manufacturer's recommendation for types of cleaning agents and methods
2) Cautions against cleaning agents and methods which are detrimental to
product
3) Recommended schedule for cleaning and maintenance
3. Content, for moisture protection and weather exposure products:
a. Manufacturer's data, giving full information on products
1) Applicable standards
2) Chemical composition
3) Details of installation
b. Instructions for inspection, maintenance and repair
D. Manual for Equipment and Systems
1. Submit 5 copies of complete manual in final form.
2. Content, for each unit of equipment and system, as appropriate:
a. Description of unit and component parts
1) Function, normal operating characteristics and limiting conditions
2) Performance curves, engineering data and tests
3) Complete nomenclature and commercial number of replaceable parts
b. Operating procedures
1) Start-up, break-in, routine and normal operating instructions
2) Regulation, control, stopping, shut-down and emergency instructions
3) Summer and winter operating instructions
4) Special operating instructions
c. Maintenance procedures
1) Routine operations
2) Guide to "trouble shooting"
3) Disassembly, repair and reassembly
4) Alignment, adjusting and checking
d. Servicing and lubrication schedule
1) List of lubricants required
e. Manufacturer's printed operating and maintenance instructions
f. Description of sequence of operation by control manufacturer
1) Predicted life of parts subject to wear
2) Items recommended to be stocked as spare parts
g. As installed control diagrams by controls manufacturer
h. Each contractor's coordination drawings
1) As installed color coded piping diagrams
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
01 78 23 - 4
DAP OPERATION AND MAINTENANCE DATA
Page 4 of 5
i. Charts of valve tag numbers, with location and function of each valve
j. List of original manufacturer's spare parts, manufacturer's current prices, and
recommended quantities to be maintained in storage
k. Other data as required under pertinent Sections of Specifications
3. Content, for each electric and electronic system, as appropriate:
a. Description of system and component parts
1) Function, normal operating characteristics, and limiting conditions
2) Performance curves, engineering data and tests
3) Complete nomenclature and commercial number of replaceable parts
b. Circuit directories of panelboards
1) Electrical service
2) Controls
3) Communications
c. As installed color coded wiring diagrams
d. Operating procedures
1) Routine and normal operating instructions
2) Sequences required
3) Special operating instructions
e. Maintenance procedures
1) Routine operations
2) Guide to "trouble shooting"
3) Disassembly, repair and reassembly
4) Adjustment and checking
f. Manufacturer's printed operating and maintenance instructions
g. List of original manufacturer's spare parts, manufacturer's current prices, and
recommended quantities to be maintained in storage
h. Other data as required under pertinent Sections of Specifications
4. Prepare and include additional data when the need for such data becomes apparent
during instruction of City's personnel.
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE
A. Provide operation and maintenance data by personnel with the following criteria:
1. Trained and experienced in maintenance and operation of described products
2. Skilled as technical writer to the extent required to communicate essential data
3. Skilled as draftsman competent to prepare required drawings
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
01 78 23 - 5
DAP OPERATION AND MAINTENANCE DATA
Page 5 of 5
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS [NOT USED]
PART 3 - EXECUTION [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
8/31/2012 D. Johnson 1.5.A.1 – title of section removed
4/7/2014 M.Domenech Revised for DAP Application
Meacham Boulevard at Mercantile Drive
CPN 105417
01 78 39 - 1
DAP PROJECT RECORD DOCUMENTS
Page 1 of 4
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
SECTION 01 78 39
PROJECT RECORD DOCUMENTS
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Work associated with the documenting the project and recording changes to project
documents, including:
a. Record Drawings
b. Water Meter Service Reports
c. Sanitary Sewer Service Reports
d. Large Water Meter Reports
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Work associated with this Item is considered subsidiary to the various Items bid.
No separate payment will be allowed for this Item.
1.3 REFERENCES [NOT USED]
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 SUBMITTALS
A. Prior to submitting a request for Final Inspection, deliver Project Record Documents to
City’s Project Representative.
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE
A. Accuracy of Records
1. Thoroughly coordinate changes within the Record Documents, making adequate
and proper entries on each page of Specifications and each sheet of Drawings and
other Documents where such entry is required to show the change properly.
2. Accuracy of records shall be such that future search for items shown in the Contract
Documents may rely reasonably on information obtained from the approved Project
Record Documents.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
01 78 39 - 2
DAP PROJECT RECORD DOCUMENTS
Page 2 of 4
3. To facilitate accuracy of records, make entries within 24 hours after receipt of
information that the change has occurred.
4. Provide factual information regarding all aspects of the Work, both concealed and
visible, to enable future modification of the Work to proceed without lengthy and
expensive site measurement, investigation and examination.
1.10 STORAGE AND HANDLING
A. Storage and Handling Requirements
1. Maintain the job set of Record Documents completely protected from deterioration
and from loss and damage until completion of the Work and transfer of all recorded
data to the final Project Record Documents.
2. In the event of loss of recorded data, use means necessary to again secure the data
to the City's approval.
a. In such case, provide replacements to the standards originally required by the
Contract Documents.
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS
2.1 OWNER-FURNISHED [OR] OWNER-SUPPLIED PRODUCTS [NOT USED]
2.2 RECORD DOCUMENTS
A. Job set
1. Promptly following receipt of the Notice to Proceed, secure from the City, at no
charge to the Contractor, 1 complete set of all Documents comprising the Contract.
B. Final Record Documents
1. At a time nearing the completion of the Work and prior to Final Inspection, provide
the City 1 complete set of all Final Record Drawings in the Contract.
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL [NOT USED]
PART 3 - EXECUTION
3.1 INSTALLERS [NOT USED]
3.2 EXAMINATION [NOT USED]
3.3 PREPARATION [NOT USED]
3.4 MAINTENANCE DOCUMENTS
A. Maintenance of Job Set
1. Immediately upon receipt of the job set, identify each of the Documents with the
title, "RECORD DOCUMENTS - JOB SET".
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
01 78 39 - 3
DAP PROJECT RECORD DOCUMENTS
Page 3 of 4
2. Preservation
a. Considering the Contract completion time, the probable number of occasions
upon which the job set must be taken out for new entries and for examination,
and the conditions under which these activities will be performed, devise a
suitable method for protecting the job set.
b. Do not use the job set for any purpose except entry of new data and for review
by the City, until start of transfer of data to final Project Record Documents.
c. Maintain the job set at the site of work.
3. Coordination with Construction Survey
a. At a minimum clearly mark any deviations from Contract Documents
associated with installation of the infrastructure.
4. Making entries on Drawings
a. Record any deviations from Contract Documents.
b. Use an erasable colored pencil (not ink or indelible pencil), clearly describe the
change by graphic line and note as required.
c. Date all entries.
d. Call attention to the entry by a "cloud" drawn around the area or areas affected.
e. In the event of overlapping changes, use different colors for the overlapping
changes.
5. Conversion of schematic layouts
a. In some cases on the Drawings, arrangements of conduits, circuits, piping,
ducts, and similar items, are shown schematically and are not intended to
portray precise physical layout.
1) Final physical arrangement is determined by the Contractor, subject to the
City's approval.
2) However, design of future modifications of the facility may require
accurate information as to the final physical layout of items which are
shown only schematically on the Drawings.
b. Show on the job set of Record Drawings, by dimension accurate to within 1
inch, the centerline of each run of items.
1) Final physical arrangement is determined by the Contractor, subject to the
City's approval.
2) Show, by symbol or note, the vertical location of the Item ("under slab", "in
ceiling plenum", "exposed", and the like).
3) Make all identification sufficiently descriptive that it may be related
reliably to the Specifications.
c. The City may waive the requirements for conversion of schematic layouts
where, in the City's judgment, conversion serves no useful purpose. However,
do not rely upon waivers being issued except as specifically issued in writing
by the City.
B. Final Project Record Documents
1. Transfer of data to Drawings
a. Carefully transfer change data shown on the job set of Record Drawings to the
corresponding final documents, coordinating the changes as required.
b. Clearly indicate at each affected detail and other Drawing a full description of
changes made during construction, and the actual location of items.
c. Call attention to each entry by drawing a "cloud" around the area or areas
affected.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS – DEVELOPER AWARDED PROJECTS
Revised April 7, 2014
Birchman Office Space
Project 105553
01 78 39 - 4
DAP PROJECT RECORD DOCUMENTS
Page 4 of 4
d. Make changes neatly, consistently and with the proper media to assure
longevity and clear reproduction.
2. Transfer of data to other Documents
a. If the Documents, other than Drawings, have been kept clean during progress of
the Work, and if entries thereon have been orderly to the approval of the City,
the job set of those Documents, other than Drawings, will be accepted as final
Record Documents.
b. If any such Document is not so approved by the City, secure a new copy of that
Document from the City at the City's usual charge for reproduction and
handling, and carefully transfer the change data to the new copy to the approval
of the City.
3.5 REPAIR / RESTORATION [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING [NOT USED]
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
4/7/2014 M.Domenech Revised for DAP Application
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 13 - 1
SELECTIVE SITE DEMOLITION
Page 1 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised March 11, 2022
SECTION 02 41 13 1
SELECTIVE SITE DEMOLITION 2
PART 1 - GENERAL 3
1.1 SUMMARY 4
A. Section Includes : 5
1. Removing sidewalks and steps 6
2. Removing ADA ramps , landings , and detectable warning surfaces 7
3. Removing driveways 8
4. Removing fences 9
5. Removing guardrail 10
6. Removing retaining walls (less than 4 feet tall) 11
7. Removing mailboxes 12
8. Removing rip rap 13
9. Removing miscellaneous concrete structures including porches and foundations 14
10. Disposal of removed materials 15
B. Deviations this f rom City of Fort Worth Standard Specification 16
1. None. 17
C. Related Specification Sections include, but are not necessarily limited to: 18
1. Division 0 – Bidding Requirements, Contract Forms, and Conditions of the 19
Contract 20
2. Division 1 – General Requirements 21
3. Section 31 23 23 – Borrow 22
1.2 PRICE AND PAYMENT PROCEDURES 23
A. Measurement and Payment 24
1. Measurement 25 a. Remove Sidewalk: Measure by square foot. 26
b. Remove Steps: measure by the square foot as seen in the plan view only. 27
c. Remove ADA Ramp: measure by each. 28
d. Remove Detectable Warning Surface: measure by each 29
e. Remove Driveway: measure by the square foot by type. 30 f. Remove F ence: measure by the linear foot. 31
g. Remove Guardrail: measure by the linear foot along the face of the rail in place 32
including metal beam guard fence transitions and single guard rail terminal 33
sections from the center of end posts. 34
h. Remove Retaining Wall (less than 4 feet tall): measure by the linear foot 35
i. Remove Mailbox, Remove and Replace Mailbox, and Relocate Mailbox: 36
measure by each. 37
j. Remove Rip Rap: measure by the square foot. 38
k. Remove Miscellaneous Concrete Structure: measure by the lump sum. 39
2. Payment 40
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 13 - 2
SELECTIVE SITE DEMOLITION
Page 2 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised March 11, 2022
a. Remove Sidewalk: full compensation for saw cutting, removal, hauling, 1 disposal, tools, equipment, labor and incidentals needed to execute work. 2
Sidewalk adjacent to or attached to retaining wall (including sidewalk that acts 3
as a wall footing) shall be paid as sidewalk removal. For utility projects, this 4
Item shall be considered subsidiary to the trench and no other compensation 5
will be allowed. 6 b. Remove Steps: full compensation for saw cutting, removal, hauling, disposal, 7
tools, equipment, labor and incidentals needed to execute work. For utility 8
projects, this Item shall be considered subsidiary to the trench and no other 9
compensation will be allowed. 10
c. Remove ADA Ramp and landing: full compensation for saw cutting, removal, 11
hauling, disposal, tools, equipment, labor and incidentals needed to execute 12
work. Work includes ramp landing removal. For utility projects, this Item shall 13
be considered subsidiary to the trench and no other compensation will be 14
allowe d. 15
d. Remove Detectable Warning Surface: full compensation for removal, hauling, 16
disposal, tools, equipment, labor and incidentals needed to execute work. Work 17 includes detectable warning surface removal from ramp. 18
e. Remove Driveway: full compensation for saw cutting, removal, hauling, 19
disposal, tools, equipment, labor and incidentals needed to remove improved 20
driveway by type. For utility projects, this Item shall be considered subsidiary 21
to the trench and no other compensation will be allowed. 22
f. Remove Fence: full compensation for removal, hauling, disposal, tools, 23
equipment, labor and incidentals needed to remove fence. For utility projects, 24
this Item shall be considered subsidiary to the trench and no other 25
compensation will be allowed. 26
g. Remove Guardrail: full compensation for removing materials, loading, hauling, 27 unloading, and storing or disposal; furnishing backfill material; backfilling the 28
postholes; and equipment, labor, tools, and incidentals. For utility projects, this 29
Item shall be considered subsidiary to the trench and no other compensation 30
will be allowed. 31
h. Remove Retaining Wall (less than 4 feet tall): full compensation for saw 32
cutting, removal, hauling, disposal, tools, equipment, labor and incidentals 33
needed to execute work. Sidewalk adjacent to or attached to retaining wall 34
(including sidewalk that acts as a wall footing) shall be paid as sidewalk 35
removal. For utility projects, this Item shall be considered subsidiary to the 36
trench and no other compensation will be allowed. 37
i. Remove Mailbox: full compensation for removal, hauling, disposal, tools, 38 equipment, labor and incidentals needed to execute work. For utility projects, 39
this Item shall be considered subsidiary to the trench and no other 40
compensation will be allowed. 41
j. Remove and Replace Mailbox and Relocate Mailbox: full compensation for 42
removal, hauling, disposal or relocation, and installation or construction of 43 replacement, tools, equipment, labor and incidentals needed to execute work for 44
different types: traditional pipe and mailbox or brick mailbox, at equal or better 45
condition on completion 46
k. Remove Rip Rap: full compensation for saw cutting, removal, hauling, 47
disposal, tools, equipment, labor and incidentals needed to execute work. For 48
utility projects, this Item shall be considered subsidiary to the trench and no 49
other compensation will be allowed. 50
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 13 - 3
SELECTIVE SITE DEMOLITION
Page 3 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised March 11, 2022
l. Remove Miscellaneous Concrete Structure: full compensation for saw cutting, 1 removal, hauling, disposal, tools, equipment, labor and incidentals needed to 2
execute work. For utility projects, this Item shall be considered subsidiary to 3
the trench and no other compensation will be allowed. 4
1.3 REFERENCES 5
A. Definitions 6
1. Improved Driveway: Driveway constructed of concrete, asphalt paving or brick unit 7
pavers. 8
1.4 ADMINISTRATIVE REQUI REMENTS [NOT USED] 9
1.5 SUBMITTALS [NOT USED] 10
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTA LS [NOT USED] 11
1.7 CLOSEOUT SUBMITTALS [NOT USED] 12
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED] 13
1.9 QUALITY ASSURANCE [NOT USED] 14
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED] 15
1.11 FIELD [SITE] CONDITI ONS [NOT USED] 16
1.12 WARRANTY [NOT USED] 17
PART 2 - PRODUCTS 18
2.1 OWNER -FURNISHED PRODUCTS [NOT USED] 19
2.2 MATERIALS 20
A. Fill Material: See Section 31 23 23 . 21
2.3 ACCESSORIES [NOT USED] 22
2.4 SOURCE QUALITY CONTROL [NOT USED] 23
PART 3 - EXECUTION 24
3.1 INSTALLERS [NOT USED ] 25
3.2 EXAMINATION [NOT USED] 26
3.3 PREPARATION [NOT USED] 27
3.4 REMOVAL 28
A. Remove Sidewalk 29
1. Remove sidewalk to nearest existing dummy, expansion or construction joint. 30
2. Sawcut when removing to nearest joint is not practical. See 3.4.K. 31
B. Remove Steps 32
1. Remove step to nearest existing dummy, expansion or construction joint. 33
2. Sawcut when removing to nearest joint is not practical. See 3.4.K. 34
C. Remove ADA Ramp 35
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 13 - 4
SELECTIVE SITE DEMOLITION
Page 4 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised March 11, 2022
1. Sawcut existing curb and gutter and pavement prior to wheel chair ramp removal. 1 See 3.4.K. 2
2. Remove ramp to nearest existing dummy, expansion or construction joint on 3
existing sidewalk. 4
D. Remove Detectable Warning Surface 5
1. Remove old detectable warning surface from ramp, including either pavers or 6 prefabricated panels 7
2. Clean any glue or residue from the surface 8
E. Remove Drive way 9
1. Sawcut existing drive, curb and gutter and pavement prior to drive removal. See 10
3.4.K. 11
2. Remove drive to nearest existing dummy, expansion or construction joint. 12
3. Sawcut when removing to nearest joint is not practical. See 3.4.K. 13
4. Remove adjacent sidewalk to nearest existing dummy, expansion or construction 14
joint on exis ting sidewalk. 15
F. Remove Fence 16
1. Remove all fence components above and below ground and backfill with acceptable 17
fill material. 18
2. Use caution in removing and salvaging fence materials. 19
3. Salvaged materials may be used to reconstruct fence as approved by City or as 20
shown on Drawings . 21
4. Contractor responsible for keeping animals (livestock, pets, etc.) within the fenced 22
areas during construction operation and while removing fences. 23
G. Remove Guardrail 24
1. Remove rail elements in original lengths. 25
2. Remove fittings from the posts and the metal rail and then pull the posts. 26
3. Do not mar or damage salvageable materials during removal. 27
4. Completely remove posts and any concrete surrounding the posts. 28
5. Furnish backfill material and backfill the hole with material equal in composition 29
and density to the surrounding soil unless otherwise directed. 30
6. Cut off or bend down eyebolts anchored to the dead man to an elevation at least 1-31 foot below the new subgrade elevation and leave in place along with the dead man. 32
H. Remove Retaining Wall (le ss than 4 feet tall) 33
1. Remove wall to nearest existing joint. 34
2. Sawcut when removing to nearest joint is not practical. See 3.4.K. 35
3. Removal includes all components of the retaining wall including footings. 36
4. Sidewalk adjacent to or attached to retaining wall: See 3.4.A 37
I. Remove Mailbox 38
1. Salvage existing materials for reuse. Mailbox materials m ay need to be used for 39
reconstruction. 40
J. Remove Rip Rap 41
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 13 - 5
SELECTIVE SITE DEMOLITION
Page 5 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised March 11, 2022
1. Remove rip rap to nearest existing dummy, expansion or construction joint. 1
2. Sawcut when removing to nearest joint is not practical. See 3.4.K. 2
K. Remove Miscellaneous C oncrete Structure 3
1. Remove portions of miscellaneous concrete structures including foundations and 4
slabs that do not interfere with proposed construction to 2 feet below the finished 5
ground line. 6
2. Cut reinforcement close to the portion of the concrete to remain in place. 7
3. Break or perforate the bottom of structures to remain to prevent the entrapment of 8
water. 9
L. Sawcut 10
1. Sawing Equipment 11
a. Power -driven 12
b. Manufactured for the purpose of sawing pavement 13
c. In good operating condition 14
d. Shall not spall or fracture the pavement to the removal area 15
2. Sawcut perpendicular to the surface completely through existing pavement. 16
3.5 REPAIR [NOT USED] 17
3.6 RE-INSTALLATION [NOT USED] 18
3.7 SITE QUALITY CONTROL [NOT USED] 19
3.8 SYSTEM STARTUP [NOT USED] 20
3.9 ADJUSTING [NOT USED] 21
3.10 CLEANING [NOT USED] 22
3.11 CLOSEOUT ACTIVITIES [NOT USED] 23
3.12 PROTECTION [NOT USED] 24
3.13 MAINTENANCE [NOT USED] 25
3.14 ATTACHMENTS [NOT USED] 26
END OF SECTION 27
28
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 D. Johnson 1.2.A.2. Modified Payment - Items will be subsidiary to trench on utility projects
3/11/2022 M Owen /S Hobbs Added measurement and payment for Remove and Replace Mailbox and Relocate
Mailbox and Remove Detectable Warning Surface
29
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 15 - 1
PAVING REMOVAL
Page 1 of 6
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 2, 2016
SECTION 02 41 15
PAVING REMOVAL
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Removing concrete paving, asphalt paving and brick paving
2. Removing concrete curb and gutter
3. Removing concrete valley gutter
4. Milling roadway paving
5. Pulverization of existing pavement
6. Disposal of removed materials
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 - Bidding Requirements, Contract Forms, and Conditions of the Contract
2. Division 1 - General Requirements
3. Section 32 11 33 - Cement Treated Base Courses
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Measurement
a. Remove Concrete Paving: measure by the square yard from back-to-back of
curbs.
b. Remove Asphalt Paving: measure by the square yard between the lips of
gutters.
c. Remove Brick Paving: measure by the square yard.
d. Remove Concrete Curb and Gutter: measure by the linear foot.
e. Remove Concrete Valley Gutter: measure by the square yard
f. Wedge Milling: measure by the square yard for varying thickness.
g. Surface Milling: measure by the square yard for varying thickness.
h. Butt Milling: measured by the linear foot.
i. Pavement Pulverization: measure by the square yard.
j. Remove Speed Cushion: measure by each.
2. Payment
a. Remove Concrete Paving: full compensation for saw cutting, removal, hauling,
disposal, tools, equipment, labor and incidentals needed to execute work. For
utility projects, this Item shall be considered subsidiary to the trench and no
other compensation will be allowed.
b. Remove Asphalt Paving: full compensation for saw cutting, removal, hauling,
disposal, tools, equipment, labor and incidentals needed to execute work. For
utility projects, this Item shall be considered subsidiary to the trench and no
other compensation will be allowed.
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 15 - 2
PAVING REMOVAL
Page 2 of 6
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 2, 2016
c. Remove Brick Paving: full compensation for saw cutting, removal, salvaging,
cleaning, hauling, disposal, tools, equipment, labor and incidentals needed to
execute work. For utility projects, this Item shall be considered subsidiary to
the trench and no other compensation will be allowed.
d. Remove Concrete Curb and Gutter: full compensation for saw cutting, removal,
hauling, disposal, tools, equipment, labor and incidentals needed to execute
work. For utility projects, this Item shall be considered subsidiary to the trench
and no other compensation will be allowed.
e. Remove Concrete Valley Gutter: full compensation for saw cutting, removal,
hauling, disposal, tools, equipment, labor and incidentals needed to execute
work.
f. Wedge Milling: full compensation for all milling, hauling milled material to
salvage stockpile or disposal, tools, labor, equipment and incidentals necessary
to execute the work.
g. Surface Milling: full compensation for all milling, hauling milled material to
salvage stockpile or disposal, tools, labor, equipment and incidentals necessary
to execute the work.
h. Butt Milling: full compensation for all milling, hauling milled material to
salvage stockpile or disposal, tools, labor, equipment and incidentals necessary
to execute the work.
i. Pavement Pulverization: full compensation for all labor, material, equipment,
tools and incidentals necessary to pulverize, remove and store the pulverized
material, undercut the base, mixing, compaction, haul off, sweep, and dispose
of the undercut material.
j. Remove speed cushion: full compensation for removal, hauling, disposal,
tools, equipment, labor, and incidentals needed to execute the work. For utility
projects, this Item shall be considered subsidiary to the trench and no other
compensation will be allowed.
k. No payment for saw cutting of pavement or curbs and gutters will be made
under this section. Include cost of such work in unit prices for items listed in
bid form requiring saw cutting.
l. No payment will be made for work outside maximum payment limits indicated
on plans, or for pavements or structures removed for CONTRACTOR's
convenience.
1.3 REFERENCES
A. ASTM International (ASTM):
a. D698, Standard Test Methods for Laboratory Compaction Characteristics of
Soil Using Standard Effort (12 400 ft-lbf/ft3 (600 kN-m/m3))
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 SUBMITTALS [NOT USED]
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 15 - 3
PAVING REMOVAL
Page 3 of 6
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 2, 2016
1.11 FIELD CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS
2.1 OWNER-FURNISHED PRODUCTS [NOT USED]
2.2 EQUIPMENT [NOT USED]
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL [NOT USED]
PART 3 - EXECUTION
3.1 EXAMINATION [NOT USED]
3.2 INSTALLERS [NOT USED]
3.3 PREPARATION
A. General:
1. Mark paving removal limits for City approval prior to beginning removal.
2. Identify known utilities below grade - Stake and flag locations.
3.4 PAVEMENT REMOVAL
A. General.
1. Exercise caution to minimize damage to underground utilities.
2. Minimize amount of earth removed.
3. Remove paving to neatly sawed joints.
4. Use care to prevent fracturing adjacent, existing pavement.
B. Sawing
1. Sawing Equipment.
a. Power-driven.
b. Manufactured for the purpose of sawing pavement.
c. In good operating condition.
d. Shall not spall or fracture the pavement structure adjacent to the removal area.
2. Sawcut perpendicular to the surface to full pavement depth, parallel and
perpendicular to existing joint.
3. Sawcut parallel to the original sawcut in square or rectangular fashion.
4. If a sawcut falls within 5 feet of an en existing dummy joint, construction joint, saw
joint, cold joint, expansion joint, edge of paving or gutter lip, remove paving to that
joint, edge or lip.
5. If a pavement edge of a cut is damaged subsequent to saw cutting, saw to a new,
neat, straight line for the purpose of removing the damaged area.
C. Remove Concrete Paving and Concrete Valley Gutter
1. Sawcut: See 3.4.B.
2. Remove concrete to the nearest expansion joint or vertical saw cut.
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 15 - 4
PAVING REMOVAL
Page 4 of 6
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 2, 2016
D. Remove Concrete Curb and Gutter
1. Sawcut: See 3.4.B.
2. Minimum limits of removal: 30 inches in length.
E. Remove Asphalt Paving
1. Sawcut: See 3.4.B.
2. Remove pavement without disturbing the base material.
3. When shown on the plans or as directed, stockpile materials designated as
salvageable at designated sites.
4. Prepare stockpile area by removing vegetation and trash and by providing for
proper drainage.
F. Milling
1. General
a. Mill surfaces to the depth shown in the plans or as directed.
b. Do not damage or disfigure adjacent work or existing surface improvements.
c. If milling exposes smooth underlying pavement surfaces, mill the smooth
surface to make rough.
d. Provide safe temporary transition where vehicles or pedestrians must pass over
the milled edges.
e. Remove excess material and clean milled surfaces.
f. Stockpiling of planed material will not be permitted within the right of way
unless approved by the City.
g. If the existing base is brick and cannot be milled, remove a 5 foot width of the
existing brick base. See 3.3.G. for brick paving removal.
2. Milling Equipment
a. Power operated milling machine capable of removing, in one pass or two
passes, the necessary pavement thickness in a five-foot minimum width.
b. Self-propelled with sufficient power, traction and stability to maintain accurate
depth of cut and slope.
c. Equipped with an integral loading and reclaiming means to immediately
remove material cut from the surface of the roadway and discharge the cuttings
into a truck, all in one operation.
d. Equipped with means to control dust created by the cutting action.
e. Equipped with a manual system providing for uniformly varying the depth of
cut while the machine is in motion making it possible to cut flush to all inlets,
manholes, or other obstructions within the paved area.
f. Variable Speed in order to leave the specified grid pattern.
g. Equipped to minimize air pollution.
3. Wedge Milling and Surface Milling
a. Wedge Mill existing asphalt, concrete or brick pavement from the lip of gutter
at a depth of 2 inches and transitioning to match the existing pavement (0-inch
cut) at a minimum width of 5 feet.
b. Surface Mill existing asphalt pavement to the depth specified,
c. Provide a milled surface that provides a uniform surface free from gouges,
ridges, oil film, and other imperfections of workmanship with a uniform
textured appearance.
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 15 - 5
PAVING REMOVAL
Page 5 of 6
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 2, 2016
d. In all situations where the existing H.M.A.C. surface contacts the curb face, the
wedge milling includes the removal of the existing asphalt covering the gutter
up to and along the face of curb.
e. Perform wedge or surface milling operation in a continuous manner along both
sides of the street or as directed.
4. Butt Joint Milling
a. Mill butt joints into the existing surface, in association with the wedge milling
operation.
b. Butt joint will provide a full width transition section and a constant depth at the
point where the new overlay is terminated.
c. Typical locations for butt joints are at all beginning and ending points of streets
where paving material is removed. Prior to the milling of the butt joints,
consult with the City for proper location and limits of these joints.
d. Butt Milled joints are required on both sides of all railroad tracks and concrete
valley gutters, bridge decks and culverts and all other items which transverse
the street and end the continuity of the asphalt surface.
e. Make each butt joint 20 feet long and milled out across the full width of the
street section to a tapered depth of 2 inch.
f. Taper the milled area within the 20-feet to a depth from 0-inch to 2-inch at a
line adjacent to the beginning and ending points or intermediate transverse
items.
g. Provide a temporary wedge of asphalt at all butt joints to provide a smooth ride
over the bump.
G. Remove Brick Paving
1. Remove masonry paving units to the limits specified in the plans or as directed by
the City.
2. Salvage existing bricks for re-use, clean, palletize, and deliver to the City Stock pile
yard at 3300 Yuma Street or as directed.
H. Pavement Pulverization
1. Pulverization
a. Pulverize the existing pavement to depth of 8 inches. See Section 32 11 33.
b. Temporarily remove and store the 8-inch deep pulverized material, then cut the
base 2 inches.
c. Start 2-inch base cut at a depth of 8 inches from the existing pulverized surface.
2. Cement Application
a. Use 3.5% Portland cement.
b. See Section 32 11 33.
3. Mixing: see Section 32 11 33.
4. Compaction: see Section 32 11 33.
5. Finishing: see Section 32 11 33.
6. Curing: see Section 32 11 33.
7. If the existing pavement has a combination of 10 inches of H.M.A.C. and crushed
stone/gravel:
a. Undercut not required
b. Pulverize 10 inches deep.
c. Remove 2-inch the total pulverized amount.
Meacham Boulevard at Mercantile Drive
CPN 105417
02 41 15 - 6
PAVING REMOVAL
Page 6 of 6
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised February 2, 2016
I. Remove speed cushion
1. Scrape or sawcut speed cushion from existing pavement without damaging existing
pavement.
3.5 REPAIR [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 FIELD QUALITY CONTROL [NOT USED]
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING [NOT USED]
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 D. Johnson 1.2.A – modified payment requirements on utility projects
2/2/2016 F. Griffin 1.2.A.2.b. – Removed duplicate last sentence.
Meacham Boulevard at Mercantile Drive
CPN 105417
03 30 00 - 1
CAST -IN-PLACE CONCRETE
Page 1 of 25
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
1 SECTION 03 30 00
2 CAST-IN-PLACE CONCRETE
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Cast-in place concrete, including formwork, reinforcement, concrete materials,
7 mixture design, placement procedures and finishes, for the following:
8 a.Piers
9 b.Footings
10 c.Slabs-on-grade
11 d.Foundation walls
12 e.Retaining walls (non TxDOT)
13 f.Suspended slabs
14 g.Blocking
15 h.Cast-in-place manholes
16 i.Concrete vaults for meters and valves
17 j.Concrete encasement of utility lines
18 B. Deviations from this City of Fort Worth Standard Specification
19 1. None.
20 C. Related Specification Sections include, but are not necessarily limited to:
21 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
22 2. Division 1 – General Requirements
23 1.2 PRICE AND PAYMENT PROCEDURES
24 A. Cast-in-Place Concrete
25 1. Measurement
26 a. This Item is considered subsidiary to the structure or Items being placed.
27 2. Payment
28 a. The work performed and the materials furnished in accordance with this Item
29 are subsidiary to the structure or Items being placed and no other compensation
30 will be allowed.
31 1.3 REFERENCES
32 A. Definitions
33 1. Cementitious Materials
34 a. Portland cement alone or in combination with 1 or more of the following:
35 1) Blended hydraulic cement
36 2) Fly ash
37 3) Other pozzolans
38 4) Ground granulated blast-furnace slag
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 2
CAST -IN-PLACE CONCRETE
Page 2 of 25
1 5) Silica fume
2 b. Subject to compliance with the requirements of this specification
3 B. Reference Standards
4 1. Reference standards cited in this Specification refer to the current reference
5 standard published at the time of the latest revision date logged at the end of this
6 Specification, unless a date is specifically cited.
7 2. American Association of State Highway and Transportation (AASHTO):
8 a. M182, Burlap Cloth Made from Jute or Kenaf.
9 3. American Concrete Institute (ACI):
10 a. ACI 117 Specification for Tolerances for Concrete Construction and Materials
11 b. ACI 301 Specifications for Structural Concrete
12 c. ACI 305.1 Specification for Hot Weather Concreting
13 d. ACI 306.1 Standard Specification for Cold Weather Concreting
14 e. ACI 308.1 Standard Specification for Curing Concrete
15 f. ACI 318 Building Code Requirements for Structural Concrete
16 g. ACI 347 Guide to Formwork for Concrete
17 4. American Institute of Steel Construction (AISC):
18 a. 303, Code of Standard Practice for Steel Buildings and Bridges.
19 5. ASTM International (ASTM):
20 a. A36, Standard Specification for Carbon Structural Steel.
21 b. A153, Standard Specification for Zinc Coating (Hot-Dip) on Iron and Steel
22 Hardware.
23 c. A193, Standard Specification for Alloy-Steel and Stainless Steel Bolting
24 Materials for High-Temperature Service and Other Special Purpose
25 Applications.
26 d. A615, Standard Specification for Deformed and Plain Carbon-Steel Bars for
27 Concrete Reinforcement.
28 e. A706, Standard Specification for Low-Alloy Steel Deformed and Plain Bars for
29 Concrete Reinforcement.
30 f. C31, Standard Practice for Making and Curing Concrete Test Specimens in the
31 Field.
32 g. C33, Standard Specification for Concrete Aggregates.
33 h. C39, Standard Test Method for Compressive Strength of Cylindrical Concrete
34 Specimens.
35 i. C42, Standard Test Method for Obtaining and Testing Drilled Cores and Sawed
36 Beams of Concrete.
37 j. C94, Standard Specification for Ready-Mixed Concrete.
38 k. C109, Standard Test Method for Compressive Strength of Hydraulic Cement
39 Mortars (Using 2-inch or {50-milimeter] Cube Specimens)
40 l. C143, Standard Test Method for Slump of Hydraulic-Cement Concrete.
41 m. C171, Standard Specification for Sheet Materials for Curing Concrete.
42 n. C150, Standard Specification for Portland Cement.
43 o. C172, Standard Practice for Sampling Freshly Mixed Concrete.
44 p. C219, Standard Terminology Relating to Hydraulic Cement.
45 q. C231, Standard Test Method for Air Content of Freshly Mixed Concrete by the
46 Pressure Method.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 3
CAST -IN-PLACE CONCRETE
Page 3 of 25
1 r. C260, Standard Specification for Air-Entraining Admixtures for Concrete.
2 s. C309, Standard Specification for Liquid Membrane-Forming Compounds for
3 Curing Concrete.
4 t. C494, Standard Specification for Chemical Admixtures for Concrete.
5 u. C595, Standard Specification for Blended Hydraulic Cements
6 v. C618, Standard Specification for Coal Fly Ash and Raw or Calcined Natural
7 Pozzolan for Use in Concrete.
8 w. C881, Standard Specification for Epoxy-Resin-Base Bonding Systems for
9 Concrete.
10 x. C989, Standard Specification for Ground Granulated Blast-Furnace Slag for
11 Use in Concrete and Mortars.
12 y. C1017, Standard Specification for Chemical Admixtures for Use in Producing
13 Flowing Concrete.
14 z. C1059, Standard Specification for Latex Agents for Bonding Fresh to Hardened
15 Concrete.
16 aa. C1064, Standard Test Method for Temperature of Freshly Mixed Hydraulic-
17 Cement Concrete.
18 bb. C1240, Standard Specification for Silica Fume Used in Cementitious Mixtures.
19 cc. E1155, Standard Test Method for Determining FF Floor Flatness and FL Floor
20 Levelness Numbers.
21 dd. F436, Standard Specification for Hardened Steel Washers.
22 6. American Welding Society (AWS).
23 a. D1.1, Structural Welding Code - Steel.
24 b. D1.4, Structural Welding Code - Reinforcing Steel.
25 7. Concrete Reinforcing Steel Institute (CRSI)
26 a. Manual of Standard Practice
27 8. Texas Department of Transportation
28 a. Standard Specification for Construction and Maintenance of Highways, Streets
29 and Bridges
30 1.4 ADMINISTRATIVE REQUIREMENTS
31 A. Work Included
32 1. Design, fabrication, erection and stripping of formwork for cast-in-place concrete
33 including shoring, reshoring, falsework, bracing, proprietary forming systems,
34 prefabricated forms, void forms, permanent metal forms, bulkheads, keys,
35 blockouts, sleeves, pockets and accessories.
36 a. Erection shall include installation in formwork of items furnished by other
37 trades.
38 2. Furnish all labor and materials required to fabricate, deliver and install
39 reinforcement and embedded metal assemblies for cast-in-place concrete, including
40 steel bars, welded steel wire fabric, ties, supports and sleeves.
41 3. Furnish all labor and materials required to perform the following:
42 a. Cast-in-place concrete
43 b. Concrete mix designs
44 c. Grouting
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 4
CAST -IN-PLACE CONCRETE
Page 4 of 25
1 1.5 SUBMITTALS
2 A. Submittals shall be in accordance with Section 01 33 00.
3 B. All submittals shall be approved by the City prior to delivery and/or fabrication for
4 specials.
5 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
6 A. Product Data
7 1. Required for each type of product indicated
8 B. Design Mixtures
9 1. For each concrete mixture submit proposed mix designs in accordance with ACI
10 318, chapter 5.
11 2. Submit each proposed mix design with a record of past performance.
12 3. Submit alternate design mixtures when characteristics of materials, Project condi-
13 tions, weather, test results or other circumstances warrant adjustments.
14 4. Indicate amounts of mixing water to be withheld for later addition at Project site.
15 a. Include this quantity on delivery ticket.
16 C. Steel Reinforcement Submittals for Information
17 1. Mill test certificates of supplied concrete reinforcing, indicating physical and chem-
18 ical analysis.
19 1.7 CLOSEOUT SUBMITTALS [NOT USED]
20 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
21 1.9 QUALITY ASSURANCE
22 A. Manufacturer Qualifications
23 1. A firm experienced in manufacturing ready-mixed concrete products and that com-
24 plies with ASTM C94 requirements for production facilities and equipment
25 2. Manufacturer certified according to NRMCA's "Certification of Ready Mixed
26 Concrete Production Facilities”
27 B. Source Limitations
28 1. Obtain each type or class of cementitious material of the same brand from the same
29 manufacturer's plant, obtain aggregate from 1 source and obtain admixtures through
30 1 source from a single manufacturer.
31 C. ACI Publications
32 1. Comply with the following unless modified by requirements in the Contract Docu-
33 ments:
34 a. ACI 301 Sections 1 through 5
35 b. ACI 117
36 D. Concrete Testing Service
37 1. Engage a qualified independent testing agency to perform material evaluation tests.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 5
CAST -IN-PLACE CONCRETE
Page 5 of 25
1 1.10 DELIVERY, STORAGE, AND HANDLING
2 A. Steel Reinforcement
3 1. Deliver, store, and handle steel reinforcement to prevent bending and damage.
4 2. Avoid damaging coatings on steel reinforcement.
5 B. Waterstops
6 1. Store waterstops under cover to protect from moisture, sunlight, dirt, oil and other
7 contaminants.
8 1.11 FIELD CONDITIONS [NOT USED]
9 1.12 WARRANTY [NOT USED]
10 PART 2 - PRODUCTS
11 2.1 OWNER-FURNISHED OR OWNER-SUPPLIED PRODUCTS [NOT USED]
12 2.2 PRODUCT TYPES AND MATERIALS
13 A. Manufacturers
14 1. In other Part 2 articles where titles below introduce lists, the following requirements
15 apply to product selection:
16 a. Available Products: Subject to compliance with requirements, products that
17 may be incorporated into the Work include, but are not limited to, products
18 specified.
19 b. Available Manufacturers: Subject to compliance with requirements,
20 manufacturers offering products that may be incorporated into the Work
21 include, but are not limited to, manufacturers specified.
22 B. Form-Facing Materials
23 1. Rough-Formed Finished Concrete
24 a. Plywood, lumber, metal or another approved material
25 b. Provide lumber dressed on at least 2 edges and 1 side for tight fit.
26 2. Chamfer Strips
27 a. Wood, metal, PVC or rubber strips
28 b. ¾-inch x ¾-inch, minimum
29 3. Rustication Strips
30 a. Wood, metal, PVC or rubber strips
31 b. Kerfed for ease of form removal
32 4. Form-Release Agent
33 a. Commercially formulated form-release agent that will not bond with, stain or
34 adversely affect concrete surfaces
35 b. Shall not impair subsequent treatments of concrete surfaces
36 c. For steel form-facing materials, formulate with rust inhibitor.
37 5. Form Ties
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 6
CAST -IN-PLACE CONCRETE
Page 6 of 25
1 a. Factory-fabricated, removable or snap-off metal or glass-fiber-reinforced
2 plastic form ties designed to resist lateral pressure of fresh concrete on forms
3 and to prevent spalling of concrete on removal.
4 b. Furnish units that will leave no corrodible metal closer than 1 inch to the plane
5 of exposed concrete surface.
6 c. Furnish ties that, when removed, will leave holes no larger than 1 inch in
7 diameter in concrete surface.
8 d. Furnish ties with integral water-barrier plates to walls indicated to receive
9 dampproofing or waterproofing.
10 C. Steel Reinforcement
11 1. Reinforcing Bars
12 a. ASTM A615, Grade 60, deformed
13 D. Reinforcement Accessories
14 1. Smooth Dowel Bars
15 a. ASTM A615, Grade 60, steel bars (smooth)
16 b. Cut bars true to length with ends square and free of burrs.
17 2. Bar Supports
18 a. Bolsters, chairs, spacers and other devices for spacing, supporting and fastening
19 reinforcing bars and welded wire reinforcement in place
20 b. Manufacture bar supports from steel wire, plastic or precast concrete according
21 to CRSI's "Manual of Standard Practice," of greater compressive strength than
22 concrete and as follows:
23 1) For concrete surfaces exposed to view where legs of wire bar supports
24 contact forms, use CRSI Class 1 plastic-protected steel wire or CRSI
25 Class 2 stainless-steel bar supports.
26 2) For slabs-on-grade, provide sand plates, horizontal runners or precast
27 concrete blocks on bottom where base material will not support chair legs
28 or where vapor barrier has been specified.
29 E. Embedded Metal Assemblies
30 1. Steel Shapes and Plates: ASTM A36
31 2. Headed Studs: Heads welded by full-fusion process, as furnished by TRW Nelson
32 Stud Welding Division or approved equal
33 F. Expansion Anchors
34 1. Available Products
35 a. Wej-it Bolt, Wej-it Corporation, Tulsa, Oklahoma
36 b. Kwik Bolt II, Hilti Fastening Systems, Tulsa, Oklahoma
37 c. Trubolt, Ramset Fastening Systems, Paris, Kentucky
38 G. Adhesive Anchors and Dowels
39 1. Adhesive anchors shall consist of threaded rods anchored with an adhesive system
40 into hardened concrete or grout-filled masonry.
41 a. The adhesive system shall use a 2-component adhesive mix and shall be
42 injected with a static mixing nozzle following manufacturer’s instructions.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 7
CAST -IN-PLACE CONCRETE
Page 7 of 25
1 b. The embedment depth of the rod shall provide a minimum allowable bond
2 strength that is equal to the allowable yield capacity of the rod, unless otherwise
3 specified.
4 2. Available Products
5 a. Hilti HIT HY 150 Max
6 b. Simpson Acrylic-Tie
7 c. Powers Fasteners AC 100+ Gold
8 3. Threaded Rods: ASTM A193
9 a. Nuts: ASTM A563 hex carbon steel
10 b. Washers: ASTM F436 hardened carbon steel
11 c. Finish: Hot-dip zinc coating, ASTM A153, Class C
12 H. Inserts
13 1. Provide metal inserts required for anchorage of materials or equipment to concrete
14 construction where not supplied by other trades:
15 a. In vertical concrete surfaces for transfer of direct shear loads only, provide
16 adjustable wedge inserts of malleable cast iron complete with bolts, nuts and
17 washers.
18 1) Provide ¾-inch bolt size, unless otherwise indicated.
19 b. In horizontal concrete surfaces and whenever inserts are subject to tension
20 forces, provide threaded inserts of malleable cast iron furnished with full depth
21 bolts.
22 1) Provide ¾-inch bolt size, unless otherwise indicated.
23 I. Concrete Materials
24 1. Cementitious Material
25 a. Use the following cementitious materials, of the same type, brand, and source,
26 throughout Project:
27 1) Portland Cement, Portland-Limestone Cement
28 a) ASTM C150, Type I/II, gray
29 b) ASTM C595, Type IL cement
30 c) Supplement with the following:
31 (1) Fly Ash
32 (a) ASTM C618, Class C or F
33 (2) Ground Granulated Blast-Furnace Slag
34 (a) ASTM C989, Grade 100 or 120.
35 2) Silica Fume
36 a) ASTM C1240, amorphous silica
37 3) Normal-Weight Aggregates
38 a) ASTM C33, Class 3S coarse aggregate or better, graded
39 b) Provide aggregates from a single source.
40 4) Maximum Coarse-Aggregate Size
41 a) ¾-inch nominal
42 5) Fine Aggregate
43 a) Free of materials with deleterious reactivity to alkali in cement
44 6) Water
45 a) ASTM C94 and potable
46 J. Admixtures
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 8
CAST -IN-PLACE CONCRETE
Page 8 of 25
1 1. Air-Entraining Admixture
2 a. ASTM C260
3 2. Chemical Admixtures
4 a. Provide admixtures certified by manufacturer to be compatible with other ad-
5 mixtures and that will not contribute water-soluble chloride ions exceeding
6 those permitted in hardened concrete.
7 b. Do not use calcium chloride or admixtures containing calcium chloride.
8 c. Water-Reducing Admixture
9 1) ASTM C494, Type A
10 d. Retarding Admixture
11 1) ASTM C494, Type B
12 e. Water-Reducing and Retarding Admixture
13 1) ASTM C494, Type D
14 f. High-Range, Water-Reducing Admixture
15 1) ASTM C494, Type F
16 g. High-Range, Water-Reducing and Retarding Admixture
17 1) ASTM C494, Type G
18 h. Plasticizing and Retarding Admixture
19 1) ASTM C1017, Type II
20 K. Waterstops
21 1. Self-Expanding Butyl Strip Waterstops
22 a. Manufactured rectangular or trapezoidal strip, butyl rubber with sodium
23 bentonite or other hydrophilic polymers, for adhesive bonding to concrete, ¾-
24 inch x 1-inch.
25 b. Available Products
26 1) Colloid Environmental Technologies Company; Volclay Waterstop-RX
27 2) Concrete Sealants Inc.; Conseal CS-231
28 3) Greenstreak; Swellstop
29 4) Henry Company, Sealants Division; Hydro-Flex
30 5) JP Specialties, Inc.; Earthshield Type 20
31 6) Progress Unlimited, Inc.; Superstop
32 7) TCMiraDRI; Mirastop
33 L. Curing Materials
34 1. Absorptive Cover
35 a. AASHTO M182, Class 2, burlap cloth made from jute or kenaf, weighing
36 approximately 9 ounces/square yard when dry
37 2. Moisture-Retaining Cover
38 a. ASTM C171, polyethylene film or white burlap-polyethylene sheet
39 3. Water
40 a. Potable
41 4. Clear, Waterborne, Membrane-Forming Curing Compound
42 a. ASTM C309, Type 1, Class B, dissipating
43 b. Available Products
44 1) Anti-Hydro International, Inc.; AH Curing Compound #2 DR WB
45 2) Burke by Edoco; Aqua Resin Cure
46 3) ChemMasters; Safe-Cure Clear
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 9
CAST -IN-PLACE CONCRETE
Page 9 of 25
1 4) Conspec Marketing & Manufacturing Co., Inc., a Dayton Superior
2 Company; W.B. Resin Cure
3 5) Dayton Superior Corporation; Day Chem Rez Cure (J-11-W)
4 6) Euclid Chemical Company (The); Kurez DR VOX
5 7) Kaufman Products, Inc.; Thinfilm 420
6 8) Lambert Corporation; Aqua Kure-Clear
7 9) L&M Construction Chemicals, Inc.; L&M Cure R
8 10) Meadows, W. R., Inc.; 1100 Clear
9 11) Nox-Crete Products Group, Kinsman Corporation; Resin Cure E
10 12) Symons Corporation, a Dayton Superior Company; Resi-Chem Clear Cure
11 13) Tamms Industries, Inc.; Horncure WB 30
12 14) Unitex; Hydro Cure 309
13 15) US Mix Products Company; US Spec Maxcure Resin Clear
14 16) Vexcon Chemicals, Inc.; Certi-Vex Enviocure 100
15 M. Related Materials
16 1. Bonding Agent
17 a. ASTM C1059, Type II, non-redispersible, acrylic emulsion or styrene
18 butadiene
19 2. Epoxy Bonding Adhesive
20 a. ASTM C881, 2-component epoxy resin, capable of humid curing and bonding
21 to damp surfaces, of class suitable for application temperature and of grade to
22 suit requirements, and as follows:
23 1) Types I and II, non-load bearing
24 2) IV and V, load bearing, for bonding
25 3) Hardened or freshly mixed concrete to hardened concrete
26 3. Reglets
27 a. Fabricate reglets of not less than 0.0217-inch thick, galvanized steel sheet
28 b. Temporarily fill or cover face opening of reglet to prevent intrusion of concrete
29 or debris.
30 4. Sleeves and Blockouts
31 a. Formed with galvanized metal, galvanized pipe, polyvinyl chloride pipe, fiber
32 tubes or wood
33 5. Nails, Spikes, Lag Bolts, Through Bolts, Anchorages
34 a. Sized as required
35 b. Shall be of strength and character to maintain formwork in place while placing
36 concrete
37 N. Repair Materials
38 1. Repair Underlayment
39 a. Cement-based, polymer-modified, self-leveling product that can be applied in
40 thicknesses of 1/8 inch or greater
41 1) Do not feather.
42 b. Cement Binder
43 1) ASTM C150, C595, Portland cement, Portland-Limestone Cement or hy-
44 draulic or blended hydraulic cement as defined in ASTM C219
45 c. Primer
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 10
CAST -IN-PLACE CONCRETE
Page 10 of 25
1 1) Product of underlayment manufacturer recommended for substrate, condi-
2 tions, and application
3 d. Aggregate
4 1) Well-graded, washed gravel, 1/8 to 1/4 inch or coarse sand as
5 recommended by underlayment manufacturer
6 e. Compressive Strength
7 1) Not less than 4100 psi at 28 days when tested according to
8 ASTM C109/C109M
9 2. Repair Overlayment
10 a. Cement-based, polymer-modified, self-leveling product that can be applied in
11 thicknesses of 1/8 inch or greater
12 1) Do not feather.
13 b. Cement Binder
14 1) ASTM C150, C595, Portland cement, Portland-Limestone Cement or hy-
15 draulic or blended hydraulic cement as defined in ASTM C219
16 c. Primer
17 1) Product of topping manufacturer recommended for substrate, conditions,
18 and application
19 d. Aggregate
20 1) Well-graded, washed gravel, 1/8 to 1/4 inch or coarse sand as recommend-
21 ed by topping manufacturer
22 e. Compressive Strength
23 1) Not less than 5000 psi at 28 days when tested according to ASTM C109
24 O. Concrete Mixtures, General
25 1. Prepare design mixtures for each type and strength of concrete, proportioned on the
26 basis of laboratory trial mixture or field test data, or both, according to ACI 301.
27 a. Required average strength above specified strength
28 1) Based on a record of past performance
29 a) Determination of required average strength above specified strength
30 shall be based on the standard deviation record of the results of at least
31 30 consecutive strength tests in accordance with ACI 318, Chapter 5.3
32 by the larger amount defined by formulas 5-1 and 5-2.
33 2) Based on laboratory trial mixtures
34 a) Proportions shall be selected on the basis of laboratory trial batches
35 prepared in accordance with ACI 318, Chapter 5.3.3.2 to produce an
36 average strength greater than the specified strength f'c by the amount
37 defined in table 5.3.2.2.
38 3) Proportions of ingredients for concrete mixes shall be determined by an in-
39 dependent testing laboratory or qualified concrete supplier.
40 4) For each proposed mixture, at least 3 compressive test cylinders shall be
41 made and tested for strength at the specified age.
42 a) Additional cylinders may be made for testing for information at earlier
43 ages.
44 2. Cementitious Materials
45 a. Limit percentage, by weight, of cementitious materials other than Portland ce-
46 ment or Portland-Limestone cement in concrete as follows, unless specified
47 otherwise:
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 11
CAST -IN-PLACE CONCRETE
Page 11 of 25
1 1) Fly Ash: 25 percent
2 2) Combined Fly Ash and Pozzolan: 25 percent
3 3) Ground Granulated Blast-Furnace Slag: 50 percent
4 4) Combined Fly Ash or Pozzolan and Ground Granulated Blast-Furnace
5 Slag: 50 percent
6 5) Portland cement minimum, with fly ash or pozzolan not exceeding 25 per-
7 cent
8 6) Silica Fume: 10 percent
9 7) Combined Fly Ash, Pozzolans, and Silica Fume: 35 percent with fly ash or
10 pozzolans not exceeding 25 percent and silica fume not exceeding 10 per-
11 cent
12 8) Combined Fly Ash or Pozzolans, Ground Granulated Blast-Furnace Slag,
13 and Silica Fume: 50 percent with fly ash or pozzolans not exceeding 25
14 percent and silica fume not exceeding 10 percent
15 3. Limit water-soluble, chloride-ion content in hardened concrete to:
16 a. 0.30 percent by weight of cement if concrete will have no exposure to chlorides
17 (typical)
18 b. 0.15 percent by weight if concrete will be exposed to chlorides
19 c. 1.0 percent by weight if concrete will have no exposure to chlorides and will be
20 continually dry and protected.
21 4. Admixtures
22 a. Use admixtures according to manufacturer's written instructions.
23 b. Do not use admixtures which have not been incorporated and tested in accepted
24 mixes.
25 c. Use water-reducing high-range water-reducing or plasticizing admixture in
26 concrete, as required, for placement and workability.
27 d. Use water-reducing and retarding admixture when required by high
28 temperatures, low humidity or other adverse placement conditions.
29 e. Use water-reducing admixture in pumped concrete, concrete for heavy-use
30 industrial slabs and parking structure slabs, concrete required to be watertight,
31 and concrete with a water-cementitious materials ratio below 0.50.
32 f. Use corrosion-inhibiting admixture in concrete mixtures where indicated.
33 P. Concrete Mixtures
34 1. Refer to TxDOT “Standard Specifications for Construction and Maintenance of
35 Highways, Streets, and Bridges” for:
36 a. Culverts
37 b. Headwalls
38 c. Wingwalls
39 2. Proportion normal-weight concrete mixture as follows:
40 a. Minimum Compressive Strength: 3,000 psi at 28 days
41 b. Maximum Water-Cementitious Materials Ratio: 0.50
42 c. Slump Limit: 5 inches or 8 inches for concrete with verified slump of 2 to 4
43 inches before adding high-range water-reducing admixture or plasticizing
44 admixture, plus or minus 1 inch
45 d. Air Content: 6 percent, plus or minus 1.5 percent at point of delivery for 3/4-
46 inch nominal maximum aggregate size
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 12
CAST -IN-PLACE CONCRETE
Page 12 of 25
1 Q. Fabricating Reinforcement
2 1. Fabricate steel reinforcement according to CRSI's "Manual of Standard Practice."
3 R. Fabrication of Embedded Metal Assemblies
4 1. Fabricate metal assemblies in the shop. Holes shall be made by drilling or
5 punching. Holes shall not be made by or enlarged by burning. Welding shall be in
6 accordance with AWS D1.1.
7 2. Metal assemblies exposed to earth, weather or moisture shall be hot dip galvanized.
8 All other metal assemblies shall be either hot dip galvanized or painted with an
9 epoxy paint. Repair galvanizing after welding with a Cold Galvanizing compound
10 installed in accordance with the manufacturer's instructions. Repair painted
11 assemblies after welding with same type of paint.
12 S. Concrete Mixing
13 1. Ready-Mixed Concrete: Measure, batch, mix, and deliver concrete according to
14 ASTM C94, and furnish batch ticket information.
15 a. When air temperature is between 85 and 90 degrees Fahrenheit, reduce mixing
16 and delivery time from 1-1/2 hours to 75 minutes; when air temperature is
17 above 90 degrees Fahrenheit, reduce mixing and delivery time to 60 minutes.
18 2. Project-Site Mixing: Measure, batch, and mix concrete materials and concrete
19 according to ASTM C94/C94M. Mix concrete materials in appropriate drum-type
20 batch machine mixer.
21 a. For mixer capacity of 1 cubic yard or smaller, continue mixing at least 1-1/2
22 minutes, but not more than 5 minutes after ingredients are in mixer, before any
23 part of batch is released.
24 b. For mixer capacity larger than 1 cubic yard, increase mixing time by 15
25 seconds for each additional 1 cubic yard.
26 c. Provide batch ticket for each batch discharged and used in the Work, indicating
27 Project identification name and number, date, mixture type, mixture time,
28 quantity, and amount of water added. Record approximate location of final
29 deposit in structure.
30 2.3 ACCESSORIES [NOT USED]
31 2.4 SOURCE QUALITY CONTROL [NOT USED]
32 PART 3 - EXECUTION
33 3.1 INSTALLERS [NOT USED]
34 3.2 EXAMINATION [NOT USED]
35 3.3 PREPARATION [NOT USED]
36 3.4 INSTALLATION
37 A. Formwork
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 13
CAST -IN-PLACE CONCRETE
Page 13 of 25
1 1. Design, erect, shore, brace, and maintain formwork, according to ACI 301, to
2 support vertical, lateral, static, and dynamic loads, and construction loads that might
3 be applied, until structure can support such loads.
4 2. Construct formwork so concrete members and structures are of size, shape,
5 alignment, elevation, and position indicated, within tolerance limits of ACI 117.
6 a. Vertical alignment
7 1) Lines, surfaces and arises less than 100 feet in height - 1 inch.
8 2) Outside corner of exposed corner columns and control joints in concrete
9 exposed to view less than 100 feet in height - 1/2 inch.
10 3) Lines, surfaces and arises greater than 100 feet in height - 1/1000 times the
11 height but not more than 6 inches.
12 4) Outside corner of exposed corner columns and control joints in concrete
13 exposed to view greater than 100 feet in height - 1/2000 times the height
14 but not more than 3 inches.
15 b. Lateral alignment
16 1) Members - 1 inch.
17 2) Centerline of openings 12 inches or smaller and edge location of larger
18 openings in slabs - 1/2 inch.
19 3) Sawcuts, joints, and weakened plane embedments in slabs - 3/4 inch.
20 c. Level alignment
21 1) Elevation of slabs-on-grade - 3/4 inch.
22 2) Elevation of top surfaces of formed slabs before removal of shores - 3/4
23 inch.
24 3) Elevation of formed surfaces before removal of shores - 3/4 inch.
25 d. Cross-sectional dimensions: Overall dimensions of beams, joists, and columns
26 and thickness of walls and slabs.
27 1) 12 inch dimension or less - plus 1/2 inch to minus 1/4 inch.
28 2) Greater than 12 inch to 3 foot dimension - plus 1/2 inch to minus 3/8 inch.
29 3) Greater than 3 foot dimension - plus 1 inch to minus 3/4 inch.
30 e. Relative alignment
31 1) Stairs
32 a) Difference in height between adjacent risers - 1/8 inch.
33 b) Difference in width between adjacent treads - 1/4 inch.
34 c) Maximum difference in height between risers in a flight of stairs - 3/8
35 inch.
36 d) Maximum difference in width between treads in a flight of stairs - 3/8
37 inch.
38 2) Grooves
39 a) Specified width 2 inches or less - 1/8 inch.
40 b) Specified width between 2 inches and 12 inches - 1/4 inch.
41 3) Vertical alignment of outside corner of exposed corner columns and control
42 joint grooves in concrete exposed to view - 1/4 inch in 10 feet.
43 4) All other conditions - 3/8 inch in 10 feet.
44 3. Limit concrete surface irregularities, designated by ACI 347R as abrupt or gradual,
45 as follows:
46 a. Class B, 1/4 inch for smooth-formed finished surfaces.
47 b. Class C, 1/2 inch for rough-formed finished surfaces.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 14
CAST -IN-PLACE CONCRETE
Page 14 of 25
1 4. Construct forms tight enough to prevent loss of concrete mortar.
2 5. Fabricate forms for easy removal without hammering or prying against concrete
3 surfaces. Provide crush or wrecking plates where stripping may damage cast
4 concrete surfaces. Provide top forms for inclined surfaces steeper than 1.5
5 horizontal to 1 vertical.
6 a. Install keyways, reglets, recesses, and the like, for easy removal.
7 b. Do not use rust-stained steel form-facing material.
8 6. Set edge forms, bulkheads, and intermediate screed strips for slabs to achieve
9 required elevations and slopes in finished concrete surfaces. Provide and secure
10 units to support screed strips; use strike-off templates or compacting-type screeds.
11 7. Construct formwork to cambers shown or specified on the Drawings to allow for
12 structural deflection of the hardened concrete. Provide additional elevation or
13 camber in formwork as required for anticipated formwork deflections due to weight
14 and pressures of concrete and construction loads.
15 8. Foundation Elements: Form the sides of all below grade portions of beams, pier
16 caps, walls, and columns straight and to the lines and grades specified. Do no earth
17 form foundation elements unless specifically indicated on the Drawings.
18 9. Provide temporary openings for cleanouts and inspection ports where interior area
19 of formwork is inaccessible. Close openings with panels tightly fitted to forms and
20 securely braced to prevent loss of concrete mortar. Locate temporary openings in
21 forms at inconspicuous locations.
22 10. Chamfer exterior corners and edges of permanently exposed concrete.
23 11. Form openings, chases, offsets, sinkages, keyways, reglets, blocking, screeds, and
24 bulkheads required in the Work. Determine sizes and locations from trades
25 providing such items.
26 12. Clean forms and adjacent surfaces to receive concrete. Remove chips, wood,
27 sawdust, dirt, and other debris just before placing concrete.
28 13. Retighten forms and bracing before placing concrete, as required, to prevent mortar
29 leaks and maintain proper alignment.
30 14. Coat contact surfaces of forms with form-release agent, according to manufacturer's
31 written instructions, before placing reinforcement, anchoring devices, and
32 embedded items.
33 a. Do not apply form release agent where concrete surfaces are scheduled to
34 receive subsequent finishes which may be affected by agent. Soak contact
35 surfaces of untreated forms with clean water. Keep surfaces wet prior to
36 placing concrete.
37 B. Embedded Items
38 1. Place and secure anchorage devices and other embedded items required for
39 adjoining work that is attached to or supported by cast-in-place concrete. Use
40 setting drawings, templates, diagrams, instructions, and directions furnished with
41 items to be embedded.
42 a. Install anchor rods, accurately located, to elevations required and complying
43 with tolerances in AISC 303, Section 7.5.
44 1) Spacing within a bolt group: 1/8 inch
45 2) Location of bolt group (center): ½ inch
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 15
CAST -IN-PLACE CONCRETE
Page 15 of 25
1 3) Rotation of bolt group: 5 degrees
2 4) Angle off vertical: 5 degrees
3 5) Bolt projection: ± 3/8 inch
4 b. Install reglets to receive waterproofing and to receive through-wall flashings in
5 outer face of concrete frame at exterior walls, where flashing is shown at lintels,
6 shelf angles, and other conditions.
7 C. Removing and Reusing Forms
8 1. Do not backfill prior to concrete attaining 70 percent of its 28-day design
9 compressive strength.
10 2. General: Formwork for sides of beams, walls, columns, and similar parts of the
11 Work that does not support weight of concrete may be removed after cumulatively
12 curing at not less than 50 degrees Fahrenheit for 24 hours after placing concrete, if
13 concrete is hard enough to not be damaged by form-removal operations and curing
14 and protection operations are maintained.
15 a. Leave formwork for beam soffits, joists, slabs, and other structural elements
16 that supports weight of concrete in place until concrete has achieved at least 70
17 percent of its 28-day design compressive strength.
18 b. Do not remove formwork supporting conventionally reinforced concrete until
19 concrete has attained 70 percent of its specified 28 day compressive strength as
20 established by tests of field cured cylinders. In the absence of cylinder tests,
21 supporting formwork shall remain in place until the concrete has cured at a
22 temperature of at least 50 degrees Fahrenheit for the minimum cumulative time
23 periods given in ACI 347, Section 3.7.2.3. Add the period of time when the
24 surrounding air temperature is below 50 degrees Fahrenheit, to the minimum
25 listed time period. Formwork for 2-way conventionally reinforced slabs shall
26 remain in place for at least the minimum cumulative time periods specified for
27 1-way slabs of the same maximum span.
28 c. Immediately reshore 2-way conventionally reinforced slabs after formwork
29 removal. Reshores shall remain until the concrete has attained the specified 28
30 day compressive strength.
31 d. Minimum cumulative curing times may be reduced by the use of high-early
32 strength cement or forming systems which allow form removal without
33 disturbing shores, but only after the Contractor has demonstrated to the
34 satisfaction of the Engineer that the early removal of forms will not cause
35 excessive sag, distortion or damage to the concrete elements.
36 e. Completely remove wood forms. Provide temporary openings if required.
37 f. Provide adequate methods of curing and thermal protection of exposed concrete
38 if forms are removed prior to completion of specified curing time.
39 g. Reshore areas required to support construction loads in excess of 20 pounds per
40 square foot to properly distribute construction loading. Construction loads up
41 to the rated live load capacity may be placed on unshored construction provided
42 the concrete has attained the specified 28 day compressive strength.
43 h. Obtaining concrete compressive strength tests for the purposes of form removal
44 is the responsibility of the Contractor.
45 i. Remove forms only if shores have been arranged to permit removal of forms
46 without loosening or disturbing shores.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 16
CAST -IN-PLACE CONCRETE
Page 16 of 25
1 3. Clean and repair surfaces of forms to be reused in the Work. Split, frayed,
2 delaminated, or otherwise damaged form-facing material will not be acceptable for
3 exposed surfaces. Apply new form-release agent.
4 4. When forms are reused, clean surfaces, remove fins and laitance, and tighten to
5 close joints. Align and secure joints to avoid offsets. Do not use patched forms for
6 exposed concrete surfaces unless approved by Engineer.
7 D. Shores and Reshores
8 1. The Contractor is solely responsible for proper shoring and reshoring.
9 2. Comply with ACI 318 and ACI 301 for design, installation, and removal of shoring
10 and reshoring.
11 a. Do not remove shoring or reshoring until measurement of slab tolerances is
12 complete.
13 3. Plan sequence of removal of shores and reshore to avoid damage to concrete.
14 Locate and provide adequate reshoring to support construction without excessive
15 stress or deflection.
16 E. Steel Reinforcement
17 1. General: Comply with CRSI's "Manual of Standard Practice" for placing
18 reinforcement.
19 a. Do not cut or puncture vapor retarder. Repair damage and reseal vapor retarder
20 before placing concrete.
21 2. Clean reinforcement of loose rust and mill scale, earth, ice, and other foreign
22 materials that would reduce bond to concrete.
23 3. Accurately position, support, and secure reinforcement against displacement.
24 Locate and support reinforcement with bar supports to maintain minimum concrete
25 cover. Do not tack weld crossing reinforcing bars.
26 a. Weld reinforcing bars according to AWS D1.4, where indicated. Only steel
27 conforming to ASTM A706 may be welded.
28 4. Installation tolerances
29 a. Top and bottom bars in slabs, girders, beams and joists:
30 1) Members 8 inches deep or less: ±3/8 inch
31 2) Members more than 8 inches deep: ±1/2 inch
32 b. Concrete Cover to Formed or Finished Surfaces: ±3/8 inches for members 8
33 inches deep or less; ±1/2 inches for members over 8 inches deep, except that
34 tolerance for cover shall not exceed 1/3 of the specified cover.
35 5. Concrete Cover
36 a. Reinforcing in structural elements deposited against the ground: 3 inches
37 b. Reinforcing in formed beams, columns and girders: 1-1/2 inches
38 c. Grade beams and exterior face of formed walls and columns exposed to
39 weather or in contact with the ground: 2 inches
40 d. Interior faces of walls: 1 inches
41 e. Slabs: 3/4 inches
42 6. Splices: Provide standard reinforcement splices by lapping and tying ends. Comply
43 with ACI 318 for minimum lap of spliced bars where not specified on the
44 documents. Do not lap splice no. 14 and 18 bars.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 17
CAST -IN-PLACE CONCRETE
Page 17 of 25
1 7. Field Welding of Embedded Metal Assemblies
2 a. Remove all paint and galvanizing in areas to receive field welds.
3 b. Field Prepare all areas where paint or galvanizing has been removed with the
4 specified paint or cold galvanizing compound, respectively.
5 F. Joints
6 1. General: Construct joints true to line with faces perpendicular to surface plane of
7 concrete.
8 2. Construction Joints: Install so strength and appearance of concrete are not
9 impaired, at locations indicated or as approved by Engineer.
10 a. Place joints perpendicular to main reinforcement. Continue reinforcement
11 across construction joints, unless otherwise indicated. Do not continue
12 reinforcement through sides of strip placements of floors and slabs.
13 b. Form keyed joints as indicated. Embed keys at least 1-1/2 inches into concrete.
14 c. Locate joints for beams, slabs, joists, and girders in the middle third of spans.
15 Offset joints in girders a minimum distance of twice the beam width from a
16 beam-girder intersection.
17 d. Locate horizontal joints in walls and columns at underside of floors, slabs,
18 beams, and girders and at the top of footings or floor slabs.
19 e. Space vertical joints in walls as indicated. Locate joints beside piers integral
20 with walls, near corners, and in concealed locations where possible.
21 f. Use a bonding agent at locations where fresh concrete is placed against
22 hardened or partially hardened concrete surfaces.
23 3. Doweled Joints: Install dowel bars and support assemblies at joints where
24 indicated. Lubricate or asphalt coat 1-1/2 of dowel length to prevent concrete
25 bonding to 1 side of joint.
26 G. Waterstops
27 1. Flexible Waterstops: Install in construction joints and at other joints indicated to
28 form a continuous diaphragm. Install in longest lengths practicable. Support and
29 protect exposed waterstops during progress of the Work. Field fabricate joints in
30 waterstops according to manufacturer's written instructions.
31 2. Self-Expanding Strip Waterstops: Install in construction joints and at other
32 locations indicated, according to manufacturer's written instructions, adhesive
33 bonding, mechanically fastening, and firmly pressing into place. Install in longest
34 lengths practicable.
35 H. Adhesive Anchors
36 1. Comply with the manufacturer's installation instructions on the hole diameter and
37 depth required to fully develop the tensile strength of the adhesive anchor or
38 reinforcing bar.
39 2. Properly clean out the hole utilizing a wire brush and compressed air to remove all
40 loose material from the hole, prior to installing adhesive material.
41 I. Concrete Placement
42 1. Before placing concrete, verify that installation of formwork, reinforcement, and
43 embedded items is complete and that required inspections have been performed.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 18
CAST -IN-PLACE CONCRETE
Page 18 of 25
1 2. Do not add water to concrete during delivery, at Project site, or during placement
2 unless approved by Engineer.
3 3. Before test sampling and placing concrete, water may be added at Project site,
4 subject to limitations of ACI 301.
5 a. Do not add water to concrete after adding high-range water-reducing
6 admixtures to mixture.
7 b. Do not exceed the maximum specified water/cement ratio for the mix.
8 4. Deposit concrete continuously in 1 layer or in horizontal layers of such thickness
9 that no new concrete will be placed on concrete that has hardened enough to cause
10 seams or planes of weakness. If a section cannot be placed continuously, provide
11 construction joints as indicated. Deposit concrete to avoid segregation.
12 a. Deposit concrete in horizontal layers of depth to not exceed formwork design
13 pressures, 15 feet maximum and in a manner to avoid inclined construction
14 joints.
15 b. Consolidate placed concrete with mechanical vibrating equipment according to
16 ACI 301.
17 c. Do not use vibrators to transport concrete inside forms. Insert and withdraw
18 vibrators vertically at uniformly spaced locations to rapidly penetrate placed
19 layer and at least 6 inches into preceding layer. Do not insert vibrators into
20 lower layers of concrete that have begun to lose plasticity. At each insertion,
21 limit duration of vibration to time necessary to consolidate concrete and
22 complete embedment of reinforcement and other embedded items without
23 causing mixture constituents to segregate.
24 d. Do not permit concrete to drop freely any distance greater than 10 feet for
25 concrete containing a high range water reducing admixture (superplasticizer) or
26 5 feet for other concrete. Provide chute or tremie to place concrete where longer
27 drops are necessary. Do not place concrete into excavations with standing
28 water. If place of deposit cannot be pumped dry, pour concrete through a tremie
29 with its outlet near the bottom of the place of deposit.
30 e. Discard pump priming grout and do not use in the structure.
31 5. Deposit and consolidate concrete for floors and slabs in a continuous operation,
32 within limits of construction joints, until placement of a panel or section is
33 complete.
34 a. Consolidate concrete during placement operations so concrete is thoroughly
35 worked around reinforcement and other embedded items and into corners.
36 b. Maintain reinforcement in position on chairs during concrete placement.
37 c. Screed slab surfaces with a straightedge and strike off to correct elevations.
38 d. Slope surfaces uniformly to drains where required.
39 e. Begin initial floating using bull floats or darbies to form a uniform and open-
40 textured surface plane, before excess bleedwater appears on the surface. Do not
41 further disturb slab surfaces before starting finishing operations.
42 6. Cold-Weather Placement: Comply with ACI 306.1 and as follows. Protect
43 concrete work from physical damage or reduced strength that could be caused by
44 frost, freezing actions, or low temperatures.
45 a. When average high and low temperature is expected to fall below 40
46 degrees Fahrenheit for 3 successive days, maintain delivered concrete mixture
47 temperature within the temperature range required by ACI 301.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 19
CAST -IN-PLACE CONCRETE
Page 19 of 25
1 b. Do not use frozen materials or materials containing ice or snow. Do not place
2 concrete on frozen subgrade or on subgrade containing frozen materials.
3 c. Do not use calcium chloride, salt, or other materials containing antifreeze
4 agents or chemical accelerators unless otherwise specified and approved in
5 mixture designs.
6 7. Hot-Weather Placement: Comply with ACI 305.1 and as follows:
7 a. Maintain concrete temperature below 95 degrees Fahrenheit at time of
8 placement. Chilled mixing water or chopped ice may be used to control
9 temperature, provided water equivalent of ice is calculated to total amount of
10 mixing water. Using liquid nitrogen to cool concrete is Contractor's option.
11 b. Fog-spray forms, steel reinforcement, and subgrade just before placing
12 concrete. Keep subgrade uniformly moist without standing water, soft spots, or
13 dry areas.
14 J. Finishing Formed Surfaces
15 1. Rough-Formed Finish: As-cast concrete texture imparted by form-facing material
16 with tie holes and defects repaired and patched. Remove fins and other projections
17 that exceed specified limits on formed-surface irregularities.
18 a. Apply to concrete surfaces not exposed to public view.
19 2. Related Unformed Surfaces: At tops of walls, horizontal offsets, and similar
20 unformed surfaces adjacent to formed surfaces, strike off smooth and finish with a
21 texture matching adjacent formed surfaces. Continue final surface treatment of
22 formed surfaces uniformly across adjacent unformed surfaces, unless otherwise
23 indicated.
24 K. Miscellaneous Concrete Items
25 1. Filling In: Fill in holes and openings left in concrete structures, unless otherwise
26 indicated, after work of other trades is in place. Mix, place, and cure concrete, as
27 specified, to blend with in-place construction. Provide other miscellaneous
28 concrete filling indicated or required to complete the Work.
29 2. Curbs: Provide monolithic finish to interior curbs by stripping forms while
30 concrete is still green and by steel-troweling surfaces to a hard, dense finish with
31 corners, intersections, and terminations slightly rounded.
32 3. Equipment Bases and Foundations: Provide machine and equipment bases and
33 foundations as shown on Drawings. Set anchor bolts for machines and equipment
34 at correct elevations, complying with diagrams or templates from manufacturer
35 furnishing machines and equipment.
36 a. Housekeeping pads: Normal weight concrete (3000 psi), reinforced with
37 #3@16 inches on center set at middepth of pad. Trowel concrete to a dense,
38 smooth finish. Set anchor bolts for securing mechanical or electrical equipment
39 during pouring of concrete fill.
40 4. Protective slabs ("Mud slabs"): Normal weight concrete (2500 psi minimum) with a
41 minimum thickness of 3-1/2 inches. Finish slab to a wood float finish.
42 L. Concrete Protecting and Curing
43 1. General: Protect freshly placed concrete from premature drying and excessive cold
44 or hot temperatures. Comply with ACI 306.1 for cold-weather protection and
45 ACI 305.1 for hot-weather protection during curing.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 20
CAST -IN-PLACE CONCRETE
Page 20 of 25
1 2. Formed Surfaces: Cure formed concrete surfaces, including underside of beams,
2 supported slabs, and other similar surfaces. If forms remain during curing period,
3 moist cure after loosening forms. If removing forms before end of curing period,
4 continue curing for the remainder of the curing period.
5 3. Unformed Surfaces: Begin curing immediately after finishing concrete. Cure
6 unformed surfaces, including floors and slabs, concrete floor toppings, and other
7 surfaces.
8 4. Cure concrete according to ACI 308.1, by 1 or a combination of the following
9 methods:
10 a. Moisture Curing: Keep surfaces continuously moist for not less than 7 days
11 with the following materials:
12 1) Water
13 2) Continuous water-fog spray
14 3) Absorptive cover, water saturated, and kept continuously wet. Cover
15 concrete surfaces and edges with 12-inch lap over adjacent absorptive
16 covers
17 b. Moisture-Retaining-Cover Curing: Cover concrete surfaces with moisture-
18 retaining cover for curing concrete, placed in widest practicable width, with
19 sides and ends lapped at least 12 inches, and sealed by waterproof tape or
20 adhesive. Cure for not less than 7 days. Immediately repair any holes or tears
21 during curing period using cover material and waterproof tape.
22 1) Moisture cure or use moisture-retaining covers to cure concrete surfaces to
23 receive floor coverings.
24 2) Moisture cure or use moisture-retaining covers to cure concrete surfaces to
25 receive penetrating liquid floor treatments.
26 3) Cure concrete surfaces to receive floor coverings with either a moisture-
27 retaining cover or a curing compound that the manufacturer certifies will
28 not interfere with bonding of floor covering used on Project.
29 c. Curing Compound: Apply uniformly in continuous operation by power spray
30 or roller according to manufacturer's written instructions. Recoat areas
31 subjected to heavy rainfall within 3 hours after initial application. Maintain
32 continuity of coating and repair damage during curing period.
33 3.5 REPAIR
34 A. Concrete Surface Repairs
35 1. Defective Concrete: Repair and patch defective areas when approved by Engineer.
36 Remove and replace concrete that cannot be repaired and patched to Engineer’s
37 approval.
38 2. Patching Mortar: Mix dry-pack patching mortar, consisting of 1 part portland
39 cement to 2-1/2 parts fine aggregate passing a No. 16 sieve, using only enough
40 water for handling and placing.
41 3. Repairing Formed Surfaces: Surface defects include color and texture
42 irregularities, cracks, spalls, air bubbles, honeycombs, rock pockets, fins and other
43 projections on the surface, and stains and other discolorations that cannot be
44 removed by cleaning.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 21
CAST -IN-PLACE CONCRETE
Page 21 of 25
1 a. Immediately after form removal, cut-out honeycombs, rock pockets, and voids
2 more than 1/2 inch in any dimension in solid concrete, but not less than 1 inch
3 in depth. Make edges of cuts perpendicular to concrete surface. Clean, dampen
4 with water, and brush-coat holes and voids with bonding agent. Fill and
5 compact with patching mortar before bonding agent has dried. Fill form-tie
6 voids with patching mortar or cone plugs secured in place with bonding agent.
7 b. Repair defects on surfaces exposed to view by blending white portland cement
8 and standard portland cement so that, when dry, patching mortar will match
9 surrounding color. Patch a test area at inconspicuous locations to verify
10 mixture and color match before proceeding with patching. Compact mortar in
11 place and strike off slightly higher than surrounding surface.
12 c. Repair defects on concealed formed surfaces that affect concrete's durability
13 and structural performance as determined by Engineer.
14 4. Repairing Unformed Surfaces: Test unformed surfaces, such as floors and slabs,
15 for finish and verify surface tolerances specified for each surface. Correct low and
16 high areas. Test surfaces sloped to drain for trueness of slope and smoothness; use
17 a sloped template.
18 a. Repair finished surfaces containing defects. Surface defects include spalls, pop
19 outs, honeycombs, rock pockets, crazing and cracks in excess of 0.01 inch wide
20 or that penetrate to reinforcement or completely through unreinforced sections
21 regardless of width, and other objectionable conditions.
22 b. After concrete has cured at least 14 days, correct high areas by grinding.
23 c. Correct localized low areas during or immediately after completing surface
24 finishing operations by cutting out low areas and replacing with patching
25 mortar. Finish repaired areas to blend into adjacent concrete.
26 d. Repair defective areas, except random cracks and single holes 1 inch or less in
27 diameter, by cutting out and replacing with fresh concrete. Remove defective
28 areas with clean, square cuts and expose steel reinforcement with at least a 3/4-
29 inch clearance all around. Dampen concrete surfaces in contact with patching
30 concrete and apply bonding agent. Mix patching concrete of same materials
31 and mixture as original concrete except without coarse aggregate. Place,
32 compact, and finish to blend with adjacent finished concrete. Cure in same
33 manner as adjacent concrete.
34 e. Repair random cracks and single holes 1 inch or less in diameter with patching
35 mortar. Groove top of cracks and cut out holes to sound concrete and clean off
36 dust, dirt, and loose particles. Dampen cleaned concrete surfaces and apply
37 bonding agent. Place patching mortar before bonding agent has dried.
38 Compact patching mortar and finish to match adjacent concrete. Keep patched
39 area continuously moist for at least 72 hours.
40 5. Perform structural repairs of concrete, subject to Engineer’s approval, using epoxy
41 adhesive and patching mortar.
42 6. Repair materials and installation not specified above may be used, subject to
43 Engineer’s approval.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 22
CAST -IN-PLACE CONCRETE
Page 22 of 25
1 3.6 RE-INSTALLATION [NOT USED]
2 3.7 FIELD QUALITY CONTROL
3 A. Testing and Inspecting: City will engage a special inspector and qualified testing and
4 inspecting agency to perform field tests and inspections and prepare test reports.
5 B. Inspections
6 1. Steel reinforcement placement
7 2. Headed bolts and studs
8 3. Verification of use of required design mixture
9 4. Concrete placement, including conveying and depositing
10 5. Curing procedures and maintenance of curing temperature
11 6. Verification of concrete strength before removal of shores and forms from beams
12 and slabs
13 C. Concrete Tests: Perform testing of composite samples of fresh concrete obtained
14 according to ASTM C172 according to the following requirements:
15 1. Testing Frequency: Obtain 1 composite sample for each day's pour of each
16 concrete mixture exceeding 5 cubic yard, but less than 25 cubic yard, plus 1 set for
17 each additional 50 cubic yard or fraction thereof.
18 2. Slump: ASTM C143; 1 test at point of placement for each composite sample, but
19 not less than 1 test for each day's pour of each concrete mixture. Perform additional
20 tests when concrete consistency appears to change.
21 3. Air Content: ASTM C231, pressure method, for normal-weight concrete; 1 test for
22 each composite sample, but not less than 1 test for each day's pour of each concrete
23 mixture.
24 4. Concrete Temperature: ASTM C1064; 1 test hourly when air temperature is 40
25 degrees Fahrenheit and below and when 80 degrees Fahrenheit and above, and 1
26 test for each composite sample.
27 5. Compression Test Specimens: ASTM C31.
28 a. Cast and laboratory cure 4 cylinders for each composite sample.
29 1) Do not transport field cast cylinders until they have cured for a
30 minimum of 24 hours.
31 6. Compressive-Strength Tests: ASTM C39;
32 a. Test 1 cylinder at 7 days.
33 b. Test 2 cylinders at 28 days.
34 c. Hold 1 cylinder for testing at 56 days as needed.
35 7. When strength of field-cured cylinders is less than 85 percent of companion
36 laboratory-cured cylinders, evaluate operations and provide corrective procedures
37 for protecting and curing in-place concrete.
38 8. Strength of each concrete mixture will be satisfactory if every average of any 3
39 consecutive compressive-strength tests equals or exceeds specified compressive
40 strength and no compressive-strength test value falls below specified compressive
41 strength by more than 500 psi.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 23
CAST -IN-PLACE CONCRETE
Page 23 of 25
1 9. Report test results in writing to Engineer, concrete manufacturer, and Contractor
2 within 48 hours of testing. Reports of compressive-strength tests shall contain
3 Project identification name and number, date of concrete placement, name of
4 concrete testing and inspecting agency, location of concrete batch in Work, design
5 compressive strength at 28 days, concrete mixture proportions and materials,
6 compressive breaking strength, and type of break for both 7- and 28-day tests.
7 10. Additional Tests: Testing and inspecting agency shall make additional tests of
8 concrete when test results indicate that slump, air entrainment, compressive
9 strengths, or other requirements have not been met, as directed by Engineer.
10 Testing and inspecting agency may conduct tests to determine adequacy of concrete
11 by cored cylinders complying with ASTM C42 or by other methods as directed by
12 Engineer.
13 a. When the strength level of the concrete for any portion of the structure, as
14 indicated by cylinder tests, falls below the specified requirements, provide
15 improved curing conditions and/or adjustments to the mix design as required to
16 obtain the required strength. If the average strength of the laboratory control
17 cylinders falls so low as to be deemed unacceptable, follow the core test
18 procedure set forth in ACI 301, Chapter 17. Locations of core tests shall be
19 approved by the Engineer. Core sampling and testing shall be at Contractors
20 expense.
21 b. If the results of the core tests indicate that the strength of the structure is
22 inadequate, any replacement, load testing, or strengthening as may be ordered
23 by the Engineer shall be provided by the Contractor without cost to the City.
24 11. Additional testing and inspecting, at Contractor's expense, will be performed to
25 determine compliance of replaced or additional work with specified requirements.
26 12. Correct deficiencies in the Work that test reports and inspections indicate does not
27 comply with the Contract Documents.
28 D. Measure floor and slab flatness and levelness according to ASTM E1155 within 48
29 hours of finishing.
30 E. Concrete Finish Measurement and Tolerances
31 1. All floors are subject to measurement for flatness and levelness and comply with
32 the following:
33 a. Slabs shall be flat within a tolerance of 5/16 inches in 10 feet when tested with
34 a 10 foot long straightedge. Apply straightedge to the slab at 3 foot intervals in
35 both directions, lapping straightedge 3 feet on areas previously checked. Low
36 spots shall not exceed the above dimension anywhere along the straightedge.
37 Flatness shall be checked the next work day after finishing.
38 b. Slabs shall be level within a tolerance of ± 1/4 inch in 10 feet, not to exceed 3/4
39 inches total variation, anywhere on the floor, from elevations indicated on the
40 Drawings. Levelness shall be checked on a 10 foot grid using a level after
41 removal of forms.
42 c. Measurement Standard: All floors are subject to measurement for flatness and
43 levelness, according to ASTM E1155.
44 2. 2 Tiered Measurement Standard
45 a. Each floor test section and the overall floor area shall conform to the 2-tiered
46 measurement standard as specified herein.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 24
CAST -IN-PLACE CONCRETE
Page 24 of 25
1 1) Minimum Local Value: The minimum local FF/FL values represent the ab-
2 solute minimum surface profile that will be acceptable for any 1 test sample
3 (line of measurements) anywhere within the test area.
4 2) Specified Overall Value: The specified overall FF/FL values represent the
5 minimum values acceptable for individual floor sections as well as the floor
6 as a whole.
7 3. Floor Test Sections
8 a. A floor test section is defined as the smaller of the following areas:
9 1) The area bounded by column and/or wall lines
10 2) The area bounded by construction and/or control joint lines
11 3) Any combination of column lines and/or control joint lines
12 b. Test sample measurement lines within each test section shall be
13 multidirectional along 2 orthogonal lines, as defined by ASTM E1155, at a
14 spacing to be determined by the City's testing agency.
15 c. The precise layout of each test section shall be determined by the City's testing
16 agency.
17 4. Concrete Floor Finish Tolerance
18 a. The following values apply before removal of shores. Levelness values (FL) do
19 not apply to intentionally sloped or cambered areas, nor to slabs poured on
20 metal deck or precast concrete.
21 1) Slabs
22 Overall Value FF45/FL30
23 Minimum Local Value FF30/FL20
24 5. Floor Elevation Tolerance Envelope
25 a. The acceptable tolerance envelope for absolute elevation of any point on the
26 slab surface, with respect to the elevation shown on the Drawings, is as follows:
27 1) Slab-on-Grade Construction: ± ¾ inch
28 2) Top surfaces of formed slabs measured prior to removal of supporting
29 shores: ± ¾ inch
30 3) Top surfaces of all other slabs: ± ¾ inch
31 4) Slabs specified to slope shall have a tolerance from the specified slope of
32 3/8 inch in 10 feet at any point, up to ¾ inch from theoretical elevation at
33 any point.
34 3.8 SYSTEM STARTUP [NOT USED]
35 3.9 ADJUSTING [NOT USED]
36 3.10 CLEANING
37 A. Defective Work
38 1. Imperfect or damaged work or any material damaged or determined to be defective
39 before final completion and acceptance of the entire job shall be satisfactorily re-
40 placed at the Contractor's expense, and in conformity with all of the requirements of
41 the Drawings and Specifications.
42 2. Perform removal and replacement of concrete work in such manner as not to impair
43 the appearance or strength of the structure in any way.
44 B. Cleaning
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICATION DOCUMENTS
Revised March 11, 2022
Birchman Office Space
CPN 105553
03 30 00 - 25
CAST -IN-PLACE CONCRETE
Page 25 of 25
1 1. Upon completion of the work remove from the site all forms, equipment, protective
2 coverings and any rubbish resulting therefrom.
3 2. After sweeping floors, wash floors with clean water.
4 3. Leave finished concrete surfaces in a clean condition, satisfactory to the City.
5 3.11 CLOSEOUT ACTIVITIES [NOT USED]
6 3.12 PROTECTION [NOT USED]
7 3.13 MAINTENANCE [NOT USED]
8 3.14 ATTACHMENTS [NOT USED]
9 END OF SECTION
10
Revision Log
DATE NAME SUMMARYOF CHANGE
12/20/2012 D. Johnson
2.2.O.3 – Removed Blue Text/Added Descriptions for water-soluble,
chloride-ion content
3.4.C.1 – Changed 75% to 70%
3/11//2022 Zelalem Arega 1.3.B.5.t, 2.2.I.1, 2.2.O.2, – Added ASTMC595 – Type ILcement
11
Meacham Boulevard at Mercantile Drive
CPN 105417
03 34 13 - 1
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
Page 1 of 7
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
SECTION 03 34 13
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
PART 1 - GENERAL
1.1 SUMMARY
A. Section includes:
1. Controlled low strength material (CLSM) for use in the following:
a. Flowable backfill
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
3. Section 03 30 00 - Cast-in-Place Concrete
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Measurement
a. This Item is considered subsidiary to the structure or Items being placed.
2. Payment
a. The work performed and the materials furnished in accordance with this Item
are subsidiary to the structure or Items being placed and no other compensation
will be allowed.
1.3 REFERENCES
A. Reference Standards
1. Reference standards cited in this Specification refer to the current reference
standard published at the time of the latest revision date logged at the end of this
Specification, unless a date is specifically cited.
B. ASTM International (ASTM):
1. C31 - Standard Practice for Making and Curing Concrete Test Specimens in the
Field.
2. C33 - Standard Specification for Concrete Aggregates.
3. C39 - Standard Test Method for Compressive Strength of Cylindrical Concrete
Specimens.
4. C143 - Standard Test Method for Slump of Hydraulic Cement Concrete.
5. C231 - Standard Test Method for Air Content of Freshly Mixed Concrete by the
Pressure Method.
6. C260 - Standard Specification for Air-Entraining Admixtures for Concrete.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 13 - 2
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
Page 2 of 7
7. C618 - Standard Specification for Coal Fly Ash and Raw or Calcined Natural
Pozzolan for Use in Concrete.
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 SUBMITTALS
A. Provide submittals in accordance with Section 01 33 00.
B. All submittals shall be approved by the City prior to delivery and/or fabrication for
specials.
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
A. Product data
B. Sieve analysis
1. Submit sieve analyses of fine and coarse aggregates being used.
a. Resubmit at any time there is a significant change in grading of materials.
2. Mix
a. Submit full details, including mix design calculations for mix proposed for use.
C. Trial batch test data
1. Submit data for each test cylinder.
2. Submit data that identifies mix and slump for each test cylinder.
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS
2.1 OWNER-FURNISHED OR OWNER-SUPPLIED PRODUCTS [NOT USED]
2.2 PRODUCT TYPES AND MATERIALS
A. Materials
1. Portland cement: Type II low alkali portland cement as specified in Section 03 30
00.
2. Fly ash: Class F fly ash in accordance with ASTM C618.
3. Water: As specified in Section 03 30 00.
4. Admixture: Air entraining admixture in accordance with ASTM C260.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 13 - 3
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
Page 3 of 7
5. Fine aggregate: Concrete sand (does not need to be in accordance with
ASTM C33). No more than 12 percent of fine aggregate shall pass a No. 200 sieve,
and no plastic fines shall be present.
6. Coarse aggregate: Pea gravel no larger than 3/8 inch.
B. Mixes
1. Performance requirements
a. Total calculated air content
1) Not less than 8.0 percent or greater than 12.0 percent.
b. Minimum unconfined compressive strength
1) Not less than 50 psi measured at 28 days.
c. Maximum unconfined compressive strength
1) Not greater than 150 psi measured at 28 days.
2) Limit the long-term strength (90 days) to 200 psi such that material could
be re-excavated with conventional excavation equipment in the future if
necessary.
d. Wet density
1) No greater than 132 pounds per cubic foot.
e. Color
1) No coloration required unless noted.
2) Submit dye or other coloration means for approval.
2. Suggested design mix
Material Weight Specific Gravity
Absolute Volume
Cubic Foot
Cement 30 pounds 3.15 0.15
Fly Ash 300 pounds 2.30 2.09
Water 283 pounds 1.00 4.54
Coarse Aggregate 1,465 pounds 2.68 8.76
Fine Aggregate 1,465 pounds 2.68 8.76
Admixture 4-6 ounces -2.70
TOTAL 3,543 pounds -27.00
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL
A. Trial batch
1. After mix design has been accepted by Engineer, have trial batch of the accepted
mix design prepared by testing laboratory acceptable to Engineer.
2. Prepare trial batches using specified cementitious materials and aggregates
proposed to be used for the Work.
3. Prepare trial batch with sufficient quantity to determine slump, workability,
consistency, and to provide sufficient test cylinders.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 13 - 4
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
Page 4 of 7
B. Test cylinders:
1. Prepare test cylinders in accordance with ASTM C31 with the following
exceptions:
a. Fill the concrete test cylinders to overflowing and tap sides lightly to settle the
mix.
b. Do not rod the concrete mix.
c. Strike off the excess material.
2. Place test cylinders in a moist curing room. Exercise caution in moving and
transporting the cylinders since they are fragile and will withstand only minimal
bumping, banging, or jolting without damage.
3. Do not remove the test cylinder from mold until the cylinder is to be capped and
tested.
4. The test cylinders may be capped with standard sulfur compound or neoprene pads:
a. Perform the capping carefully to prevent premature fractures.
b. Use neoprene pads a minimum of 1/2 inch thick, and 1/2 inch larger in diameter
than the test cylinders.
c. Do not perform initial compression test until the cylinders reach a minimum
age of 3 days.
C. Compression test 8 test cylinders: Test 4 test cylinders at 3 days and 4 at 28 days in
accordance with ASTM C39 except as modified herein:
1. The compression strength of the 4 test cylinders tested at 28 days shall be equal to
or greater than the minimum required compression strength, but not exceed
maximum compression strength.
D. If the trial batch tests do not meet the Specifications for strength or density, revise and
resubmit the mix design, and prepare additional trial batch and tests. Repeat until an
acceptable trial batch is produced that meets the Specifications.
1. All the trial batches and acceptability of materials shall be paid by the
CONTRACTOR.
2. After acceptance, do not change the mix design without submitting a new mix
design, trial batches, and test information.
E. Determine slump in accordance with ASTM C143 with the following exceptions:
1. Do not rod the concrete material.
2. Place material in slump cone in 1 semi-continuous filling operation, slightly
overfill, tap lightly, strike off, and then measure and record slump.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 13 - 5
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
Page 5 of 7
PART 3 - EXECUTION
3.1 INSTALLERS [NOT USED]
3.2 EXAMINATION [NOT USED]
3.3 PREPARATION [NOT USED]
3.4 INSTALLATION
A. Place CLSM by any method which preserves the quality of the material in terms of
compressive strength and density:
1. Limit lift heights of CLSM placed against structures and other facilities that could
be damaged due to the pressure from the CLSM, to the lesser of 4 feet or the lift
height indicated on the Drawings. Do not place another lift of CLSM until the last
lift of CLSM has set and gained sufficient strength to prevent lateral load due to the
weight of the next lift of CLSM.
2. The basic requirement for placement equipment and placement methods is the
maintenance of its fluid properties.
3. Transport and place material so that it flows easily around, beneath, or through
walls, pipes, conduits, or other structures.
4. Use a slump of the placed material greater than 9 inches, and sufficient to allow the
material to flow freely during placement:
a. After trial batch testing and acceptance, maintain slump developed during
testing during construction at all times within ± 1 inch.
5. Use a slump, consistency, workability, flow characteristics, and pumpability (where
required) such that when placed, the material is self-compacting, self-densifying,
and has sufficient plasticity that compaction or mechanical vibration is not required.
6. When using as embedment for pipe take appropriate measures to ensure line and
grade of pipe.
3.5 REPAIR [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 FIELD QUALITY CONTROL
A. General
1. Make provisions for and furnish all material for the test specimens, and provide
manual assistance to assist the Engineer in preparing said specimens.
2. Be responsible for the care of and providing curing condition for the test specimens.
B. Tests by the City
1. During the progress of construction, the City will have tests made to determine
whether the CLSM, as being produced, complies with the requirements specified
hereinbefore. Test cylinders will be made and delivered to the laboratory by the
Engineer and the testing expense will be borne by the City.
2. Test cylinders
a. Prepare test cylinders in accordance with ASTM C31 with the following
exceptions:
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 13 - 6
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
Page 6 of 7
1) Fill the concrete test cylinders to overflowing and tap sides lightly to settle
the mix.
2) Do not rod the concrete mix.
3) Strike off the excess material.
b. Place the cylinders in a safe location away from the construction activities.
Keep the cylinders moist by covering with wet burlap, or equivalent. Do not
sprinkle water directly on the cylinders.
c. After 2 days, place the cylinders in a protective container for transport to the
laboratory for testing. The concrete test cylinders are fragile and shall be
handled carefully. The container may be a box with a Styrofoam or similar
lining that will limit the jarring and bumping of the cylinders.
d. Place test cylinders in a moist curing room. Exercise caution in moving and
transporting the cylinders since they are fragile and will withstand only
minimal bumping, banging, or jolting without damage.
e. Do not remove the test cylinder from mold until the cylinder is to be capped
and tested.
f. The test cylinders may be capped with standard sulfur compound or neoprene
pads:
1) Perform the capping carefully to prevent premature fractures.
2) Use neoprene pads a minimum of 1/2 inch thick, and 1/2 inch larger in
diameter than the test cylinders.
3) Do not perform initial compression test until the cylinders reach a
minimum age of 3 days.
3. The number of cylinder specimens taken each day shall be determined by the
Inspector.
a. Test 1 cylinder at 3 days and 2 at 28 days in accordance with ASTM C39
except as modified herein.
b. The compression strength of the cylinders tested at 28 days shall be equal to or
greater than the minimum required compression strength, but not exceed
maximum compression strength.
4. The City will test the air content of the CLSM. Test will be made immediately after
discharge from the mixer in accordance with ASTM C231.
5. Test the slump of CLSM using a slump cone in accordance with ASTM C143 with
the following exceptions:
a. Do not rod the concrete material.
b. Place material in slump cone in 1 semi-continuous filling operation, slightly
overfill, tap lightly, strike off, and then measure and record slump.
6. If compressive strength of test cylinders does not meet requirements, make
corrections to the mix design to meet the requirements of this specification.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 13 - 7
CONTROLLED LOW STRENGTH MATERIAL (CLSM)
Page 7 of 7
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING [NOT USED]
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
03 34 16 - 1
CONCRETE BASE MATERIAL FOR TRENCH REPAIR
Page 1 of 4
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
SECTION 03 34 16
CONCRETE BASE MATERIAL FOR TRENCH REPAIR
PART 1 - GENERAL
1.1 SUMMARY
A. Section includes:
1. Concrete base material for trench repair
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
3. Section 03 30 00 – Cast-in-Place Concrete
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Measurement
a. This Item is considered subsidiary to the structure or Items being placed.
2. Payment
a. The work performed and the materials furnished in accordance with this Item
are subsidiary to the structure or Items being placed and no other compensation
will be allowed.
1.3 REFERENCES
A. Reference Standards
1. Reference standards cited in this Specification refer to the current reference
standard published at the time of the latest revision date logged at the end of this
Specification, unless a date is specifically cited.
B. ASTM International (ASTM):
1. C31, Standard Practice for Making and Curing Concrete Test Specimens in the
Field.
2. C33, Standard Specification for Concrete Aggregates.
3. C39, Standard Test Method for Compressive Strength of Cylindrical Concrete
Specimens.
4. C143, Standard Test Method for Slump of Hydraulic-Cement Concrete.
5. C172, Standard Practice for Sampling Freshly Mixed Concrete.
6. C231, Standard Test Method for Air Content of Freshly Mixed Concrete by the
Pressure Method.
7. C260, Standard Specification for Air-Entraining Admixtures for Concrete.
8. C618, Standard Specification for Coal Fly Ash and Raw or Calcined Natural
Pozzolan for Use in Concrete.
9. C1064, Standard Test Method for Temperature of Freshly Mixed Hydraulic-
Cement Concrete.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 16 - 2
CONCRETE BASE MATERIAL FOR TRENCH REPAIR
Page 2 of 4
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 SUBMITTALS
A. Provide submittals in accordance with Section 01 33 00.
B. All submittals shall be approved by the City prior to delivery and/or fabrication for
specials.
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
A. Submit proposed mix design for Engineer’s review a minimum of 2 weeks prior to start
of low density concrete backfill work.
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS
2.1 OWNER-FURNISHED OR OWNER-SUPPLIED PRODUCTS [NOT USED]
2.2 PRODUCT TYPES AND MATERIALS
A. Mix Design
1. Performance requirements
a. Concrete Base Material for Trench Repair
1) 28-day compressive strength of not less than 750 psi and not more than
1,200 psi.
B. Materials
1. Portland cement
a. Type II low alkali portland cement as specified in Section 03 30 00.
2. Fly ash
a. Class F fly ash in accordance with ASTM C618.
3. Water
a. As specified in Section 03 30 00.
4. Admixture
a. Air entraining admixture in accordance with ASTM C260.
5. Fine aggregate
a. Concrete sand (does not need to be in accordance with ASTM C33).
b. No more than 12 percent of fine aggregate shall pass a No. 200 sieve, and no
plastic fines shall be present.
6. Coarse aggregate
a. Pea gravel no larger than 3/8 inch.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 16 - 3
CONCRETE BASE MATERIAL FOR TRENCH REPAIR
Page 3 of 4
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL [NOT USED]
PART 3 - EXECUTION
3.1 INSTALLERS [NOT USED]
3.2 EXAMINATION [NOT USED]
3.3 PREPARATION [NOT USED]
3.4 INSTALLATION
A. Place concrete base material by any method which preserves the quality of the material
in terms of compressive strength and density.
1. The basic requirement for placement equipment and placement methods is the
maintenance of its fluid properties.
2. Transport and place material so that it flows easily around, beneath, or through
walls, pipes, conduits, or other structures.
3. Use a slump, consistency, workability, flow characteristics, and pumpability (where
required) such that when placed, the material is self-compacting, self-densifying,
and has sufficient plasticity that compaction or mechanical vibration is not required.
3.5 REPAIR [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 FIELD QUALITY CONTROL
A. General
1. Make provisions for and furnish all material for the test specimens, and provide
manual assistance to assist the Engineer in preparing said specimens.
2. Be responsible for the care of and providing curing condition for the test specimens.
B. Concrete Tests: Perform testing of composite samples of fresh concrete obtained
according to ASTM C172 according to the following requirements:
1. Testing Frequency: Obtain 1 composite sample for each day's pour of each
concrete mixture up to 25 cubic yards, plus 1 set for each additional 50 cubic yards
or fraction thereof.
2. Slump: ASTM C143; 1 test at point of placement for each composite sample, but
not less than 1 test for each day's pour of each concrete mixture. Perform additional
tests when concrete consistency appears to change.
3. Air Content: ASTM C231, pressure method, for normal-weight concrete; 1 test for
each composite sample, but not less than 1 test for each day's pour of each concrete
mixture.
4. Concrete Temperature: ASTM C1064; 1 test hourly when air temperature is 40
degrees Fahrenheit and below and when 80 degrees Fahrenheit and above, and 1
test for each composite sample.
5. Compression Test Specimens: ASTM C31.
a. Cast and laboratory cure 4 cylinders for each composite sample.
1) Do not transport field cast cylinders until they have cured for a minimum of
24 hours.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 34 16 - 4
CONCRETE BASE MATERIAL FOR TRENCH REPAIR
Page 4 of 4
6. Compressive-Strength Tests: ASTM C39
a. Test 1 cylinder at 7 days.
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING [NOT USED]
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
03 80 00 - 1
MODIFICATIONS TO EXISTING CONCRETE
Page 1 of 7
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
SECTION 03 80 00
MODIFICATIONS TO EXISTING CONCRETE STRUCTURES
PART 1 - GENERAL
1.1 SUMMARY
A. Section includes:
1. Modifications to existing concrete structures, including:
a. Manholes
b. Junction boxes
c. Vaults
d. Retaining walls
e. Wing and head walls
f. Culverts
2. This section does not include modifications to Reinforced Concrete Pipe.
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Measurement
a. This Item is considered subsidiary to the structure or Items being placed.
2. Payment
a. The work performed and the materials furnished in accordance with this Item
are subsidiary to the structure or Items being placed and no other compensation
will be allowed.
1.3 REFERENCES
A. Reference Standards
1. Reference standards cited in this Specification refer to the current reference
standard published at the time of the latest revision date logged at the end of this
Specification, unless a date is specifically cited.
2. ASTM International (ASTM):
a. A615, Deformed and Plain Billet-Steel Bars for Concrete Reinforcement.
b. C881, Standard Specification for Epoxy-Resin-Base Bonding Systems for
Concrete.
c. C882, Standard Test Method for Bond Strength of Epoxy-Resin Systems Used
with Concrete by Slant Sheer.
d. D570, Standard Test Method for Water Absorption of Plastics.
e. D638, Standard Test Method for Tensile Properties of Plastics.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 80 00 - 2
MODIFICATIONS TO EXISTING CONCRETE
Page 2 of 7
f. D695, Standard Test Method for Compressive Properties of Rigid Plastics.
g. D732, Standard Test Method for Shear Strength of Plastics by Punch Tool.
h. D790, Standard Test Methods for Flexural Properties of Unreinforced and
Reinforced Plastics and Electrical Insulating Materials.
B. Where reference is made to 1 of the above standards, the revision in effect at the time of
bid opening applies.
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 SUBMITTALS
A. Provide submittals in accordance with Section 01 33 00.
B. All submittals shall be approved by the City prior to delivery and/or fabrication for
specials.
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
A. Product Data
1. Submit manufacturer's Product Data on all product brands proposed for use to the
Engineer for review.
2. Include the manufacturer's installation and/or application instructions.
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE
A. When removing materials or portions of existing structures and when making openings
in existing structures, take precautions and all erect all necessary barriers, shoring and
bracing, and other protective devices to prevent damage to the structures beyond the
limits necessary for the new work, protect personnel, control dust, and to prevent
damage to the structures or contents by falling or flying debris.
B. Core sanitary sewer manhole penetrations.
1.10 DELIVERY, STORAGE, AND HANDLING
A. Deliver the specified products in original, unopened containers with the manufacturer's
name, labels, product identification, and batch numbers.
B. Store and condition the specified product as recommended by the manufacturer.
1.11 FIELD CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS
2.1 OWNER-FURNISHED OR OWNER-SUPPLIED PRODUCTS [NOT USED]
2.2 PRODUCT TYPES AND MATERIALS
A. Manufacturers
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 80 00 - 3
MODIFICATIONS TO EXISTING CONCRETE
Page 3 of 7
1. In other Part 2 articles where titles below introduce lists, the following requirements
apply to product selection:
a. Available Products
1) Subject to compliance with requirements, products that may be
incorporated into the Work include, but are not limited to, products
specified.
b. Available Manufacturers
1) Subject to compliance with requirements, manufacturers offering products
that may be incorporated into the Work include, but are not limited to,
manufacturers specified.
B. Materials
1. General
a. Comply with this Section and any state or local regulations.
C. Steel Reinforcement
1. Reinforcing Bars
a. ASTM A615, Grade 60, deformed.
D. Epoxy Bonding Agent
1. A 2-component, solvent-free, asbestos-free, moisture-insensitive epoxy resin
material used to bond plastic concrete to hardened concrete complying with the
requirements of ASTM C881, Type V, and the additional requirements specified
herein.
2. Properties of the cured material
a. Compressive Strength (ASTM D695)
1) 8,500 psi minimum at 28 days
b. Tensile Strength (ASTM D638)
1) 4,000 psi minimum at 14 days
c. Flexural Strength (ASTM D790 - Modulus of Rupture)
1) 6,300 psi minimum at 14 days
d. Shear Strength (ASTM D732)
1) 5,000 psi minimum at 14 days
e. Water Absorption (ASTM D570 - 2 hour boil)
1) 1 percent maximum at 14 days
f. Bond Strength (ASTM C882) Hardened to Plastic
1) 1,500 psi minimum at 14 days moist cure
g. Color
1) Gray
h. Available Manufacturers:
1) Sika Corporation, Lyndhurst, New Jersey - Sikadur 32, Hi-Mod
2) BASF, Cleveland, Ohio - Concresive 1438
E. Epoxy Paste
1. A 2-component, solvent-free, asbestos free, moisture insensitive epoxy resin
material used to bond dissimilar materials to concrete such as setting railing posts,
dowels, anchor bolts, and all-threads into hardened concrete and complying with
the requirements of ASTM C881, Type I, Grade 3, and the additional requirements
specified herein.
2. Properties of the cured material
a. Compressive Properties (ASTM D695): 10,000 psi minimum at 28 days
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 80 00 - 4
MODIFICATIONS TO EXISTING CONCRETE
Page 4 of 7
b. Tensile Strength (ASTM D638): 3,000 psi minimum at 14 days. Elongation at
Break - 0.3 percent minimum
c. Flexural Strength (ASTM D790 - Modulus of Rupture): 3,700 psi minimum at
14 days
d. Shear Strength (ASTM D732): 2,800 psi minimum at 14 days
e. Water Absorption (ASTM D570): 1.0 percent maximum at 7 days
f. Bond Strength (ASTM C882): 2,000 psi at 14 days moist cure
g. Color: Concrete grey
h. Available Manufacturers
1) Overhead Applications
a) Sika Corporation, Lyndhurst, New Jersey - Sikadur 32, Hi-Mod LV
b) BASF - Concresive 1438
2) All Other Applications
a) Sika Corporation, Lyndhurst, New Jersey - Sikadur Hi-mod LV 31
b) BASF - Concresive 1401
F. Repair Mortars
1. Provide an asbestos free, moisture insensitive, polymer-modified, Portland cement-
based cementitious trowel grade mortar for repairs on horizontal or vertical
surfaces.
a. Available Manufacturers
1) Sika Corporation, Lyndhurst New Jersey - SikaTop 122
2) BASF – Emaco Nanocrete R3
G. Pipe Penetration Sealants
1. 1 component polyurethane, extrudable swelling bentonite-free waterstop that is
chemically resistant, not soluble in water and capable of withstanding wet/dry
cycling.
a. Available Manufacturers
1) Sika Corporation, Lyndhurst New Jersey – SikaSwell S-2
2) Approved equal
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL [NOT USED]
PART 3 - EXECUTION
3.1 INSTALLERS [NOT USED]
3.2 EXAMINATION [NOT USED]
3.3 PREPARATION
A. General
1. Cut, repair, reuse, demolish, excavate or otherwise modify parts of the existing
structures or appurtenances, as indicated on the Drawings, specified herein, or
necessary to permit completion of the Work. Finishes, joints, reinforcements,
sealants, etc., are specified in respective Sections. Comply with other requirements
of this of Section and as shown on the Drawings.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 80 00 - 5
MODIFICATIONS TO EXISTING CONCRETE
Page 5 of 7
2. Store, mix, and apply all commercial products specified in this Section in strict
compliance with the manufacturer's recommendations.
3. Make repairs in all cases where concrete is repaired in the vicinity of an expansion
joint or control joint to preserve the isolation between components on either side of
the joint.
4. When drilling holes for dowels/bolts at new or existing concrete, stop drilling if
rebar is encountered and relocate the hole to avoid rebar as approved by the
Engineer. Do not cut rebar without prior approval by the Engineer.
B. Concrete Removal
1. Remove concrete designated to be removed to specific limits as shown on the
Drawings or directed by the Engineer, by chipping, jack-hammering, or saw-cutting
as appropriate in areas where concrete is to be taken out. Do not jackhammer
sanitary sewer manhole penetrations. Remove concrete in such a manner that
surrounding concrete or existing reinforcing to be left in place and existing in place
equipment is not damaged.
2. Where existing reinforcing is exposed due to saw cutting/core drilling and no new
material is to be placed on the sawcut surface, apply a coating or surface treatment
of epoxy paste to the entire cut surface to a thickness of 1/4 inch.
3. In all cases where the joint between new concrete or grout and existing concrete
will be exposed in the finished work, except as otherwise shown or specified,
provide a 1-inch deep saw cut on each exposed surface of the existing concrete at
the edge of concrete removal.
4. Repair concrete specified to be left in place that is damaged using approved means
to the satisfaction of the Engineer.
5. The Engineer may from time to time direct additional repairs to existing concrete.
Make these repairs as specified or by such other methods as may be appropriate.
C. Connection Surface Preparation
1. Prepare connection surfaces as specified below for concrete areas requiring
patching, repairs or modifications as shown on the Drawings, specified herein, or as
directed by the Engineer.
2. Remove all deteriorated materials, dirt, oil, grease, and all other bond inhibiting
materials from the surface by dry mechanical means, i.e., sandblasting, grinding,
etc., as approved by the Engineer. Be sure the areas are not less than 1/2-inch in
depth. Irregular voids or surface stones need not be removed if they are sound, free
of laitance, and firmly embedded into parent concrete, subject to the Engineer's
final inspection.
3. If reinforcing steel is exposed, it must be cleaned by wire brush or other similar
means to remove all contaminants, rust, etc., as approved by the Engineer. If 1/2 of
the diameter of the reinforcing steel is exposed, chip out behind the steel. Chip a
minimum of 1 inch behind the steel. Do not Damage reinforcing to be saved during
the demolition operation.
4. Clean reinforcing from existing demolished concrete that is shown to be
incorporated in new concrete by wire brush or other similar means to remove all
loose material and products of corrosion before proceeding with the repair. Cut,
bend, or lap to new reinforcing as shown on the Drawings and provided with 1-inch
minimum cover all around.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 80 00 - 6
MODIFICATIONS TO EXISTING CONCRETE
Page 6 of 7
5. The following are specific concrete surface preparation "methods" to be used where
called for on the Drawings, specified herein, or as directed by the Engineer.
a. Method A
1) After the existing concrete surface at connection has been roughened and
cleaned, thoroughly moisten the existing surface with water.
2) Brush on a 1/16-inch layer of cement and water mixed to the consistency of
a heavy paste.
3) Immediately after application of cement paste, place new concrete or grout
mixture as detailed on the Drawings.
b. Method B
1) After the existing concrete surface has been roughened and cleaned, apply
epoxy bonding agent at connection surface.
2) Comply strictly with the manufacturer's recommendations for the field
preparation and application of the epoxy bonding agent.
3) Place new concrete or grout mixture to limits shown on the Drawings
within time constraints recommended by the manufacturer to ensure bond.
c. Method C
1) Drill a hole 1/4 inch larger than the diameter of the dowel.
2) Blow the hole clear of loose particles and dust just prior to installing epoxy.
First fill the drilled hole with epoxy paste, then butter the dowels/bolts with
paste then insert by tapping.
3) Unless otherwise shown on the Drawings, drill and set deformed bars to a
depth of 10 bar diameters and smooth bars to a depth of 15 bar diameters.
4) If not noted on the Drawings, the Engineer will provide details regarding
the size and spacing of dowels.
d. Method D
1) Combination of Method B and C.
3.4 INSTALLATION [NOT USED]
3.5 REPAIR [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 FIELD QUALITY CONTROL [NOT USED]
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING [NOT USED]
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
03 80 00 - 7
MODIFICATIONS TO EXISTING CONCRETE
Page 7 of 7
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
31 10 00 - 1
SITE CLEARING
Page 1 of 6
1 SECTION 31 10 00
2 SITE CLEARING
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Preparation of right-of-way and other designated areas for construction operations
7 by removing and disposing of all obstructions including clearing and grubbing and
8 trees, when removal of such obstructions is not specifically shown on the Drawings
9 to be paid by other Sections.
10 B. Deviations from this City of Fort Worth Standard Specification
11 1. None.
12 C. Related Specification Sections include but are not necessarily limited to
13 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
14 2. Division 1 – General Requirements
15 3. Section 02 41 13 – Selective Site Demolition
16 4. Section 02 41 14 – Utility Removal/Abandonment
17 1.2 PRICE AND PAYMENT PROCEDURES
18 A. Measurement and Payment
19 1. Site Clearing
20 a. Measurement
21 1) Measurement for this Item shall be by lump sum, square yard, or per acre.
22 b. Payment
23 1) The work performed and the materials furnished in accordance with this
24 Item shall be paid for at the lump sum, square yard, or per acre price bid for
25 “Site Clearing”.
26 c. The price bid shall include:
27 1) Pruning of designated trees and shrubs
28 2) Removal and disposal of structures and obstructions (unless separate bid
29 item is provided under 02 41 13 “Selective Site Demolition or 02 41 14
30 “Utility Removal/Abandonment”).
31 3) Removal and disposal of trees under 6-inch in diameter when bidding by
32 lump sum or square yard
33 4) Removal of ALL trees when bidding by acre.
34 5) Backfilling of holes
35 6) Clean-up
36 2. Tree Removal (for trees 6-inch or larger in diameter when Site Clearing is bid by
37 lump sum or square yard)
38 a. Measurement
39 1) Measurement for this Item shall be per each.
40 2) Measurement of diameter for tree removal shall be at standard “Diameter at
41 Breast Height” or DBH, where Breast Height shall be 54” above grade.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
1 3)
2 b. Payment
31 10 00 - 2
SITE CLEARING
Page 2 of 6
3 1) The work performed and the materials furnished in accordance with this
4 Item shall be paid for at the unit price bid per each “Tree Removal” for:
5 a) Various diameter ranges
6 c. The price bid shall include:
7 1) Removal and disposal of tree, including removal of root to a depth at least 2
8 foot below grade
9 2) Grading and backfilling of holes
10 3) Excavation
11 4) Clean-up
12 3. Tree Removal and Transplantation
13 a. Measurement
14 1) Measurement for this Item shall be per each.
15 b. Payment
16 1) The work performed and the materials furnished in accordance with this
17 Item shall be paid for at the unit price bid per each “Tree Transplant” for:
18 a) Various diameter ranges
19 c. The price bid shall include:
20 1) Pruning of designated trees and shrubs
21 2) Moving tree with truck mounted tree spade
22 3) Grading and backfilling of holes
23 4) Replanting tree at temporary location (determined by Contractor)
24 5) Maintaining tree until Work is completed
25 6) Replanting tree into original or designated location
26 7) Excavation
27 8) Fertilization
28 9) Mulching
29 10) Watering
30 11) Clean-up
31 12) Warranty period
32 4. Tree Protection
33 a. Measurement
34 1) Measurement for this Item shall be per each as designated on Construction
35 Drawings for protection
36 b. Payment
37 1) The work performed and the materials furnished in accordance with this
38 Item shall be paid for at the unit price bid per each “Tree Protection” for:
39 a) Various caliper ranges
40 c. The price bid shall include:
41 1) Protection of tree utilizing measures designated on Construction Drawings
42 2) Installation of work of barriers as designated on Construction Drawings
43 3) Maintenance of protection measures throughout construction completed
44 4) Replanting tree into original or designated location
45 5) Excavation
46 6) Fertilization
47 7) Mulching
48 8) Clean-up including removal on constriction completion of protection
49 measures
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
1 5.
31 10 00 - 3
SITE CLEARING
Page 3 of 6
2 1.3 REFERENCES [NOT USED]
3 1.4 ADMINSTRATIVE REQUIREMENTS
4 A. Permits
5 1. Contractor shall obtain Tree Removal Permits and Urban Forestry Permits as
6 required by the City’s Tree Ordinance. PARD-Forestry details can be found here:
7 Forestry – Welcome to the City of Fort Worth (fortworthtexas.gov). Urban Forestry
8 Compliance's ordinance and requirements are within Zoning and can be found here:
9 Zoning – Welcome to the City of Fort Worth (fortworthtexas.gov).
10 B. Preinstallation Meetings
11 1. Hold a preliminary site clearing meeting and include the Contractor, City Forester
12 (if City owned tree) or representative of Urban Forestry if privately owned trees),
13 City Inspector, and the Project Manager for the purpose of reviewing the
14 Contractor’s tree removal plan. Clearly mark all trees to remain on the project site
15 prior to the meeting.
16 2. The Contractor will provide the City with a Disposal Letter in accordance to
17 Division 01.
18 1.5 SUBMITTALS [NOT USED]
19 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
20 1.7 CLOSEOUT SUBMITTALS [NOT USED]
21 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
22 1.9 QUALITY ASSURANCE [NOT USED]
23 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
24 1.11 FIELD CONDITIONS [NOT USED]
25 1.12 WARRANTY [NOT USED]
26 PART 2 - PRODUCTS [NOT USED]
27 PART 3 - EXECUTION
28 3.1 INSTALLERS [NOT USED]
29 3.2 EXAMINATION [NOT USED]
30 3.3 PREPARATION
31 A. All trees identified to be protected and/or preserved should be clearly flagged with
32 survey tape as per Construction Drawings.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
31 10 00 - 4
SITE CLEARING
Page 4 of 6
1 B. Following taping and prior to any removals or site clearing, the Contractor shall meet
2 with the City, the Engineer and the Landowner, if necessary, to confirm trees to be
3 saved.
4 3.4 INSTALLATION
5 A. Protection of Trees
6 1. Protect designated trees and prune trees and shrubs as shown on the Drawings.
7 Refer to the Drawings for tree protection details.
8 2. If the Drawings do not provide tree protection details, protected trees shall be
9 fenced by placing 6-foot tall metal T-posts in a square around the tree trunk with
10 the corners located on the canopy drip line, unless instructed otherwise.
11 3. When site conditions do not allow for the T-posts to be installed at the drip line, the
12 T-posts may be installed no less than 8 feet from the tree trunk. 4-foot high 12 ½
13 gauge stock fencing or orange plastic snow fence shall be attached to the T-posts to
14 form the enclosure.
15 4. For city-owned trees, PARD-Forestry permission required to install protective
16 fencing inside of canopy dripline (Critical Root Zone).
17 5.Additional trunk protection (cladding) is required when protective fencing is
18 approved within the Critical Root Zone.
19 6. Do not park equipment, service equipment, store materials, or disturb the root area
20 under the branches of trees designated for preservation.
21 7. When shown on the Drawings, treat cuts on trees with an approved tree wound
22 dressing within 30 minutes of making a pruning cut or otherwise causing damage to
23 the tree.
24 8. Trees and brush shall be mulched on-site.
25 a. Burning as a method of disposal is not allowed.
26 B. Hazardous Materials
27 1. The Contractor will notify the Engineer immediately if any hazardous or
28 questionable materials not shown on the Drawings are encountered. This includes;
29 but not limited to:
30 a. Floor tiles
31 b. Roof tiles
32 c. Shingles
33 d. Siding
34 e. Utility piping
35 2. The testing, removal, and disposal of hazardous materials will be in accordance
36 with Division 1.
37 C. Site Clearing
38 1. Clear areas shown on the Drawings of all obstructions, except those landscape
39 features that are to be preserved. Such obstructions include, but are not limited to:
40 a. Remains of buildings and other structures
41 b. Foundations
42 c. Floor slabs
43 d. Concrete
44 e. Brick
45 f. Lumber
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
31 10 00 - 5
SITE CLEARING
Page 5 of 6
1 g.Plaster
2 h.Septic tank drain fields
3 i.Abandoned utility pipes or conduits
4 j.Equipment
5 k.Trees
6 l.Fences
7 m.Retaining walls
8 n.Other items as specified on the Drawings
9 2. Remove vegetation and other landscape features not designated for preservation,
10 whether above or below ground, including, but not limited to:
11 a.Curb and gutter
12 b.Driveways
13 c.Paved parking areas
14 d.Miscellaneous stone
15 e.Sidewalks
16 f.Drainage structures
17 g.Manholes
18 h.Inlets
19 i.Abandoned railroad tracks
20 j.Scrap iron
21 k.Other debris
22 3. Remove culverts, storm sewers, manholes, and inlets in proper sequence to
23 maintain traffic and drainage in accordance with Section 02 41 14.
24 4. In areas receiving embankment, remove obstructions not designated for
25 preservation to 2 feet below natural ground.
26 5. In areas to be excavated, remove obstructions to 2 feet below the excavation level.
27 6. In all other areas, remove obstructions to 1 foot below natural ground.
28 7. When allowed by the Drawings or directed by the Engineer, cut trees and stumps
29 off to ground level.
30 a. Removal of existing structures shall be as per Section 02 41 13.
31 D. Disposal
32 1. Dispose of all trees within 24 hours of removal at an approved off-site facility.
33 2. All materials and debris removed becomes the property of the Contractor, unless
34 otherwise stated on the Drawings.
35 3. The Contractor will dispose of material and debris off-site in accordance with local,
36 state, and federal laws and regulations.
37 3.5 REPAIR [NOT USED]
38 3.6 RE-INSTALLATION [NOT USED]
39 3.7 FIELD QUALITY CONTROL [NOT USED]
40 3.8 SYSTEM STARTUP [NOT USED]
41 3.9 ADJUSTING [NOT USED]
42 3.10 CLEANING [NOT USED]
43 3.11 CLOSEOUT ACTIVITIES [NOT USED]
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
1 3.12 PROTECTION [NOT USED]
2 3.13 MAINTENANCE [NOT USED]
3 3.14 ATTACHMENTS [NOT USED]
31 10 00 - 6
SITE CLEARING
Page 6 of 6
4 END OF SECTION
5
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 D. Johnson 1.4.A Permits: Removed ordinance number and added City’s website address
3/22/2021 M Owen 1.2 Clarified measurement and payment. 1.4. Clarified administrative requirements.
3.4 Clarified additional installation requirements for tree protection and disposal.
6
Meacham Boulevard at Mercantile Drive
CPN 105417
31 23 16 - 1
UNCLASSIFIED EXCAVATION
Page 1 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised January 28, 2013
1 SECTION 31 23 16
2 UNCLASSIFIED EXCAVATION
3 [Text in Blue is for information or guidance. Remove all blue text in the final project document.]
4 PART 1 - GENERAL
5 1.1 SUMMARY
6 A. Section Includes:
7 1. Excavate areas as shown on the Drawings or as directed. Removal of materials
8 encountered to the lines, grades, and typical sections shown on the Drawings and
9 removal from site. Excavations may include construction of
10 a. Roadways
11 b. Drainage Channels
12 c. Site Excavation
13 d. Excavation for Structures
14 e. Or any other operation involving the excavation of on-site materials
15 B. Deviations from this City of Fort Worth Standard Specification
16 1. None.
17 C. Related Specification Sections include, but are not necessarily limited to:
18 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
19 2. Division 1 – General Requirements
20 3. Section 31 23 23 – Borrow
21 4. Section 31 24 00 – Embankments
22 1.2 PRICE AND PAYMENT PROCEDURES
23 A. Measurement and Payment [Measurement and payment method in this Specification
24 should coordinate with the method chosen in Section 31 23 23 and Section 31 24 00.]
25 1. Excavation by Plan Quantity [This method requires the Design Engineer to
26 estimate quantities. Care should be taken to verify calculation procedures are in
27 accordance with all Specification Sections.]
28 a. Measurement
29 1) Measurement for this Item shall be by the cubic yard in its final position
30 using the average end area method. Limits of measurement are shown on
31 the Drawings.
32 2) When measured by the cubic yard in its final position, this is a plans
33 quantity measurement Item. The quantity to be paid is the quantity shown
34 in the proposal, unless modified by Article 11.04 of the General
35 Conditions. Additional measurements or calculations will be made if
36 adjustments of quantities are required.
37 b. Payment
38 1) The work performed and materials furnished in accordance with this Item
39 and measured as provided under “Measurement” will be paid for at the unit
40 price bid per cubic yard of “Unclassified Excavation by Plan”. No
41 additional compensation will be allowed for rock or shrinkage/swell
42 factors, as these are the Contractor’s responsibility.
Meacham Boulevard at Mercantile Drive
CPN 105417
31 23 16 - 2
UNCLASSIFIED EXCAVATION
Page 2 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised January 28, 2013
1 c. The price bid shall include:
2 1) Excavation
3 2) Excavation Safety
4 3) Drying
5 4) Dust Control
6 5) Reworking or replacing the over excavated material in rock cuts
7 6) Hauling
8 7) Disposal of excess material not used elsewhere onsite
9 8) Scarification
10 9) Clean-up
11 2. Excavation by Surveyed Quantity [This method is intended for Projects in heavily
12 wooded areas or other areas where the accuracy required to determine quantities
13 for measurement and payment is unattainable during design.]
14 a. Measurement
15 1) Measurement for this Item shall be by the cubic yard in its final position
16 calculated using the average end area or composite method.
17 a) The City will perform a reference survey once the Site has been cleared
18 to obtain existing ground conditions.
19 b) The City will perform a final post-construction survey.
20 c) The Contractor will be paid for the cubic yardage of Excavated material
21 calculated as the difference between the two surveys.
22 d) Partial payments will be based on estimated plan quantity
23 measurements calculated by the Engineer.
24 b. Payment
25 1) The work performed and materials furnished in accordance with this Item
26 and measured as provided under “Measurement” will be paid for at the unit
27 price bid per cubic yard of “Unclassified Excavation by Survey”.
28 c. The price bid shall include:
29 1) Excavation
30 2) Excavation Safety
31 3) Drying
32 4) Dust Control
33 5) Reworking or replacing the over excavated material in rock cuts
34 6) Hauling
35 7) Disposal of excess material not used elsewhere onsite
36 8) Scarification
37 9) Clean-up
38 1.3 REFERENCES [NOT USED]
39 A. Definitions
40 1. Unclassified Excavation – Without regard to materials, all excavations shall be
41 considered unclassified and shall include all materials excavated. Any reference to
42 Rock or other materials on the Drawings or in the specifications is solely for the
43 City and the Contractor’s information and is not to be taken as a classification of
44 the excavation.
45 1.4 ADMINSTRATIVE REQUIREMENTS
46 A. The Contractor will provide the City with a Disposal Letter in accordance to Division
47 01.
Meacham Boulevard at Mercantile Drive
CPN 105417
31 23 16 - 3
UNCLASSIFIED EXCAVATION
Page 3 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised January 28, 2013
1 1.5 SUBMITTALS [NOT USED]
2 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
3 1.7 CLOSEOUT SUBMITTALS [NOT USED]
4 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
5 1.9 QUALITY ASSURANCE
6 A. Excavation Safety
7 1. The Contractor shall be solely responsible for making all excavations in a safe
8 manner.
9 2. All excavation and related sheeting and bracing shall comply with the requirements
10 of OSHA excavation safety standards 29 CFR part 1926 and state requirements.
11 1.10 DELIVERY, STORAGE, AND HANDLING
12 A. Storage
13 1. Within Existing Rights-of-Way (ROW)
14 a. Soil may be stored within existing ROW, easements or temporary construction
15 easements, unless specifically disallowed in the Contract Documents.
16 b. Do not block drainage ways, inlets or driveways.
17 c. Provide erosion control in accordance with Section 31 25 00.
18 d. When the Work is performed in active traffic areas, store materials only in
19 areas barricaded as provided in the traffic control plans.
20 e. In non-paved areas, do not store material on the root zone of any trees or in
21 landscaped areas.
22 2. Designated Storage Areas
23 a. If the Contract Documents do not allow the storage of spoils within the ROW,
24 easement or temporary construction easement, then secure and maintain an
25 adequate storage location.
26 b. Provide an affidavit that rights have been secured to store the materials on
27 private property.
28 c. Provide erosion control in accordance with Section 31 25 00.
29 d. Do not block drainage ways.
30 1.11 FIELD CONDITIONS
31 A. Existing Conditions
32 1. Any data which has been or may be provided on subsurface conditions is not
33 intended as a representation or warranty of accuracy or continuity between soils. It
34 is expressly understood that neither the City nor the Engineer will be responsible
35 for interpretations or conclusions drawn there from by the Contractor.
36 2. Data is made available for the convenience of the Contractor.
Meacham Boulevard at Mercantile Drive
CPN 105417
31 23 16 - 4
UNCLASSIFIED EXCAVATION
Page 4 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised January 28, 2013
1 1.12 WARRANTY [NOT USED]
2 PART 2 - PRODUCTS [NOT USED]
3 2.1 OWNER-FURNISHED [NOT USED]
4 2.2 PRODUCT TYPES AND MATERIALS
5 A. Materials
6 1. Unacceptable Fill Material
7 a. In-situ soils classified as ML, MH, PT, OL or OH in accordance with ASTM
8 D2487
9 PART 3 - EXECUTION
10 3.1 INSTALLERS [NOT USED]
11 3.2 EXAMINATION [NOT USED]
12 3.3 PREPARATION [NOT USED]
13 3.4 CONSTRUCTION
14 A. Accept ownership of unsuitable or excess material and dispose of material off-site
15 accordance with local, state, and federal regulations at locations.
16 B. Excavations shall be performed in the dry, and kept free from water, snow and ice
17 during construction with eh exception of water that is applied for dust control.
18 C. Separate Unacceptable Fill Material from other materials, remove from the Site and
19 properly dispose according to disposal plan.
20 D. Maintain drainage in the excavated area to avoid damage to the roadway sections and
21 proposed or existing structures.
22 E. Correct any damage to the subgrade caused by weather, at no additional cost to the
23 City.
24 F. Shape slopes to avoid loosening material below or outside the proposed grades.
25 Remove and dispose of slides as directed.
26 G. Rock Cuts
27 1. Excavate to finish grades.
28 2. In the event of over excavation due to contractor error below the lines and grades
29 established in the Drawings, use approved embankment material compacted in
30 accordance with Section 31 24 00 to replace the over excavated at no additional
31 cost to City.
32 H. Earth Cuts
33 1. Excavate to finish subgrade
Meacham Boulevard at Mercantile Drive
CPN 105417
31 23 16 - 5
UNCLASSIFIED EXCAVATION
Page 5 of 5
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised January 28, 2013
1 2. In the event of over excavation due to contractor error below the lines and grades
2 established in the Drawings, use approved embankment material compacted in
3 accordance with Section 31 24 00 to replace the over excavated at no additional
4 cost to City.
5 3. Manipulate and compact subgrade in accordance with Section 31 24 00.
6 3.5 REPAIR [NOT USED]
7 3.6 RE-INSTALLATION [NOT USED]
8 3.7 FIELD QUALITY CONTROL
9 A. Subgrade Tolerances
10 1. Excavate to within 0.1 foot in all directions.
11 2. In areas of over excavation, Contractor provides fill material approved by the City
12 at no expense to the City.
13 3.8 SYSTEM STARTUP [NOT USED]
14 3.9 ADJUSTING [NOT USED]
15 3.10 CLEANING [NOT USED]
16 3.11 CLOSEOUT ACTIVITIES [NOT USED]
17 3.12 PROTECTION [NOT USED]
18 3.13 MAINTENANCE [NOT USED]
19 3.14 ATTACHMENTS [NOT USED]
20 END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 D. Johnson 1.2 - Measurement and Payment Section modified; Blue Text added for clarification
1/28/13 D. Johnson 1.2 – Modified Bid Item names in payment section to differentiate between Payment
Methods on bid list.
21
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
31 25 00 - 1
EROSION AND SEDIMENT CONTROL
Page 1 of 9
1 SECTION 31 25 00
2 EROSION AND SEDIMENT CONTROL
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Implementation of the project’s Storm Water Pollution Prevention Plan (SWPPP)
7 and installation, maintenance, removal of erosion and sediment controls devices,
8 and establishment of final stabilization.
9 B. Deviations from this City of Fort Worth Standard Specification
10 1. None.
11 C. Related Specification Sections include, but are not necessarily limited to:
12 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
13 2. Division 1 – General Requirements
14 1.2 PRICE AND PAYMENT PROCEDURES
15 A. Measurement and Payment
16 1. Storm Water Pollution Prevention Plan <1 acre
17 a. Measurement
18 1) This Item is considered subsidiary to the various Items bid.
19 b. Payment
20 1) The work performed and the materials furnished in accordance with this
21 Item are subsidiary to the structure or Items being bid and no other
22 compensation will be allowed.
23 2. Storm Water Pollution Prevention Plan ≥ 1 acre
24 a. Measurement for this Item shall be by lump sum.
25 b. Payment
26 1) The work performed and the materials furnished in accordance with this
27 Item shall be paid for at the lump sum price bid for “SWPPP ≥ 1 acre”.
28 c. The price bid shall include:
29 1) Preparation of SWPPP
30 2) Implementation
31 3) Permitting fees
32 4) Installation
33 5) Maintenance
34 6) Removal
35 7) Obtaining and/or complying with grading and/or fill permits, if required
36 8) Final stabilization
37 1.3 REFERENCES
38 A. Reference Standards
39 1. Reference standards cited in this Specification refer to the current reference
40 standard published at the time of the latest revision date logged at the end of this
41 Specification, unless a date is specifically cited.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
1 2. ASTM Standard:
31 25 00 - 2
EROSION AND SEDIMENT CONTROL
Page 2 of 9
2 a. ASTM D3786, Standard Test Method for Bursting Strength of Textile
3 Fabrics—Diaphragm Bursting Strength Tester Method
4 b. ASTM D4632, Standard Test Method for Grab Breaking Load and Elongation
5 of Geotextiles
6 c. ASTM D4751, Standard Test Method for Determining Apparent Opening Size
7 of a Geotextile
8 d. ASTM D4833, Standard Test Method for Index Puncture Resistance of
9 Geomembranes and Related Products
10 3. Texas Commission on Environmental Quality (TCEQ) TPDES General Permit No.
11 TXR150000
12 4. TxDOT Departmental Material Specifications (DMS)
13 a. DMS-6230 “Temporary Sediment Control Fence Fabric”
14 1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
15 1.5 SUBMITTALS
16 A. Storm Water Pollution Prevention Plan (SWPPP)
17 B. TCEQ Notice of Intent (NOI) for Storm Water Discharges Associated with
18 Construction Activity under the TPDES General Permit
19 C. Construction Site Notice
20 D. TCEQ Notice of Termination (NOT) for Storm Water Discharges Associated with
21 Construction Activity under the TPDES General Permit
22 E. Notice of Change (if applicable)
23 F. Grading and/or fill permit, if required
24
25 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
26 1.7 CLOSEOUT SUBMITTALS [NOT USED]
27 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
28 1.9 QUALITY ASSURANCE [NOT USED]
29 1.10 DELIVERY, STORAGE AND HANDLING [NOT USED]
30 1.11 FIELD [SITE] CONDITIONS [NOT USED]
31 1.12 WARRANTY [NOT USED]
32 PART 2 - PRODUCTS
33 2.1 OWNER-FURNISHED [OR] OWNER-SUPPLIED PRODUCTS [NOT USED]
34 2.2 PRODUCT TYPES AND MATERIALS
35 A. Rock Filter Dams
36 1. Aggregate
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
31 25 00 - 3
EROSION AND SEDIMENT CONTROL
Page 3 of 9
1 a. Furnish aggregate with hardness, durability, cleanliness and resistance to
2 crumbling, flaking and eroding acceptable to the Engineer.
3 b. Provide the following:
4 1) Types 1, 2 and 4 Rock Filter Dams
5 a) Use 3 to 6 inch aggregate.
6 2) Type 3 Rock Filter Dams
7 a) Use 4 to 8 inch aggregate.
8 2. Wire
9 a. Provide minimum 20 gauge galvanized wire for the steel wire mesh and tie
10 wires for Types 2 and 3 rock filter dams
11 b. Type 4 dams require:
12 1) Double-twisted, hexagonal weave with a nominal mesh opening of 2½
13 inches x 3 ¼ inches
14 2) Minimum 0.0866 inch steel wire for netting
15 3) Minimum 0.1063 inch steel wire for selvages and corners
16 4) Minimum 0.0866 inch for binding or tie wire
17 B. Geotextile Fabric
18 1. Place the aggregate over geotextile fabric meeting the following criteria:
19 a. Tensile Strength of 250 pounds, per ASTM D4632
20 b. Puncture Strength of 135 pounds, per ASTM D4833
21 c. Mullen Burst Rate of 420 psi, per ASTM D3786
22 d. Apparent Opening Size of No. 20 (max), per ASTM D4751
23 C. Stabilized Construction Entrances
24 1. Provide materials that meet the details shown on the Drawings and this Section.
25 a. Provide crushed aggregate for long and short-term construction exits.
26 b. Furnish aggregates that are clean, hard, durable and free from adherent coatings
27 such as salt, alkali, dirt, clay, loam, shale, soft or flaky materials and organic
28 and injurious matter.
29 c. Use 3 to 5 inch coarse aggregate with a minimum thickness of 12 inches.
30 d. The aggregate shall be placed over a geotextile fabric meeting the following
31 criteria:
32 1) Tensile Strength of 300 pounds, per ASTM D4632
33 2) Puncture Strength of 120 pounds, per ASTM D4833
34 3) Mullen Burst Rate of 600 psi, per ASTM D3786
35 4) Apparent Opening Size of No. 40 (max), per ASTM D4751
36 D. Embankment for Erosion Control
37 1. Provide rock, loam, clay, topsoil or other earth materials that will form a stable
38 embankment to meet the intended use.
39 E. Sandbags
40 1. Provide sandbag material of polypropylene, polyethylene or polyamide woven
41 fabric with a minimum unit weight of 4 ounces per square yard, a Mullen burst-
42 strength exceeding 300 psi, and an ultraviolet stability exceeding 70 percent.
43 2. Use natural coarse sand or manufactured sand meeting the gradation given in Table
44 1 to fill sandbags.
45 3. Filled sandbags must be 24 to 30 inches long, 16 to 18 inches wide, and 6 to 8
46 inches thick.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
1 Table 1
2 Sand Gradation
31 25 00 - 4
EROSION AND SEDIMENT CONTROL
Page 4 of 9
Sieve #Maximum Retained (% by Weight)
4 3 percent
100 80 percent
200 95 percent
3 F. Temporary Sediment Control Fence
4 1. Provide a net-reinforced fence using woven geo-textile fabric.
5 2. Logos visible to the traveling public will not be allowed.
6 a. Fabric
7 1) Provide fabric materials in accordance with DMS-6230, “Temporary
8 Sediment Control Fence Fabric.”
9 b. Posts
10 1) Provide essentially straight wood or steel posts with a minimum length of
11 48 inches, unless otherwise shown on the Drawings.
12 2) Soft wood posts must be at least 3 inches in diameter or nominal 2 x 4 inch
13 3) Hardwood posts must have a minimum cross-section of 1-1/2 x 1-1/2 inch
14 4) T- or L-shaped steel posts must have a minimum weight of 1.3 pounds per
15 foot.
16 c. Net Reinforcement
17 1) Provide net reinforcement of at least 12-1/2 gauge galvanized welded wire
18 mesh, with a maximum opening size of 2 x 4 inch, at least 24 inches wide,
19 unless otherwise shown on the Drawings.
20 d. Staples
21 1) Provide staples with a crown at least 3/4 inch wide and legs 1/2 inch long.
22 2.3 ACCESSORIES [NOT USED]
23 2.4 SOURCE QUALITY CONTROL [NOT USED]
24 PART 3 - EXECUTION
25 3.1 INSTALLERS [NOT USED]
26 3.2 EXAMINATION [NOT USED]
27 3.3 PREPARATION [NOT USED]
28 3.4 INSTALLATION
29 A. Storm Water Pollution Prevention Plan
30 1. Develop and implement the project’s Storm Water Pollution Prevention Plan
31 (SWPPP) in accordance with the TPDES Construction General Permit TXR150000
32 requirements. Prevent water pollution from storm water runoff by using and
33 maintaining appropriate structural and nonstructural BMPs to reduce pollutants
34 discharges to the MS4 from the construction site.
35 B. Control Measures
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
31 25 00 - 5
EROSION AND SEDIMENT CONTROL
Page 5 of 9
1 1. Implement control measures in the area to be disturbed before beginning
2 construction, or as directed. Limit the disturbance to the area shown on the
3 Drawings or as directed.
4 2. Control site waste such as discarded building materials, concrete truck washout
5 water, chemicals, litter and sanitary waste at the construction site.
6 3. If, in the opinion of the Engineer, the Contractor cannot control soil erosion and
7 sedimentation resulting from construction operations, the Engineer will limit the
8 disturbed area to that which the Contractor is able to control.
9 4. Immediately correct ineffective control measures. Implement additional controls as
10 directed. Remove excavated material within the time requirements specified in the
11 applicable storm water permit.
12 5. Upon acceptance of vegetative cover by the City, remove and dispose of all
13 temporary control measures, temporary embankments, bridges, matting, falsework,
14 piling, debris, or other obstructions placed during construction that are not a part of
15 the finished work, or as directed.
16 C. Do not locate disposal areas, stockpiles, or haul roads in any wetland, water body, or
17 streambed.
18 D. Do not install temporary construction crossings in or across any water body without the
19 prior approval of the appropriate resource agency and the Engineer.
20 E. Provide protected storage area for paints, chemicals, solvents, and fertilizers at an
21 approved location. Keep paints, chemicals, solvents, and fertilizers off bare ground and
22 provide shelter for stored chemicals.
23 F. Installation and Maintenance
24 1. Perform work in accordance with the TPDES Construction General Permit
25 TXR150000.
26 2. When approved, sediments may be disposed of within embankments, or in areas
27 where the material will not contribute to further siltation and when appropriate
28 stabilization is provided.
29 3. Dispose of removed material in accordance with federal, state, and local
30 regulations.
31 4. Remove devices upon approval or when directed.
32 a. Upon removal, finish-grade and dress the area.
33 b. Stabilize disturbed areas in accordance with the permit, and as shown on the
34 Drawings or directed.
35 5. The Contractor retains ownership of stockpiled material and must remove it from
36 the project when new installations or replacements are no longer required.
37 G. Rock Filter Dams for Erosion Control
38 1. Remove trees, brush, stumps and other objectionable material that may interfere
39 with the construction of rock filter dams.
40 2. Place sandbags as a foundation when required or at the Contractor’s option.
41 3. For Types 1, 2, 3, and 5, place the aggregate to the lines, height, and slopes
42 specified, without undue voids.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
31 25 00 - 6
EROSION AND SEDIMENT CONTROL
Page 6 of 9
1 4. For Types 2 and 3, place the aggregate on the mesh and then fold the mesh at the
2 upstream side over the aggregate and secure it to itself on the downstream side with
3 wire ties, or hog rings, or as directed.
4 5. Place rock filter dams perpendicular to the flow of the stream or channel unless
5 otherwise directed.
6 6. Construct filter dams according to the following criteria, unless otherwise shown on
7 the Drawings:
8 a. Type 1 (Non-reinforced)
9 1) Height - At least 18 inches measured vertically from existing ground to top
10 of filter dam
11 2) Top Width - At least 2 feet
12 3) Slopes - At most 2:1
13 b. Type 2 (Reinforced)
14 1) Height - At least 18 inches measured vertically from existing ground to top
15 of filter dam
16 2) Top Width - At least 2 feet
17 3) Slopes - At most 2:1
18 c. Type 3 (Reinforced)
19 1) Height - At least 36 inches measured vertically from existing ground to top
20 of filter dam
21 2) Top Width - At least 2 feet
22 3) Slopes - At most 2:1
23 d. Type 4 (Sack Gabions)
24 1) Unfold sack gabions and smooth out kinks and bends.
25 2) For vertical filling, connect the sides by lacing in a single loop–double loop
26 pattern on 4- to 5-inches spacing. At 1 end, pull the end lacing rod until
27 tight, wrap around the end, and twist 4 times. At the filling end, fill with
28 stone, pull the rod tight, cut the wire with approximately 6 inches
29 remaining, and twist wires 4 times.
30 3) For horizontal filling, place sack flat in a filling trough, fill with stone, and
31 connect sides and secure ends as described above.
32 4) Lift and place without damaging the gabion.
33 5) Shape sack gabions to existing contours.
34 e. Type 5
35 1) Provide rock filter dams as shown on the Drawings.
36 H. Construction Entrances
37 1. When tracking conditions exist, prevent traffic from crossing or exiting the
38 construction site or moving directly onto a public roadway, alley, sidewalk, parking
39 area, or other right of way areas other than at the location of construction entrances.
40 2. Place the exit over a foundation course, if necessary.
41 a. Grade the foundation course or compacted subgrade to direct runoff from the
42 construction exits to a sediment trap as shown on the Drawings or as directed.
43 3. At drive approaches, make sure the construction entrance is the full width of the
44 drive and meets the length shown on the Drawings.
45 a. The width shall be at least 14 feet for 1-way and 24 feet for 2-way traffic for all
46 other points of ingress or egress or as directed by the Engineer.
47 I. Earthwork for Erosion Control
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
31 25 00 - 7
EROSION AND SEDIMENT CONTROL
Page 7 of 9
1 1. Perform excavation and embankment operations to minimize erosion and to remove
2 collected sediments from other erosion control devices.
3 a. Excavation and Embankment for Erosion Control Measures
4 1) Place earth dikes, swales or combinations of both along the low crown of
5 daily lift placement, or as directed, to prevent runoff spillover.
6 2) Place swales and dikes at other locations as shown on the Drawings or as
7 directed to prevent runoff spillover or to divert runoff.
8 3) Construct cuts with the low end blocked with undisturbed earth to prevent
9 erosion of hillsides.
10 4) Construct sediment traps at drainage structures in conjunction with other
11 erosion control measures as shown on the Drawings or as directed.
12 5) Where required, create a sediment basin providing 3,600 cubic feet of
13 storage per acre drained, or equivalent control measures for drainage
14 locations that serve an area with 10 or more disturbed acres at 1 time, not
15 including offsite areas.
16 b. Excavation of Sediment and Debris
17 1) Remove sediment and debris when accumulation affects the performance of
18 the devices, after a rain, and when directed.
19 2) Remove sediment from sediment traps and sedimentation ponds no later
20 than the time that design capacity has been reduced by 50%.
21 J. Sandbags for Erosion Control
22 1. Construct a berm or dam of sandbags that will intercept sediment-laden storm water
23 runoff from disturbed areas, create a retention pond, detain sediment and release
24 water in sheet flow.
25 2. Fill each bag with sand so that at least the top 6 inches of the bag is unfilled to
26 allow for proper tying of the open end.
27 3. Place the sandbags with their tied ends in the same direction.
28 4. Offset subsequent rows of sandbags 1/2 the length of the preceding row.
29 5. Place a single layer of sandbags downstream as a secondary debris trap.
30 6. Place additional sandbags as necessary or as directed for supplementary support to
31 berms or dams of sandbags or earth.
32 K. Temporary Sediment-Control Fence
33 1. Provide temporary sediment-control fence near the downstream perimeter of a
34 disturbed area to intercept sediment from sheet flow.
35 2. Incorporate the fence into erosion-control measures used to control sediment in
36 areas of higher flow. Install the fence as shown on the Drawings, as specified in this
37 Section, or as directed by the Engineer or City representative.
38 a. Post Installation
39 1) Embed posts at least 18 inches deep, or adequately anchor, if in rock, with a
40 spacing of 6 to 8 feet and install on a slight angle toward the run-off source.
41 b. Fabric Anchoring
42 1) Dig trenches along the uphill side of the fence to anchor 6 to 8 inches of
43 fabric.
44 2) Provide a minimum trench cross-section of 6 x 6 inches
45 3) Place the fabric against the side of the trench and align approximately 2
46 inches of fabric along the bottom in the upstream direction.
47 4) Backfill the trench, then hand-tamp.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
1 c. Fabric and Net Reinforcement Attachment
31 25 00 - 8
EROSION AND SEDIMENT CONTROL
Page 8 of 9
2 1) Unless otherwise shown under the Drawings, attach the reinforcement to
3 wooden posts with staples, or to steel posts with T-clips, in at least 4 places
4 equally spaced.
5 2) Sewn vertical pockets may be used to attach reinforcement to end posts.
6 3) Fasten the fabric to the top strand of reinforcement by hog rings or cord
7 every 15 inches or less.
8 d. Fabric and Net Splices
9 1) Locate splices at a fence post with a minimum lap of 6 inches attached in at
10 least 6 places equally spaced, unless otherwise shown under the Drawings.
11 a) Do not locate splices in concentrated flow areas.
12 2) Requirements for installation of used temporary sediment-control fence
13 include the following:
14 a) Fabric with minimal or no visible signs of biodegradation (weak fibers)
15 b) Fabric without excessive patching (more than 1 patch every 15 to 20
16 feet)
17 c) Posts without bends
18 d) Backing without holes
19 3.5 REPAIR/RESTORATION [NOT USED]
20 3.6 RE-INSTALLATION [NOT USED]
21 3.7 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
22 3.8 SYSTEM STARTUP [NOT USED]
23 3.9 ADJUSTING [NOT USED]
24 3.10 CLEANING
25 A. Waste Management
26 1. Remove sediment, debris and litter as needed.
27 3.11 CLOSEOUT ACTIVITIES
28 A. Erosion control measures remain in place and are maintained until all soil disturbing
29 activities at the project site have been completed.
30 B. Establish a uniform vegetative cover with a density of 70 percent on all unpaved areas,
31 on areas not covered by permanent structures, or in areas where permanent erosion
32 control measures (i.e. riprap, gabions, or geotextiles) have been employed.
33 C. Once vegetative cover is achieved, the contractor shall remove all temporary control
34 measures, before final project acceptance. It is the contractor’s responsibility to remove
35 all temporary control measures, unless transfer of maintenance and subsequent removal
36 is transferred to another entity in writing.
37 D. Upon achievement of final stabilization, submit NOT to TCEQ, and provide a copy of
38 the NOT to the City of Fort Worth’'s Environmental Quality Division, if required.
39 E. Complete and submit a Final Grading Certificate to Development Services, if required.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised April 29, 2021
Birchman Office Space
CPN 105553
1 3.12 PROTECTION [NOT USED]
2 3.13 MAINTENANCE
31 25 00 - 9
EROSION AND SEDIMENT CONTROL
Page 9 of 9
3 A. Install and maintain the integrity of temporary erosion and sedimentation control
4 devices to accumulate silt and debris until earthwork construction and permanent
5 erosion control features are in place or the disturbed area has been adequately stabilized
6 as determined by the Engineer.
7 B. If a device ceases to function as intended, repair or replace the device or portions
8 thereof as necessary.
9 C. Perform inspections of the construction site as prescribed in the Construction General
10 Permit TXR150000.
11 D. Records of inspections and modifications based on the results of inspections must be
12 maintained and available in accordance with the permit.
13 3.14 ATTACHMENTS [NOT USED]
14 END OF SECTION
15
Revision Log
DATE NAME SUMMARY OF CHANGE
April 29, 2021 M Owen
1.1 A. 1. Revised language re: what section includes, 1.2 A. 2. c. Clarified items
included in price, 1.5 Added items to list of submittals, 2.2Revised language under
product types/materials, 3.4 Revised language under “ Installation”, and 3.11 C.
Added language to clarify responsibility to remove temporary protection device and
emphasize clearing of ROW
16
Meacham Boulevard at Mercantile Drive
CPN 105417
32 11 23 - 1
FLEXIBLE BASE COURSES
Page 1 of 7
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
SECTION 32 11 23
FLEXIBLE BASE COURSES
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Foundation course for surface course or for other base course composed of flexible
base constructed in one or more courses in conformity with the typical section.
B. Deviations from this City of Fort Worth Standard Specification
1. None
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms, and Conditions of the
Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Measurement
a. Measurement for this Item will be by the square yard of Flexible Base Course
for various:
1) Depths
2) Types
3) Gradations
2. Payment
a. The work performed and materials furnished in accordance with this Item and
measured as provided under “Measurement” will be paid for at the unit price
bid per square yard of Flexible Base Course.
3. The price bid shall include:
a. Preparation and correction of subgrade
b. Furnishing of material
c. Hauling
d. Blading
e. Sprinkling
f. Compacting
1.3 REFERENCES
A. Definitions
1. RAP – Recycled Asphalt Pavement.
B. Reference Standards
1. Reference standards cited in this specification refer to the current reference standard
published at the time of the latest revision date logged at the end of this
specification, unless a date is specifically cited.
2. ASTM International (ASTM):
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 11 23 - 2
FLEXIBLE BASE COURSES
Page 2 of 7
a. D698, Standard Test Methods for Laboratory Compaction Characteristics of
Soil Using Standard Effort (12 400 ft-lbf/ft3 (600 kN-m/m3))
3. Texas Department of Transportation (TXDOT):
a. Tex-104-E, Determining Liquid Limits of Soils
b. Tex-106-E, Calculating the Plasticity Index of Soils
c. Tex-107-E, Determining the Bar Linear Shrinkage of Soils
d. Tex-110-E, Particle Size Analysis of Soils
e. Tex-116-E, Ball Mill Method for Determining the Disintegration of Flexible
Base Material
f. Tex-117-E, Triaxial Compression for Disturbed Soils and Base Materials
g. Tex-411-A, Soundness of Aggregate Using Sodium Sulfate or Magnesium
Sulfate
h. Tex-413-A, Determining Deleterious Material in Mineral Aggregate
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 ACTION SUBMITTALS [NOT USED]
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS [NOT USED]
2.1 OWNER-FURNISHED PRODUCTS [NOT USED]
2.2 MATERIALS
A. General
1. Furnish uncontaminated materials of uniform quality that meet the requirements of
the Drawings and specifications.
2. Obtain materials from approved sources.
3. Notify City of changes to material sources.
4. The City may sample and test project materials at any time before compaction
throughout the duration of the project to assure specification compliance.
B. Aggregate
1. Furnish aggregate of the type and grade shown on the Drawings and conforming to
the requirements of Table 1.
2. Each source must meet Table 1 requirements for liquid limit, plastiCity index, and
wet ball mill for the grade specified.
3. Do not use additives such as but not limited to lime, cement, or fly ash to modify
aggregates to meet the requirements of Table 1, unless shown on the Drawings.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 11 23 - 3
FLEXIBLE BASE COURSES
Page 3 of 7
Table 1
Material Requirements
Property Test Method Grade 1 Grade 2
Master gradation sieve
size (% retained)
2-1/2 in.–0
1-3/4 in.0 0–10
7/8 in.10–35 –
3/8 in.30–50 –
No. 4 45–65 45–75
No. 40
Tex-110-E
70–85 60–85
Liquid limit, % max.1 Tex-104-E 35 40
PlastiCity index, max.1 Tex-106-E 10 12
Wet ball mill, % max.2 40 45
Wet ball mill, % max.
increase passing the
No. 40 sieve
Tex-116-E 20 20
Classification3 1.0 1.1–2.3
Min. compressive
strength3, psi
lateral pressure 0 psi 45 35
lateral pressure 15 psi
Tex-117-E
175 175
1. Determine plastic index in accordance with Tex-107-E (linear
shrinkage) when liquid limit is unattainable as defined in
Tex-104-E.
2. When a soundness value is required by the Drawings, test
material in accordance with Tex-411-A.
3. Meet both the classification and the minimum compressive
strength, unless otherwise shown on the Drawings.
4. Material Tolerances
a. The City may accept material if no more than 1 of the 5 most recent gradation
tests has an individual sieve outside the specified limits of the gradation.
b. When target grading is required by the Drawings, no single failing test may
exceed the master grading by more than 5 percentage points on sieves No. 4
and larger or 3 percentage points on sieves smaller than No. 4.
c. The City may accept material if no more than 1 of the 5 most recent plasticity
index tests is outside the specified limit. No single failing test may exceed the
allowable limit by more than 2 points.
5. Material Types
a. Do not use fillers or binders unless approved.
b. Furnish the type specified on the Drawings in accordance with the following:
1) Type A
a) Crushed stone produced and graded from oversize quarried aggregate
that originates from a single, naturally occurring source.
b) Do not use gravel or multiple sources.
2) Type B
a) Only for use as base material for temporary pavement repairs.
b) Do not exceed 20 percent RAP by weight unless shown on Drawings.
3) Type D
a) Type A material or crushed concrete.
b) Crushed concrete containing gravel will be considered Type D
material.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 11 23 - 4
FLEXIBLE BASE COURSES
Page 4 of 7
c) The City may require separate dedicated stockpiles in order to verify
compliance.
d) Crushed concrete must meet the following requirements:
(1) Table 1 for the grade specified.
(2) Recycled materials must be free from reinforcing steel and other
objectionable material and have at most 1.5 percent deleterious
material when tested in accordance with TEX-413-A.
C. Water
1. Furnish water free of industrial wastes and other objectionable matter.
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL [NOT USED]
PART 3 - EXECUTION
3.1 INSTALLERS [NOT USED]
3.2 EXAMINATION [NOT USED]
3.3 PREPARATION
A. General
1. Shape the subgrade or existing base to conform to the typical sections shown on the
Drawings or as directed.
2. When new base is required to be mixed with existing base:
a. Deliver, place, and spread the new flexible base in the required amount.
b. Manipulate and thoroughly mix the new base with existing material to provide
a uniform mixture to the specified depth before shaping.
B. Subgrade Compaction
1. Proof roll the roadbed before pulverizing or scarifying in accordance with the
following:
a. Proof Rolling
1) City Project Representative must be on-site during proof rolling operations.
2) Use equipment that will apply sufficient load to identify soft spots that rut
or pump.
a) Acceptable equipment includes fully loaded single-axle water truck
with a 1500 gallon capacity.
3) Make at least 2 passes with the proof roller (down and back = 1 pass).
4) Offset each trip by at most 1 tire width.
5) If an unstable or non-uniform area is found, correct the area.
b. Correct
1) Soft spots that rut or pump greater than 3/4 inch
2) Areas that are unstable or non-uniform
2. Installation of base material cannot proceed until compacted subgrade approved by
the City.
3.4 INSTALLATION
A. General
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 11 23 - 5
FLEXIBLE BASE COURSES
Page 5 of 7
1. Construct each layer uniformly, free of loose or segregated areas, and with the
required density and moisture content.
2. Provide a smooth surface that conforms to the typical sections, lines, and grades
shown on the Drawings or as directed.
3. Haul approved flexible base in clean, covered trucks.
B. Equipment
1. General
a. Provide machinery, tools, and equipment necessary for proper execution of the
work.
2. Rollers
a. The Contractor may use any type of roller to meet the production rates and
quality requirements of the Contract unless otherwise shown on the Drawings
or directed.
b. When specific types of equipment are required, use equipment that meets the
specified requirements.
c. Alternate Equipment.
1) Instead of the specified equipment, the Contractor may, as approved,
operate other compaction equipment that produces equivalent results.
2) Discontinue the use of the alternate equipment and furnish the specified
equipment if the desired results are not achieved.
d. City may require Contractor to substitute equipment if production rate and
quality requirements of the Contract are not met.
C. Placing
1. Spread and shape flexible base into a uniform layer by approved means the same
day as delivered unless otherwise approved.
2. Place material such that it is mixed to minimize segregation.
3. Construct layers to the thickness shown on the Drawings, while maintaining the
shape of the course.
4. Where subbase or base course exceeds 6 inches in thickness, construct in 2 or more
courses of equal thickness.
5. Minimum lift depth: 3 inches
6. Control dust by sprinkling.
7. Correct or replace segregated areas as directed.
8. Place successive base courses and finish courses using the same construction
methods required for the first course.
D. Compaction
1. General
a. Compact using density control unless otherwise shown on the Drawings.
b. Multiple lifts are permitted when shown on the Drawings or approved.
c. Bring each layer to the moisture content directed. When necessary, sprinkle the
material to the extent necessary to provide not less than the required density.
d. Compact the full depth of the subbase or base to the extent necessary to remain
firm and stable under construction equipment.
2. Rolling
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 11 23 - 6
FLEXIBLE BASE COURSES
Page 6 of 7
a. Begin rolling longitudinally at the sides and proceed towards the center,
overlapping on successive trips by at least 1/2 the width of the roller unit.
b. On superelevated curves, begin rolling at the low side and progress toward the
high side.
c. Offset alternate trips of the roller.
d. Operate rollers at a speed between 2 and 6 mph as directed.
e. Rework, recompact, and refinish material that fails to meet or that loses
required moisture, density, stability, or finish before the next course is placed or
the project is accepted.
f. Continue work until specification requirements are met.
g. Proof roll the compacted flexible base in accordance with the following:
1) Proof Rolling
a) City Project Representative must be on-site during proof rolling
operations.
b) Use equipment that will apply sufficient load to identify soft spots that
rut or pump.
(1) Acceptable equipment includes fully loaded single-axle water truck
with a 1500 gallon capacity.
c) Make at least 2 passes with the proof roller (down and back = 1 pass).
d) Offset each trip by at most 1 tire width.
e) If an unstable or non-uniform area is found, correct the area.
2) Correct
a) Soft spots that rut or pump greater than 3/4 inch.
b) Areas that are unstable or non-uniform.
3. Tolerances
a. Maintain the shape of the course by blading.
b. Completed surface shall be smooth and in conformity with the typical sections
shown on the Drawings to the established lines and grades.
c. For subgrade beneath paving surfaces, correct any deviation in excess of 1/4
inch in cross section in length greater than 16 feet measured longitudinally by
loosening, adding or removing material. Reshape and recompact by sprinkling
and rolling.
d. Correct all fractures, settlement or segregation immediately by scarifying the
areas affected, adding suitable material as required. Reshape and recompact by
sprinkling and rolling.
e. Should the subbase or base course, due to any reason, lose the required
stability, density and finish before the surfacing is complete, it shall be
recompacted at the sole expense of the Contractor.
4. Density Control
a. Minimum Density: 95 percent compaction as determined by ASTM D698.
b. Moisture content: minus 2 to plus 4 of optimum.
E. Finishing
1. After completing compaction, clip, skin, or tight-blade the surface with a
maintainer or subgrade trimmer to a depth of approximately 1/4 inch.
2. Remove loosened material and dispose of it at an approved location.
3. Seal the clipped surface immediately by rolling with an appropriate size pneumatic
tire roller until a smooth surface is attained.
4. Add small increments of water as needed during rolling.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 11 23 - 7
FLEXIBLE BASE COURSES
Page 7 of 7
5. Shape and maintain the course and surface in conformity with the typical sections,
lines, and grades as shown on the Drawings or as directed.
6. In areas where surfacing is to be placed, correct grade deviations greater than 1/4
inch in 16 feet measured longitudinally or greater than 1/4 inch over the entire
width of the cross-section.
7. Correct by loosening, adding, or removing material.
8. Reshape and recompact in accordance with 3.4.C.
3.5 REPAIR/RESTORATION [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 QUALITY CONTROL
A. Density Test
1. City to measure density of flexible base course.
a. Notify City Project Representative when flexible base ready for density testing.
b. Spacing directed by City (1 per block minimum).
c. City Project Representative determines location of density testing.
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING [NOT USED]
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 1
CONCRETE PAVING
Page 1 of 22
1 SECTION 32 13 13
2 CONCRETE PAVING
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A.Section includes:
6 1. Finished pavement constructed of Portland cement concrete including
7 monolithically poured curb on the prepared subgrade or other base course.
8 B.Deviations from this City of Fort Worth Standard Specification
9 1. None.
10 C.Related Specification Sections include, but are not necessarily limited to:
11 1. Division 0 - Procurement and Contracting Requirements
12 2. Division 1 - General Requirements
13 3. Section 32 01 29 - Concrete Paving Repair
14 4. Section 32 13 73 - Concrete Paving Joint Sealants
15 1.2 PRICE AND PAYMENT PROCEDURES
16 A.Measurement
17 1. Measurement
18 a. Measurement for this Item shall be by the square yard of completed and
19 accepted Concrete Pavement in its final position as measured from back of curb
20 for various:
21 1) Classes
22 2) Thicknesses
23 2. Payment
24 a. The work performed and materials furnished in accordance with this Item will
25 be paid for at the unit price bid per square yard of Concrete Pavement.
26 3. The price bid shall include:
27 a.Shaping and fine grading the placement area
28 b.Furnishing and applying all water required
29 c.Furnishing, loading and unloading, storing, hauling and handling all concrete
30 ingredients including all freight and royalty involved
31 d.Mixing, placing, finishing and curing all concrete
32 e.Furnishing and installing all reinforcing steel
33 f.Furnishing all materials and placing longitudinal, warping, expansion, and
34 contraction joints, including all steel dowels, dowel caps and load transmission
35 units required, wire and devices for placing, holding and supporting the steel
36 bar, load transmission units, and joint filler material in the proper position; for
37 coating steel bars where required by the Drawings
38 g.Sealing joints
39 h.Monolithically poured curb
40 i.Cleanup
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 2
CONCRETE PAVING
Page 2 of 22
1 1.3 REFERENCES
2 A.Reference Standards
3 1. Reference standards cited in this specification refer to the current reference standard
4 published at the time of the latest revision date logged at the end of this
5 specification, unless a date is specifically cited.
6 2. ASTM International (ASTM):
7 a. A615/A615M, Deformed and Plain Billet-Steel Bars for Concrete
8 Reinforcement
9 b. C31, Standard Practice for Making and Curing Concrete Test Specimens in the
10 Field
11 c. C33, Concrete Aggregates
12 d. C39, Standard Test Method for Compressive Strength of Cylindrical Concrete
13 Specimens
14 e. C42, Standard Test Method for Obtaining and Testing Drilled Cores and Sawed
15 Beams of Concrete
16 f. C94/C94M, Standard Specifications for Ready-Mixed Concrete
17 g. C150, Portland Cement
18 h. C595, Portland-Limestone Cement
19 i. C156, Standard Test Method for Water Loss (from a mortar specimen) Through
20 Liquid Membrane-Forming Curing Compounds for Concrete
21 j. C172, Standard Practice for Sampling Freshly Mixed Concrete
22 k. C260, Air Entraining Admixtures for Concrete
23 l. C309, Liquid Membrane-Forming Compounds for Curing Concrete, Type 2
24 m. C494, Chemical Admixtures for Concrete, Types “A”, “D”, “F” and “G”
25 n. C618, Coal Fly Ash and Raw or Calcined Natural Pozzolan for use as a Mineral
26 Admixture in Concrete
27 o. C881, Standard Specification for Epoxy-Resin-Base Bonding Systems for
28 Concrete
29 p. C1064, Standard Test Method for Temperature of Freshly Mixed Hydraulic-
30 Cement Concrete
31 q. C1602, Standard Specification for Mixing Water Used in the Production of
32 Hydraulic Cement Concrete.
33 r. D698, Laboratory Compaction Characteristics of Soil Using Standard Effort
34 (12,400 ft-lbf/ft3)
35 3. American Concrete Institute (ACI):
36 a. ACI 305.1-14 Specification for Hot Weather Concreting
37 b. ACI 306.1-90, Standard Specification for Cold Weather Concreting
38 c. ACI 318, Building Code Requirements for Structural Concrete and Commentary
39 1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
40 1.5 SUBMITTALS [NOT USED]
41 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
42 A. Mix Design: submit for approval. See Item 2.4.A.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 3
CONCRETE PAVING
Page 3 of 22
1 1.7 CLOSEOUT SUBMITTALS [NOT USED]
2 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
3 1.9 QUALITY ASSURANCE [NOT USED]
4 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
5 1.11 FIELD CONDITIONS
6 A.Weather Conditions
7 1. Place concrete when concrete temperature is between 40F and 95°F when
8 measured in accordance with ASTM C1064 at point of placement.
9 2. Hot Weather Concreting
10 a. Concrete paving operations shall be approved by the City project manager or
11 designee when the concrete temperature exceeds 95F.
12 b. Concrete shall not be placed when concrete temperature is above 100°F under
13 any circumstances.
14 3. Cold Weather Concreting
15 a. No concrete shall be placed when ambient temp in shade and away from
16 artificial heat is below 40F and falling. Concrete may be placed when ambient
17 temp is above 35F and rising. Unless the City project manager or designee
18 approves paving to continue, suspend concreting operations if a descending air
19 temperature in the shade and away from artificial heat falls below 40F. Do not
20 resume concreting operations until an ascending air temperature in the shade and
21 away from artificial heat reaches 35F and rising. Contractor should take all the
22 precautions necessary to prevent freezing of concrete. Frozen concrete must be
23 removed and replaced.
24 4. It is to be distinctly understood that the contractor is responsible for the quality and
25 strength of the concrete placed under any weather conditions.
26 B.Time: Place concrete after sunrise and no later than shall permit the finishing of the
27 pavement in natural light, or as directed by the City.
28 1.12 WARRANTY [NOT USED]
29 PART 2 - PRODUCTS
30 2.1 OWNER-FURNISHED PRODUCTS [NOT USED]
31 2.2 MATERIALS
32 A.Cementitious Material: ASTM C150, ASTM C595 Type IL Cement.
33 B.Aggregates: ASTM C33.
34 C.Water: ASTM C1602.
35 D.Admixtures: When admixtures are used, conform to the appropriate specification:
36 1. Air-Entraining Admixtures for Concrete: ASTM C260.
37 2. Chemical Admixtures for Concrete: ASTM C494, Types “A”, “D”, “F” and “G.”
38 3. Fly Ash
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 4
CONCRETE PAVING
Page 4 of 22
1 a. Coal Fly Ash and Raw or Calcined Natural Pozzolan for Use in Concrete:
2 ASTM C618.
3 b. Fly ash may be substituted at one pound per pound of cement up to 25% of the
4 specified cement content when such batch design is approved by the Engineer.
5 E. Steel Reinforcement: ASTM A615.
6 F. Steel Wire Reinforcement: Not used for concrete pavement.
7 G.Dowels and Tie Bars
8 1. Dowel and tie bars: ASTM A615.
9 2. Dowel Caps
10 a. Provide and install dowel caps with enough range of movement to allow
11 complete closure of the expansion joint.
12 b. Caps for dowel bars shall be of the length shown on the Drawings and shall have
13 an internal diameter sufficient to permit the cap to freely slip over the bar.
14 c. In no case shall the internal diameter exceed the bar diameter by more 1/8 inch,
15 and one end of the cap shall be tightly closed.
16 3. Epoxy for Dowel and Tie Bars: ASTM C881.
17 a. See following table for approved producers of epoxies and adhesives
18
Pre-Qualified Producers of Epoxies and Adhesives
Product Name Producer
Concresive 1420 BASF
HTE-50 Hilti
T 308 +Powers Fasteners
P E 1000+Powers Fasteners
C-6 Ramset-Redhead
Epcon G-5 Ramset-Redhead
Pro-Poxy-300 Fast Tube Unitex
Shep-Poxy TxIII CMC Construction Services
Ultrabond 1300 Tubes Adhesives Technology
Ultrabone 2300 N.S. A-22-2300
Slow Set Adhesives Technology
Dynapoxy EP-430 Pecora Corp.
EDOT Simpson Strong Tie
ET22 Simpson Strong Tie
SET 22 Simpson Strong Tie
SpecPoxy 3000FS SpecChem
19
20 b. Epoxy Use, Storage and Handling
21 1) Package components in airtight containers and protect from light and
22 moisture.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 5
CONCRETE PAVING
Page 5 of 22
1 2) Include detailed instructions for the application of the material and all
2 safety information and warnings regarding contact with the components.
3 3) Epoxy label requirements
4 a) Resin or hardener components
5 b) Brand name
6 c) Name of manufacturer
7 d) Lot or batch number
8 e) Temperature range for storage
9 f) Date of manufacture
10 g) Expiration date
11 h) Quantity contained
12 4) Store epoxy and adhesive components at temperatures recommended by the
13 manufacturer.
14 5) Do not use damaged or previously opened containers and any material that
15 shows evidence of crystallization, lumps skinning, extreme thickening, or
16 settling of pigments that cannot be readily dispersed with normal agitation.
17 6) Follow sound environmental practices when disposing of epoxy and
18 adhesive wastes.
19 7) Dispose of all empty containers separately.
20 8) Dispose of epoxy by completely emptying and mixing the epoxy before
21 disposal
22 H.Reinforcement Bar Chairs
23 1. Reinforcement bar chairs or supports shall be of adequate strength to support the
24 reinforcement bars and shall not bend or break under the weight of the
25 reinforcement bars or Contractor’s personnel walking on the reinforcing bars.
26 2. Bar chairs may be made of metal (free of rust), precast mortar or concrete blocks or
27 plastic.
28 3. For approval of plastic chairs, representative samples of the plastic shall show no
29 visible indications of deterioration after immersion in a 5-percent solution of
30 sodium hydroxide for 120-hours.
31 4. Bar chairs may be rejected for failure to meet any of the requirements of this
32 specification.
33 I. Joint Filler
34 1. Joint filler is the material placed in concrete pavement and concrete structures to
35 allow for the expansion and contraction of the concrete.
36 2. Wood Boards: Used as joint filler for concrete paving.
37 a. Boards for expansion joint filler shall be of the required size, shape and type
38 indicated on the Drawings or required in the specifications.
39 1) Boards shall be of selected stock of redwood or cypress. The boards shall
40 be sound heartwood and shall be free from sapwood, knots, clustered
41 birdseyes, checks and splits.
42 2) Joint filler, boards, shall be smooth, flat and straight throughout, and shall
43 be sufficiently rigid to permit ease of installation.
44 3) Boards shall be furnished in lengths equal to the width between
45 longitudinal joints, and may be furnished in strips or scored sheet of the
46 required shape.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 6
CONCRETE PAVING
Page 6 of 22
1 3. Dimensions. The thickness of the expansion joint filler shall be shown on the
2 Drawings; the width shall be not less than that shown on the Drawings, providing
3 for the top seal space.
4 4. Rejection. Expansion joint filler may be rejected for failure to meet any of the
5 requirements of this specification.
6 J. Joint Sealants. Provide Joint Sealants in accordance with Section 32 13 73.
7 K.Curing Materials
8 1. Membrane-Forming Compounds.
9 a. Conform to the requirements of ASTM C309, Type 2, white pigmented
10 compound and be of such nature that it shall not produce permanent
11 discoloration of concrete surfaces nor react deleteriously with the concrete.
12 b. The compound shall produce a firm, continuous uniform moisture-impermeable
13 film free from pinholes and shall adhere satisfactorily to the surfaces of damp
14 concrete.
15 c. It shall, when applied to the damp concrete surface at the specified rate of
16 coverage, dry to touch in 1 hour and dry through in not more than 4 hours under
17 normal conditions suitable for concrete operations.
18 d. It shall adhere in a tenacious film without running off or appreciably sagging.
19 e. It shall not disintegrate, check, peel or crack during the required curing period.
20 f. The compound shall not peel or pick up under traffic and shall disappear from
21 the surface of the concrete by gradual disintegration.
22 g. The compound shall be delivered to the job site in the manufacturer's original
23 containers only, which shall be clearly labeled with the manufacturer's name, the
24 trade name of the material and a batch number or symbol with which test
25 samples may be correlated.
26 h. When tested in accordance with ASTM C156 Standard Test Method for Water
27 Loss (from a mortar specimen) Through Liquid Membrane-Forming Curing
28 Compounds for Concrete, the liquid membrane-forming compound shall restrict
29 the loss of water present in the test specimen at the time of application of the
30 curing compound to not more than 0.01-oz.-per-2 inches of surface.
31 2.3 ACCESSORIES [NOT USED]
32 2.4 SOURCE QUALITY CONTROL
33 A.Mix Design
34 1. Concrete Mix Design and Control
35 a. The City has a pre-approved list of concrete mix designs. The pre-approved list
36 can be found on the City website under Project Resources Folder. These mix
37 designs meet the requirements of applicable City specifications and the
38 Contractor may use mix designs from the list without the need for review and
39 approval. The contractor shall notify the City in writing which mix in the pre-
40 approved list the contractor uses for a project.
41 b. For a mix design not included in the pre-approved list, the Contractor shall
42 submit a design of the concrete mix it proposes to use and a full description of
43 the source of supply of each material component at least 10 calendar days prior
44 to the start of concrete paving operations.
45 c. The design of the concrete mix shall produce a quality concrete complying with
46 these specifications and shall include the following information:
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 1) Design Requirements and Design Summary
2 2) Material source
3 3) Dry weight of cement/cubic yard and type
4 4) Dry weight of fly ash/cubic yard and type, if used
32 13 13 - 7
CONCRETE PAVING
Page 7 of 22
5 5) Saturated surface dry weight of fine and coarse aggregates/cubic yard
6 6) Design water/cubic yard
7 7) Quantities, type, and name of admixtures with manufacturer's data sheets
8 8) Current strength tests or strength tests in accordance with ACI 318
9 9) Current Sieve Analysis and -200 Decantation of fine and coarse aggregates
10 and date of tests
11 10) Fineness modulus of fine aggregate
12 11) Specific Gravity and Absorption Values of fine and coarse aggregates
13 12) L.A. Abrasion of coarse aggregates
14 d. Once mix design approved by City, maintain intent of mix design and
15 maximum water to cement ratio.
16 e. No concrete may be placed on the job site until the mix design has been
17 approved by the City.
18 2. Quality of Concrete
19 a. Consistency
20 1) In general, the consistency of concrete mixtures shall be such that:
21 a) Mortar shall cling to the coarse aggregate
22 b) Aggregate shall not segregate in concrete when it is transported to the
23 place of deposit
24 c) Concrete, when dropped directly from the discharge chute of the mixer,
25 shall flatten out at the center of the pile, but the edges of the pile shall
26 stand and not flow
27 d) Concrete and mortar shall show no free water when removed from the
28 mixer
29 e) Concrete shall slide and not flow into place when transported in metal
30 chutes at an angle of 30 degrees with the horizontal
31 f) Surface of the finished concrete shall be free from a surface film or
32 laitance
33 2) When field conditions are such that additional moisture is needed for the
34 final concrete surface finishing operation, the required water shall be applied
35 to the surface by hand sprayer only and be held to a minimum amount.
36 3) The concrete shall be workable, cohesive, possess satisfactory finishing
37 qualities and be of the stiffest consistency that can be placed and vibrated into
38 a homogeneous mass.
39 4) Excessive bleeding shall be avoided.
40 5) If the strength or consistency required for the class of concrete being
41 produced is not secured with the minimum cement specified or without
42 exceeding the maximum water/cement ratio, the Contractor may use, or the
43 City may require, an approved cement dispersing agent (water reducer); or
44 the Contractor shall furnish additional aggregates, or aggregates with
45 different characteristics, or the Contractor may use additional cement in
46 order to produce the required results.
47 6) The additional cement may be permitted as a temporary measure, until
48 aggregates are changed and designs checked with the different aggregates
49 or cement dispersing agent.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 8
CONCRETE PAVING
Page 8 of 22
1 7) The Contractor is solely responsible for the quality of the concrete
2 produced.
3 8) The City reserves the right to independently verify the quality of the
4 concrete through inspection of the batch plant, testing of the various
5 materials used in the concrete and by casting and testing concrete cylinders
6 or beams on the concrete actually incorporated in the pavement.
7 b. Standard Class
8 1) Unless otherwise shown on the Drawings or detailed specifications, the
9 standard class for pavement and related concrete for streets and alleys is
10 shown in the following table:
11
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 9
CONCRETE PAVING
Page 9 of 22
1 Standard Classes of Pavement and Related Concrete
2 1.All exposed horizontal concrete shall have a minimum of 3% entrained-air.
3 2.Minimum Compressive Strength Required.
4
5 a)Concrete Sidewalks and Curb & Gutter: Class A
6 b)Cast-In-Place Concrete Structures: Class CIP and Class C
7 c)Machine-Laid concrete: Class P
8 d)Hand-Laid concrete: Class H
9 e)Structural Concrete: Class S
10 f)High Early Strength Concrete: Class HES
11 (1) When shown on the Drawings or allowed, provide Class HES
12
13
14
15
16
17
18
19 c. Slump
concrete for very early opening of pavements area or leave outs to
traffic.
(2) Design class HES to meet the requirements of class specified for
concrete pavement and a minimum compressive strength of 2,600
psi in 24 hours, unless other early strength and time requirements
are shown on the Drawings allowed.
20 1) Slump requirements for pavement and related concrete shall be as specified
21 in the following table:
22
23 Concrete Pavement and Related Concrete Slump Requirements Add classes of
24 concrete
Concrete Use
Recommended
Design
and Placement
Slump,
Acceptable
Placement Slump,
(Inch)
Class of
Concrete
1
Minimum
Cementitiou
s
(Lb. /CY)
28 Day
Min.
Compressi
ve
Strength2
(Psi)
Max.
w/cm
Ratio
Course
Aggregat
e
Maximu
m
Size
(Inch)
General Usage
(Informational Only)
A 470 3,000 0.58 1-1/2
Sidewalks and ADA
ramps, driveways, curb
& gutter, median
pavement
CIP 470 3.000 0.50 1-1/2
Inlets, manholes,
junction boxes,
encasement, blocking,
collars, light pole
foundations
C 517 3,600 0.45 1-1/2 Headwalls, wingwalls,
culverts, drilled shafts
P 517 3,600 0.45 1-1/2 Machine placed Paving
H 564 4,500 0.45 1-1/2 Hand Placed Paving
HES 564 4,500 0.45 1-1/2 HES Paving
S 564 4,000 0.45 1-1/2
Bridge slabs, top slabs of
direct traffic culverts,
approach slabs
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 10
CONCRETE PAVING
Page 10 of 22
(Inch)
Slip-Form/Form-Riding Paving 1-1/2 1 – 3
Hand Formed Paving 4 3 – 5
Headwalls, wingwalls, culverts, inlets,
manholes, junction boxes, encasement,
blocking, collars, light pole foundations,
slabs, sidewalk, curb and gutter, concrete
valley gutter and other miscellaneous
concrete
4 3 – 5
Drilled shafts 61/2 51/2 – 71 2/
1
2 2) No concrete shall be permitted with slump in excess of the maximums
3 shown.
4 3) Any concrete mix failing to meet the above consistency requirements,
5 although meeting the slump requirements, shall be considered unsatisfactory,
6 and the mix shall be changed to correct such unsatisfactory conditions.
7 PART 3 - EXECUTION
8 3.1 INSTALLERS [NOT USED]
9 3.2 EXAMINATION [NOT USED]
10 3.3 PREPARATION [NOT USED]
11 3.4 INSTALLATION
12 A.Equipment
13 1. All equipment necessary for the construction of this item shall be on the project.
14 2. The equipment shall include spreading devices (augers), internal vibration,
15 tamping, and surface floating necessary to finish the freshly placed concrete in such
16 a manner as to provide a dense and homogeneous pavement.
17 3. Machine-Laid Concrete Pavement
18 a. Fixed-Form Paver. Fixed-form paving equipment shall be provided with forms
19 that are uniformly supported on a sufficiently firm subbase to prevent sagging
20 under the weight of machine.
21 b. Slip-Form Paver
22 1) Slip-form paving equipment shall be provided with traveling side forms of
23 sufficient dimensions, shape and strength so as to support the concrete
24 laterally for a sufficient length of time during placement.
25 2) City may reject use of Slip-Form Paver if paver requires over-digging and
26 impacts trees, mailboxes or other improvements.
27 4. Hand-Laid Concrete Pavement
28 a. Machines that do not incorporate these features, such as roller screeds or
29 vibrating screeds, shall be considered tools to be used in hand-laid concrete
30 construction, as slumps, spreading methods, vibration, and other procedures are
31 more common to hand methods than to machine methods.
32 5. City may reject equipment and stop operation if equipment does not meet
33 requirements.
34 B.Concrete Mixing and Delivery
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 1. Transit Batching: shall not be used – onsite mixing not permitted
2 2. Ready Mixed Concrete
32 13 13 - 11
CONCRETE PAVING
Page 11 of 22
3 a. The concrete shall be produced in an approved method conforming to the
4 requirements of this specification and ASTM C94/C94M.
5 b. City shall have access to ready mix plant to obtain material samples.
6 c. When ready-mix concrete is used, sample concrete per ASTM C172 Alternate
7 Procedure 2:
8 1) As the mixer is being emptied, individual samples shall be taken after the
9 discharge of approximately 10 percent and 90 percent of the load.
10 2) The method of sampling shall provide that the samples are representative of
11 widely separated portions, but not from the very ends of the batch.
12 d. The mixing of each batch, after all materials are in the drum, shall continue until
13 it produces a thoroughly mixed concrete of uniform mass as determined by
14 established mixer performance ratings and inspection, or appropriate uniformity
15 tests as described in ASTM C94.
16 e. The entire contents of the drum shall be discharged before any materials are
17 placed therein for the succeeding batch.
18 f. Retempering or remixing shall not be permitted.
19 3. Delivery
20 a. Deliver concrete at an interval not exceeding 30 minutes or as determined by
21 City to prevent cold joint.
22 4. Delivery Tickets
23 a. For all operations, the manufacturer of the concrete shall, before unloading,
24 furnish to the purchaser with each batch of concrete at the site a delivery ticket
25 on which is printed, stamped, or written, the following information to determine
26 that the concrete was proportioned in accordance with the approved mix design:
27 1) Name of concrete supplier
28 2) Serial number of ticket
29 3) Date
30 4) Truck number
31 5) Name of purchaser
32 6) Specific designation of job (name and location)
33 7) Specific class, design identification and designation of the concrete in
34 conformance with that employed in job specifications
35 8) Amount of concrete in cubic yards
36 9) Time loaded or of first mixing of cement and aggregates
37 10) Water added by receiver of concrete
38 11) Type and amount of admixtures
39 C.Subgrade
40 1. When manipulation or treatment of subgrade is required on the Drawings, the work
41 shall be performed in proper sequence with the preparation of the subgrade for
42 pavement.
43 2. The roadbed shall be excavated and shaped in conformity with the typical sections
44 and to the lines and grades shown on the Drawings or established by the City.
45 3. All holes, ruts and depressions shall be filled and compacted with suitable material
46 and, if required, the subgrade shall be thoroughly wetted and reshaped.
47 4. Irregularities of more than 1/2 inch., as shown by straightedge or template, shall be
48 corrected.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 12
CONCRETE PAVING
Page 12 of 22
1 5. The subgrade shall be uniformly compacted to at least 95 percent of the maximum
2 density as determined by ASTM D698.
3 6. Moisture content shall be within minus 2 percent to plus 4 percent of optimum.
4 7. The prepared subgrade shall be wetted down sufficiently in advance of placing the
5 pavement to ensure its being in a firm and moist condition.
6 8. Sufficient subgrade shall be prepared in advance to ensure satisfactory prosecution
7 of the work.
8 9. The Contractor shall notify the City at least 24 hours in advance of its intention to
9 place concrete pavement.
10 10. After the specified moisture and density are achieved, the Contractor shall maintain
11 the subgrade moisture and density in accordance with this Section.
12 11. In the event that rain or other conditions may have adversely affected the condition
13 of the subgrade or base, additional tests may be required as directed by the City.
14 D.Placing and Removing Forms
15 1. Placing Forms
16 a. Forms for machine-laid concrete
17 1) The side forms shall be metal, of approved cross section and bracing, of a
18 height no less than the prescribed edge thickness of the concrete section, and a
19 minimum of 10 feet in length for each individual form.
20 2) Forms shall be of ample strength and staked with adequate number of pins
21 capable of resisting the pressure of concrete placed against them and the
22 thrust and the vibration of the construction equipment operating upon them
23 without appreciable springing, settling or deflection.
24 3) The forms shall be free from warps, bends or kinks and shall show no
25 variation from the true plane for face or top.
26 4) Forms shall be jointed neatly and tightly and set with exactness to the
27 established grade and alignment.
28 5) Forms shall be set to line and grade at least 200 feet, where practicable, in
29 advance of the paving operations.
30 6) In no case shall the base width be less than 8 inches for a form 8 inches or
31 more in height.
32 7) Forms must be in firm contact with the subgrade throughout their length
33 and base width.
34 8) If the subgrade becomes unstable, forms shall be reset, using heavy stakes
35 or other additional supports may be necessary to provide the required
36 stability.
37 b. Forms for hand-laid concrete
38 1) Forms shall extend the full depth of concrete and be a minimum of 1-1/2
39 inches in thickness or equivalent when wooden forms are used, or be of a
40 gauge that shall provide equivalent rigidity and strength when metal forms are
41 used.
42 2) For curves with a radius of less than 250 feet, acceptable flexible metal or
43 wood forms shall be used.
44 3) All forms showing a deviation of 1/8 inch in 10 feet from a straight line
45 shall be rejected.
46 2. Settling. When forms settle over 1/8 inch under finishing operations, paving
47 operations shall be stopped the forms reset to line and grade and the pavement then
48 brought to the required section and thickness.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 3. Cleaning. Forms shall be thoroughly cleaned after each use.
2 4. Removal.
32 13 13 - 13
CONCRETE PAVING
Page 13 of 22
3 a. Forms shall remain in place until the concrete has taken its final set.
4 b. Avoid damage to the edge of the pavement when removing forms.
5 c. Repair damage resulting from form removal and honeycombed areas with a
6 mortar mix within 24 hours after form removal unless otherwise approved.
7 d. Clean joint face and repair honeycombed or damaged areas within 24 hours
8 after a bulkhead for a transverse construction joint has been removed unless
9 otherwise approved.
10 e. When forms are removed before 72 hours after concrete placement, promptly
11 apply membrane curing compound to the edge of the concrete pavement.
12 E. Placing Reinforcing Steel, Tie, and Dowel Bars
13 1. General
14 a. When reinforcing steel tie bars, dowels, etc., are required they shall be placed as
15 shown on the Drawings.
16 b. All reinforcing steel shall be clean, free from rust in the form of loose or
17 objectionable scale, and of the type, size and dimensions shown on the
18 Drawings.
19 c. Reinforcing bars shall be securely wired together at the alternate intersections
20 and all splices and shall be securely wired at each intersection dowel and load-
21 transmission unit intersected.
22 d. All bars shall be installed in their required position as shown on the Drawings.
23 e. The storing of reinforcing or structural steel on completed roadway slabs
24 generally shall be avoided and, where permitted, such storage shall be limited to
25 quantities and distribution that shall not induce excessive stresses.
26 2. Splices
27 a. Provide standard reinforcement splices by lapping and tying ends.
28 b. Comply with ACI 318 for minimum lap of spliced bars where not specified on
29 the Drawings.
30 3. Installation of Reinforcing Steel
31 a. All reinforcing bars and bar mats shall be installed in the slab at the required
32 depth below the finished surface and supported by and securely attached to bar
33 chairs installed on prescribed longitudinal and transverse centers as shown by
34 sectional and detailed drawings on the Drawings.
35 b. Chairs Assembly. The chair assembly shall be similar and equal to that shown
36 on the Drawings and shall be approved by the City prior to extensive fabrication.
37 c. After the reinforcing steel is securely installed above the subgrade as specified
38 in Drawings and as herein prescribed, no loading shall be imposed upon the bar
39 mats or individual bars before or during the placing or finishing of the concrete.
40 4. Installation of Dowel Bars
41 a. Install through the predrilled joint filler and rigidly support in true horizontal
42 and vertical positions by an assembly of bar chairs and dowel baskets.
43 b. Dowel Baskets
44 1) The dowels shall be held in position exactly parallel to surface and
45 centerline of the slab, by a dowel basket that is left in the pavement.
46 2) The dowel basket shall hold each dowel in exactly the correct position so
47 firmly that the dowel’s position cannot be altered by concreting operations.
48 c. Dowel Caps
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 14
CONCRETE PAVING
Page 14 of 22
1 1) Install cap to allow the bar to move not less than 1-1/4 inch in either
2 direction. Grease bar before adding cap to prevent bonding with the concrete.
3 5. Tie Bar and Dowel Placement
4 a. Place at mid-depth of the pavement slab, parallel to the surface.
5 b. Place as shown on the Drawings.
6 6. Epoxy for Tie and Dowel Bar Installation
7 1) Epoxy bars as shown on the Drawings.
8 2) Use only drilling operations that do not damage the surrounding structures.
9 3) Blow out drilled holes with compressed air.
10 4) Completely fill the drilled hole with approved epoxy before inserting the tie
11 bar into the hole.
12 5) Install epoxy grout and bar at least 6 inches embedded into concrete.
13 F. Joints
14 1. Joints shall be placed where shown on the Drawings or where directed by the City.
15 2. The plane of all joints shall make a right angle with the surface of the pavement.
16 3. No joints shall have an error in alignment of more than 1/2 inch at any point.
17 4. Joint Dimensions
18 a. The width of the joint shall be shown on the Drawings, creating the joint
19 sealant reservoir.
20 b. The depth of the joint shall be shown on the Drawings.
21 c. Dimensions of the sealant reservoir shall be in accordance with manufacturer’s
22 recommendations.
23 d. After curing, the joint sealant shall be 1/8 inch to 1/4 inch below the pavement
24 surface at the center of the joint.
25 5. Transverse Expansion Joints
26 a. Expansion joints shall be installed perpendicularly to the surface and to the
27 centerline of the pavement at the locations shown on the Drawings, or as
28 approved by the City. Expansion joints shall continue to the farthest outside
29 edge of paving and adjacent slabs, and should extend through monolithic or
30 attached curbs so that there is no restriction to the movement of the joint at any
31 point.
32 b. Joints shall be of the design width, and spacing shown on the Drawings, or as
33 approved by the City.
34 c. Dowel bars, shall be of the size and type shown on the Drawings, or as
35 approved by the City, and shall be installed at the specified spacing.
36 d. Support dowel bars with dowel baskets.
37 e. Dowels shall not restrict the free opening and closing of the expansion join and
38 shall not make planes of weaknesses in the pavement.
39 f. Greased Dowels for Expansion Joints.
40 1) Coat dowels with a thin film of grease or other approved de-bonding
41 material.
42 2) Provide dowel caps on the lubricated end of each dowel bar.
43 g. Proximity to Existing Structures. When the pavement is adjacent to or around
44 existing structures, expansions joints shall be constructed in accordance with the
45 details shown on the Drawings.
46 6. Transverse Contraction Joints
47 a. Contraction or dummy joints shall be installed at the locations and at the
48 intervals shown on the Drawings.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 15
CONCRETE PAVING
Page 15 of 22
1 b. Joints shall be of the design width, and spacing shown on the Drawings, or as
2 approved by the City.
3 c. Dowel bars, shall be of the size and type shown on the Drawings, or as
4 approved by the City, and shall be installed at the specified spacing.
5 d. Saw joints in a single cut to the width and depth the plans show. Begin sawing
6 as soon as the concrete hardens sufficiently to prevent excessive raveling along
7 the saw cut and finish before conditions induce uncontrolled cracking.
8 e. The joints shall be constructed by sawing to a 1/4 - inch width and to a depth of
9 1/4 of the actual pavement thickness, or deeper if so indicated on the Drawings.
10 f. Complete sawing as soon as possible in hot weather conditions and within a
11 maximum of 24 hours after saw cutting begins under cool weather conditions.
12 g. If sharp edge joints are being obtained, the sawing process shall be sped up to
13 the point where some raveling is observed.
14 h. Damage by blade action to the slab surface and to the concrete immediately
15 adjacent to the joint shall be minimized.
16 i. Any portion of the curing membrane which has been disturbed by sawing
17 operations shall be restored by spraying the areas with additional curing
18 compound.
19 7. Transverse Construction Joints
20 a. Construction joints formed at the close of each day’s work or when the placing
21 of concrete has been interrupted for 30-minutes or longer shall be constructed
22 by use of metal or wooden bulkheads cut true to the section of the finished
23 pavement and cleaned.
24 b. Wooden bulkheads shall be constructed using material of a thickness not less
25 than nominal 2” lumber.
26 c. Longitudinal bars shall be held securely in place in a plane perpendicular to the
27 surface and at right angles to the centerline of the pavement.
28 d. Edges shall be rounded to 1/4-inch radius.
29 e. Any surplus concrete on the subgrade shall be removed upon the resumption of
30 the work.
31 8. Longitudinal Construction Joints
32 a. Longitudinal construction joints shall be of the type shown on the Drawings.
33 9. Joint Filler
34 a. Joint filler shall be as specified in 2.2.I of the size and shape shown on the
35 Drawings.
36 b. Redwood Board joints shall be used for all pavement joints except for
37 expansion joints that are coincident with a butt joint against existing
38 pavements.
39 c. Boards with less than 25-percent of moisture at the time of installation shall be
40 thoroughly wetted on the job.
41 d. Green lumber of much higher moisture content is desirable and acceptable.
42 e. The joint filler shall be appropriately drilled to admit the dowel bars when
43 required.
44 f. The bottom edge of the filler shall extend to or slightly below the bottom of the
45 slab. The top edge shall be held not less than 1/2 inch below the finished
46 surface of the pavement in order to allow the finishing operations to be
47 continuous.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 16
CONCRETE PAVING
Page 16 of 22
1 g. The joint filler may be composed of more than one length of board in the
2 length of joint, but no board of a length less than 6 foot may be used unless
3 otherwise shown on the Drawings.
4 h. After the removal of the side forms, the ends of the joints at the edges of the
5 slab shall be carefully opened for the entire depth of the slab.
6 10. Joint Sealing. Routine pavement joints shall be filled consistent with paving details
7 and as specified in Section 32 13 73. Materials shall generally be handled and
8 applied according to the manufacturer’s recommendations as specified in Section
9 32 13 73.
10 G.Placing Concrete
11 1. Unless otherwise specified in the Drawings, the finished pavement shall be
12 constructed monolithically and constructed by machined laid method unless
13 impractical. The City will make determination of what is practical. The maximum
14 length of concrete lane that can be placed by hand pouring is 50 linear feet.
15 2. The concrete shall be rapidly deposited on the subgrade in successive batches and
16 shall be distributed to the required depth and for the entire width of the pavement
17 by approved methods.
18 3. Any concrete not placed as herein prescribed within the time limits in the following
19 table will be rejected. Time begins when the water is added to the mixer.
20 Temperature – Time Requirements
Concrete Temperature
(at point of placement)
Max Time – minutes
(no retarding agent)
Max Time – minutes
(with retarding agent)1
Non-Agitated Concrete
All temperatures 45 45
Agitated Concrete
Above 90°F 45 75
Above 75°F thru 90°F 60 90
75°F and Below 60 120
21 1 Normal dosage of retarder.
22
23 4. Rakes shall not be used in handling concrete.
24 5. At the end of the day, or in case of unavoidable interruption or delay of more than
25 30 minutes or longer to prevent cold joints, a transverse construction joint shall be
26 placed in accordance with 3.4.F.7 of this Section.
27 6. Honeycombing
28 a. Special care shall be taken in placing and vibrating the concrete against the
29 forms and at all joints and assemblies so as to prevent honeycombing Concrete
30 shall be uniformly consolidated throughout its width and depth, free from honey
31 combed areas, and has a consistent void-free closed surface.
32 b. Excessive voids and honeycombing in the edge of the pavement, revealed by the
33 removal of the side forms, may be cause for rejection of the section of slab in
34 which the defect occurs.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 H.Finishing
2 1. Machine
3 a. Tolerance Limits
32 13 13 - 17
CONCRETE PAVING
Page 17 of 22
4 1) While the concrete is still workable, it shall be tested for irregularities with
5 a 10-foot straightedge placed parallel to the centerline of the pavement so as
6 to bridge depressions and to touch all high spots.
7 2) Ordinates measured from the face of the straightedge to the surface of the
8 pavement shall at no place exceed 1/16 inch-per-foot from the nearest point of
9 contact.
10 3) In no case shall the maximum ordinate to a 10-foot straightedge be greater
11 than 1/8 inch.
12 4) Any surface not within the tolerance limits shall be reworked and
13 refinished.
14 b. Edging
15 1) The edges of slabs and all joints requiring edging shall be carefully tooled
16 with an edger of the radius required by the Drawings at the time the concrete
17 begins to take its “set” and becomes non-workable.
18 2) All such work shall be left smooth and true to lines.
19 2. Hand
20 a. Hand finishing permitted only in intersections and areas inaccessible to a
21 finishing machine.
22 b. When the hand method of striking off and consolidating is permitted, the
23 concrete, as soon as placed, shall be approximately leveled and then struck off
24 with screed bar to such elevation above grade that, when consolidated and
25 finished, the surface of the pavement shall be at the grade elevation shown on
26 the Drawings.
27 .
28 c. The straightedge and joint finishing shall be as prescribed herein.
29 I. Curing
30 1. The curing of concrete pavement shall be thorough and continuous throughout the
31 entire curing period.
32 2. Failure to provide proper curing as herein prescribed shall be considered as
33 sufficient cause for immediate suspension of the paving operations.
34 3. The curing method as herein specified does not preclude the use of any of the other
35 commonly used methods of curing, and the City may approve another method of
36 curing if so requested by the Contractor.
37 4. If any selected method of curing does not afford the desired results, the City shall
38 have the right to order that another method of curing be instituted.
39 5. After removal of the side forms, the sides of the slab shall receive a like coating
40 before earth is banked against them.
41 6. The solution shall be applied, under pressure with a spray nozzle, in such a manner
42 as to cover the entire surfaces thoroughly and completely with a uniform film.
43 7. The rate of application shall be such as to ensure complete coverage and shall not
44 exceed 20-square-yards-per-gallon of curing compound.
45 8. When thoroughly dry, it shall provide a continuous and flexible membrane, free
46 from cracks or pinholes, and shall not disintegrate, check, peel or crack during the
47 curing period.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 18
CONCRETE PAVING
Page 18 of 22
1 9. If for any reason the seal is broken during the curing period, it shall be immediately
2 repaired with additional sealing solution.
3 10. When tested in accordance with ASTM C156 Standard Test Method for Water Loss
4 (from a mortar specimen) Through Liquid Membrane-Forming Curing Compounds
5 for Concrete, the curing compound shall provide a film which shall have retained
6 within the test specimen a percentage of the moisture present in the specimen when
7 the curing compound was applied according to the following.
8 11. Contractor shall maintain and properly repair damage to curing materials on
9 exposed surfaces of concrete pavement continuously for a least 72 hours.
10 J. Monolithic Curbs
11 1. Concrete for monolithic curb shall be the same as for the pavement and shall be
12 placed within 20 minutes of the placement of the slab concrete.
13 2. After the concrete has been struck off and sufficiently set, the exposed surfaces
14 shall be thoroughly worked to achieve an acceptable surface finish.
15 3. The exposed edges shall be rounded by the use of an edging tool to the radius
16 indicated on the Drawings.
17 4. All exposed surfaces of curb shall be brushed to a smooth and uniform surface.
18 K.Pavement Leaveouts
19 1. Pavement leaveouts as necessary to maintain and provide for local traffic shall be
20 provided at location indicated on the Drawings or as directed by the City.
21 2. The extent and location of each leaveout required and a suitable crossover
22 connection to provide for traffic movements shall be determined in the field by the
23 City.
24 3.5 REPAIR
25 A.Repair of concrete pavement concrete shall be consistent with the Drawings and as
26 specified in Section 32 01 29.
27 3.6 RE-INSTALLATION [NOT USED]
28 3.7 SITE QUALITY CONTROL
29 A.Concrete Placement
30 1. Place concrete using a fully automated paving machine. Hand paving is only
31 permitted in areas such as intersections where use of paving machine is not
32 practical.
33 a. All concrete pavement not placed by hand shall be placed using a fully
34 automated paving machine as approved by the City.
35 b. Screeds are considered hand placement paving method.
36 B.Testing of Materials
37 1. Samples of all materials for testing shall be provided by the contractor at no
38 expense to the City, unless otherwise specified in the special provisions or in the
39 Drawings.
40 2. In the event the initial sampling and testing does not comply with the specifications,
41 all subsequent testing of the material in order to determine if the material is
42 acceptable shall be at the Contractor’s expense at the same rate charged by the
43 commercial laboratories.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 19
CONCRETE PAVING
Page 19 of 22
1 3. All testing shall be in accordance with applicable ASTM Standards and concrete
2 testing technician must be ACI certified or equivalent.
3 C.Pavement Thickness Test
4 1. Pavement thickness test shall be performed by a commercial testing laboratory
5 approved by the City every 100 feet or fraction thereof in accordance with TxDOT
6 Designation: Tex-423-A, unless otherwise shown on the plans. Test locations shall
7 be at the discretion of the City.
8 2. In the event a deficiency in the thickness of pavement is revealed during normal
9 testing operations, core samples shall be taken at the contractor’s expense to verify
10 deficiency of more than 0.2 in. from plan thickness and to isolate the deficient area.
11 3. Where the average thickness of pavement in the area found to be deficient in
12 thickness by more than 0.20 inch, but not more than 0.50-inch, payment shall be
13 made at an adjusted price as specified in the following table.
14
Deficiency in Thickness
Determined by Cores
Proportional Part
Of Contract Price
Inches Allowed
0.00 – 0.20 100 percent
0.21 – 0.30 80 percent
0.31 – 0.40 70 percent
0.41 – 0.50 60 percent
15
16 4. Any area of pavement found deficient in thickness by more than 0.50 inch but not
17 more than 0.75 inch or 1/10 of the thickness specified on the Drawings, whichever
18 is greater, shall be evaluated by the City.
19 5. If, in the judgment of the City the area of such deficiency should not be removed
20 and replaced, there shall be no payment for the area retained.
21 6. If, in the judgment of the City, the area of such deficiency warrants removal, the
22 area shall be removed and replaced, at the Contractor’s entire expense, with
23 concrete of the thickness shown on the Drawings.
24 7. Any area of pavement found deficient in thickness by more than 0.75 inch or more
25 than 1/10 of the plan thickness, whichever is greater, shall be removed and replaced
26 with concrete of the thickness shown on the Drawings at the Contractor’s sole
27 expense.
28 8. No additional payment over the contract unit price shall be made for any pavement
29 of a thickness exceeding that required by the Drawings.
30 D.Pavement Strength Test
31 1. During the progress of the work the commercial testing laboratory casts test
32 cylinders for conforming to ASTM C31, to maintain a check on the compressive
33 strengths of the concrete being placed.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 20
CONCRETE PAVING
Page 20 of 22
1 2. Test cylinders shall be taken from a representative portion of concrete being placed
2 for every 150-cubic yards of concrete pavement placed, but in no case shall fewer
3 than 1 set of cylinders be taken per day of placement. After the cylinders have been
4 cast, they shall remain on the job site and then transported, moist cured, and tested
5 in accordance with ASTM C31 and ASTM C39.
6 3. In each set, one of the cylinders shall be tested at 7 days (3 days for HES concrete),
7 two cylinders shall be tested at 28 days (three cylinders for 4” by 8” cylinders), and
8 the remaining cylinder shall be retained for testing at 56 days, if necessary.
9 Concrete must attain its design strength within 56 days. The 4” by 8” cylinders are
10 acceptable only when the nominal maximum aggregate size of the mix is less than
11 1-1/4 inch.
12 4. If the average 28-day test results indicate deficient strength, the Contractor may, at
13 its option and expense, core the pavement in question and have the cores tested by
14 an approved laboratory in accordance with ASTM C42 and ACI 318 protocol. The
15 average of all cores must meet 100 percent of the minimum specified strength, with
16 no individual core resulting in less than 90 percent of design strength, in order to
17 override the results of the cylinder tests.
18 5. In the event cylinders and/or cores do not meet minimum specified strength,
19 additional cores may be taken to identify the limits of deficient concrete pavement
20 at the expense of the Contractor.
21 6. Cylinders and/or cores must meet minimum specified strength. Pavement not
22 meeting the minimum specified strength shall be subject to the money penalties or
23 removal and placement at the Contractor’s expense as shown in the following table.
24
Percent Deficient Percent of Contract Price Allowed
Greater Than 0 percent - Not More Than 10 percent 90-percent
Greater Than 10 percent - Not More Than 15 percent 80-percent
Greater Than 15 percent 0-percent or removed and replaced at the entire cost
and expense of Contractor as directed by City
25
26 7. Deficiency shall be determined on a panel by panel basis.
27 8. The amount of penalty shall be deducted from payment due to Contractor
28 9. No additional payment over the contract unit price shall be made for any pavement
29 with a strength exceeding that required by the Drawings and/or specifications.
30 E. Cracked Concrete Acceptance Policy
31 1. If cracks exist in concrete pavement upon completion of the project, the Project
32 Inspector shall decide as to the need for action to address the cracking as to its
33 cause and recommended remedial work.
34 2. If the recommended remedial work is routing and sealing of the cracks to protect
35 the subgrade, the Inspector shall make the determination as to whether to rout and
36 seal the cracks at the time of final inspection and acceptance or at any time prior to
37 the end of the project maintenance period. The Contractor shall perform the routing
38 and sealing work as directed by the Project Inspector, at no cost to the City,
39 regardless of the cause of the cracking.
40 3. If remedial work beyond routing and sealing is determined to be necessary, the
41 Inspector and the Contractor shall meet to determine the cause of the cracking.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 21
CONCRETE PAVING
Page 21 of 22
1 a. If agreement is reached that the cracking is due to deficient materials or
2 workmanship, the Contractor shall perform the remedial work at no cost to the
3 City. Remedial work in this case shall be limited to removing and replacing the
4 deficient work with new material and workmanship that meets the requirements
5 of the contract.
6 b. If the Inspector and the Contractor agree that the cause of the cracking is not
7 deficient materials or workmanship, the City may request the Contractor to
8 provide an estimate of the cost of the necessary remedial work and/or additional
9 work to address the cause of the cracking, and the Contractor will perform that
10 work at the agreed-upon price if the City elects to do so.
11 4. If the Inspector and the Contractor cannot agree on the cause of the cracking, the
12 City may hire an independent geotechnical engineer, acceptable to the Contractor,
13 to perform testing and analysis to determine the cause of the cracking. The
14 contractor shall pay 50 percent of the costs of the independent testing. Contractor
15 shall provide one half of the estimated costs of the independent testing to be held by
16 the City.
17 5. If the independent geotechnical engineer determines that the primary cause of the
18 cracking is the Contractor’s deficient material or workmanship, the remedial work
19 will be performed at the Contractor’s entire expense and the Contractor will also
20 reimburse the City for the City’s portion of cost of the geotechnical investigation.
21 Remedial work in this case shall be limited to removing and replacing the deficient
22 work with new material and workmanship that meets the requirements of the
23 contract.
24 6. If the geotechnical engineer determines that the primary cause of the cracking is not
25 the Contractor’s deficient material or workmanship, the City will return the held
26 funds to the Contractor. The Contractor, on request, will provide the City an
27 estimate of the costs of the necessary remedial work and/or additional work and
28 will perform the work at the agreed-upon price as directed by the City.
29 3.8 SYSTEM STARTUP [NOT USED]
30 3.9 ADJUSTING [NOT USED]
31 3.10 CLEANING [NOT USED]
32 A.No concrete washout, mix, slurry, cuts, mud or solids etc., may enter the storm water
33 system including curb lines. Equipment washout allowed only in areas shown on
34 drawings and test materials or slag must be removed from site prior to final acceptance.
35 3.11 CLOSEOUT ACTIVITIES [NOT USED]
36 3.12 PROTECTION [NOT USED]
37 3.13 MAINTENANCE [NOT USED]
38 3.14 ATTACHMENTS [NOT USED]
39
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 13 13 - 22
CONCRETE PAVING
Page 22 of 22
1 END OF SECTION
2
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 1.2.A – Modified items to be included in price bid
05/21/2014 Doug Rademaker 2.2.D – Modified to clarify acceptable fly ash substitution in concrete paving
03/19/2021
Zelalem
Arega/Doug
Black
1.11.A – modified to clarify concrete placement temperature restrictions
2.4.A, B, D – to clarify concrete quality control process and requirements
3.7. C & D - to modify and clarify the pavement strength test and change in
pavement thickness measurement methodology
3.7.E – Modified to clarify cracked concrete acceptance policy
3/11/2022 Zelalem Arega 1.3.A.h, 2.2 – Added ASTM C595, Type IL cement
6/10/2022 M Owen 3.4 G. 1. – Clarified language re: machine laid vs. hand poured
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Meacham Boulevard at Mercantile Drive
CPN 105417
- 1
CONCRETE SIDEWALKS, DRIVEWAYS AND BARRIER FREE RAMPS
Page 1 of 6
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
1 SECTION 32 13 20
2 CONCRETE SIDEWALKS, DRIVEWAYS AND BARRIER FREE RAMPS
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A.Section Includes:
6 1. Concrete sidewalks
7 2. Driveways
8 3. Barrier free ramps
9 B.Deviations from this City of Fort Worth Standard Specification
10 1. None.
11 C.Related Specification Sections include, but are not necessarily limited to:
12 1. Division 0 - Bidding Requirements, Contract Forms, and Conditions of the Contract
13 2. Division 1 - General Requirements
14 3. Section 02 41 13 - Selective Site Demolition
15 4. Section 32 13 13 - Concrete Paving
16 5. Section 32 13 73 - Concrete Paving Joint Sealants
17 1.2 PRICE AND PAYMENT PROCEDURES
18 A.Measurement and Payment
19 1. Concrete Sidewalk
20 a. Measurement
21 1) Measurement for this Item shall be by the square foot of completed and
22 accepted Concrete Sidewalk in its final position for various:
23 a) Thicknesses
24 b) Types
25 b. Payment
26 1) The work performed and materials furnished in accordance with this Item
27 and measured as provided under “Measurement” will be paid for at the unit
28 price bid per square foot of Concrete Sidewalk.
29 c. The price bid shall include:
30 1) Excavating and preparing the subgrade
31 2) Furnishing and placing all materials
32 3) Thickened edge under sidewalk limits, if adjacent to curb or retaining wall
33
34 2. Concrete Curb at Back of Sidewalk (6 to 12-inch max)
35 a. Measurement
36 1) Measurement for this Item shall be by the linear foot of completed and
37 accepted Concrete Curb at the Back of Sidewalk within the 6 to 12-inch curb
38 height at back of walk in its final position.
39 b. Payment
40 1) The work performed and materials furnished in accordance with this Item
41 and measured as provided under “Measurement” will be paid for at the unit
42 price bid per linear foot of Concrete Curb at the Back of Sidewalk.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
- 2
CONCRETE SIDEWALKS, DRIVEWAYS AND BARRIER FREE RAMPS
Page 2 of 6
1 c. The price bid shall include:
2 1) Excavating and preparing the subgrade
3 2) Furnishing and placing all materials, including concrete and reinforcing
4 steel
5 3) Excavation in back of “retaining” curb
6 4) Furnishing, placing, and compacting backfill
7 3. Concrete Driveway
8 a. Measurement
9 1) Measurement for this Item shall be by the square foot of completed and
10 accepted Concrete Driveway in its final position for various:
11 a) Thicknesses
12 b) Types
13 2) Dimensions will be taken from the back of the projected curb, including the
14 area of the curb radii and will extend to the limits specified in the Drawings.
15 3) Sidewalk portion of drive will be included in driveway measurement.
16 4) Curb on drive will be included in the driveway measurement.
17 b. Payment
18 1) The work performed and materials furnished in accordance with this Item
19 and measured as provided under “Measurement” will be paid for at the unit
20 price bid per square foot of Concrete Driveway.
21 c. The price bid shall include:
22 1) Excavating and preparing the subgrade
23 2) Furnishing and placing all materials
24 3) Temporary asphalt transition at width shown on plans (typically 9 inches)
25 when the pavement adjacent to the driveway will be improved
26
27 4. Barrier Free Ramps
28 a. Measurement
29 1) Measurement for this Item shall be per each Barrier Free Ramp completed
30 and accepted for various:
31 a) Types
32 b. Payment
33 1) The work performed and materials furnished in accordance with this Item
34 and measured as provided under “Measurement” will be paid for at the unit
35 price bid per each “Barrier Free Ramp” installed.
36 c. The price bid shall include:
37 1) Excavating and preparing the subgrade
38 2) Furnishing and placing all materials
39 3) Curb Ramp
40 4) Landing and detectable warning surface as shown on the Drawings
41 5) Adjacent flares or side curb
42 6) Concrete gutter width along ramp opening
43 7) Doweling into adjacent concrete pavement, if applicable
44 1.3 REFERENCES
45 A.Abbreviations and Acronyms
46 1. TAS – Texas Accessibility Standards
47 2. TDLR – Texas Department of Licensing and Regulation
48 B.Reference Standards
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
- 3
CONCRETE SIDEWALKS, DRIVEWAYS AND BARRIER FREE RAMPS
Page 3 of 6
1 1. Reference standards cited in this Specification refer to the current reference
2 standard published at the time of the latest revision date logged at the end of this
3 Specification, unless a date is specifically cited.
4 2. American Society for Testing and Materials (ASTM)
5 a. D545, Test Methods for Preformed Expansion Joint Fillers for Concrete
6 Construction (Non-extruding and Resilient Types)
7 b. D698, Test Methods for Laboratory Compaction Characteristics of Soil Using
8 Standard Effort (12,400 ft-lbf/ft3)
9 1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
10 1.5 SUBMITTALS [NOT USED]
11 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
12 A.Mix Design: submit for approval. Section 32 13 13.
13 B.Product Data: submit product data and sample for pre-cast detectable warning for barrier
14 free ramp.
15 1.7 CLOSEOUT SUBMITTALS [NOT USED]
16 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
17 1.9 QUALITY ASSURANCE [NOT USED]
18 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
19 1.11 FIELD CONDITIONS
20 A.Weather Conditions: Placement of concrete shall be as specified in Section 32 13 13.
21 1.12 WARRANTY [NOT USED]
22 PART 2 - PRODUCTS
23 2.1 OWNER-FURNISHED PRODUCTS [NOT USED]
24 2.2 EQUIPMENT AND MATERIALS
25 A.Forms: wood or metal straight, free from warp and of a depth equal to the thickness of the
26 finished work.
27 B.Concrete: see Section 32 13 13.
28 1. Unless otherwise shown on the Drawings or detailed specifications, the standard
29 class for concrete sidewalks, driveways and barrier free ramps is shown in the
30 following table:
31 Standard Classes of Pavement Concrete
Class of
Concrete1
Minimum
Cementitious,
Lb./CY
28 Day Min.
Compressive
Strength2
psi
Maximum
Water/
Cementitious
Ratio
Course
Aggregate
Maximum
Size,
inch
A 470 3000 0.58 1-1/2
32 C.Reinforcement: see Section 32 13 13.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
- 4
CONCRETE SIDEWALKS, DRIVEWAYS AND BARRIER FREE RAMPS
Page 4 of 6
1 1. Sidewalk, driveway and barrier free ramp reinforcing steel shall be #3 deformed
2 bars at 18 inches on-center-both-ways at the center plane of all slabs, unless
3 otherwise shown on the Drawings or detailed specifications.
4 D.Joint Filler
5 1. Wood Filler: see Section 32 13 13.
6 2. Pre-Molded Asphalt Board Filler
7 a. Use only in areas where not practical for wood boards.
8 b. Pre-molded asphalt board filler: ASTM D545.
9 c. Install the required size and uniform thickness and as specified in Drawings.
10 d. Include 2 liners of 0.016 asphalt impregnated kraft paper filled with a mastic
11 mixture of asphalt and vegetable fiber and/or mineral filler.
12 E. Expansion Joint Sealant: see Section 32 13 73 where shown on the Drawings.
13 2.3 ACCESSORIES [NOT USED]
14 2.4 SOURCE QUALITY CONTROL [NOT USED]
15 PART 3 - EXECUTION
16 3.1 INSTALLERS [NOT USED]
17 3.2 EXAMINATION [NOT USED]
18 3.3 PREPARATION
19 A.Surface Preparation
20 1. Excavation: Excavation required for the construction of sidewalks, driveways and
21 barrier free ramps shall be to the lines and grades as shown on the Drawings or as
22 established by the City.
23 2. Fine Grading
24 a. The Contractor shall do all necessary filling, leveling and fine grading required
25 to bring the subgrade to the exact grades specified and compacted to at least 90
26 percent of maximum density as determined by ASTM D698.
27 b. Moisture content shall be within minus 2 to plus 4 of optimum.
28 c. Any over-excavation shall be repaired to the satisfaction of the City.
29 B.Demolition / Removal
30 1. Sidewalk, Driveway and/ or Barrier Free Ramp Removal: see Section 02 41 13.
31 3.4 INSTALLATION
32 A.General
33 1. Concrete sidewalks shall have a minimum thickness of 4 inches.
34 2. Sidewalks constructed in driveway approach sections shall have a minimum
35 thickness equal to that of driveway approach or as called for by Drawings and
36 specifications within the limits of the driveway approach.
37 3. Driveways shall have a minimum thickness of 6 inches. Standard cross-slopes for
38 walks shall be 2 percent max in accordance with current TAS/TDLR guidelines.
39 The construction of the driveway approach shall include the variable height radius
40 curb or a pan driveway approach in accordance with the Drawings.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
- 5
CONCRETE SIDEWALKS, DRIVEWAYS AND BARRIER FREE RAMPS
Page 5 of 6
1 4. All pedestrian facilities shall comply with provisions of TAS including location,
2 slope, width, shapes, texture and coloring. Pedestrian facilities installed by the
3 Contractor and not meeting TAS must be removed and replaced to meet TAS (no
4 separate pay).
5 B.Forms: Forms shall be securely staked to line and grade and maintained in a true position
6 during the depositing of concrete.
7 C.Reinforcement: see Section 32 13 13.
8 D.Concrete Placement: see Section 32 13 13.
9 E. Finishing
10 1. Concrete sidewalks, driveways and barrier free ramps shall be finished to a true,
11 even surface.
12 2. Trowel and then brush transversely to obtain a smooth uniform brush finish.
13 3. Provide exposed aggregate finish for driveways and sidewalks if specified.
14 4. Edge joints and sides shall with suitable tools.
15 F. Joints
16 1. Expansion joints for sidewalks, driveways and barrier free ramps shall be formed
17 using redwood.
18 2. Expansion joints shall be placed at intervals ten times the width of the sidewalk.
19 3. Expansion joints shall also be placed at all intersections, sidewalks with concrete
20 driveways, curbs, formations, other sidewalks and other adjacent old concrete work.
21 Similar material shall be placed around all obstructions protruding into or through
22 sidewalks or driveways.
23 4. All expansion joints shall be 1/2 inch in thickness.
24 5. Edges of all construction and expansion joints and outer edges of all sidewalks shall
25 be finished to approximately a 1/2 inch radius with a suitable finishing tool.
26 6. Sidewalks shall be marked at intervals equal to the width of the walk with a
27 marking tool. Saw cutting of joints to the required depth may be desirable on wider
28 sidewalks and is acceptable if approved by the City
29 7. When sidewalk is against the curb, expansion joints shall be spaced to match those
30 in the curb, possibly in addition to the required spacing above.
31 G.Barrier Free Ramp
32 1. Furnish and install red color detectable warning surface included in Standard
33 Product List, or approved equal.
34 2. Detectable warning surface shall be a minimum of 24-inch in depth in the direction
35 of pedestrian travel, and extend to the limit of the width of the curb ramp (exclusive
36 of flares), the landing or the blended transition.
37 3. Locate detectable warning surface so that the edge nearest the curb line is at the
38 extension of the back of the curb.
39 4. Detectable warning surface may be curved along the corner radius.
40 5. Install detectable warning surface according to manufacturer’s instructions.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
- 6
CONCRETE SIDEWALKS, DRIVEWAYS AND BARRIER FREE RAMPS
Page 6 of 6
1 3.5 REPAIR/RESTORATION [NOT USED]
2 3.6 RE-INSTALLATION [NOT USED]
3 3.7 FIELD QUALITY CONTROL [NOT USED]
4 3.8 SYSTEM STARTUP [NOT USED]
5 3.9 ADJUSTING [NOT USED]
6 3.10 CLEANING [NOT USED]
7 3.11 CLOSEOUT ACTIVITIES [NOT USED]
8 3.12 PROTECTION [NOT USED]
9 3.13 MAINTENANCE [NOT USED]
10 3.14 ATTACHMENTS [NOT USED]
11 END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 D. Johnson 1.2.A.3 – Measurement and Payment for Barrier Free Ramps modified to match
updated City Details
4/30/2013 F. Griffin Corrected Part 1, 1.2, A, 3, b, 1 to read; from . . . square foot of Concrete Sidewalk.
to . . .each “Barrier Free Ramp” installed.
June 5, 2018 M Owen Revised Measurement and Payment.section.
April 29, 2021 M Owen 1.2 A. 4. c. Revise Barrier Free Ramp – Payment Section
December 9,
2021 M Owen 1.2 A. 1.c. and 1.2 A. 3. c. Clarified what is included in bid items for sidewalk and
driveway, respectively
December 9,
2022 M Owen 3.4 G. Remove reference to specific DWS and referred to SPL, revised to clarify
limit of DWS, and revised reference to back of curb for placement of DWS.
12
Meacham Boulevard at Mercantile Drive
CPN 105417
32 13 73 - 1
CONCRETE PAVING JOINT SEALANTS
Page 1 of 4
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
SECTION 32 13 73
CONCRETE PAVING JOINT SEALANTS
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Specification for silicone joint sealing for concrete pavement and curbs.
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 - Bidding Requirements, Contract Forms, and Conditions of the Contract
2. Division 1 - General Requirements
3. Section 32 13 13 - Concrete Paving
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Measurement
a. Measurement for this Item shall be by the linear foot of Joint Sealant completed
and accepted only when specified in the Drawings to be a pay item.
2. Payment
a. The work performed and materials furnished in accordance with this Item are
subsidiary to the various items bid and no other compensation will be allowed,
unless specifically specified on Drawings.
1.3 REFERENCES
A. Reference Standards
1. Reference standards cited in this Specification refer to the current reference
standard published at the time of the latest revision date logged at the end of this
Specification, unless a date is specifically cited.
2. ASTM International (ASTM):
a. D5893, Standard Specification for Cold Applied, Single Component,
Chemically Curing Silicone Joint Sealant for Portland Cement Concrete
Pavements
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 ACTION SUBMITTALS [NOT USED]
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
A. Test and Evaluation Reports
1. Prior to installation, furnish certification by an independent testing laboratory that
the silicone joint sealant meets the requirements of this Section.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 13 73 - 2
CONCRETE PAVING JOINT SEALANTS
Page 2 of 4
2. Submit verifiable documentation that the manufacturer of the silicone joint sealant
has a minimum 2-year demonstrated, documented successful field performance
with concrete pavement silicone joint sealant systems.
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
1.11 FIELD CONDITIONS
A. Do not apply joint sealant when the air and pavement temperature is less than 35
degrees F
B. Concrete surface must be clean, dry and frost free.
C. Do not place sealant in an expansion-type joint if surface temperature is below 35
degrees F or above 90 degrees F.
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS
2.1 OWNER FURNISHED PRODUCTS [NOT USED]
2.2 MATERIALS & EQUIPMENT
A. Materials
1. Joint Sealant: ASTM D5893.
2. Joint Filler, Backer Rod and Breaker Tape
a. The joint filler sop shall be of a closed cell expanded polyethylene foam backer
rod and polyethylene bond breaker tape of sufficient size to provide a tight seal.
b. The back rod and breaker tape shall be installed in the saw-cut joint to prevent
the joint sealant from flowing to the bottom of the joint.
c. The backer rod and breaker tape shall be compatible with the silicone joint
sealant and no bond or reaction shall occur between them.
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL [NOT USED]
PART 3 - EXECUTION
3.1 INSTALLERS [NOT USED]
3.2 EXAMINATION [NOT USED]
3.3 PREPARATION [NOT USED]
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 13 73 - 3
CONCRETE PAVING JOINT SEALANTS
Page 3 of 4
3.4 INSTALLATION
A. General
1. The silicone sealant shall be cold applied.
2. Allow concrete to cure for a minimum of 7 days to ensure it has sufficient strength
prior to sealing joints.
3. Perform joint reservoir saw cutting, cleaning, bond breaker installation, and joint
sealant placement in a continuous sequence of operations.
4. See Drawings for the various joint details with their respective dimensions.
B. Equipment
1. Provide all necessary equipment and keep equipment in a satisfactory working
condition.
2. Equipment shall be inspected by the City prior to the beginning of the work.
3. The minimum requirements for construction equipment shall be as follows:
a. Concrete Saw. The sawing equipment shall be adequate in size and power to
complete the joint sawing to the required dimensions.
b. Air Compressors. The delivered compressed air shall have a pressure in excess
of 90 psi and shall be suitable for the removal of all free water and oil from the
compressed air.
c. Extrusion Pump. The output shall be capable of supplying a sufficient volume
of sealant to the joint.
d. Injection Tool. This mechanical device shall apply the sealant uniformly into
the joint.
e. Sandblaster. The design shall be for commercial use with air compressors as
specified in this Section.
f. Backer Rod Roller and Tooling Instrument. These devices shall be clean and
free of contamination. They shall be compatible with the joint depth and width
requirements.
C. Sawing Joints: see Section 32 13 13.
D. Cleaning joints
1. Dry saw in 1 direction with reverse cutting blade then sand blast.
2. Use compressed air to remove the resulting dust from the joint.
3. Sandblast joints after complete drying.
a. Attach nozzle to a mechanical aiming device so that the sand blast will be
directed at an angle of 45 degrees and at a distance of 1 to 2 inches from the
face of the joint.
b. Sandblast both joint faces sandblasted in separate, 1 directional passes.
c. When sandblasting is complete, blow-out using compressed air.
d. The blow tube shall fit into the joints.
4. Check the blown joint for residual dust or other contamination.
a. If any dust or contamination is found, repeat sandblasting and blowing until the
joint is cleaned.
b. Do not use solvents to remove stains and contamination.
5. Place the bond breaker and sealant in the joint immediately upon cleaning.
6. Bond Breaker Rod and Tape: install in the cleaned joint prior to the application of
the joint sealant.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 20, 2012
Birchman Office Space
CPN 105553
32 13 73 - 4
CONCRETE PAVING JOINT SEALANTS
Page 4 of 4
7. Do not leave open, cleaned joints unsealed overnight.
E. Joint Sealant
1. Apply the joint sealant upon placement of the bond breaker rod and tape, using the
mechanical injection tool.
2. Do not seal joints unless they are clean and dry.
3. Remove and discard excess sealant left on the pavement surface.
a. Do not excess use to seal the joints.
4. The pavement surface shall present a clean final condition as determined by City.
5. Do not allow traffic on the fresh sealant until it becomes tack-free.
F. Approval of Joints
1. The City may request a representative of the sealant manufacturer to be present at
the job site at the beginning of the final cleaning and sealing of joints.
a. The representative shall demonstrate to the Contractor and the City the
acceptable method for sealant installation.
b. The representative shall approve the clean, dry joints before the sealing
operation commences.
3.5 REPAIR/RESTORATION [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 FIELD QUALITY CONTROL [NOT USED]
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING [NOT USED]
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
32 16 13 - 1
CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
Page 1 of 7
1 SECTION 32 16 13
2 CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
3
4 PART 1 - GENERAL
5 1.1 SUMMARY
6 A.Section Includes:
7 1. Concrete Curbs and Gutters
8 2. Concrete Valley Gutters
9 B.Deviations from this City of Fort Worth Standard Specification
10 1. None.
11 C.Related Specification Sections include, but are not necessarily limited to:
12 1. Division 0 - Bidding Requirements, Contract Forms, and Conditions of the Contract
13 2. Division 1 - General Requirements
14 3. Section 02 41 13 - Selective Site Demolition
15 4. Section 32 13 13 - Concrete Paving
16 5. Section 32 13 73 - Concrete Paving Joint Sealants
17 6. Section 32 11 23 – Flexible Base Courses
18
19 1.2 PRICE AND PAYMENT PROCEDURES
20 A.Measurement and Payment
21 1. Concrete Curb and Gutter
22 a. Measurement
23 1) Measurement for this Item shall be by the linear foot of Concrete Curb and
24 Gutter.
25 b. Payment
26 1) The work performed and materials furnished in accordance with this Item
27 and measured as provided under “Measurement” will be paid for at the unit
28 price bid per linear foot of Concrete Curb and Gutter complete and in place by
29 curb height.
30 c. The price bid shall include:
31 1) Excavation and preparing the subgrade, including placement of flexbase or
32 cement treated base under curb & gutter and 12” behind back of curb
33 2) Required excavation and backfill behind the curb
34 3) Removal and disposal of all excavated material
35 4) Furnishing and placing all materials, including foundation course,
36 reinforcing steel, and expansion material
37 5) Temporary asphalt transition at width shown on plans (typically 9 inches)
38 when the pavement adjacent to the curb & gutter will be improved
39 2. Concrete Valley Gutter
40 a. Measurement
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
32 16 13 - 2
CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
Page 2 of 7
1 1) Measurement for this Item shall be by the square yard of Concrete Valley
2 Gutter.
3 b. Payment
4 1) The work performed and materials furnished in accordance with this Item
5 and measured as provided under “Measurement” will be paid for at the unit
6 price bid per square yard of Concrete Valley Gutter complete and in place for:
7 a) Various street types
8 c. The price bid shall include:
9 1) Required excavation
10 2) Preparing the subgrade, including placement of flexbase or stabilized
11 cement treated subgrade
12 3) Furnishing and placing all materials, including foundation course,
13 reinforcing steel, and expansion material
14 4) Temporary asphalt transition at width shown on plans (typically 9”) when
15 the pavement adjacent to the valley gutter will improved
16 3. Concrete Laydown Curb
17 a. Measurement
18 1) Measurement for this Item shall be by the linear foot of Concrete Laydown
19 Curb, when crossing on-street parking or parking lots.
20 2) Laydown Curb pay item is not to be used when crossing driveways or
21 alleys.
22 b. Payment
23 1) The work performed and materials furnished in accordance with this Item
24 and measured as provided under “Measurement” will be paid for at the unit
25 price bid per linear foot of Concrete Laydown Curb complete and in place by
26 curb height.
27 c. The price bid shall include:
28 1) Excavation and preparing the subgrade, including placement of flexbase or
29 cement treated base under curb & gutter and 12” behind back of curb
30 2) Required excavation and backfill behind the curb
31 3) Removal and disposal of all excavated material
32 4) Furnishing and placing all materials, including foundation course,
33 reinforcing steel, and expansion material
34 5) Temporary asphalt transition at width shown on plans (typically 9 inches)
35 when the pavement adjacent to the curb & gutter will be improved
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
32 16 13 - 3
CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
Page 3 of 7
1 1.3 REFERENCES [NOT USED]
2 1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
3 1.5 ACTION SUBMITTALS [NOT USED]
4 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
5 1.7 CLOSEOUT SUBMITTALS [NOT USED]
6 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
7 1.9 QUALITY ASSURANCE [NOT USED]
8 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
9 1.11 FIELD CONDITIONS
10 A.Weather Conditions: See Section 32 13 13.
11 1.12 WARRANTY [NOT USED]
12 PART 2 - PRODUCTS
13 2.1 OWNER FURNISHED PRODUCTS [NOT USED]
14 2.2 EQUIPMENT AND MATERIALS
15 A.Forms: See Section 32 13 13.
16 B.Concrete:
17 1. Unless otherwise shown on the Drawings or detailed specifications, the standard
18 class for concrete curb & gutter and valley gutter is shown in the following table:
19
20 Standard Classes of Pavement Concrete
Item Class of
Concret
e
Minimum
Cementitious
,
Lb./CY
28 Day
Min.
Compressiv
e
Strength
psi
Maximum
Water/
Cementitiou
s
Ratio
Course
Aggregat
e
Maximu
m
Size,
inch
Curb
&
Gutte
r
A 470 3,000 0.58 1-1/2
Valle
y
Gutte
r
H 564 4,500 0.45 1-1/2
21 C.Reinforcement: See Section 32 13 13.
22 D.Joint Filler
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
1 1. Wood Filler: see Section 32 13 13.
2 2. Pre-Molded Asphalt Board Filler
32 16 13 - 4
CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
Page 4 of 7
3 a. Use only in areas where not practical for wood boards
4 b. Pre-molded asphalt board filler: ASTM D545
5 c. Install the required size and uniform thickness and as specified in the Drawings.
6 d. Include two liners of 0.016 asphalt impregnated kraft paper filled with a mastic
7 mixture of asphalt and vegetable fiber and/or mineral filler.
8 E. Expansion Joint Sealant: See Section 32 13 73.
9 2.3 ACCESSORIES [NOT USED]
10 2.4 SOURCE QUALITY CONTROL [NOT USED]
11 PART 3 - EXECUTION
12 3.1 INSTALLERS [NOT USED]
13 3.2 EXAMINATION [NOT USED]
14 3.3 PREPARATION
15 A.Demolition / Removal: See Section 02 41 13.
16 3.4 INSTALLATION
17 A.Forms
18 1. Extend forms the full depth of concrete.
19 2. Wood forms: minimum of 1-1/2 inches in thickness
20 3. Metal Forms: a gauge that shall provide equivalent rigidity and strength
21 4. Use acceptable wood or metal forms for curves with a radius of less than 250 feet.
22 5. All forms showing a deviation of 1/8 inch in 10 feet from a straight line shall be
23 rejected.
24 B.Reinforcing Steel
25 1. Place all necessary reinforcement for City approval prior to depositing concrete.
26 2. All steel must be free from paint and oil and all loose scale, rust, dirt and other
27 foreign substances.
28 3. Remove foreign substances from steel before placing.
29 4. Wire all bars at their intersections and at all laps or splices.
30 5. Lap all bar splices a minimum of 20 diameters of the bar or 12 inches, whichever is
31 greater.
32 C.Concrete Placement
33 1. Deposit concrete to maintain a horizontal surface.
34 2. Work concrete into all spaces and around any reinforcement to form a dense mass
35 free from voids.
36 3. Work coarse aggregate away from contact with the forms
37 4. Hand-Laid Concrete – Curb and gutter
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
32 16 13 - 5
CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
Page 5 of 7
1 a. Shape and compact subgrade to the lines, grades and cross section shown on the
2 Drawings.
3 b. Lightly sprinkle subgrade material immediately before concrete placement.
4 c. Deposit concrete into forms.
5 d. Shape the concrete to the required curb and gutter design and provide a brush
6 finish.
7 5. Machine-Laid Concrete – Curb and Gutter
8 a. Hand-tamp and sprinkle subgrade material before concrete placement.
9 b. Provide clean surfaces for concrete placement.
10 c. Place the concrete to correct line and grade with approved self-propelled
11 equipment.
12 d. Brush finish surfaces immediately after extrusion or slipforming.
13 6. Hand-Laid Concrete – Concrete Valley Gutter: See Section 32 13 13.
14 7. Expansion joints
15 a. Place expansion joints in the curb and gutter at 200-foot intervals and at
16 intersection returns and other rigid structures.
17 b. Place tooled joints at 15-foot intervals or matching abutting sidewalk joints and
18 pavement joints to a depth of 1-1/2 inches.
19 c. Place expansion joints at all intersections with concrete driveways, structures,
20 valley gutters, and existing curb and gutters.
21 d. Make expansion joints no less than 1/2 inch in thickness, extending the full
22 depth of the concrete.
23 e. Make expansion joints perpendicular and at right angles to the face of the curb.
24 f. Neatly trim any expansion material extending above the surface of the finished
25 work.
26 g. Make expansion joints in the curb and gutter coincide with existing concrete
27 expansion joints.
28 h. Longitudinal dowels across the expansion joints in the curb and gutter are
29 required.
30 i. Install 3 - 1/2” round, smooth bars, 24 inches in length, for dowels at each
31 expansion joint.
32 j. Coat 1/2 of the dowel with a bond breaker and terminate with a dowel cap that
33 provides a minimum of 1-inch free expansion.
34 k. Support dowels by an approved method.
35 D.Curing: see Section 32 13 13.
36 3.5 REPAIR/RESTORATION [NOT USED]
37 3.6 RE-INSTALLATION [NOT USED]
38 3.7 FIELD QUALITY CONTROL
39 A.Inspections
40 1. Steel reinforcement placement
41 2. Headed bolts and studs
42 3. Verification of use of required design mixture
43 4. Concrete placement, including conveying and depositing
44 5. Curing procedures and maintenance of curing temperature
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
32 16 13 - 6
CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
Page 6 of 7
1 B.Concrete Tests: Perform testing of fresh concrete sample obtained according to
2 ASTM C172 with the following requirements:
3 1. Testing Frequency: Obtain 1 fresh concrete sample for each day's pour of each
4 concrete mixture exceeding 5 cubic yards, but less than 150 cubic yards, plus 1 set
5 for each additional 150 cubic yard or fraction thereof.
6 2. Slump: ASTM C143; 1 test at point of placement for each concrete sample, but not
7 less than 1 test for each day's pour of each concrete mixture. Perform additional
8 tests when concrete consistency appears to change.
9 3. Air Content: ASTM C231, pressure method, for normal-weight concrete; 1 test for
10 each sample, but not less than 1 test for each day's pour of each concrete mixture.
11 4. Concrete Temperature: ASTM C1064; 1 test for each concrete sample.
12 5. Compression Test Specimens: ASTM C31.
13 a. Cast and laboratory cure 3 cylinders for each fresh concrete sample.
14 1) Do not transport field cast cylinders until they have cured for a
15 minimum of 24 hours.
16 6. Compressive-Strength Tests: ASTM C39;
17 a. Test 1 cylinder at 7 days.
18 b. Test 2 cylinders at 28 days.
19 7. Upload test results into Buzzsaw within 48 hours of testing. Reports of
20 compressive-strength tests shall contain Project identification name and number,
21 date of concrete placement, name of concrete tester and inspector, location of
22 concrete batch in Work, design compressive strength at 28 days, concrete mixture
23 proportions and materials, compressive breaking strength, and type of break for
24 both 7- and 28-day tests.
25 8. Additional Tests: Additional tests of concrete shall be made when test results
26 indicate that slump, air entrainment, compressive strengths, or other City
27 specification requirements have not been met. The Lab Services division may
28 conduct or request tests to determine adequacy of concrete by cored cylinders
29 complying with ASTM C42 or by other methods as directed by the Project
30 Manager.
31 a. When the strength level of the concrete for any portion of the structure, as
32 indicated by cylinder tests, falls below the specified requirements, provide
33 improved curing conditions and/or adjustments to the mix design as required to
34 obtain the required strength. If the average strength of the laboratory control
35 cylinders falls so low as to be deemed unacceptable, follow the core test
36 procedure set forth in ACI 301, Chapter 17. Locations of core tests shall be
37 approved by the Project Engineer. Core sampling and testing shall be at
38 Contractors expense.
39 b. If the results of the core tests indicate that the strength of the structure is
40 inadequate, any replacement, load testing, or strengthening as may be ordered by
41 the Project Engineer shall be provided by the Contractor without cost to the
42 City.
43 9. Additional testing and inspecting, at Contractor's expense, will be performed to
44 determine compliance of replaced or additional work with specified requirements.
45 10. Correct deficiencies in the Work that test reports and inspections indicate does not
46 comply with the Contract Documents.
47 3.8 SYSTEM STARTUP [NOT USED]
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised December 9, 2022
Birchman Office Space
CPN 105553
32 16 13 - 7
CONCRETE CURB AND GUTTERS AND VALLEY GUTTERS
Page 7 of 7
1 3.9 ADJUSTING [NOT USED]
2 3.10 CLEANING [NOT USED]
3 3.11 CLOSEOUT ACTIVITIES [NOT USED]
4 3.12 PROTECTION [NOT USED]
5 3.13 MAINTENANCE [NOT USED]
6 3.14 ATTACHMENTS [NOT USED]
7 END OF SECTION
8
Revision Log
DATE NAME SUMMARY OF CHANGE
12/20/2012 D. Johnson 1.2.A.2. Modified payment item to vary by street type
10/05/2016 Z. Arega Added Subsection 2.2.B.1 and Subsection 3.7
12/09/2021 M Owen
1.2 A. 1. c. Clarified what price bid includes for curb & gutter
1..2 A. 2. d. Clarified what price bid includes for valley gutter
2.2 B. 1. Updated table: Valley gutter concrete shall meet hand poured concrete
paving requirements
6/10/2022 M Owen 1.2 A. 1. C. Clarify that price for curb & gutter to include excavation and removal
and disposal of excavated material
12/9/2022 M Owen 1.2 A. 3. Added Laydown Curb to measurement and payment section
9
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 17 23 - 1
PAVEMENT MARKINGS
Page 1 of 11
1 SECTION 32 17 23
2 PAVEMENT MARKINGS
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A.Section Includes:
6 1. Pavement Markings
7 a. Thermoplastic, hot-applied, spray (HAS) pavement markings
8 b. Thermoplastic, hot-applied, extruded (HAE) pavement markings
9 c. Preformed polymer tape
10 d. Preformed heat-activated thermoplastic tape
11 e. Preformed Contrast Markings
12 2. Raised markers
13 3. Work zone markings
14 4. Removal of pavement markings and markers
15 B.Deviations from this City of Fort Worth Standard Specification
16 1. None.
17 C.Related Specification Sections include, but are not necessarily limited to:
18 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
19 2. Division 1 – General Requirements
20 1.2 PRICE AND PAYMENT PROCEDURES
21 A.Measurement and Payment
22 1. Pavement Markings
23 a. Measurement
24 1) Measurement for this Item shall be per linear foot of material placed.
25 b. Payment
26 1) The work performed and materials furnished in accordance with this Item
27 and measured as provided under “Measurement” shall be paid for at the unit
28 price bid per linear foot of “Pvmt Marking” installed for:
29 a) Various Widths
30 b) Various Types
31 c) Various Materials
32 d) Various Colors
33 c. The price bid shall include:
34 1) Installation of Pavement Marking
35 2) Glass beads, when required
36 3) Surface preparation
37 4) Clean-up
38 5) Testing (when required)
39 2. Legends
40 a. Measurement
41 1) Measurement for this Item shall be per each Legend installed.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 b. Payment
32 17 23 - 2
PAVEMENT MARKINGS
Page 2 of 11
2 1) The work performed and materials furnished in accordance with this Item
3 shall be paid for at the unit price bid per each “Legend” installed for:
4 a) Various types
5 b) Various applications
6 c. The price bid shall include:
7 1) Installation of Pavement Marking
8 2) Glass beads, when required
9 3) Surface preparation
10 4) Clean-up
11 5) Testing
12 3. Preformed Thermoplastic – Contrast Markings
13 a. Measurement
14 1) Measurement for this Item shall be per linear foot of material placed or per
15 each for legend items
16 b. Payment
17 1) The work performed and materials furnished in accordance with this Item
18 shall be paid for at the unit price bid per linear foot or per each for legends for
19 “Preformed Thermoplastic – Contract Markings” installed for:
20 a) Various Widths
21 b) Various Types
22 c) Various Applications
23 c. The price bid shall include:
24 1) Installation of Contrast Markings, including solid black and solid white or
25 yellow material as preformed
26 2) Railroad Legend shall include X and RR legend markings and three 24”
27 stop bars
28 3) Surface preparation
29 4) Clean-up
30 5) Testing
31 4. Raised Markers
32 a. Measurement
33 1) Measurement for this Item shall be per each Raised Marker installed.
34 b. Payment
35 1) The work performed and materials furnished in accordance with this Item
36 shall be paid for at the unit price bid per each “Raised Marker” installed for:
37 a) Various types
38 c. The price bid shall include:
39 1) Installation of Raised Markers
40 2) Surface preparation
41 3) Clean-up
42 4) Testing
43 5. Work Zone Tab Markers
44 a. Measurement
45 1) Measurement for this Item shall be per each Tab Marker installed.
46 b. Payment
47 1) The work performed and materials furnished in accordance with this Item
48 shall be paid for at the unit price bid per each “Tab Marker” installed for:
49 a) Various types
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 c. The price bid shall include:
2 1) Installation of Tab Work Zone Markers
3 6. Fire Lane Markings
4 a. Measurement
5 1) Measurement for this Item shall be per the linear foot.
6 b. Payment
32 17 23 - 3
PAVEMENT MARKINGS
Page 3 of 11
7 1) The work performed and materials furnished in accordance with this Item
8 and measured as provided under “Measurement” shall be paid for at the unit
9 price bid per linear foot of “Fire Lane Marking” installed.
10 c. The price bid shall include:
11 1) Surface preparation
12 2) Clean-up
13 3) Testing
14 7. Pavement Marking Removal
15 a. Measurement
16 1) Measure for this Item shall be per linear foot.
17 b. Payment
18 1) The work performed and materials furnished in accordance with this Item
19 and measured as provided under “Measurement” shall be paid for at the unit
20 price bid per linear foot of “Remove Pvmt Marking” performed for:
21 a) Various widths
22 c. The price bid shall include:
23 1) Removal of Pavement Markings
24 2) Clean-up
25 8. Raised Marker Removal
26 a. Measurement
27 1) Measurement for this Item shall be per each Pavement Marker removed.
28 b. Payment
29 1) The work performed and materials furnished in accordance with this Item
30 shall be paid for at the unit price bid per each “Remove Raised Marker”
31 performed.
32 c. The price bid shall include:
33 1) Removal of each Marker
34 2) Disposal of removed materials
35 3) Clean-up
36 9. Legend Removal
37 a. Measurement
38 1) Measure for this Item shall be per each Legend removed.
39 b. Payment
40 1) The work performed and materials furnished in accordance with this Item
41 and measured as provided under “Measurement” shall be paid for at the unit
42 price bid per linear foot of “Remove Legend” performed for:
43 a) Various types
44 b) Various applications
45 c. The price bid shall include:
46 1) Removal of Pavement Markings
47 2) Clean-up
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 1.3 REFERENCES
2 A.Reference Standards
32 17 23 - 4
PAVEMENT MARKINGS
Page 4 of 11
3 1. Reference standards cited in this Specification refer to the current reference
4 standard published at the time of the latest revision date logged at the end of this
5 Specification, unless a date is specifically cited.
6 2. Texas Manual on Uniform Traffic Control Devices (MUTCD), 2011 Edition
7 a. Part 3, Markings
8 3. American Association of State Highway and Transportation Officials (AASHTO)
9 a. Standard Specification for Glass Beads Used in Pavement Markings, M 247-09
10 4. Federal Highway Administration (FHWA)
11 a. 23 CFR Part 655, FHWA Docket No. FHWA-2009-0139
12 5. Texas Department of Transportation (TxDOT)
13 a. DMS-4200, Pavement Markers (Reflectorized)
14 b. DMS-4300, Traffic Buttons
15 c. DMS-8220, Hot Applied Thermoplastic
16 d. DMS-8240, Permanent Prefabricated Pavement Markings
17 e. DMS-8241, Removable Prefabricated Pavement Markings
18 f. DMS-8242, Temporary Flexible-Reflective Road Marker Tabs
19 1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
20 1.5 SUBMITTALS
21 A.Submittals shall be in accordance with Section 01 33 00.
22 B.All submittals shall be approved by the City prior to delivery and/or fabrication for
23 specials.
24 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
25 1.7 CLOSEOUT SUBMITTALS [NOT USED]
26 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
27 1.9 QUALITY ASSURANCE [NOT USED]
28 1.10 DELIVERY, STORAGE, AND HANDLING
29 A.Storage and Handling Requirements
30 1. The Contractor shall secure and maintain a location to store the material in
31 accordance with Section 01 50 00.
32 1.11 FIELD [SITE] CONDITIONS [NOT USED]
33 1.12 WARRANTY [NOT USED]
34 PART 2 - PRODUCTS
35 2.1 OWNER-SUPPLIED PRODUCTS
36 A.New Products
37 1. Refer to Drawings to determine if there are owner-supplied products for the Project.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 2.2 MATERIALS
2 A.Manufacturers
32 17 23 - 5
PAVEMENT MARKINGS
Page 5 of 11
3 1. Only the manufacturers as listed in the City’s Standard Products List will be
4 considered as shown in Section 01 60 00.
5 a. The manufacturer must comply with this Specification and related Sections.
6 2. Any product that is not listed on the Standard Products List is considered a
7 substitution and shall be submitted in accordance with Section 01 25 00.
8 B.Materials
9 1. Pavement Markings
10 a. Thermoplastic, hot applied, spray
11 1) Refer to Drawings and City Standard Detail Drawings for width of
12 longitudinal lines.
13 2) Product shall be especially compounded for traffic markings.
14 3) When placed on the roadway, the markings shall not be slippery when wet,
15 lift from pavement under normal weather conditions nor exhibit a tacky
16 exposed surface.
17 4) Cold ductility of the material shall permit normal road surface expansion
18 and contraction without chipping or cracking.
19 5) The markings shall retain their original color, dimensions and placement
20 under normal traffic conditions at road surface temperatures of 158 degrees
21 Fahrenheit and below.
22 6) Markings shall have uniform cross-section, clean edges, square ends and no
23 evidence of tracking.
24 7) The density and quality of the material shall be uniform throughout the
25 markings.
26 8) The thickness shall be uniform throughout the length and width of the
27 markings.
28 9) The markings shall be 95 percent free of holes and voids, and free of
29 blisters for a minimum of 60 days after application.
30 10) The material shall not deteriorate by contact with sodium chloride, calcium
31 chloride or other chemicals used to prevent roadway ice or because of the oil
32 content of pavement markings or from oil droppings or other effects of traffic.
33 11) The material shall not prohibit adhesion of other thermoplastic markings if,
34 at some future time, new markings are placed over existing material.
35 a) New material shall bond itself to the old line in such a manner that no
36 splitting or separation takes place.
37 12) The markings placed on the roadway shall be completely retroreflective
38 both internally and externally with traffic beads and shall exhibit uniform
39 retro-directive reflectance.
40 13) Traffic beads
41 a) Manufactured from glass
42 b) Spherical in shape
43 c) Essentially free of sharp angular particles
44 d) Essentially free of particles showing cloudiness, surface scoring or
45 surface scratching
46 e) Water white in color
47 f) Applied at a uniform rate
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 17 23 - 6
PAVEMENT MARKINGS
Page 6 of 11
1 g) Meet or exceed Specifications shown in AASHTO Standard
2 Specification for Glass Beads Used in Pavement Markings, AASHTO
3 Designation: M 247-09.
4 b. Thermoplastic, hot applied, extruded
5 1) Product shall be especially compounded for traffic markings
6 2) When placed on the roadway, the markings shall not be slippery when wet,
7 lift from pavement under normal weather conditions nor exhibit a tacky
8 exposed surface.
9 3) Cold ductility of the material shall permit normal road surface expansion
10 and contraction without chipping or cracking.
11 4) The markings shall retain their original color, dimensions and placement
12 under normal traffic conditions at road surface temperatures of 158 degrees
13 Fahrenheit and below.
14 5) Markings shall have uniform cross-section, clean edges, square ends and no
15 evidence of tracking.
16 6) The density and quality of the material shall be uniform throughout the
17 markings.
18 7) The thickness shall be uniform throughout the length and width of the
19 markings.
20 8) The markings shall be 95 percent free of holes and voids, and free of
21 blisters for a minimum of 60 days after application.
22 9) The minimum thickness of the marking, as measured above the plane
23 formed by the pavement surface, shall not be less than 1/8 inch in the center
24 of the marking and 3/32 inch at a distance of ½ inch from the edge.
25 10) Maximum thickness shall be 3/16 inch.
26 11) The material shall not deteriorate by contact with sodium chloride, calcium
27 chloride or other chemicals used to prevent roadway ice or because of the oil
28 content of pavement markings or from oil droppings or other effects of traffic.
29 12) The material shall not prohibit adhesion of other thermoplastic markings if,
30 at some future time, new markings are placed over existing material. New
31 material shall bond itself to the old line in such a manner that no splitting or
32 separation takes place.
33 13) The markings placed on the roadway shall be completely retroreflective
34 both internally and externally with traffic beads and shall exhibit uniform
35 retro-directive reflectance.
36 14) Traffic beads
37 a) Manufactured from glass
38 b) Spherical in shape
39 c) Essentially free of sharp angular particles
40 d) Essentially free of particles showing cloudiness, surface scoring or
41 surface scratching
42 e) Water white in color
43 f) Applied at a uniform rate
44 g) Meet or exceed Specifications shown in AASHTO Standard
45 Specification for Glass Beads Used in Pavement Markings, AASHTO
46 Designation: M 247-09.
47 c. Preformed Polymer Tape
48 1) Material shall meet or exceed the Specifications for SWARCO Director 35,
49 3M High Performance Tape Series 3801 ES, or approved equal.
50 d. Preformed Heat-Activated Thermoplastic Tape
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 17 23 - 7
PAVEMENT MARKINGS
Page 7 of 11
1 1) Material shall meet or exceed the Specifications for HOT Tape Brand 0.125
2 mil preformed thermoplastic or approved equal.
3 2. Raised Markers
4 a. Markers shall meet the requirements of the Texas Manual on Uniform Traffic
5 Control Devices.
6 b. Non-reflective markers shall be Type Y (yellow body) and Type W (white body)
7 round ceramic markers and shall meet or exceed the TxDOT Specification
8 DMS-4300.
9 c. The reflective markers shall be plastic, meet or exceed the TxDOT Specification
10 DMS-4200 for high-volume retroreflective raised markers and be available in
11 the following types:
12 1) Type I-C, white body, 1 face reflects white
13 2) Type II-A-A, yellow body, 2 faces reflect amber
14 3) Type II-C-R, white body, 1 face reflects white, the other red
15
16 3. Work Zone Markings
17 a. Tabs
18 1) Temporary flexible-reflective roadway marker tabs shall meet requirements
19 of TxDOT DMS-8242, “Temporary Flexible-Reflective Road Marker Tabs.”
20 2) Removable markings shall not be used to simulate edge lines.
21 3) No segment of roadway open to traffic shall remain without permanent
22 pavement markings for a period greater than 14 calendar days.
23 b. Raised Markers
24 1) All raised pavement markers shall meet the requirements of DMS-4200.
25 c. Striping
26 1) Work Zone striping shall meet or exceed the TxDOT Specification DMS-
27 8200.
28 2.3 ACCESSORIES [NOT USED]
29 2.4 SOURCE QUALITY CONTROL
30 A.Performance
31 1. Minimum maintained retroreflectivity levels for longitudinal markings shall meet
32 the requirements detailed in the table below for a minimum of 30 calendar days.
Posted Speed (mph)
≤ 30 35 – 50 ≥ 55
2-lane roads with centerline
markings only (1)n/a 100 250
All other roads (2)n/a 50 100
33 (1) Measured at standard 30-m geometry in units of mcd/m2/lux.
34 (2) Exceptions:
35 A. When raised reflective pavement markings (RRPMs) supplement or substitute for a
36 longitudinal line, minimum pavement marking retroreflectivity levels are not applicable as
37 long as the RRPMs are maintained so that at least 3 are visible from any position along that
38 line during nighttime conditions.
39 B. When continuous roadway lighting assures that the markings are visible, minimum
40 pavement marking retroreflectivity levels are not applicable.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
1 PART 3 - EXECUTION
32 17 23 - 8
PAVEMENT MARKINGS
Page 8 of 11
2 3.1 EXAMINATION [NOT USED]
3 3.2 PREPARATION
4 A.Pavement Conditions
5 1. Roadway surfaces shall be free of dirt, grease, loose and/or flaking existing
6 markings and other forms of contamination.
7 2. New Portland cement concrete surfaces shall be cleaned sufficiently to remove the
8 curing membrane.
9 3. Pavement to which material is to be applied shall be completely dry.
10 4. Pavement shall be considered dry, if, on a sunny day after observation for 15
11 minutes, no condensation develops on the underside of a 1 square foot piece of
12 clear plastic that has been placed on the pavement and weighted on the edges.
13 5. Equipment and methods used for surface preparation shall not damage the
14 pavement or present a hazard to motorists or pedestrians.
15 3.3 INSTALLATION
16 A.General
17 1. The materials shall be applied according to the manufacturer’s recommendations.
18 2. Markings and markers shall be applied within temperature limits recommended by
19 the material manufacturer, and shall be applied on clean, dry pavement having a
20 surface temperature above 50 degrees Fahrenheit.
21 3. Markings that are not properly applied due to faulty application methods or being
22 placed in the wrong position or alignment shall be removed and replaced by the
23 Contractor at the Contractor’s expense. If the mistake is such that it would be
24 confusing or hazardous to motorists, it shall be remedied the same day of
25 notification. Notification will be made by phone and confirmed by fax. Other
26 mistakes shall be remedied within 5 days of written notification.
27 4. When markings are applied on roadways open to traffic, care will be taken to
28 ensure that proper safety precautions are followed, including the use of signs,
29 cones, barricades, flaggers, etc.
30 5. Freshly applied markings shall be protected from traffic damage and disfigurement.
31 6. Temperature of the material must be equal to the temperature of the road surface
32 before allowing traffic to travel on it.
33 B.Pavement Markings
34 1. Thermoplastic, hot applied, spray
35 a. This method shall be used to install and replace long lines – centerlines, lane
36 lines, edge lines, turn lanes, and dots.
37 b. Markings shall be applied at a 110-mil thickness.
38 c. Markings shall be applied at a 90-mil thickness when placed over existing
39 markings.
40 d. A sealer shall be used if concrete or asphalt is older than three (3) years.
41 e. Typical setting time shall be between 4 minutes and 10 minutes depending upon
42 the roadway surface temperature and the humidity factor.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 17 23 - 9
PAVEMENT MARKINGS
Page 9 of 11
1 f. Retroreflective raised markers shall be used to supplement the centerlines, lane
2 lines, and turn lanes. Refer to City Standard Detail Drawings for placement.
3 g. Minimum retroreflectivity of markings shall meet or exceed values shown in
4 subparagraph 2.4.A.1 of this Specification.
5 2. Thermoplastic, hot applied, extruded
6 a. This method shall be used to install and replace crosswalks and stop-lines.
7 b. Markings shall be applied at a 125-mil thickness.
8 c. Minimum retroreflectivity of markings shall meet or exceed values shown in
9 this Specification.
10 3. Preformed Polymer Tape
11 a. This method shall be used to install and replace crosswalks, stop-lines, and
12 legends.
13 b. The applied marking shall adhere to the pavement surface with no slippage or
14 lifting and have square ends, straight lines and clean edges.
15 c. Minimum retroreflectivity of markings shall meet or exceed values shown in
16 this Specification.
17 4. Preformed Heat-Activated Thermoplastic Tape
18 a. This method shall be used to install and replace crosswalks, stop-lines, and
19 legends.
20 b. The applied marking shall adhere to the pavement surface with no slippage or
21 lifting and have square ends, straight lines and clean edges.
22 c. Minimum retroreflectivity of markings shall meet or exceed values shown in
23 this Specification.
24 C.Raised Markers
25 1. All permanent raised pavement markers on Portland Cement roadways shall be
26 installed with epoxy adhesive. Bituminous adhesive is not acceptable.
27 2. All permanent raised pavement markers on new asphalt roadways may be installed
28 with epoxy or bituminous adhesive.
29 3. A chalk line, chain or equivalent shall be used during layout to ensure that
30 individual markers are properly aligned. All markers shall be placed uniformly
31 along the line to achieve a smooth continuous appearance.
32 D.Work Zone Markings
33 1. Work shall be performed with as little disruption to traffic as possible.
34 2. Install longitudinal markings on pavement surfaces before opening to traffic.
35 3. Maintain lane alignment traffic control devices and operations until markings are
36 installed.
37 4. Install markings in proper alignment in accordance with the Texas MUTCD and as
38 shown on the Drawings.
39 5. Place standard longitudinal lines no sooner than 3 calendar days after the placement
40 of a surface treatment, unless otherwise shown on the Drawings.
41 6. Place markings in proper alignment with the location of the final pavement
42 markings.
43 7. Do not use raised pavement markers for words, symbols, shapes, or diagonal or
44 transverse lines.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 17 23 - 10
PAVEMENT MARKINGS
Page 10 of 11
1 8. All markings shall be visible from a distance of 300 feet in daylight conditions and
2 from a distance of at least 160 feet in nighttime conditions, illuminated by low-
3 beam automobile headlight.
4 9. The daytime and nighttime reflected color of the markings must be distinctly white
5 or yellow.
6 10. The markings must exhibit uniform retroreflective characteristics.
7 11. Epoxy adhesives shall not be used to work zone markings.
8 3.4 REMOVALS
9 1. Pavement Marking and Marker Removal
10 a. The industry’s best practice shall be used to remove existing pavement markings
11 and markers.
12 b. If the roadway is being damaged during the marker removal, Work shall be
13 halted until consultation with the City.
14 c. Removals shall be done in such a matter that color and texture contrast of the
15 pavement surface will be held to a minimum.
16 d. Repair damage to asphaltic surfaces, such as spalling, shelling, etc., greater than
17 ¼ inch in depth resulting from the removal of pavement markings and markers.
18 Driveway patch asphalt emulsion may be broom applied to reseal damage to
19 asphaltic surfaces.
20 e. Dispose of markers in accordance with federal, state, and local regulations.
21 f. Use any of the following methods unless otherwise shown on the Drawings.
22 1) Surface Treatment Method
23 a) Apply surface treatment at rates shown on the Drawings or as directed.
24 Place a surface treatment a minimum of 2 feet wide to cover the existing
25 marking.
26 b) Place a surface treatment, thin overlay, or microsurfacing a minimum
27 of 1 lane in width in areas where directional changes of traffic are
28 involved or in other areas as directed by the City.
29 2) Burn Method
30 a) Use an approved burning method.
31 b) For thermoplastic pavement markings or prefabricated pavement
32 markings, heat may be applied to remove the bulk of the marking material
33 prior to blast cleaning.
34 c) When using heat, avoid spalling pavement surfaces.
35 d) Sweeping or light blast cleaning may be used to remove minor residue.
36 3) Blasting Method
37 a) Use a blasting method such as water blasting, abrasive blasting, water
38 abrasive blasting, shot blasting, slurry blasting, water-injected abrasive
39 blasting, or brush blasting as approved.
40 b) Remove pavement markings on concrete surfaces by a blasting method
41 only.
42 4) Mechanical Method
43 a) Use any mechanical method except grinding.
44 b) Flail milling is acceptable in the removal of markings on asphalt and
45 concrete surfaces.
46 2. If a location is to be paved over, no additional compensation will be allowed for
47 marking or marker removal.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORTH
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS
Revised June 10, 2022
Birchman Office Space
CPN 105553
32 17 23 - 11
PAVEMENT MARKINGS
Page 11 of 11
1 3.5 REPAIR / RESTORATION [NOT USED]
2 3.6 RE-INSTALLATION [NOT USED]
3 3.7 FIELD QUALITY CONTROL
4 A.All lines must have clean edges, square ends, and be uniform cross-section.
5 B.The density and quality of markings shall be uniform throughout their thickness.
6
7
C.The applied markings shall have no more than 5 percent, by area, of holes or voids and
shall be free of blisters.
8 3.8 SYSTEM STARTUP [NOT USED]
9 3.9 ADJUSTING [NOT USED]
10 3.10 CLEANING
11 A.Contractor shall clean up and remove all loose material resulting from construction
12 operations.
13 3.11 CLOSEOUT ACTIVITIES [NOT USED]
14 3.12 PROTECTION [NOT USED]
15 3.13 MAINTENANCE [NOT USED]
16 3.14 ATTACHMENTS [NOT USED]
17 END OF SECTION
18
Revision Log
DATE NAME SUMMARY OF CHANGE
11/22/13 S. Arnold Removed paint type marking, updated references, added sealer language
6/10/22 M Owen 1.1 A and 1.2 A – Revised to address preformed “contrast” pavement markings
19
Meacham Boulevard at Mercantile Drive
CPN 105417
0 | Page
ATTACHMENT A
CITY OF FORT WORTH
ADVANCE
TRANSPORTATION
CONTROLLER CABINET
(ATCC) SPECIFICATIONS
Page 1 of 12
Contents
ATC CABINET SPECIFICATIONS ...................................................................................................................... 3
ATC Cabinet Requirements ....................................................................................................................... 3
Cabinet Housings ...................................................................................................................................... 3
Housing Package ................................................................................................................................... 3
Housing Construction ............................................................................................................................ 3
Material Thickness ................................................................................................................................ 3
Welds .................................................................................................................................................... 3
Aluminum Surface Protection ............................................................................................................... 4
Anti‐Graffiti Paint .................................................................................................................................. 4
Enclosure Door Frames and Door Seals ................................................................................................ 4
Gasketing .............................................................................................................................................. 4
Cage Mounting Supports ...................................................................................................................... 4
Lifting Eyes and Exterior Bolt Heads ..................................................................................................... 4
Door Latches and Locks ......................................................................................................................... 4
Latch/Lock Mechanism ......................................................................................................................... 5
Lock & Keys ........................................................................................................................................... 5
Cam ....................................................................................................................................................... 5
Housing Ventilation ............................................................................................................................... 5
Intake & Filter ....................................................................................................................................... 5
Fan ......................................................................................................................................................... 5
Hinges .................................................................................................................................................... 5
Door Catches ......................................................................................................................................... 6
Police Panel ........................................................................................................................................... 6
Rack Cage .............................................................................................................................................. 6
Clearance between Rails ....................................................................................................................... 6
Cage Connection ................................................................................................................................... 6
Cage Location ........................................................................................................................................ 6
ATC Cabinet Assemblies ............................................................................................................................ 6
General .................................................................................................................................................. 6
Output Assembly (16‐Channel) ............................................................................................................. 7
Output Assembly (32‐Channel) ............................................................................................................. 7
Field Output Termination Assembly (16‐Channel) ............................................................................... 7
Input Assembly (24‐Channel) ................................................................................................................ 7
Input Assembly (48‐Channel) ................................................................................................................ 7
Service Assembly (1‐Flasher) ................................................................................................................ 8
Service Assembly (2‐Flasher) ................................................................................................................ 8
SB1/SB2 and DC Power Bus .................................................................................................................. 8
AC Clean Power Bus .............................................................................................................................. 8
ATC Cabinet Components ........................................................................................................................ 9
Model 2202‐HV Universal High‐Density Switch Pack / Flasher Units (HDSP‐FU) ................................. 9
Model 2212‐HV Cabinet Monitor Unit (CMUip) ................................................................................... 9
Model 2220 Auxiliary Display Unit (ADU) ............................................................................................. 9
Model 2218 Serial Interface Unit (SIU2) ............................................................................................. 10
Model 2216 Cabinet Power Supply (CPS) ........................................................................................... 10
Model 2205 High‐Density Flash Transfer Relay (HDFTR) .................................................................... 10
Main Contactor ................................................................................................................................... 10
Page 2 of 12
ATCC CABINET CONFIGURATION EXAMPLE ................................................................................................ 11
General .................................................................................................................................................... 11
Output Assembly (16‐Channel): .......................................................................................................... 12
Output Assembly (32‐Channel): .......................................................................................................... 12
Field Output Termination Assembly (16‐Channel): ............................................................................ 12
Input Assembly (24‐Channel): ............................................................................................................. 12
Page 3 of 12
ATC CABINET SPECIFICATIONS
This specification describes the Advanced Transportation Controller Cabinet (ATCC) for City of Fort
Worth. The City has chosen to stop procurement of 170 cabinets any more, and instead will be procure
and implement new ATC cabinets from here on after.
As a part of the ATC Cabinet, the intention is to standardize on internal Assemblies regardless of the
specific housing configuration of the ATC Cabinet chosen. The common parts shall include: Service
Assembly (SA), Input Assembly (IA), Output Assembly (OA), AC Clean Power Bus, combo SB1/SB2 and
DC Power Bus, Field Input Termination Assembly (FITA), and Field Output Termination Assembly
(FOTA). The housing and the cage(s) shall depend on the ATC Cabinet configuration. The ATC Cabinet
Inspection and Testing Requirement shall comply with the Electrical, Environmental and Testing
Requirements of the ITS Cabinet Standard v01.02.17b.
ATC Cabinet Requirements
This section describes the functional and physical requirements of the corresponding ATC Cabinets.
Cabinet Housings
Housing Package
The housings shall include, but not be limited to, the following:
• Enclosure & Doors
• Gasketing
• Lifting Eyes & External Bolt Heads
• Door Latches & Locks
• Ventilation
• Cage Supports & Mounting
• Door Hinges & Catches
• Police Panel
• Aluminum Surfaces
Housing Construction
The housing shall be rainproof. It shall have front and rear doors, each equipped with a lock and handle.
The enclosure top shall be crowned to prevent standing water.
Material Thickness
The enclosure, doors, lifting eyes, gasket channels, police panel door, spacer supports and all supports
welded to the enclosure and doors shall be fabricated of 0.125 inch minimum thickness aluminum sheet.
The filter shell, filter through, fan support and police panel enclosure shall be fabricated of 0.080 inch
minimum thickness aluminum sheet. The spacer supports shall have the option to use 0.059 inch
minimum stainless steel sheet.
Welds
All exterior seams for enclosure and doors shall be continuously welded and shall be smooth. All edges
shall be filled to a radius of 0.03125 inch minimum. Exterior cabinet welds shall be done by gas Tungsten
arc TIG process only. ER5356 aluminum alloy bare welding electrodes conforming to AWS A5.10
Page 4 of 12
requirements shall be used for welding on aluminum. Procedures, welders and welding operators shall
conform to the requirements and practices in AWS B3.0 and C5.6 for aluminum. Internal cabinet welds
shall be done by gas metal arc MIG or gas Tungsten arc TIG process.
Aluminum Surface Protection
The aluminum surface protection shall be either MILL FINISH or ANTI-GRAFFITI Paint.
Anti‐Graffiti Paint
The aluminum surface shall be cleaned, etched and rinsed. The cleaning and etching procedure shall be
to immerse in inhabited alkaline cleaner at 71 degrees C for five minutes (Oakite 61A, Diversey 909 or
equivalent in mix of the 6 to 8 ounces per gallon to distilled water). Rinse in cold water. Etch in a sodium
solution at 66 degrees C for 5 minutes 90.5 ounce sodium fluoride plus 5 ounces of sodium hydroxide mix
per gallon to distilled water. Rinse in cold water.
Desmut in a 50% by volume nitric acid solution at 20 degrees C for 2 minutes. Rinse in cold water. Dry
surfaces by preheating in an oven for 15 minutes at 400 degrees F. Remove and coat the surfaces using
TCI Wheel Silver # 9811- 0110 with a minimum film build of not more than 2 mils total thickness. Place
back into preheated oven for 10 minutes minimum at 360 degrees F to gel the base coat. Remove and
coat the surfaces using TCI Anti-graffiti Clear # 9810-0231. Place back into oven and fully cure at 380
degrees F for 40 minutes.
Enclosure Door Frames and Door Seals
The enclosure door frames shall be double-flanged out on all four sides and shall have strikers to hold
tension on, and to form a firm seal between, the door gasketing and the frame. The dimension between
the door edge and the enclosure external surface when the door is closed and locked shall be 0.156 inch
(+/-0.08 inches).
Gasketing
Gasketing shall be provided on all door openings and shall be dust-tight. Gaskets shall be 0.25 inches
minimum thickness closed cell neoprene or silicone (BOYD R- 108480 or equal) and shall be
permanently bonded to the metal. A gasket top and side channels shall be provided to support the top
gasket on the door to prevent gasket gravitational fatigue.
Cage Mounting Supports
Cage mounting supports shall be provided on either side, level with the bottom edge of the door opening,
for horizontal support and bolt attachment; side cage supports provided for the bracket cage supports;
and bracket cage support attachments.
Lifting Eyes and Exterior Bolt Heads
The housing shall be provided with 2 lifting eyes for placing the cabinet on its foundation. Each eye
opening shall have a minimum diameter of 0.75 inch. Each eye shall be able to support the weight load of
1000 lbs. All bolt heads shall be tamperproof type.
Door Latches and Locks
The latching handles shall have provision for padlocking in the closed position. Each handle shall be 0.75
inch minimum diameter stainless steel with a minimum of 0.50 inch shank. The padlocking attachment
shall be placed at 4 inch from the handle shank center. An additional 4 inch minimum gripping length shall
be provided.
Page 5 of 12
Latch/Lock Mechanism
The latching mechanism shall be a three-point draw roller type. The pushrods shall be turned edgewise at
the outward supports and have a cross section of 0.25 inch thick by 0.75 inch wide minimum. Rollers
shall have a minimum diameter of 0.875 inch with nylon wheels and steel ball bearings. When the door is
closed and latched, the door shall be locked. The lock and lock support shall be rigidly mounted on the
door. The lock shall be mounted in the upper quadrant, above the handle when in its full open position. In
the locked position, the bolt throw shall extend a minimum of 0.25 inch (+/-0.03125 inches) into the latch
cam area. A seal shall be provided to prevent dust or water entry through the lock opening.
Lock & Keys
The locks shall be Corbin 2 type. One key shall be supplied with each lock. The keys shall be removable
in the locked position only. The locks shall have rectangular, spacing loaded bolts.
The bolt shall have a 0.281 inch throw and shall be 0.75 inch wide by 0.375 inch thick.
Tolerance is 0.035 inch. A swing away cover shall be placed over the key entrance to protect the lock
mechanism.
Cam
The center latch cam shall be fabricated of a minimum thickness of 0.188 inch aluminum, or 11 gauge
steel. The bolt surface shall horizontally cover the cam thickness. The cam shall be structured to only
allow the door to open when the handle is moved toward the center of the door.
Housing Ventilation
Housing ventilation shall include intake, exhaust, filtration, and continuous running fan assembly or a
thermostat controlled fan.
Intake & Filter
The louvered vent depth shall be a maximum of 0.25 inch. A removable and reusable air filter shall be
housed behind the door vents. The filter filtration area shall cover the vent opening area.
A filter shell shall be provided that fits over the filter providing mechanical support for the filter.
This shell shall be louvered to direct the incoming air downward. The shell sides and top shall be bent
over a minimum of 0.25 inch to house the filter. The filter resident in its shell shall be held firmly in place
with a bottom trough and spring loaded upper clamp. No incoming air shall bypass the filter. The bottom
filter shall be formed into a waterproof sump with drain holes to the outside housing. The filter shall be 16
inch wide by 12 inch high by 0.875 inch thick. The filter shall be an ECO-AIR Product E35S or equal. The
intake (including filter with shell) and exhaust areas shall pass a minimum of 60 cubic feet of air per
minute for housing #1; 120 cubic feet of air per minute for Housing #3; and 26 cubic feet of air per minute
for housing #2.
Fan
Each electric fan shall be equipped with ball or roller bearings and shall have a minimum capacity of 100
cubic feet of free air delivery per minute. The fan shall be mounted within the housing and protected with
a finger guard. The fan should be powered from 120 Vac.
Hinges
Stainless steel hinges (two bolts per leaf) shall be provided to bolt the enclosure to the doors.
Housing #1 and housing #3 shall have four hinges per door, and housing #2 shall have three hinges per
door. Each hinge shall be 3.5 inch minimum length and have a fixed pin. The pin ends shall be welded to
hinge and ground smooth. The pins and bolts shall be covered by the door edge and not accessible when
the door is closed. A ground strap between the door and the main cabinet housing shall be required when
120 VAC components are mounted on the door.
Page 6 of 12
Door Catches
Front and rear doors shall be provided with catches to hold the door open at both 90 and 165 (+/-
10) Degrees. The catch minimum diameter shall be 0.375 inch aluminum rods. The catches must be
capable of holding the door open at 90 degrees in a 60 mph wind acting at an angle perpendicular to the
plane of the door.
Police Panel
A police panel assembly shall be provided to allow limited control access. The panel door shall be
equipped with a lock and master police key. The front and back of the panel shall be enclosed with a rigid
metal covering so that no parts having live voltage are exposed. The panel assembly shall have a drain to
prevent water from collecting within the assembly. The drain shall be channeled to the outside. The series
35X cabinets shall have one switch provided and labeled "SIGNALS ON - OFF” and one switch provided
and labeled "FLASH / AUTO". The MANUAL CONTROL ENABLE ON-OFF switch and a receptacle for
the INTERVAL ADVANCE cord shall be provided. An INTERVAL ADVANCE cord, six feet in length, shall
be provided.
Rack Cage
A standard rack cage shall be installed inside the housing for mounting of the ATC Controller unit and
cabinet assemblies. The EIA rack portion of the cage shall consist of four continuous, adjustable
equipment mounting angles. The mounting angle nominal thickness shall be 11- gauge plated steel. The
mounting angles shall be tapped with 10-32 threads with EIA universal spacing. The mounting angle shall
comply with standard EIA-310-B and shall be supported at the top and bottom by either welded or bolted
support angles to form a cage. The mounting angles shall provide holes to mount the side panels.
Clearance between Rails
Clearance between rails for mounting assemblies shall be 17.75 inch.
Cage Connection
The cage shall be bolted to the cabinet at four points via the housing cage supports and four points via
associated spacer brackets (top and bottom).
Cage Location
The cage(s) shall be centered within the cabinet door opening(s).
ATC Cabinet Assemblies
General
This document describes the functional and physical requirements of the ATC Cabinet. The ATC Cabinet
shall adhere to the following requirements:
The Assemblies shall be completely removable from or installable in the ATC Cabinet cage
without removing any other equipment and using only a standard slotted or Phillips screwdriver.
All equipment in the ATC Cabinet shall be clearly and permanently labeled.
The marker strips shall be made of material that can be easily and legibly written on using a
pencil or ballpoint pen. Marker strips shall be located immediately below the item they are to
identify and must be clearly visible with the items installed.
Guides (top and bottom) shall be provided for assembly plug-in units. The guides shall begin 0.50
inch from the assembly front panel face.
High-voltage components (over 50 V) shall not be exposed per NEC.
Page 7 of 12
All fuses, circuit breakers, switches (except police panel switches) and indicators shall be readily
visible and accessible when the ATC Cabinet front door is open.
When servicing the ATC Cabinet the Output Assembly, Input Assembly, Cabinet Power Supply,
and Controller shall be replaceable without putting the intersection into a dark condition, i.e. Flash
mode shall be maintained.
Wire raceway shall be integrated as part of the ATC Cabinet allowing for neat internal and field
wiring.
Output Assembly 24VDC bypass switch shall provide a momentary 24VDC voltage to the HDSPs
during flash mode for troubleshooting purposes.
All Assemblies shall be modular with pluggable cabling.
Replacing the ATC Cabinet fan shall not require any tool.
Output Assembly (16‐Channel)
The Output Assembly shall be an EIA-310B rack mounted assembly. The Output Assembly shall house
eight Model 2202-HV Universal High-Density Switch Pack / Flasher Units (HDSP-FU) providing forty eight
load circuits.
One resident Model 2218 Serial Interface Unit (SIU2) shall provide interface and control.
The Output Assembly shall house a CMUip-2212-HV Cabinet Monitor Unit (CMUip), Main Contactor, Stop
Time Switch, Flash / Auto Switch, four Circuit Breakers and Momentary 24VDC Bypass Switch.
Output Assembly (32‐Channel)
The Output Assembly shall be an EIA‐310B rack mounted assembly. The Output Assembly shall house
sixteen Model 2202‐HV Universal High‐Density Switch Pack / Flasher Units (HDSP‐FU) providing ninety
six load circuits.
Two resident Model 2218 Serial Interface Units (SIU2) shall provide interface and control.
The Output Assembly shall house a CMUip-2212-HV Cabinet Monitor Unit (CMUip), the Main Contactor,
Stop Time Switch, Flash / Auto Switch, eight Circuit Breakers and Momentary 24VDC Bypass Switch.
Field Output Termination Assembly (16‐Channel)
The 16-Channel Field Output Termination Assembly shall be coupled with the 16-Channel Output
Assembly and shall house eight Model 2205 High-Density Flash Transfer Relays (HDFTR).
The HDFTR and Flash Program Blocks (FPB) shall be provided to control and select the color (red,
yellow, or dark) during ATC Cabinet Flash mode.
Transient Protectors shall be provided at the field terminals for the protection of the HDSP-FU when
requested.
Input Assembly (24‐Channel)
The Input Assembly shall be an EIA-310B rack mounted assembly providing twelve slots of
22/44 pin PCB sockets. A Model 2218 Serial Interface Unit (SIU2) shall be provided in its location mated
to a DIN 96-pin connector. The SIU2 shall provide interface and control between the ATC Controller and
the input units via system SB1/SB2. This Input Assembly shall be wired for a mix of twelve 2-channel and
4-channel devices.
Input Assembly (48‐Channel)
The Input Assembly shall be an EIA-310B rack mounted assembly providing twelve slots of 22/44 pin
PCB sockets. Two Model 2218 Serial Interface Units (SIU2) shall be provided in its location mated to a
DIN 96-pin connector. The SIU2 shall provide interface and control between the ATC Controller and the
input units via system SB1/SB2. The Input Assembly shall be capable of supporting twelve 4-channel
devices. This Input Assembly shall be wired for a mix of twelve 2-channel and 4-channel devices.
Page 8 of 12
Service Assembly (1‐Flasher)
The Service Assembly shall be modular and shall be mounted on the lower left of the EIA when viewed
from the front. It shall house: a Model 2202-HV Universal HDSP-FU, EDCO SHA-1250 or approved
equal, BBS landing wire terminals, GFCI, Convenient Outlets and Circuit Breakers.
Service Assembly (2‐Flasher)
The Service Assembly shall be modular and shall be mounted on the lower left of the EIA when viewed
from the front. It shall house: two Model 2202-HV Universal HDSP-FU, EDCO SHA-1250 or approved
equal, BBS landing wire terminals, GFCI, Convenient Outlets and Circuit Breakers.
SB1/SB2 and DC Power Bus
SB1/SB2 and DC Power Bus shall include eight DB25 connectors to interconnect the SB1/SB2
communication ports of the assemblies and controller. It shall include a termination circuit at the end of
the connections (S8) to prevent radio frequency signal reflection. SB1/SB2 and DC Power Bus shall
include one Phoenix plug block or equal to bring the DC power to the SB1/SB2 and DC Power Bus; such
power shall be distributed to the ATC Cabinet Assemblies through seven Phoenix receptacle blocks or
equal. The copper traces for the DC voltages shall support at least 10 Amps.
The SB1/SB2 and DC Power Bus shall be mounted in the EIA rails and it shall swing out to provide
access to the back of the assemblies mounted in the opposite side.
AC Clean Power Bus
The AC Clean Power Bus shall include eight single NEMA 5-15 receptacles, to provide AC clean power to
the ATC Cabinet Assemblies, the controller and Cabinet Power Supply. It shall be mounted on the EIA
rails and it shall swing out to provide access to the back of the assemblies mounted in opposite side.
Page 9 of 12
ATC Cabinet Components
Model 2202‐HV Universal High‐Density Switch Pack / Flasher Units (HDSP‐FU)
When located in the Output Assembly, the Model 2202-HV HDSP-FU shall be:
Two channels per card
o 6 outputs rated at 5 mA to 1 Amp (1-135 watts)
o Over-current protected
o Load current monitored for each output
Modular PCB-based plug-in device containing six solid-state switches
1.2” x 4.5” card format with DIN style connector
LED compatible to <2 watts
CMUip controlled output over-ride for fail-safe operation
“ID” Led for each channel driven by CMUip based trouble-shooting
Serial Bus #3 compatible
When located in the Service Assembly, the Model 2202-HV HDSP-FU shall be:
Two channels per card
o Four outputs rated at 5 mA to 2 Amps each
o Over-current protected
o Load current monitored for each output
Modular PCB-based plug-in device containing four solid-state switches
1.2” x 4.5” card format with DIN style connector
Supports CMUip Flasher Alarm function
Model 2212‐HV Cabinet Monitor Unit (CMUip)
The CMUip-2212-HV Cabinet Monitor Unit (CMUip) shall be a compact, pluggable and modular.
32 channel fully monitor output capability
Direct SB#3 communication to each HDSP-FU for field voltage and load current status
Ethernet port for diagnostics
CMUip is programmed with interchangeable Datakey
Built-in Diagnostic Wizard: The CMUip analyzes the ATC Controller output commands and
HDSP-FU field input status
o Isolates whether the cabinet fault was caused by an ATC malfunction or a failure in the
load bay or field wiring
o Identifies the faulty channel(s) and output directly
o Provides guidance on how the technician should isolate the cause of the malfunction
Model 2220 Auxiliary Display Unit (ADU)
The ADU-2220 shall be a rack mounted display module.
32 channels of RYG status plus a Blue LED for fault status provides a full view of the intersection
signal states.
The LCD menu driven display provides detailed status information from the CMUip along with an
interface to the patented EDI SmartMonitor® technology.
o The built-in Diagnostic Wizard provides a concise view of the signal states involved in the
fault, pinpoints faulty signal inputs, and provides guidance on how the technician should
isolate the cause of the malfunction.
View status, configuration settings, voltages, currents, and event logs.
Page 10 of 12
Model 2218 Serial Interface Unit (SIU2)
The Model 2218 Serial Interface Unit (SIU2) shall be modular PCB-based plug-in device.
SIU2 is housed in each Input and Output Assembly.
o The SIU2 converts serial data from the ATC Controller into parallel outputs to the
assembly.
o The SIU2 converts parallel inputs from the assembly into serial data to the ATC
Controller.
54 programmable inputs / outputs
4 opto-isolated inputs
Diagnostic monitoring software uses the front panel EIA-232 port
1.5 inch width faceplate
Model 2216 Cabinet Power Supply (CPS)
The PS-2216 Cabinet Power Supply (CPS) shall be a rack mounted and high efficiency design and shall
be either of the following:
PS2216EP-24-HV Cabinet Power Supply (48v, 24v)
PS2216-2412-HV Cabinet Power Supply (48v, 24v, 12v)
Outputs
o 1 Amp at 48 Vdc
o 5 Amps at 24 Vdc (maximum)
o 5 Amps at 12 Vdc (maximum) for PS-2216-2412 only
Power Factor corrected input
1U height with Phoenix connector or equal
Fuse and LED indicator for each output
.
Model 2205 High‐Density Flash Transfer Relay (HDFTR)
The Model 2205 High-Density Flash Transfer Relay (HDFTR) shall be:
Hermetically Sealed Cover - Moisture proof, prevents contact contamination, insect proof (fire ant,
etc.)
Dry Nitrogen Filled - Protects contacts from corrosion, prevents condensation
Metal Can - Robust design, shock/impact resistant
Solid Pins - Robust, bend proof
Ratings: 5 Amps @ 120 Vac switching, 10 Amps surge
48 Vdc coil voltage
LED indicator to display contact transfer position
Main Contactor
Input: 48 Vdc coil voltage
Output: 60 Amps @ 120Vac
Contacts: SPST-NO
Equipped with input indicator
Operation at rated current:1,000,000
Power: less than 3 Watts
Located in the Output Assembly
Page 11 of 12
ATCC CABINET CONFIGURATION EXAMPLE
General
The ATC Cabinet shall consist of Assemblies and Components needed to carry out a specific application.
ATC Cabinet versions provided here are EXAMPLES of possible configurations.
Traffic Signal Cabinet Application:
350i: 4-Door Cabinet with “P/R” Base Ground Mount
352i: 2-Door Cabinet with “332/342” Base Ground Mount
356i: 2-Door Cabinet with”336/356” Base, Adaptor Mount
ATC Cabinet Configuration Table
Modules / Assemblies 352i-ATCC 356i-ATCC 350i-ATCC
Housing #1 / Cage #1 1
Housing #2 / Cage #2 1
Housing #3 / Two Cage #1 1
Side Panel Cage #1 2 4
Side Panel Cage #2 2
Service Assembly (1-Flasher) 1 1
Service Assembly (2-Flasher) 1
AC Clean Power Bus 1 1 1
SB1 / SB2 and DC Power Bus 1 1 12
Output Assembly (16-Channel) or (32-
Channel) 1 1 1
Field Output Termination Assembly (16-
Channel) 12 1 12
Input Assembly (24-Channel) maximum
120 channels, or
Input Assembly (48-Channel) maximum
120 channels
13 1 15
13 1 13
Field Input Termination Assembly * * *
Model 2216 Cabinet Power Supply 1 1 1
Auxiliary Display Unit 1 1 1
LED - Cabinet Light Assembly 12 12 12
Drawer Assembly 1 1 12
*This is optional and depends on the end user’s discretion.
Page 12 of 12
The ATC Cabinet shall also be supplied with the following components:
Output Assembly (16‐Channel):
(1-8ea **) Model 2202-HV HDSP-FU
(1 ea) Model 2218 SIU2
(1 ea) Model 2212-HV CMUip
Output Assembly (32‐Channel):
(1-16ea **) Model 2202-HV HDSP-FU
(2 ea) Model 2218 SIU2
(1 ea) Model 2212-HV CMUip
Field Output Termination Assembly (16‐Channel):
(1-8 ea **) Model 2205 HDFTR
(1-8 ea **) Transient Protector
(16 ea) Red Flash Program Blocks
(4 ea) Yellow Flash Program Blocks
(4 ea) White Flash Program Blocks
Input Assembly (24‐Channel):
(1 ea) Model 2218 SIU2
Input Assembly (48‐Channel):
(2 ea) Model 2218 SIU2
Service Assembly (1‐Flasher):
(1 ea) Model 2202-HV HDSP-FU
(1 ea) EDCO SHA-1250 or approved equal
Service Assembly (2‐Flasher):
(2 ea) Model 2202-HV HDSP-FU
(1 ea) EDCO SHA-1250 or approved equal
** Quantity at the end user’s discretion.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
SPECIAL SPECIFICATION
ADVANCED TRANSPORTATION CONTROLLER
Attachment B
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page i
Table of Contents
SECTION 1 – GENERAL SPECIFICATIONS ....................................................................................... 1
2070.1 Description. ........................................................................................................................... 1
2070.2 Interchangeability ................................................................................................................. 1
2070.3 Compliance............................................................................................................................ 1
2070.4 Reference Standards and Specifcations ................................................................................ 1
2070.5 Barcode ................................................................................................................................. 2
2070.6 Warranty ............................................................................................................................... 2
2070.7 Definitions. ............................................................................................................................ 2
2070.8 Assemblies and Associated Modules .................................................................................... 3
2070.9 Documentation ..................................................................................................................... 4
2070.10 Packaging .......................................................................................................................... 5
2070.11 Delivery ............................................................................................................................. 5
2070.12 Measurement and Payment ............................................................................................. 5
2070.13 Metals ............................................................................................................................... 5
2070.14 Aluminum .......................................................................................................................... 5
2070.15 Stainless Steel ................................................................................................................... 5
2070.16 Cold Rolled Steel ............................................................................................................... 5
2070.17 Plating ............................................................................................................................... 5
2070.18 Mechanical Hardware ....................................................................................................... 5
2070.19 Electrical Isolation ............................................................................................................. 5
2070.20 Equipment Grounding ....................................................................................................... 6
2070.21 Daughter Boards ............................................................................................................... 6
COMPONENTS ...................................................................................................................................... 6
2070.22 General .............................................................................................................................. 6
2070.23 Electronic Components ..................................................................................................... 6
2070.24 Capacitors.......................................................................................................................... 6
2070.25 Potentiometers ................................................................................................................. 6
2070.26 Resistors ............................................................................................................................ 7
2070.27 Semiconductor Devices ..................................................................................................... 7
2070.28 Transformers and Inductors .............................................................................................. 7
2070.29 Triacs ................................................................................................................................. 7
2070.30 Circuit Breakers and Fuses Circuit Breakers ...................................................................... 7
2070.31 Load Circuit Breaker Auxiliary Internal Switches .............................................................. 7
2070.32 Fuses.................................................................................................................................. 8
2070.33 Switches ............................................................................................................................ 8
2070.34 Terminal Blocks ................................................................................................................. 8
2070.35 Wiring, Cabling, and Harnesses ......................................................................................... 8
2070.36 Indicators and Character Displays ..................................................................................... 9
2070.37 Connectors ........................................................................................................................ 9
2070.38 Surge Protection Device .................................................................................................. 10
MECHANICAL .................................................................................................................................... 10
2070.39 Assemblies ...................................................................................................................... 10
2070.40 Locking Devices ............................................................................................................... 10
2070.41 PCB Design and Connectors ............................................................................................ 10
2070.42 Model and Serial Numbers ............................................................................................. 10
2070.43 Workmanship .................................................................................................................. 11
2070.44 Tolerances ....................................................................................................................... 11
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page ii
ENGINEERING .................................................................................................................................... 11
2070.45 Human Engineering ......................................................................................................... 11
2070.46 Design Engineering .......................................................................................................... 11
2070.47 Generated Noise ............................................................................................................. 11
PRINTED CIRCUIT BOARDS ........................................................................................................... 11
2070.48 Design, Fabrication and Mounting. ................................................................................. 11
2070.49 Soldering ......................................................................................................................... 12
2070.50 Definitions ....................................................................................................................... 12
QUALITY CONTROL ......................................................................................................................... 13
2070.51 General ............................................................................................................................ 13
2070.52 Manufacturers’ Quality Control and Testing Certification .............................................. 13
2070.53 Components. ................................................................................................................... 13
2070.54 Subassembly, Unit or Module ......................................................................................... 13
2070.55 Pre‐delivery Repair .......................................................................................................... 13
2070.56 Electrical, Environmental and Testing Requirements ..................................................... 13
SECTION II - TYPE 2070 ATC CONTROLLER UNIT ...................................................................... 14
2070.57 Controller Unit ................................................................................................................ 14
2070.58 Unit Version Configuration ............................................................................................. 14
2070.59 Communication and Option Modules ............................................................................. 14
2070.60 Operating System & Board Support Package Requirements .......................................... 14
2070.61 Chassis ............................................................................................................................. 15
2070.62 Power Fail and Power Restoration Operation ................................................................ 15
2070.63 Power Limitations ........................................................................................................... 15
2070.64 EIA‐485 Communications Circuitry ................................................................................. 15
2070.65 EIA‐485 Line Drivers/Receivers ....................................................................................... 15
2070.66 Sockets ............................................................................................................................ 15
2070.67 Frame Address ................................................................................................................ 16
SECTION III - TYPE 2070-1C CPU Module ........................................................................................ 17
2070.68 Type 2070 – 1C Module .................................................................................................. 17
2070.69 The C13S Connector ........................................................................................................ 17
2070.70 Serial Port SP8 ................................................................................................................. 17
2070.71 LINESYNC and POWERDOWN ......................................................................................... 17
2070.72 NRESET ............................................................................................................................ 17
2070.73 Engine Board ................................................................................................................... 17
2070.74 Ethernet Ports ................................................................................................................. 17
2070.75 Network Switches ........................................................................................................... 17
2070.76 Universal Serial Bus (USB) ............................................................................................... 18
2070.77 Host Module Identification ............................................................................................. 18
2070.78 ATC Controller Board Support Package (BSP) ................................................................. 18
SECTION IV - MODEL 2070-1C CPU (Engine Board) ....................................................................... 21
2070.79 General ............................................................................................................................ 21
2070.80 Model 2070 ‐1C CPU Module Processor ......................................................................... 21
2070.81 FLASH Memory ................................................................................................................ 21
2070.82 Dynamic RAM (DRAM) .................................................................................................... 21
2070.83 Static RAM (SRAM) .......................................................................................................... 21
2070.84 Standby Power ................................................................................................................ 21
2070.85 Real‐Time Clock (RTC) ..................................................................................................... 21
2070.86 CPU_RESET ...................................................................................................................... 21
2070.87 CPU_ACTIVE .................................................................................................................... 21
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page iii
APPLICATION PROGRAM INTERFACE (API) ............................................................................ 22
2070.88 ATC API Standard ............................................................................................................ 22
2070.89 Integrated Security .......................................................................................................... 22
2070.90 Serial Communications Interface Ports ........................................................................... 22
2070.91 Serial Peripheral Interface Port ....................................................................................... 24
2070.92 Serial Peripheral Interface (SPI) ...................................................................................... 24
2070.93 Data Key .......................................................................................................................... 25
2070.94 Start‐Up Consideration and Sequence ............................................................................ 26
SECTION V – TYPE 2070-2 FIELD I/O MODULE ............................................................................. 27
2070.95 Type 2070‐2A Field I/O Module (FI/O) ............................................................................ 27
2070.96 Type 2070‐2B Field I/O Module (FI/O) ............................................................................ 27
2070.97 Field F/O Controller Unit (FCU) ....................................................................................... 27
2070.98 Parallel Input Port ........................................................................................................... 27
2070.99 Parallel Output Port ........................................................................................................ 27
2070.100 Output Operation ............................................................................................................ 27
OTHER MODULE CIRCUIT FUNCTIONS. ................................................................................... 28
2070.101 Maximum Capacitive Load .............................................................................................. 28
2070.102 External WDT “Enable” Shunt/Toggle Switch ................................................................. 28
2070.103 WATCHDOG Circuit ......................................................................................................... 28
2070.104 One KHz Reference ......................................................................................................... 28
2070.105 32 Bit Millisecond Counter .............................................................................................. 28
2070.106 Power Up ......................................................................................................................... 28
2070.107 Logic Switch ..................................................................................................................... 28
SERIAL COMMUNICATIONS/LOGIC CIRCUITRY ................................................................... 28
2070.108 System Serial Port 5 (SP5) EIA 485 Signal........................................................................ 28
2070.109 System Serial Port 3 (SP3) EIA 485 Signal........................................................................ 29
2070.110 LINE SYNC and POWER DOWN ........................................................................................ 29
2070.111 CPU RESET and POWER UP ............................................................................................. 29
2070.112 Module 2070‐2B .............................................................................................................. 29
2070.113 Internal Isolation ............................................................................................................. 29
2070.114 Buffers ............................................................................................................................. 29
I/O FUNCTIONS. ................................................................................................................................. 29
2070.115 Inputs .............................................................................................................................. 29
2070.116 Data Filtering ................................................................................................................... 29
2070.117 Outputs ........................................................................................................................... 30
2070.118 Standard Function ........................................................................................................... 30
2070.119 CASE A ............................................................................................................................. 30
2070.120 Interrupts ........................................................................................................................ 31
2070.121 Communication Service Routine ..................................................................................... 31
2070.122 Communication Processing ............................................................................................. 31
2070.123 Input Processing .............................................................................................................. 31
DATA COMMUNICATIONS PROTOCOLS. .................................................................................. 31
2070.124 Communication Protocol ................................................................................................ 31
2070.125 Frame Types .................................................................................................................... 32
2070.126 Request Module Status ................................................................................................... 32
2070.127 Status Bits ........................................................................................................................ 33
2070.128 Request Module Status ................................................................................................... 33
2070.129 MC Management ............................................................................................................ 33
2070.130 Configure Inputs Commands........................................................................................... 34
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page iv
2070.131 Poll Raw Input Data ......................................................................................................... 34
2070.132 Poll Filtered Input Data ................................................................................................... 35
2070.133 Poll Input Transition Buffer ............................................................................................. 36
2070.134 Active Input ..................................................................................................................... 37
2070.135 The Block Number byte ................................................................................................... 37
2070.136 Set Outputs ..................................................................................................................... 37
2070.137 Configure Input Tracking Functions ................................................................................ 38
2070.138 Definitions are as follows: ............................................................................................... 38
2070.139 Timestamp Value ............................................................................................................ 39
2070.140 Outputs Tracks Inputs ..................................................................................................... 39
2070.141 Number of Item ............................................................................................................... 39
2070.142 Configure Complex Output Functions ............................................................................. 39
2070.143 Configure Complex Outputs Bit Fields ............................................................................ 40
2070.144 Controlling Input Signals ................................................................................................. 41
2070.145 Number of Items ............................................................................................................. 41
2070.146 Configure Watchdog ....................................................................................................... 41
2070.147 Timeout Value ................................................................................................................. 42
2070.148 Watchdog Timeout Value ............................................................................................... 42
2070.149 Controller Identification .................................................................................................. 42
2070.150 Module Identification ..................................................................................................... 42
SECTION VI - TYPE 2070-3D FRONT PANEL ASSEMBLY. ........................................................... 43
2070.151 General ............................................................................................................................ 43
2070.152 Keyboards ........................................................................................................................ 43
2070.153 Ethernet Port ................................................................................................................... 43
2070.154 FPA Layout....................................................................................................................... 43
2070.155 CPU Active Indicator ....................................................................................................... 43
2070.156 Display Liquid Crystal Display (LCD) ................................................................................ 43
2070.157 Characters and Angles of Liquid Crystal Display (LCD) .................................................... 43
2070.158 Backlight .......................................................................................................................... 43
2070.159 Cursor Display ................................................................................................................. 44
2070.160 FPA Controller ................................................................................................................. 44
2070.161 FPA RESET ........................................................................................................................ 44
2070.162 Keypress .......................................................................................................................... 44
2070.163 Auto‐Repeat .................................................................................................................... 44
2070.164 AUX .................................................................................................................................. 44
2070.165 Controller Circuitry .......................................................................................................... 44
2070.166 Character Overwrite ........................................................................................................ 45
2070.167 Auto‐Wrap ....................................................................................................................... 45
2070.168 Cursor Positioning ........................................................................................................... 45
2070.169 Blinking Characters ......................................................................................................... 45
2070.170 Tab Stops ......................................................................................................................... 45
2070.171 Auto‐Scroll ....................................................................................................................... 45
2070.172 Displayable Characters .................................................................................................... 46
2070.173 Display Back Light Illuminate .......................................................................................... 46
2070.174 Command Codes ............................................................................................................. 46
2070.175 Controller Circuit ............................................................................................................. 46
2070.176 C50 ENABLE FUNCTION ................................................................................................... 46
2070.177 Front Panel ...................................................................................................................... 46
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page v
SECTION VII - TYPE 2070-3D USB FRONT PANEL ASSEMBLY ................................................. 47
2070.178 General ............................................................................................................................ 47
2070.179 Universal Serial Bus (USB) ............................................................................................... 47
2070.180 Alternate Front Panel Assembly Layout .......................................................................... 47
2070.181 1C‐CPU USB ..................................................................................................................... 47
SECTION VIII - TYPE 2070-4A POWER SUPPLY MODULE. ........................................................ 48
2070.182 Model 2070‐4A Power Supply Module ........................................................................... 48
2070.183 On/Off Power Switch ...................................................................................................... 48
2070.184 Input Protection .............................................................................................................. 48
2070.185 +5VDC Standby Power .................................................................................................... 48
2070.186 Monitor Circuitry ............................................................................................................. 48
2070.187 ACFAIL/POWER DOWN ................................................................................................... 48
2070.188 Monitor Circuitry Switch ................................................................................................. 48
2070.189 60 Hz Square Wave LINESYNC ......................................................................................... 48
2070.190 LINESYNC ......................................................................................................................... 49
2070.191 Line/Load Regulation ...................................................................................................... 49
2070.192 Efficiency ......................................................................................................................... 49
2070.193 Ripple and Noise ............................................................................................................. 49
2070.194 Voltage Overshoot .......................................................................................................... 49
2070.195 Overvoltage Protection ................................................................................................... 49
2070.196 Circuit Protection ............................................................................................................ 49
2070.197 Inrush Current ................................................................................................................. 49
2070.198 Holdup Time .................................................................................................................... 49
2070.199 Remote Sense ................................................................................................................. 50
SECTION IX - UNIT CHASSIS TYPE 2070. ........................................................................................ 51
2070.200 General ............................................................................................................................ 51
2070.201 Serial Motherboard ......................................................................................................... 51
SECTION X - TYPE 2070 NEMA ........................................................................................................... 52
2070.202 ATC NEMA Standard Controller Units ............................................................................. 52
2070.203 N1C Unit Consisting ......................................................................................................... 52
2070.204 N2C Unit Consisting ......................................................................................................... 52
2070.205 Address ............................................................................................................................ 52
FIELD I/O MODULE ........................................................................................................................... 52
2070.206 2070‐2N Field I/O Module .............................................................................................. 52
2070.207 Requirements Exceptions ............................................................................................... 52
2070.208 Types ............................................................................................................................... 53
2070.209 Power .............................................................................................................................. 53
2070.210 Isolation ........................................................................................................................... 53
2070.211 FCU Output ...................................................................................................................... 53
2070.212 Connectors A, C15S pin out and functions ...................................................................... 53
2070.213 Serial Port 3 ..................................................................................................................... 53
4AN POWER SUPPLY MODULE ..................................................................................................... 54
2070.214 4AN POWER SUPPLY MODULE ........................................................................................ 54
MODEL 2070- 8 FIELD I/O MODULE ............................................................................................. 54
2070.215 2070‐9 Module ................................................................................................................ 54
2070.216 Module Front Panel ........................................................................................................ 54
2070.217 Label ................................................................................................................................ 54
2070.218 Module Power Supply ..................................................................................................... 54
2070.219 Incoming AC Power ......................................................................................................... 55
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page vi
2070.220 Module PC Boards ........................................................................................................... 55
2070.221 POWERDOWN, NRESET, and LINESYNC .......................................................................... 55
2070.222 Requirements .................................................................................................................. 55
2070.223 EIA‐232 Serial Port .......................................................................................................... 55
2070.224 HAR 2 Harness ................................................................................................................. 55
2070.225 Fault and Voltage Monitor Circuitry ............................................................................... 55
2070.226 Figures ............................................................................................................................. 56
SECTION XI - TYPE 2070 PERIPHERAL EQUIPMENT. ................................................................ 57
2070.227 General Notes ................................................................................................................. 57
2070.228 Type 2070‐6 A & B Async/ Modem Serial Communication Modules.............................. 57
2070.229 Type 2070‐7A Async Serial Comm Module ..................................................................... 58
SECTION XII – GLOSSARY .................................................................................................................. 59
2070.230 Terms and Abbreviations ................................................................................................ 59
APPENDIX A – ELECTRICAL ENVIRONMENTAL AND TESTING REQUIREMENTS .......... 63
A1 ENVIORNMENTAL AND TEST PROCEDURES ........................................................................ 63
A2 Inspection ............................................................................................................................ 64
A3 Definitions of Design Acceptance Testing (DAT) and Production Testing. ......................... 64
A4 Environmental and Operating Requirements ..................................................................... 64
A5 Transients, Power Service. .................................................................................................. 65
A6 Nondestructive Transient Immunity. .................................................................................. 66
TEST FACILITIES .............................................................................................................................. 66
A1 Test Facilities ....................................................................................................................... 66
TEST PROCEDURE: TRANSIENTS, TEMPERATURE, VOLTAGE, AND HUMIDITY ........ 66
A1 Test A: Placement in Environmental Chamber and Check‐Out of Hook‐Up ....................... 66
A2 Test B: Transient Tests (Power Service) .............................................................................. 66
A3 Test C—Low‐Temperature Low‐Voltage Tests.................................................................... 68
A4 Test D—Low‐Temperature High‐Voltage Tests .................................................................. 69
A5 Test E—High‐Temperature High‐Voltage Tests .................................................................. 69
A6 Test F—High‐Temperature Low‐Voltage Tests ................................................................... 70
A7 Test G—Test Termination ................................................................................................... 70
A8 Test H—Appraisal of Equipment under Test ...................................................................... 70
A9 Vibration Test ...................................................................................................................... 71
A10 Shock (Impact) Test. ............................................................................................................ 72
A11 Power Interruption Tests .................................................................................................... 73
APPENDIX B – DETAILED DRAWINGS ............................................................................................ 75
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A1 of 107
SPECIAL SPECIFICATION
ADVANCED TRANSPORTATION CONTROLLER
SECTION 1 – GENERAL SPECIFICATIONS
2070.1 Description.
Furnish Type 2070 Advanced Transportation Controller (ATC) unit. The Advanced
Transportation Controller (ATC) is a general purpose programmable controller that is
intended for continuous unattended operation in harsh environments.
This specification defines specific, interchangeable modules that are combined to form the
Type 2070 ATC, capable of running control software that could be provided from a variety
of providers. This specification lays out compositions for the Type 2070 ATC
configurations to be used in the City. The Type 2070 ATC is designed such that all
components are fully standardized and are therefore interchangeable.
All furnished equipment shall be new and unused. Vacuum or gaseous tubes and electro-
mechanical devices (unless specifically called out) shall not be used.
2070.2 Interchangeability
All assemblies described in this specification and their respective associated devices shall
electrically and mechanically intermate and be compatible with each other.
2070.3 Compliance.
The Supplier shall guarantee that the 2070 ATC Controller Unit facilitates application
portability by abstracting application software from the ATC hardware thereby allowing
application programs to operate on the 2070 ATC, regardless of software manufacturer. This
will be accomplished thorough a layered software architecture and open source operating
system as defined in 2070.78 of this specification.
“Burn-in” each controller unit and provide a Quality Control report as described in this
specification. The certification report shall be furnished by the manufacturer and attached to
each controller unit. The report shall indicate the dates of the “burn-in” period, number of
hours, and “burn-in” temperature, and other pertinent test information requested by the City.
2070.4 Reference Standards and Specifcations
This specification incorporates the latest approved versions of the following standards by
reference:
Advanced Transportation Controller (ATC) Standard Version 5.2b published jointly
by the American Association of State Highways and Transportation Officials
(AASHTO), the Institute on Transportation Engineers (ITE), and the National Electrical
Manufacturers Association (NEMA), January 24, 2006.
Transportation Electrical Equipment Specifications published by the State of
California, Department of Transportation (CALTRANS), dated March 12, 2009.
NEMA TS2-2003 v2.03 – Traffic Controller Assemblies with NTCIP Requirements –
Published by the National Electrical Manufacturers Association, 2003
When specifications defined in this specification differ from specifications in the above
referenced documents, this specification shall prevail.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A2 of 107
Any applicable update and/or revision approved and incorporated into these standards
and specifications shall be automatically incorporated into the City’s ATC
Specification.
2070.5 Barcode
Each Controller Unit shall have a unique barcode place on the front. The Barcode shall be
.002” Premium polyester material or approved equal. The barcode shall be 1 ½” x 3/4”. The
adhesive shall be MC59 or approved equal. Temperature range shall be –40 degrees
Fahrenheit to 250 degrees Fahrenheit. Barcode shall be Code 39. The shelf life is 12
months when stored at 72 degrees Fahrenheit and 50 percent relative humidity. The barcode
for the controller unit shall be 4.7 CPI (low density). All barcodes are guaranteed to have no
skips in sequence. All barcodes and numerals shall be subsurface printed and produce in
black.
2070.6 Warranty
The Vendor shall fully guarantee all items, equipment and materials provided under this
contract. The duration of the warranty or guarantee shall be the standard of the industry,
with a minimum period of 36 MONTHS from the date of shipment to the City. The Vendor
shall mark each device with the date of shipment and "City of Fort Worth (or purchasing
agency)." The warranty shall cover all Manufacturer's defects, including parts, labor, and
shipping costs. Any item found not in accordance with this Specification will be rejected,
and returned to Vendor at the Vendor's expense for immediate replacement.
Repair: The Manufacturer shall perform warranty repair or replacement and return
component within 30 calendar days after receiving equipment.
Extension: Following warranty repair or replacement, the warranty period (for that item or
module) shall be extended for an additional period of one (1) year.
Vendor: If the equipment Vendor is other than the Manufacturer, then the Vendor shall be
fully responsible for all warranties and requirements of this Specification.
Vendor’s Responsibility: The City will determine the supplier’s responsibility for any
controller unit assembly failure if failure occurs within the warranty period. The City will
contact the supplier with instructions on the pickup and delivery of defective controller
assembly component. The supplier shall be responsible for all shipping and related handling
charges.
2070.7 Definitions.
The Type 2070 Controller Housing defines a controller housing that is intended to fit an EIA
19 in. rack mounted form commonly found in the Type 332 and ITS family of cabinets. In
addition, A NEMA base module is defined for those NEMA TS1 and TS2 shelf mounted
applications.
Engine Board. All computational functions are concentrated on an engine board within
the ATC that meets requirements of CPU and RAM memory, FLASH memory storage,
serial ports, Ethernet interface, standardized pin out interface, clock/calendar
maintenance, and Board Support Package.
CPU Module. The CPU module consists of the main CPU, memory, software and
interfaces to the remainder of the controller. The CPU module identified in this
specification is the Type 2070-1C configuration and is intended to interface with the
“engine board” specified by the ATC AASHTO/ITE/ NEMA v5.2b Standard and this
specification.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A3 of 107
Field I/O Module. The Field I/O Module provides a mechanism for input and output
interfaces. There are two options for the Field I/O Module identified in this
specification. The Type 2070-2A Modules is intended to provide a parallel I/O interface
with the Type 332 family of cabinets using the C1S connector. The Type 2070-2B
Module is intended to provide a serial I/O interface to the ITS cabinet family and the
NEMA interface to TS1 cabinets. The Type 2070-2N is for the NEMA TS2 Type 1
cabinets.
Front Panel Assembly Module. A controller Front Panel contains a keyboard display
that comprises the user field interface. The Front Panel on the Type 2070 ATC Unit
specified shall be the Type 2070-3D Front Panel. The 2070-3D Front Panel includes
large character (16 lines of 40 characters each) Liquid Crystal Display (LCD).
Power Supply Module. The power supply module is used to convert 120 volt power to
voltages required to operate the electronics inside the Type 2070 ATC controller unit.
This power supply shall meet certain minimum electrical characteristics defined herein
for its intended use. The power supply shall meet certain minimum electrical
characteristics defined herein for its intended use. The Type 2070-4AN identifies the
corresponding power supplies needed to support the NEMA TS1 and TS2 standards.
This power supply has the Power-up and Power-down signals adjusted to meet NEMA
specifications.
Communications Modules. This standard includes serial and modem communication
modules. The modem communication module shall be a type 2070-6B. The Type
2070-7A communication modules are for serial communications.
NEMA Interface. This standard includes requirements for an optional module to
interface with the NEMA TS1 and NEMA TS2 Type 1 cabinets. The Type 2070-8
NEMA Field I/O Module is an external module that attaches to the bottom of the 2070
and provides for the typical “A,” “B,” and “C” NEMA connectors.
2070.8 Assemblies and Associated Modules
The 2070 ATC assemblies and associated modules to be provided include the following:
(1) Type 2070- LC Controller Unit (Type 332 Family of Cabinets)
Type 2070-1C CPU Module
Type 2070-2A Field I/O Module
Type 2070-3D Front Panel Assembly
Type 2070- 4A Power Supply
Type 2070-6B Internal Modems (Optional)
Type 2070-7A Serial MA Module (Optional)
(2) Type 2070-LCS Controller Unit (ITS Cabinets)
Type 2070-1C CPU Module)
Type 2070-2B Field I/O Module
Type 2070-3D Front Panel Assembly
Type 2070-4A Power Supply
Type 2070-6B Internal Modem (Optional)
Type 2070-7A Serial MA Module (Optional)
(3) Type 2070-N1C Controller Unit
Type 2070-1C CPU Module
Type 2070-2B Field I/O Module
Type 2070-3D Front Panel Assembly
Type 2070-4AN Power Supply Module
Type 2070-7A Serial MA Module (Optional)
Type 2070-8 NEMA Module
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A4 of 107
(4) Type 2070-N2C Controller Unit
Type 2070-1C CPU Module
Type 2070-2N Field I/O Module – this module contains 120VAC outlet
(accommodates 2070-4 line cord) and has a built-in CPU and memory emulating the
2070-8 NEMA base.
Type 2070-3D Front Panel Assembly
Type 2070-4AN Power Supply Module
Type 2070-7A Serial MA Module (Optional)
2070.9 Documentation
All documentation shall be provided in digital format on a CD and one hard copy of the
Documentation Manual shall be supplied for each item purchased up to 200 manuals per
order. The manual shall be bound in durable covers made of either 65-pound stock paper or
clear plastic. The manual shall be printed on 8-1/2 in. by 11 in. paper, with the exception
that schematics, layouts, parts lists and plan details may be on 11 in. by 17 in. sheets, with
each sheet neatly folded to 8-1/2 in. by 11 in. size. A minimum of Times New Roman or
Arial 10 point font shall be used for all manual text, excluding drawings and schematics.
Drawing text may use a smaller font size.
Manual Contents. Each manual shall include the following sections in the order listed:
Front Cover - The date, serial numbers, model numbers and revision numbers of
equipment covered by the manuals shall be printed on the front cover of the manuals.
Table of Contents
Glossary
Manufacturer Contact Information
Address
Telephone Number
Fax Number
General Email Address
General Description
General Characteristics
Installation
Adjustments
Theory of Operation
Systems Description (include block diagram).
Detailed Description of Circuit Operation.
Maintenance
Preventive Maintenance.
Trouble Analysis.
Trouble Shooting Sequence Chart.
Wave Forms.
Voltage Measurements.
Alignment Procedures.
Parts List (include circuit and board designation, part type and class, power rating,
component manufacturer, mechanical part manufacturer, data specification sheets for
special design components and original manufacturer's part number).
Electrical Interconnection Details & Drawings. Schematic and Logic Diagram
Assembly Drawings and a pictorial diagram showing physical locations and
identification of each component or part.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A5 of 107
Draft Manual. A preliminary draft of the manual shall be submitted to the City for approval
prior to final printing.
2070.10 Packaging
Each item delivered shall be individually packed in its own shipping container. When loose
Styrofoam is used for packing, the item shall be sealed in a plastic bag to prevent direct
contact with the Styrofoam.
2070.11 Delivery
Each item delivered for testing shall be complete ready for testing, and shall include
documentation manuals.
2070.12 Measurement and Payment
The work performed, materials furnished, equipment, labor, tools, and incidentals will not be
measured or paid for directly, but will be subsidiary to pertinent Items.
2070.13 Metals
All sharp edges and corners shall be rounded and free of any burrs.
2070.14 Aluminum
Sheet shall be 15 gauge American Standard (0.060-in.) minimum thick Type 3003-H14 or
Type 5052-H32 ASTM Designation B209 aluminum alloy. Rod, Bar and Extruded shall be
Type 6061-T6, or equal.
2070.15 Stainless Steel
Sheet shall be annealed or one-quarter-hard complying with the ASTM Designation: A666
for Type 304, Grades A or B, stainless steel sheet.
2070.16 Cold Rolled Steel
Sheet, Rod, Bar and Extruded shall be Type 1018/1020.
2070.17 Plating
All cold roll steel shall be plated. All plating shall be either cadmium plating meeting the
requirements of Federal Specification QQ-P-416C, Type 2 Class l or zinc plating meeting
the requirements of ASTM B633-85 Type II SC4.
2070.18 Mechanical Hardware
All bolts, nuts, washers, screws, hinges and hinge pins shall be stainless steel unless
otherwise specified.
2070.19 Electrical Isolation
Within the circuit of any device, module, or Printed Circuit Board (PCB), electrical isolation
shall be provided between DC logic ground, equipment ground and the AC- conductor. They
shall be electrically isolated from each other by 500 MΩ, minimum, when tested at the input
terminals with 500 VDC.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A6 of 107
2070.20 Equipment Grounding
Equipment grounding practices specified in the NEMA TS2 Standard shall be followed. In
particular, all external metallic surfaces such as faceplates, chassis, and connector housing
shall be connected to the equipment ground signal input of the power supply.
2070.21 Daughter Boards
Keyboards and LCD/LED Displays are considered daughter boards. Daughter boards shall
be mechanically secured with a minimum of four spacers/metal screws. Connectors shall be
either Flat Cable or PCB Headers. Components are to be mounted under the daughter board.
COMPONENTS
2070.22 General
All components shall be of such design, fabrication, nomenclature or other identification as
to be purchased from a wholesale distributor or from the component manufacturer. When a
component is of such special design that it precludes the purchase of identical components
from any wholesale distributor or component manufacturer, one spare duplicate component
shall be furnished with each 20, or fraction thereof, components used. The electronic circuit
design shall be such that all components of the same generic type, regardless of
manufacturer, shall function equally in accordance with the specifications.
2070.23 Electronic Components
No device to be socket mounted unless specifically called out. No component to be operated
above 80% of its maximum rated voltage, current or power ratings. Digital components
shall not be operated above 3% over their nominal voltage, current or power ratings.
No component to be provided where the manufactured date is three years older than the
contract award date. The design life of all components, operating for twenty-four hours a
day and operating in their circuit application, shall be ten years or longer.
Components shall be arranged so they are easily accessible, replaceable and identifiable for
testing and maintenance. Where damage by shock or vibration exists, a clamp, fastener,
retainer, or hold-down bracket shall support the component mechanically.
The Manufacturer shall submit detailed engineering technical data on all components at the
request of the Department. The Manufacturer shall certify that the component application
meets the requirements of this standard.
2070.24 Capacitors
The DC and AC voltage ratings as well as the dissipation factor of a capacitor shall exceed
the worst-case design parameters of the circuitry by 150% except for supercaps. Supercaps
are capacitors rated less than 10 working volts DC with capacitance values greater than or
equal to 1.0F. Supercaps shall be required to meet only their stated ratings. Capacitor
encasements shall be resistant to cracking, peeling and discoloration. All capacitors shall be
insulated and shall be marked with their capacitance values and working voltages.
Electrolytic capacitors shall not be used for capacitance values of less than 1.0 µF and shall
be marked with polarity.
2070.25 Potentiometers
Potentiometers with ratings from 1 to 2 watts shall meet Military Type RV4 requirements.
Under 1 Watt potentiometers shall be used only for trimmer type function. The
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A7 of 107
potentiometer power rating shall be at least 100% greater than the maximum power
requirements of the circuit.
2070.26 Resistors
Fixed carbon film, deposited carbon, or composition-insulated resistors shall conform to the
performance requirements of Military Specifications MIL-R-11F or MIL-R-22684. All
resistors shall be insulated and be marked with their resistance values. Resistance values
shall be indicated by the EIA color codes, or stamped value. The value of the resistors shall
not vary by more than 5% between -37 degrees C and 74 degrees C.
Special ventilation or heat sinking shall be provided for all 2- watt or greater resistors. They
shall be insulated from the PCB.
2070.27 Semiconductor Devices
All transistors, integrated circuits, and diodes shall be a standard type listed by EIA and
clearly identifiable.
All metal oxide semiconductor components shall contain circuitry to protect their inputs and
outputs against damage due to high static voltages or electrical fields.
Device pin "1" locations shall be properly marked on the PCB adjacent to the pin.
2070.28 Transformers and Inductors
All power transformers and inductors shall have the manufacturer's name or logo and part
number clearly and legibly printed on the case or lamination. All transformers and inductors
shall have their windings insulated, be protected to exclude moisture, and their leads color
coded with an approved EIA color code or identified in a manner to facilitate proper
installation.
2070.29 Triacs
Each triac with a designed circuit load of greater than 0.5 Amperes at 120 VAC shall be
mounted to a heat sink with thermal conductive compound or material, in addition to being
mechanically secured.
2070.30 Circuit Breakers and Fuses Circuit Breakers
Circuit Breakers and Fuses Circuit breakers shall be listed by UL or ETL. The trip and
frame sizes shall be plainly marked (marked on the breaker by the manufacturer), and the
ampere rating visible from the front of the breaker. Contacts shall be silver alloy and
enclosed in an arc-quenching chamber. An ambient air temperature range of from -18
degrees C to 50 degrees C shall not influence overload tripping. The minimum Interrupting
Capacity shall be 5,000 amperes, RMS when the breaker is secondary to a UL approved fuse
or primary circuit breaker and both breakers in concert provide the rated capacity. For
circuit breakers 80 amperes and above, the minimum interrupting capacity shall be 10,000
amperes, RMS. Circuit breakers shall be the trip-free type with medium trip delay
characteristic (Carling switch Time Delay Curve #24 or equal).
2070.31 Load Circuit Breaker Auxiliary Internal Switches
The Load Circuit Breakers used to power Switch Packs shall have auxiliary switches. The
auxiliary switches shall “open” when the load breaker has tripped and the system will
transfer the power from the Main Contactor to the Flash or Blank condition.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A8 of 107
2070.32 Fuses
All Fuses that are resident in a bayonet style fuse holder shall have the fuse size rating
labeled on the holder or on the panel adjacent to the holder. Fuses shall be easily accessible
and removable without use of tools.
2070.33 Switches
Dual-inline-package (DIP). DIP quick snap switches shall be rated for a minimum of
30,000 operations per position at 50 mA, 30 VDC. The switch contact resistance shall be
100 milliohms maximum at 2 mA, 30 VDC. The contacts shall be gold over brass.
Logic Switches. The switch contacts shall be rated for a minimum of 1-ampere resistive load
at 120 VAC and shall be silver over brass (or equal). The switch shall be rated for a
minimum of 40,000 operations.
Power Switches. The switch contacts shall be rated for a minimum of 5 amperes resistive
load at 120 VAC or 28 VDC and be silver over brass (or equal). The switch shall be rated
for a minimum of 40,000 operations.
Power. Ratings shall be the same as CONTROL, except the contact rating shall be a
minimum of 10 amperes at 125 VAC.
2070.34 Terminal Blocks
The terminal blocks shall be barrier type, rated at20amperes and 600 VAC RMS minimum.
The terminal screws shall be 0.3125 in. minimum length nickel-plated brass binder head type
with screw inserts of the same material. Screw size is called out under the associated file,
panel or assembly.
Screw Lug and Cam Driven Connectors. Provided the connectors mate, screw lug cam
driven devices or crimp pin connectors shall be allowable if the interface is part of a harness.
For field termination, screw lug and cam driven assemblies are interchangeable for field
wiring termination, provided they both accommodate 22-gauge wire on the inputs and 22-
gauge wire on the outputs.
2070.35 Wiring, Cabling, and Harnesses
Wiring, Cabling and Harnesses shall be neat, firm and properly bundled with external
protection. They shall be tie-wrapped and routed to minimize crosstalk and electrical
interference. Each harness shall be of adequate length to allow any conductor to be
connected properly to its associated connector or termination point. Conductors within an
encased harness have no color requirements. Printed circuit motherboards are to be used
where possible to eliminate or reduce cabinet wiring.
Wiring containing AC shall be bundled separately or shielded separately from all DC logic
voltage control circuits.
Wiring shall be routed to prevent conductors from being in contact with metal edges.
Wiring shall be arranged so that any removable assembly may be removed without
disturbing conductors not associated with that assembly.
All conductors, except those that can be readily traced, shall be labeled. Labels attached to
each end of the conductor shall identify the destination of the other end of the conductor.
All conductors shall conform to MIL-W-16878E/1 or better and have a minimum of 19
strands of copper. The insulation shall be polyvinyl chloride with a minimum thickness of 10
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A9 of 107
mils or greater. Where insulation thickness is 15 mils or less, the conductor shall conform to
MIL-W-16878/17.
Conductor color identification shall be as follows:
AC- circuits – white
Equip. Ground - solid green or continuous green color with 1 or more yellow stripes
DC logic ground - continuous white with a red stripe
AC+ circuits - continuous black or black with colored stripe
DC logic ungrounded or signal - any color not specified
2070.36 Indicators and Character Displays
All indicators and character displays shall be readily visible at a radius of up to 4 feet within
the cone of visibility when the indicator is subjected to 97,000 lux (9,000 foot-candles) of
white light with the light source at 45 degrees (+/-2 degrees) to the front panel.
All indicators and character displays shall have a minimum 90 degrees cone of visibility
with its axis perpendicular to the panel on which the indicator is mounted. All indicators
shall be self-luminous. All indicators shall have a rated life of 100,000 hours minimum.
Each LED indicator shall be white or clear when off. Indicators supplied on equipment
requiring handles shall be mounted such that a horizontal clearance is provided. Liquid
Crystal Displays (LCD) shall be readable at temperatures of -20 degrees C to +70 degrees C.
All controller unit functions are required to operate at temperatures of –37 degrees C to +74
degrees C.
2070.37 Connectors
Connectors shall be keyed to prevent improper insertion of the wrong connector where
equipment damage or operator injury may result. The mating connectors shall be designated
as the connector number and male/female relationship, such as C1P (plug or PCB edge
connector) and C1S (socket).
Type T. Type T connector shall be a single row, 10 position, feed through terminal block.
The terminal block shall be a barrier type with 6-32, 0.25 in. or longer, nickel plated brass
binder head screws. Each terminal shall be permanently identified as to its function.
Plastic Circular and Type M Connectors. Pin and socket contacts for connectors shall be
beryllium copper construction subplated with 1.27 microns nickel and plated with 0.76
microns gold. Pin diameter shall be 0.0618 in. All pin and socket connectors shall use the
AMP #601105-1 or #91002-1 contact insertion tool and the AMP #305183 contact
extraction tool or equal.
Card Edge and Two Piece PCB. Edge connectors shall have bifurcated gold-plated
contacts. The PCB receptacle connector shall meet or exceed the following:
Operating Voltage: 600 VAC (RMS)
Current Rating: 5.0 Amperes
Insulation Material: Diallyl Phthalate or Thermoplastic
Insulation Resistance: 5,000 Megohms Contact
Material: Copper alloy plated with 0.00005 in. of nickel and
0.000015 in. of gold
Contact Resistance: 0.006 Ohm maximum
The two-piece PCB connector shall meet or exceed the DIN 41612.
The PCB 22/44 Connector shall have 22 independent contacts per side; dual sided with
0.156 in. contact centers.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A10 of 107
Wire Terminal. Each wire terminal shall be solderless with PVC insulation and a heavy-
duty short -locking spade type connector. Crimp terminal connectors using a Controlled-
Cycle type crimping tool.
Flat Cable. Each flat cable connector shall be designed for use with 26 AWG cable; have
dual cantilevered phosphor bronze contacts plated with 0.00015 in. of gold over 0.00005 in.
of nickel; and have a current rating of 1 Ampere minimum and an insulation resistance of 5
Megohms minimum.
PCB Header Post. Each PCB header post shall be 0.025 in. square by 0.3425 in. high from
the plane of the PCB to the end of the pin; be mounted on 0.10 in. centers; and be tempered
hard brass plated with 0.00015 in. of gold over 0.00005 in. of nickel.
PCB Header Socket. Each PCB header socket block shall be nylon or diallyl phthalate.
Each PCB header socket contact shall be removable, but crimp-connected to its conductor.
List the part number of the extraction tool recommended by its manufacturer. Each PCB
header socket contact shall be brass or phosphor bronze plated with 0.0015 in. of gold over
0.00005 in. of nickel.
2070.38 Surge Protection Device
The surge suppression device shall comply with ANSI/IEEE C62.41 (100 Kilohertz Ring
Wave, the 1.2/50 microseconds – 8/20 Combination Wave and the EFT Burst) at voltages
and currents specified at “Location Category B2” and at “Test Severity” level III (i.e. up to
4.0 Kilovolts, open-circuit).
MECHANICAL
2070.39 Assemblies
All assemblies shall be modular, easily replaceable and incorporate plug-in capability for
their associated devices or PCBs. Assemblies shall be provided with two guides for each
plug-in PCB or associated device (except relays). The guides shall extend to within 0.75 in.
from the face of either the socket or connector and front edge of the assembly. If Nylon
guides are used, attach the guides securely to the file or assembly chassis.
2070.40 Locking Devices
All screw type fasteners shall utilize locking devices or locking compounds except finger
screws, which are captive.
2070.41 PCB Design and Connectors
No components, traces, brackets or obstructions are to be within 0.125 in. of the board edge
(guide edges). The manufacturer's name or logo, model number, serial number, and circuit
issue or revision number shall appear and be readily visible on all PCBs.
2070.42 Model and Serial Numbers
The manufacturer's model number and circuit issue or revision number shall appear on the
rear panel of all equipment supplied (where such panel exists). In addition to any
assignment of model numbers by the manufacturer, the TYPE number shall be displayed on
the front panel in bold type, at least 0.25 in. high.
A permanent label shall be affixed to the inside near and center floor of the Type 2070 unit
chassis when viewed from the front. The label shall display the unit's serial number and be
permanent and easy to read.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A11 of 107
2070.43 Workmanship
Workmanship shall conform to the requirements of this specification and be in accordance
with the highest industry standards.
2070.44 Tolerances
The following tolerances shall apply, except as specifically shown on the plans or in these
specifications:
Sheet Metal +/-0.0525 in.
PCB +0 in., - 0.010 in.
Edge Guides +/-0.015 in.
*Note: These dimensional tolerances do not apply to material gauge or thickness.
ENGINEERING
2070.45 Human Engineering
Equipment. The equipment shall be engineered for simplicity, ease of operation and
maintenance.
Knobs. Knobs shall be a minimum of 0.5 in. in diameter and a minimum separation of 0.5
in. edge to edge.
PCBs. PCBs shall slide smoothly in their guides while being inserted into or removed from
the frame and fit snugly into the plug-in PCB connectors. PCBs shall require a force no less
than 5 pounds-force or greater than 50 pounds-force for insertion or removal.
2070.46 Design Engineering
The design shall be inherently temperature compensated to prevent abnormal operation. The
circuit design shall include such compensation as is necessary to overcome adverse effects
due to temperature in the specified environmental range. The design shall take into
consideration the protection of personnel from all dangerous voltages.
2070.47 Generated Noise
No item, component or subassembly is to emit an audible noise level exceeding the peak
level of 55 dBa when measured at a distance of one meter away from its surface, except as
otherwise noted. No item, component or subassembly is to emit a noise level sufficient to
interfere with processing and communication functions of the controller circuits.
PRINTED CIRCUIT BOARDS
2070.48 Design, Fabrication and Mounting.
Contacts of PCBs. All contacts on PCBs shall be plated with a minimum thickness of
0.00003 in. gold over a minimum thickness of 0.000075 in. nickel.
PCB Design. PCB design shall be such that when a component is removed and replaced, no
damage is done to the board, other components, conductive traces or tracks.
Fabrication. Fabrication of PCBs shall be in compliance with Military Specification MIL-
P-13949, except as follows:
Copper Tracks - NEMA FR-4 glass cloth base epoxy resin copper clad laminates
0.0625 in. minimum thickness shall be used. Inter-component wiring shall be by
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A12 of 107
laminated copper clad track having a minimum weight of 2.0 ounces per square foot
with adequate cross section for current to be carried. All copper tracks shall be
plated or soldered to provide complete coverage of all exposed copper tracks.
Jumper wires to external PCB components shall be from plated-through padded
holes and as short as possible.
Pits, Dents, Bows and Twists. All PCBs shall conform to Section 3.3 of Military
Specification MIL-P-13949G Grade of Pits and Dents and be of Grade B quality
(3.5.1.3) or better. The class of permissible bow or twist shall be Class C (Table V)
or better. The class of permissible warp or twist shall be Class A (Table II) or better.
NOTE: Omit Sections 4.2 through 6.6 of Military Specification MIL-P-13949G
(inclusive) except as referenced in previous sections of this specification.
Mounting. The mounting of parts and assemblies on the PCB shall conform to Military
Specification MIL-STD-275E, except as follows:
Semiconductor Devices. Semiconductor devices that dissipate more than 250
milliwatts or cause a temperature rise of 10 degrees C or more shall be mounted with
spacers, transipads or heat sinks to prevent contact with the PCB.
Residual Flux. When completed, remove all residual flux from the PCB.
Resistence. The resistance between any two isolated, independent conductor paths
shall be at least 100 Megohms when a 500 VDC potential is applied.
Coating. All PCBs shall be coated with a moisture resistant coating.
Lateral Separation. Where less than 0.25 in. lateral separation is provided between
the PCB (or the components of a PCB) and any metal surface, a 0.0625 in. (+/-
0.0005 in.) Thick Mylar (polyester) plastic cover shall be provided on the metal to
protect the PCB.
Connector Edges. Each PCB connector edge shall be chamfered at 30 degrees from board
side planes. The key slots shall also be chamfered so that the connector keys are not
extracted upon removal of board or jammed upon insertion. The key slots shall be 0.045 in.
(+/-0.005 in.) for 0.1 in. spacing and 0.055 in. (+/-0.005 in.) for 0.156 in. spacing.
2070.49 Soldering
Hand Soldering. Hand soldering shall comply with Military Specification MIL-STD-2000.
Automatic Flow Soldering. Automatic flow soldering shall be a constant speed conveyor
system with the conveyor speed set at optimum to minimize solder peaks or points.
Temperature shall be controlled to within +/- 8 degrees C of the optimum temperature. The
soldering process shall result in the complete coverage of all copper runs, joints and
terminals with solder except that which is covered by an electroplating process. Wherever
clinching is not used, provide a method of holding the components in the proper position for
the flow process.
Time-Temperature. If exposure to the temperature bath is of such a time-temperature
duration, as to come within 80% of any component's maximum specified time-temperature
exposure, that component shall be hand soldered to the PCB after the flow process has been
completed.
2070.50 Definitions
Definitions for the purpose of this section on PCBs shall be taken from MIL-P-55110D
Section 3.3 and any current addendum.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A13 of 107
QUALITY CONTROL
2070.51 General
Material in this section is considered a supplement to that provided in Appendix A. In the
case of apparent inconsistencies, the material in Appendix A of this specification shall
prevail.
2070.52 Manufacturers’ Quality Control and Testing Certification
A compliant test report that is part of the quality control procedure shall be supplied with
each delivered unit. Along with pass fail information this report shall include the quality
control procedure, test report format and the name of the tester. It should be counter-signed
by a corporate officer.
The quality control procedure shall include the following:
Design acceptance testing of all supplied components
Physical and functional testing of controller units
Environmental testing report(s) and final acceptance
Acceptance testing of all supplied components
Physical and functional testing of all modules and items
Verification of a minimum burn-in of all equipment
2070.53 Components.
All components shall be lot sampled to assure a consistent high conformance standard to the
design specification of the equipment.
2070.54 Subassembly, Unit or Module
Complete electrical, environmental and timing compliance testing shall be performed on
each module, unit, printed circuit or subassembly. Components will be tested as a complete
controller assembly. Housing, chassis, and connection terminals shall be inspected for
mechanical sturdiness, and harnessing to sockets to be electrically tested for proper wiring
sequence. The equipment shall be visually and physically inspected to assure proper
placement, mounting, and compatibility of subassemblies.
2070.55 Pre-delivery Repair
Any defects or deficiencies found by the inspection system involving mechanical structure
or wiring shall be returned through the manufacturing process or special repair process for
correction.
PCB flow soldering is allowed a second time if copper runs and joints are not satisfactorily
coated on the first run. Do not flow solder a PCB more than twice.
Hand soldering is allowed for printed circuit repair.
2070.56 Electrical, Environmental and Testing Requirements
Electrical, Environmental and Testing Requirements are provided in Appendix A of this
Specification.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A14 of 107
SECTION II - TYPE 2070 ATC CONTROLLER UNIT
2070.57 Controller Unit
The Controller Unit is composed of the Type 2070 Unit CHASSIS, modules, and assemblies
per their version.
2070.58 Unit Version Configuration
The Type 2070 Controller Unit Version defines the module composition to be delivered as
follows:
MODEL 2070 CONTROLLER CONFIGURATIONS
ASSOCIATED DEVICES LC LCS N1C N2C
2070 Unit Chassis 1 1 1 1
1C Type 2070-1C CPU Module 1 1 1 1
2A Type 2070-2A Field I/O Module 1
2B Type 2070-2B Field I/O Module 1 1
2N Type 2070 -2N Field I/O Module 1
3 Type 2070-3D Front Panel Assy. 1 1 1 1
4B Type 2070-4A Power Supply 1 1
4AN Type 2070-4AN Power Supply 1 1
8 Type 2070-8 NEMA Module 1
6B Type 2070 – 6B Comm. Module opt opt opt opt
7A Type 2070-7A Comm. Module opt opt opt opt
Notes:
1) 2070 LC and LCS are the same units using the 1C CPU Module with a 2A FIO
and 2B communication interface to drive the Type 332 and Serial cabinets,
respectively.
2) 2070N versions includes the 1C CPU Module. The communications and option
modules/assemblies must be called out separately from the unit version. The 2N
Field I/O module is designed to replace the 2070-8 NEMA Base and use the TS2
serial interface. The 2070N versions are described in SECTION X - TYPE 2070
NEMA.
2070.59 Communication and Option Modules
The communications and option modules/assemblies must be called out separately from the
unit version.
2070.60 Operating System & Board Support Package Requirements
The ATC shall use a Linux operating system (O/S) and shall include standard POSIX
libraries for application support including real-time extensions of POSIX 1003.1b. To
facilitate application level access to the ATC hardware, a Board Support Package (BSP)
shall be provided for access to hardware-specific drivers.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A15 of 107
After boot-up the ATC Linux O/S shall make available to applications, access to the low
level drivers (block, character and network) provided by the kernel (subject to current open
source requirements) or through kernel modules.
2070.61 Chassis
The CHASSIS Top and Bottom, Internal Structure Supports, Back Plane Mounting Surface,
Module Plates, Power Supply Enclosure, and Front Panel shall be made of 63-gauge
minimum aluminum sheet. The CHASSIS Side panels shall be 0.090 inches minimum
sheet.
2070.62 Power Fail and Power Restoration Operation
It is noted that the Power Failure Power Restoration operations of this unit are specific to the
requirements of the user. All associated modules are to comply with said operations.
2070.63 Power Limitations
2070 UNIT module / assembly power limitations are as follows:
Types +5VDC +12VDC
ISO
+12VDC
ser
-12 VDC
ser
2070-1C CPU 2.0A 250Ma
2070-2A FI/O 250 mA 750 mA ----- -----
2070-2B FI/O 250 mA 500 mA ----- -----
2070-3D FPA 500 mA ----- 50 mA 50 mA
2070-6 All Comm. 900 mA ----- 300 mA 300 mA
2070-7 All Comm. 250 mA ----- 50 mA 50 mA
2070.64 EIA-485 Communications Circuitry
All circuitry associated with the EIA-485 Communications links shall be capable of reliably
passing a minimum of 1.0 megabits per second.
2070.65 EIA-485 Line Drivers/Receivers
The EIA-485 Line Drivers/Receivers shall be socket mounted or surface mounted and shall
not draw more than 35 mA in active state and 20 mA in inactive state. A 100-Ohm
Termination Resistor shall be provided across each Differential Line Receiver Input. The
Motherboard’s control signals (e.g., SP1-RTS) shall be active, or asserted, when the positive
terminal (e.g., SP1-RTS+) is a lower voltage than its corresponding negative terminal (e.g.,
SP1-RTS-). A control signal is inactive when its positive terminal voltage is higher than its
negative terminal. Receive and transmit data signals shall be read as a "1" when the positive
terminal's (e.g., SP1-TXD+) voltage is higher than its corresponding negative terminal (e.g.,
SP1-TXD-). A data value is "0" when its positive terminal's (e.g., SP1-TXD+) voltage is
lower than its negative terminal (e.g., SP1-TXD-).
2070.66 Sockets
Sockets for devices (called out to be socket mounted) shall be “xx” pin AUGAT 500/800
series AG10DPC or equal.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A16 of 107
2070.67 Frame Address
SDLC. SP5 and SP3 SDLC frame address assignments (Command/Response) are as follows:
SP5 SP3
CPU 2070-1 “19” “19”
FI/O 2070-2A & 8 “20” “Not Applicable”
Manufacturer Use 128-254 128-254
CPU Broadcast to all “255” “255”
All other addresses are reserved by this standard. The SDLC response shall contain the
frame address of the Command sender.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A17 of 107
SECTION III - TYPE 2070-1C CPU Module
2070.68 Type 2070 – 1C Module
The TYPE 2070-1C CPU shall be a single board module meeting the 2X WIDE board
requirements. The module shall be furnished normally resident in MOTHERBOARD Slot
A5.
2070.69 The C13S Connector
The C13S Connector shall be a DB25S connector and shall be located on the Module 2070-
1C CPU front panel and shall contain signals for SP8, LINESYNC, NRESET,
POWERDOWN, and an isolated BIAS +5VDC as specified in the following paragraphs and
as listed in Figure A9-15 located in Appendix D if this specification. TX and RX LEDs
shall be provided as shown in Figure A9-15 in Appendix D of this specification.
2070.70 Serial Port SP8
System Serial Port 8 (SP8) shall be isolated, converted to EIA-485, and then routed to
Connector C13S. SP8 shall meet all SP2 Port requirements except where noted.
2070.71 LINESYNC and POWERDOWN
LINESYNC and POWERDOWN lines shall each be isolated, converted to EIA-485, and
then routed to connector C13S for external module use.
2070.72 NRESET
CP Reset and POWER UP lines shall be isolated, then OR’d to NRSET. NRESET shall then
be converted to EIA-485 and routed to connector C13S for external module use.
2070.73 Engine Board
The TYPE 2070-1C CPU module shall use an Engine Board compliant to the
AASHTO/ITE/NEMA ATC Standard with exceptions as defined in Section IV. The Engine
Board shall be used for execution of the application software. No other microprocessor or
memory of the 2070-1C CPU to be used for execution of the application software.
2070.74 Ethernet Ports
The ETHERNET ports of the Engine Board shall be brought out on an RJ 45 Connectors
mounted on the 2070-1C front panel. The front panel LED indicators for the two CPU
Ethernet ports shall be provided as indicated in Figure A9-15 in the Appendix.
2070.75 Network Switches
The Model 2070-1C CPU Module shall be provided with two integrated Store-and-Forward
Network Switches per the IEEE 802.3u and 802.3x specifications. One switch shall be
configured with port 1 and 2 connected to the front panel RJ-45 connectors and port 3 shall
be connected to the CPU ENET 1 port. The second switch shall be configured with port 1
connected to the front panel RJ-45, port 2 shall be connected to the CPU ENET 2 port. Port
3 shall be used to route Ethernet across the Motherboard to the “A” Connectors. DC
Grounding plane around the network connectors and lines shall be provided. Port 3 Network
Lines shall be assigned to: NetP5 TX+, TX-, RX+ and RX- respectively.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A18 of 107
2070.76 Universal Serial Bus (USB)
Except as noted in SECTION VII - TYPE 2070-3D USB FRONT PANEL ASSEMBLY,
the TYPE 2070-1C CPU module shall include a USB port compliant to the
AASHTO/ITE/NEMA ATC Standard, with exceptions that the USB shall conform to
appropriate sections of the USB v3.0 specification for both hardware and software
operations. USB shall be brought out from the Engine Board to a USB Connector mounted
on the 2070-1C front panel. The USB Mass Storage device shall use the FAT file system as
configured in the latest approved version of Annex A – Minimum Linux Kernel
Configuration of the ATC AASHTO/ITE/NEMA Standard.
2070.77 Host Module Identification
The TYPE 2070-1C CPU module shall use a Host Module that provides the mechanical and
electrical interfaces to the Engine Board and Mother Board. The TYPE 2070-1C CPU
module shall implement the host module identification using the Engine Board SPI serial
port, compliant to the latest approved version of the AASHTO/ITE/NEMA ATC Standard.
2070.78 ATC Controller Board Support Package (BSP)
The BSP supplied by the manufacturer shall provide operating-system-level support for
engine board. The ATC shall use a Linux operating system (O/S) and shall include standard
POSIX libraries for application support including real-time extensions of POSIX 1003.1b.
To facilitate application level access to the ATC hardware, a Board Support Package (BSP)
shall be provided for access to hardware-specific drivers.
After boot-up the ATC Linux O/S shall make available to applications, access to the low
level drivers (block, character and network) provided by the kernel (subject to current open
source requirements) or through kernel modules.
The BSP supplied by a manufacturer shall include the following components:
1) A Linux compatible kernel that shall be configured to include, at minimum, the features
specified in the latest approved version of Annex A – Minimum Linux Kernel
Configuration of the ATC AASHTO/ITE/NEMA Standard.
2) Drivers that support all functionality defined by Section 5.3 of the ATC
AASHTO/ITE/NEMA Standard (and Section III and IV of this specification), On-Board
Resources; and Section 5.4.3 (and paragraph 2070.69 of this specification), Serial Interface
Ports, of the ATC AASHTO/ITE/NEMA Standard, and be capable of operating in an
interrupt driven environment where appropriate. Drivers for the following engine board
hardware are required:
Function Character Block Network Interrupt
/dev/sp1 Asynchronous Port X X
/dev/sp1s Synchronous Port X X
/dev/sp2 Asynchronous Port X X
/dev/sp2s Synchronous Port X X
/dev/sp3 Asynchronous Port X X
/dev/sp3s Synchronous Port X X
/dev/sp4 Asynchronous Port (Note 1) X X
/dev/sp5s Synchronous Port X X
/dev/sp6 Asynchronous Port X X
/dev/sp8 Asynchronous Port X X
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A19 of 107
Function Character Block Network Interrupt
/dev/sp8s Synchronous Port X X
Ethernet 1 X X
Ethernet 2 X X
USB X X
SPI X X
CPU Reset X
CPU Active LED X
Power Down X X
RTC X
Datakey Present X X
Flash File System X X
SRAM File System X
Notes: A Linux console shall be provided on /dev/tty4 (/dev/console) at boot-up. All
terminal outputs during boot time shall be made to that interface. All inputs are made via a
terminal program to that interface. This interface is the default stdin / stdout of Linux. The
communication parameters are initially 38400 baud, n, 8, 1. The same communication
parameters shall be used by the boot-loader in order to ensure a continuous output to the
serial terminal / console. After booting and all applications are loaded, /dev/tty4 shall be
available to applications as /dev/sp4 unless the single-user mode Linux feature has been
invoked via Ctrl-C during the boot process before control is passed to any application
programs.
See the latest approved version of Annex B – Required Device Driver Interfaces of the
ATC AASHTO/ITE/NEMA Standard for BSP-specified driver interface details.
3) Utility applications, modules, libraries and supporting data which include, but are not
limited to, the following:
Package Version* Programs Remarks
Busybox 1.00p8 [, addgroup, adduser, adjtimex, ar,
ash, basename, busybox, cat,
chgrp, chmod, chown, chroot,
clear, cmp, cp, crond, crontab, cut,
date, dd, delgroup, deluser, df,
dirname, dmesg, dos2unix,
du, echo, egrep, env, expr, false,
fgrep, find, freeramdisk, getty,
grep, gunzip, gzip, halt, head,
hexdump, hostid, hostname,
hwclock, id, ifconfig, ifdown, ifup,
inetd, init, insmod, install,
kill, killall, klogd, last, ln, logger,
login, logname, logread, ls,
lsmod, makedevs, md5sum, mesg,
mkdir, mkfifo, mknod, mktemp,
modprobe, more, mount, mv,
netstat, nslookup, passwd, patch,
pidof, ping, pivot_root, printf, ps,
pwd, rdate, reboot, renice, reset,
UNIX shell and commands
collection
http://www.busybox.net/
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A20 of 107
rm, rmdir, rmmod, route, run-parts,
rx, sed, sh, sleep, sort, start-stop-
daemon, stty, su, sulogin, sync,
sysctl, syslogd, tail, tar, tee, telnet,
telnetd, test, time, top, touch, tr,
true, tty, umount, uname, uniq,
unix2dos, unzip, uptime, usleep,
vi, wc, which, who, whoami,
xargs, yes, zcat
UclibC 0.9.27 ld.so, libc, libcrypt.so, libdl.so
libm.so, libnsl.so, libnss_dns.so,
libnss_files.so, libpthread.so,
libresolv.so, libutil.so
Uclibc Equivalent
http://www.uclibc.org/
downloads
*or higher
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A21 of 107
SECTION IV - MODEL 2070-1C CPU (Engine Board)
2070.79 General
Appendix B of this specification provides a copy of the AASHTO/ITE/NEMA ATC
Standard Annex B. Annex B specifies the device driver interfaces required by the standard.
Linux drivers are specified and no further detail is given. Each driver interface summary is
described below.
2070.80 Model 2070 -1C CPU Module Processor
The Model 2070-1C CPU Module Processor shall utilize a Freescale 32 bit MPC series
processor with PowerQUICK architecture that shall have a minimum computational
capability of 60 MIPS calculated using the Dhrystone v2.1 benchmark.
2070.81 FLASH Memory
The Model 2070-1C CPU Module shall contain a minimum of 64Mbytes of FLASH
Memory for storage of OS Software and user application.
2070.82 Dynamic RAM (DRAM)
The Model 2070-1C CPU Module shall contain a minimum of 64 Mbytes of DRAM or
equivalent volatile memory for application and OS program execution.
2070.83 Static RAM (SRAM)
The Model 2070-1C CPU Module shall contain a minimum of 1 MB minimum of SRAM
memory for non-volatile parameter storage.
2070.84 Standby Power
The Model 2070-1C CPU Module Engine Board shall provide the Standby Power required
for supporting the SRAM and RTC.
2070.85 Real-Time Clock (RTC)
The Model 2070-1C Module shall be provided with a software settable, hardware RTC that
meets the requirements of the ASHTO/ITE/NEMA ATC Standard except that in the absence
of VPRIMARY, the RTC shall operate from VSTANBY as listed in Figure A9-16 of
Appendix D of this Specification. Operating System Time shall be maintained by utilizing
the RTC and LINESYNC as defined by 2070-162 of this specification.
2070.86 CPU_RESET
A software-driven CPU_RESET Signal (Active Low) shall be provided to reset other
system devices and shall be accessible by application programs as well as by the command
line as “cpureset”. CPU_RESET shall be executed when the Controller starts up or is
rebooted using the reboot command.
2070.87 CPU_ACTIVE
An Active Low signal shall be provided to drive the Front Panel Assembly CPU_ACTIVE
LED indicator. This signal shall cause to the LED to default to ON when the controller
starts up.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A22 of 107
APPLICATION PROGRAM INTERFACE (API)
2070.88 ATC API Standard
The Model 2070-1C Module shall be fully compliant and shall be provided, upon request,
with an installed copy of the Application Program Interface (API) compliant to the latest
ASHTO/ITE/NEMA ATC API Standard.
2070.89 Integrated Security
The Model 2070-1C Module shall be implemented with integrated security support for DES,
3DES, MD-5, SHA-1, AES and ARC-4 encryption algorithms as well as a public key
accelerator and an on-chip random number generator.
2070.90 Serial Communications Interface Ports
The engine board shall provide seven serial communications ports. These ports are
described below. Each port shall be capable of operating at a completely independent bit
rate from all other ports. All interface pins shall operate at logic-levels. Input pins are
indicated by (I), output pins by (O). All ports are not expected to operate at maximum speed
simultaneously. The following communication channel loads for test purposes, with no
other activity present shall be the following:
SP1,2,8 = Continuous full-duplex, asynchronous communications at 19.2Kbps
SP4,6 = Continuous full-duplex, asynchronous communications at 38.4Kbps
SP3S = Continuous full-duplex, synchronous communications at 153.6Kbps
SP5S = Continuous full-duplex synchronous communications at 614.4Kbps
All Ethernet Ports: At 10% loading, with 3% average hits to processor per minute
No other applications or I/O activities are required to be operational during this test.
Serial Port 1 (SP1)
Principal Usage: general-purpose
Operating Modes: ASYNC / SYNC / HDLC / SDLC
Asynchronous Rates (bps): 1200 / 2400 / 4800 / 9600 / 19.2k / 38.4k Optional:
57.6k / 115.2k
Synchronous Rates (bps): 19.2k / 38.4k / 57.6k / 76.8k / 153.6k
Interface Pins: SP1_TXD: Transmit Data (O)
SP1_RXD: Receive Data (I)
SP1_RTS: Request To Send (O)
SP1_CTS: Clear To Send (I)
SP1_CD: Carrier Detect (I)
SP1_TXC_INT: Transmit Clock Internal (O)
SP1_TXC_EXT: Transmit Clock External (I)
SP1_RXC_EXT: Receive Clock External (I)
Serial Port 2 (SP2)
Principal Usage: general-purpose
Operating Modes: ASYNC / SYNC / HDLC / SDLC
Asynchronous Rates (bps): 1200 / 2400 / 4800 / 9600 / 19.2k / 38.4k Optional:
57.6k / 115.2k
Synchronous Rates (bps): 19.2k / 38.4k / 57.6k / 76.8k / 153.6k
Interface Pin: SP2_TXD: Transmit Data (O)
SP2_RXD: Receive Data (I)
SP2_RTS: Request To Send (O)
SP2_CTS: Clear To Send (I)
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A23 of 107
SP2_CD: Carrier Detect (I)
SP2_TXC_INT: Transmit Clock Internal (O)
SP2_TXC_EXT: Transmit Clock External (I)
SP2_RXC_EXT: Receive Clock External (I)
Serial Port 3 (SP3)
Principal Usage: in-cabinet devices
Operating Modes: ASYNC / SYNC / HDLC / SDLC
Asynchronous Rates (bps): 1200 / 2400 / 4800 / 9600 / 19.2k / 38.4k Optional:
57.6k / 115.2k
Synchronous Rates (bps): 153.6k / 614.4k
Interface Pins: SP3_TXD: Transmit Data (O)
SP3_RXD: Receive Data (I)
SP3_RTS: Request To Send (O)
SP3_CTS: Clear To Send (I)
SP3_CD: Carrier Detect (I)
SP3_TXC_INT: Transmit Clock Internal (O)
SP3_TXC_EXT: Transmit Clock External (I)
SP3_RXC_EXT: Receive Clock External (I)
Serial Port 4 (SP4)
Principal Usage: external user-interface (console) and general purpose
Operating Modes: ASYNC
Asynchronous Rates (bps): 1200 / 2400 / 4800 / 9600 / 19.2k / 38.4k Optional:
57.6k / 115.2k
Interface Pins: SP4_TXD: Transmit Data (O)
SP4_RXD: Receive Data (I)
Serial Port 5 (SP5)
Principal Usage: in-cabinet devices
Operating Modes: SYNC / HDLC / SDLC
Synchronous Rates (bps): 153.6k / 614.4k
Interface Pins: SP5_TXD: Transmit Data (O)
SP5_RXD: Receive Data (I)
SP5_TXC_INT: Transmit Clock Internal (O)
SP5_RXC_EXT: Receive Clock External (I)
Serial Port 6 (SP6)
Principal Usage: front panel user-interface
Operating Modes: ASYNC
Asynchronous Rates (bps): 1200 / 2400 / 4800 / 9600 / 19.2k / 38.4k Optional:
57.6k / 115.2k
Interface Pins: SP6_TXD: Transmit Data (O)
SP6_RXD: Receive Data (I)
Serial Port 8 (SP8)
Principal Usage: general-purpose
Operating Modes: ASYNC / SYNC / HDLC / SDLC
Asynchronous Rates (bps): 1200 / 2400 / 4800 / 9600 / 19.2k / 38.4k Optional:
57.6k / 115.2k
Synchronous Rates (bps): 19.2k / 38.4k / 57.6k / 76.8k / 153.6k
Interface Pins: SP8_TXD: Transmit Data (O)
SP8_RXD: Receive Data (I)
SP8_RTS: Request To Send (O)
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A24 of 107
SP8_CTS: Clear To Send (I)
SP8_CD: Carrier Detect (I)
SP8_TXC_INT: Transmit Clock Internal (O)
SP8_RXC_EXT: Receive Clock External (I)
2070.91 Serial Peripheral Interface Port
The engine board shall provide a synchronous Serial Peripheral Interface Port. All SPI
interface pins shall be at HCT logic-levels. Input pins are indicated by (I), output pins by
(O).
The implementation of SPI_SEL_1 is required to support DataKey operations.
The implementation of SPI_SEL_2 is required to support a host module serial EEPROM
device containing controller configuration information. The content and organization of the
information will be described in the BSP. This EEPROM device shall have the following
characteristics:
Function in a manner similar to a 25020-type (2K-bit) SPI EEPROM device
Have a minimum size of 2 Kbit organized as 256 words of 8 bits each
Provide 5V interface signals
Operate properly with up to a 2.0 MHz SPI clock
Utilize SPI Mode 0 (CPOL=0, CPHA=0)
Be write-protected (using *WP pin) whenever POWERUP is LOW
Be readable from application software during normal ATC operation
Support the following instruction set:
Instruction Description Instruction
Format
WREN Write Enable 0000 X110
WRDI Write Disable 0000 X100
RDSR Read Status Register 0000 X101
WRSR Write Status Register 0000 X001
READ Read from Memory
Array 0000 A8011
WRITE Write to Memory Array 0000 A8010
Note: A8 represents MSB address bit A8
SPI_SEL_3 is currently unimplemented and is reserved for future SPI-related expansion.
SPI_SEL_4 is manufacturer specific.
2070.92 Serial Peripheral Interface (SPI)
Principal Usage: DataKey / serial EEPROM interface
Operating Modes: SYNC
Synchronous Rates (bps): (application-specific)
Interface Pins: SPI_MOSI: Master-Out-Slave-In (O)
SPI_MISO: Master-In-Slave-Out (I)
SPI_CLK: Clock (O)
SPI_SEL_1: Select 1 (O)
SPI_SEL_2: Select 2 (O)
SPI_SEL_3: Select 3 (O)
SPI_SEL_4: Select 4 (O)
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A25 of 107
2070.93 Data Key
Provide a DATAKEY Keyceptacle (KC4210, KC4210PCB or equal) shall be mounted on
the CPU module front panel. Power shall not be applied to the receptacle if the key is not
present.
The Manufacturer shall supply a 3.3 Volt, 8-Mb Memory Size Datakey (SFK8Mb or equal)
with each MODEL 1C CPU module. The Datakey shall be temperature rated for –40°C to
+85°C (-40°F to 185°F) operation, be blue in color, and shall be initialized to the format and
default values defined below. External capability to program the CPU Datakey shall be
provided by the Manufacturer.
When programmed, the memory on the key of header shall be organized as follows:
Bytes Description Default Values
1-2
16 bit Frame Check Sequence (FCS)
calculated as defined in clause 4.6.2 of
ISO/IEC 3309. This FCS is calculated across
bytes 3-64
3 Key Type See table below
4 Header Version 2
5-8 Latitude 0.0
9-12 Longitude 0.0
13-14 Controller ID 0xFFFF
15-16 Communication drop number 0xFFFF
17-20 IP Address 10.20.70.51
21-24 Subnet Mask 255.255.255.0
25-28 Default Gateway 10.20.70.254
29 Startup Override 0xFF
30-64 Reserved for Agency use All bytes set to 0xFF
65 to End User Data All bytes set to 0xFF
When programmed, Byte 3 of the header must contain the Key Type value as defined in the
following table:
Key Type Model No. Memory Size Sector Size Part Number
1 DK1000 1 KiloByte 2 Byte 611-0006-002A
2 LCK16000 16 KiloBytes 2 Byte 611-0070-008A
3 SFK2Mb 2 megabytes 64 KiloBytes 611-0089-004A
4 SFK4Mb 4 megabytes 64 KiloBytes 611-0104-002A
5 SFK8Mb 8 megabytes 64 KiloBytes 611-0132-006A
6 SFK32MB 32 megabytes 64 KiloBytes 611-0164-005A
The data format in the CPU Datakey header for the Latitude and Longitude fields shall
comply with IEEE/ANSI 754-1985 STD. All the other fields follow a Big Endian Format as
implemented by Motorola CPUs.
The Startup Override byte, not the Key Type, may be used to override the default controller
startup procedure as defined below.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A26 of 107
2070.94 Start-Up Consideration and Sequence
The engine board low-level hardware and O/S software initialization shall be completed and
application software shall be capable of exercising control of all ATC unit hardware within a
maximum of 4.5 seconds from the rise of both the POWERUP and POWERDOWN signals
to the HIGH state. In order that the startup time requirement may be verified, an application
program shall be provided by the manufacturer, as an independently-loaded software
module, which will activate the CPU_ACTIVE signal.
Start-Up Sequence. The engine board shall provide circuitry to prevent writing to the
SRAM area and to keep the processor in a RESET state any time that VPRIMARY is less
than the minimum-specified operating voltage regardless of the state of the POWERUP or
POWERDOWN signals.
The BSP supplied by the vendor shall provide operating-system-level support for the engine
board. See Paragraph 2070.60 Operating System & Board Support Package Requirements.
Startup Sequence
The BSP performs many steps starting from system reset to configure all low-level
hardware, file systems and system level drivers for such items as SP4, SP6, timers, etc.
The bootstrap code:
Initializes the microprocessor(s) internal registers
Does low level memory subsystem and peripheral initialization
Decompresses the Linux kernel, if compressed, and moves it from flash
EPROM to DRAM
Creates an initial RAM disk (initrd) if needed
Boots the kernel
The kernel then:
Parses the kernel command line if provided
Determines the processor MIPs rating (BogoMIPS)
Determines available memory and many other things
Loads compiled-in BSP drivers
Creates the RAM disk(s) from the flash EPROM image
Frees up memory used by the initial RAM disk
Starts processing the startup scripts
The startup scripts, which run before the prompt is displayed on the terminal, should then:
Install any additional time-critical BSP driver modules.
(The steps listed above must be completed within the time period specified above.)
Start time-critical user applications
Start IP stack protocol modules
Start other driver modules
Start other applications
The file /etc/inittab is the main location to put calls to startup scripts.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A27 of 107
SECTION V – TYPE 2070-2 FIELD I/O MODULE
2070.95 Type 2070-2A Field I/O Module (FI/O)
The TYPE 2070-2A MODULE consists of the Field Controller Unit; Parallel Input/Output
Ports; other Module Circuit Functions (includes muzzle switch); Serial Communication
Circuitry; Module Connectors C1S, C11S, and C12S mounted on the module front plate;
VDC Power Supply (+12VDC to +5VDC); and required resident software.
2070.96 Type 2070-2B Field I/O Module (FI/O)
The TYPE 2070-2B MODULE shall consist of the Serial Communication Circuitry, DC
Power Supply, and Module Connector C12S mounted on the module front plate only.
2070.97 Field F/O Controller Unit (FCU)
The FCU shall include a programmable microprocessor/controller unit together with all
required clocking and support circuitry. The FCU shall be provided with in-circuit re-
programmability via JTAG or BDM port. FCU shall be provided with operational software
necessary to meet housekeeping and functional requirements resident in socketed firmware.
2070.98 Parallel Input Port
The Parallel Input Ports shall provide 64 bits of input using ground-true logic. Each input
shall be read logic “1” when the input voltage at its field connector input is less than 3.5
VDC, and be read logic “0” when either the input current is less than 100 µA or the input
voltage exceeds 8.5 VDC. Each input shall have an internal pull-up to the Isolated +12 VDC
and not deliver greater than 20 Ma to a short circuit to ground. The pull-up resistance shall
not be less than 10K or more than 50 K Ohms.
2070.99 Parallel Output Port
The Parallel Output Ports shall provide 64 bits of output. Each output written as logic “1”
shall have a voltage at its field connector output of less than 4.o VDC. Each output written
as logic “0” shall provide an open circuit (1 Mega Ohm or more) at its field connector
output. Each output shall consist of an open-collector capable of driving 40 VDC minimum
and sinking 100 Ma minimum. Each output circuit shall be capable of switching from logic
“1” to “0” within 100 µs when connected to a load of 100K-Ohms minimum. Each output
circuit shall be protected from transients of 10 ±2µs duration, ±300 VDC from 1 K-Ohm
source, with a maximum rate of 1 pulse per second.
2070.100 Output Operation
Each output shall latch the data written and remain stable until either new data is written or
the active-low reset signal. Upon an active-low reset signal, each output shall latch LOGIC
“0” and retain that state until a new writing. The state of all output circuits at the time of
Power Up or in Power Down state shall be open. It shall be possible to simultaneously
assert all outputs within 100 µs of each other. An output circuit state not changed during a
new writing shall not glitch when other output circuits are updated.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A28 of 107
OTHER MODULE CIRCUIT FUNCTIONS.
2070.101 Maximum Capacitive Load
A maximum capacitive load of 100 picrofarads shall be presented to the LINESYNC input
signal. The EIA-485 compliant differential LINESYNC signals shall be derived from the
LINESYNC signal.
2070.102 External WDT “Enable” Shunt/Toggle Switch
An External WDT “Enable” Shunt/Toggle Switch shall be provided on the board. With the
jumper IN and NRESET transitions HIGH (FCU active), the FCU shall output a state change
on Output 39 Monitor Watchdog Timer Input) every 100 milliseconds for 10 seconds or due
to Set Output Command. When the shunt is missing (open), the feature will not apply. This
feature is required to operate with the Type 210 Monitor Unit only.
2070.103 WATCHDOG Circuit
An FCU Watchdog Circuit shall be provided. It shall be enabled by FIELD I/O firmware at
Power Up with a value of 100 milliseconds. Its enabled state shall be machine readable and
reported in the FI/O status byte. Once enabled, the watchdog timer shall not be disabled
without resetting the FI/O. Failure of the FI/O to reset the watchdog timer within the
prescribed timeout will result in a hardware reset.
2070.104 One KHz Reference
A synchronizable 1 KHz time reference. It shall maintain a frequency accuracy of ±0.01%
(±0.1 counts per second).
2070.105 32 Bit Millisecond Counter
A 32-bit MILLISECOND COUNTER (MC) for “time stamping” shall be provided.” Each 1
KHz reference interrupt shall increment the MC.
2070.106 Power Up
At Power Up, the FCU loss of communication timer shall indicate loss of communication
until the user program sends the Request Module Status message to reset the “E” Bit.
2070.107 Logic Switch
A LOGIC Switch shall be provided resident on the module board. The switch shall function
to disconnect Serial Port 3 (SP3) from the external world, Connector C12S. Its purpose is to
prevent multiple use of SP3. An LED shall be provided on the module front panel labeled
“SP3 ON”. If LED light ON, SP3 is active and available at C12S.
SERIAL COMMUNICATIONS/LOGIC CIRCUITRY
2070.108 System Serial Port 5 (SP5) EIA 485 Signal
System Serial Port 5 (SP5) EIA-485 signal lines shall enter the Field I/O Module and be split
into two multi-drop isolated ports. Route one to the FCU and the other converted to EIA-
485, then routed to Connector C12S.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A29 of 107
2070.109 System Serial Port 3 (SP3) EIA 485 Signal
System Serial Port 3 (SP3) EIA-485 signal lines shall enter the Field I/O Module and be
isolated, converted back to EIA-485 and then routed to Connector C12S.
2070.110 LINE SYNC and POWER DOWN
LINE SYNC and POWER DOWN lines shall be split and isolated, one routed to the FCU
for shut down functions and the other changed to EIA-485; then routed to connector C12S
for external module use.
2070.111 CPU RESET and POWER UP
CPU_ RESET and POWER UP (SysReset) lines shall be isolated and “OR’d” to form
NRESET. NRESET shall be used to reset the FCU and other module devices. NRESET
shall also be converted to EIA-485 then routed to Connector C12S.
2070.112 Module 2070-2B
If the Type 2070 module is a –2B, routing to FCU does not apply.
2070.113 Internal Isolation
Isolation is between internal +5 DC / DCG#1 and +12 DC ISO / DCG #2. +12 DC ISO is
for board power and external logic.
2070.114 Buffers
Transition Buffer capable of holding a minimum of 1024 recorded entries shall be provided.
The Transition Buffer shall default to empty. There shall be two entry types: Transition and
Rollover. The inputs shall be monitored for state transition. At each transition (If the input
has been configured to report transition), a transition entry shall be added to the Transition
Buffer. The MC shall be monitored for rollover. At each rollover transition ($xxxx FFFF -
$xxxx 0000), a rollover entry shall be added to the Transition Buffer. For rollover entries,
all bits of byte 1 are set to indicate that this is a rollover entry. Transition Buffer blocks are
sent to the CPU Module upon command. Upon confirmation of their reception, the blocks
shall be removed from the Transition Buffer.
I/O FUNCTIONS.
2070.115 Inputs
Input scanning shall begin at I0 (bit 0) and proceed to the highest numbered input I63, from
LSB to MSB in increasing input number. Each complete input scan shall finish within 100
µs. Once sampled, the logic state of an input shall be held until the next input scan. Each
input shall be sampled 1,000 times per second. The time interval between samples must be 1
ms (±100 µs). If configured to report, each input that has transitioned since its last
sampling shall be identified by input number, transition state, and timestamp (at the time the
input scan began) and be added as an entry to the Transition Buffer. If multiple inputs
change state during one input sample, these transitions shall be entered into the Input
Transition Buffer by increasing input number. The MC shall be sampled within 10 µs of the
completion of the input scan.
2070.116 Data Filtering
If configured, the inputs shall be filtered by the FCU to remove signal bounce. The filtered
input signals shall then be monitored for changes as noted. The filtering parameters for each
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A30 of 107
input shall consist of Ignore Input Flag and the ON and OFF filter samples. If the Ignore
Input flag is set, no input transitions will be recorded. The ON and OFF filter samples shall
determine the number of consecutive samples an input shall be ON and OFF, respectively,
before a change of state is recognized. If the change of state is shorter than the specified
value, the change of state shall be ignored. The ON and OFF filter values shall be in the
range of 0 to 255. A filter value of 0, for either or both values, shall result in no filtering for
this input. The default values for input signals after reset shall be as follows:
Filtering Enabled
On and off filter values shall be set to 5
Transition monitoring Disabled (Timestamps are not logged)
2070.117 Outputs
Simultaneous assertion of all outputs shall occur within 100 µs. Each output shall be
capable of being individually configured in state to ON, OFF, or a state synchronized with
either phase of LINESYNC. The condition of the outputs shall only be "ON" if the FI/O
continues to receive active communications from the CPU Module. If there is no valid
communications with the CPU Module for 2.0 seconds, all outputs shall revert to the OFF
condition, and the Module Status Byte shall be updated to reflect the loss of communication
from the CPU Module.
2070.118 Standard Function
Each output shall be controlled by the data and control bits in the CPU Module Field I/O
frame protocol as follows:
Output Bit Translation
Case
Output
Data
Bit
Output
Control
Bit
Function
A 0 0 Output in the OFF state
B 1 1
Output is a square wave, synchronized to the
LINESYNC signal. When LINESYNC is ON (1), the
output is OFF, and when LINESYNC is OFF (0), the
output is ON.
C 0 1
Output is a square wave, synchronized to the
LINESYNC signal. When LINESYNC is ON (1), the
output is ON, and when LINESYNC is OFF (0), the
output is OFF
D 1 0 Output is in the ON state.
2070.119 CASE A
In Case A above, the corresponding output shall be turned OFF if previously ON and if
previously OFF remain OFF until otherwise configured. For half-cycle switching (cases B
and C), all outputs to be changed shall be changed within 50 µs after the corresponding
LINESYNC transition and shall remain in the same state during the entire half cycle. In
Case D above, the corresponding output shall be turned ON if previously OFF and if
previously ON remains ON until otherwise configured. All outputs shall neither glitch nor
change state unless configured to do so.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A31 of 107
2070.120 Interrupts
All interrupts shall be capable of asynchronous operation with respect to all processing and
all other interrupts. MILLISECOND Interrupt shall be activated by the 1 KHz reference
once per ms. A timestamp rollover flag set by MC rollover shall be cleared only on
command. LINESYNC Interrupt both the 0-1 and 1-0 transitions of the LINESYNC signal
shall generate this interrupt. The LINESYNC interrupt shall monitor the MC interrupt and
set the MC error flag if there has not been an interrupt from the 1 KHz source for 0.5
seconds (≥60 consecutive LINESYNC interrupts). The LINESYNC interrupt shall
synchronize the 1 KHz time reference with the 0-1 transition of the LINESYNC signal once
a second. A LINESYNC error flag shall be set if the LINESYNC interrupt has not
successfully executed for 0.5 seconds or longer (≥500 consecutive ms interrupts).
2070.121 Communication Service Routine
A low-level communication service routine shall be provided to handle reception,
transmission, and EIA-485 communication faults. The communication server shall
automatically:
For Transmission
Generate the opening and closing flags
Generate the CRC value
Generate the abort sequence (minimum of 8 consecutive '1' bits) when commanded
by the FCU
Provide zero bit insertion
For Receiving
Detect the opening and closing flags
Provide address comparison, generating an interrupt for messages addressed to the
Field I/O Module, and ignoring messages not addressed to the Field I/O Module
Strip out inserted zeros
Calculate the CRC value, compare it to the received value, and generate an interrupt
on an error
Generate an interrupt if an abort sequence is received
2070.122 Communication Processing
This task shall be to process the command messages received from the CPU Module,
prepare, and start the response transmission. The response message transmission shall begin
within 4 milliseconds of the receipt of the received message. Message type processing time
constraint shall not exceed 70 milliseconds per message.
2070.123 Input Processing
This task shall process the raw input data scanned in by the 1 ms interrupt routine, perform
all filtering, and maintain the transition queue entries.
DATA COMMUNICATIONS PROTOCOLS.
2070.124 Communication Protocol
All communication between the CPU Module and the Field I/O shall be SDLC-compatible
command-response protocol, support 0 bit stuffing, and operate at a data rate of 614.4
kilobits per second. The CPU Module shall always initiate the communication and should
the command frame be incomplete or there is an error, no Field I/O response will be
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A32 of 107
transmitted. The amount of bytes of a command or response is dependent upon the Field I/O
Module identification.
2070.125 Frame Types
The frame type shall be determined by the value of the first byte of the message. The
command frames type values 112-127 ($70-$7F) and associated response frame type values
240-255 ($F0- $FF) are allocated to the manufacturer diagnostics. All other frame types not
called out are reserved. The command-response Frame Type values and message times shall
be as follows:
Frame Types
Module
Command
I/0 Module
Response Description
Minimum
Message
Time
Maximum
Message
Time
0-43 128-171 Reserved for NEMA TS-2
44-48 172-176 Reserved
49 177 Request Module Status 250 µs 275 µs
50 178 MC Management 222.5 µs 237.5 µs
51 179 Configure Inputs 344.5 µs 6.8750 µs
52 180 Poll Raw Input Data 317.5 µs 320 µs
53 181 Poll Filtered Input Data 317.5 µs 320 µs
54 182 Poll Input Transition Buffer 300 µs 10.25 µs
55 183 Set Outputs 405 µs 410 µs
56 184 Configure Input Tracking 340 µs 10.25 µs
57 185 Configure Complex Outputs 340 µs 6.875 µs
58 186 Configure Watchdog 222.5 µs 222.5 µs
59 187 Controller Identification 222.5 µs 222.5 µs
60 188 I/O Module Identification 222.5 µs 222.5 µs
61-62 189-190 Reserved (note below) --- ---
63 191 Poll variable length raw input
(note below) 317.5 µs 320 µs
64 192 Variable length command outputs 405 µs 410 µs
65 193 Reserved (note below) --- ---
67 195 Reserved (note below) --- ---
68-111 196-239 Reserved --- ---
112-127 240-255 Manufacture Diagnostics --- ---
Note: ITS Cabinet Monitor. Messages 61 / 189, 62 / 190, 65 / 193, are reserved for ITS
Cabinet Monitor Unit. See ITS Cabinet Monitor System Serial Bus #1 for Command and
Response Frames. Message 63 / Message 191 shall be the same as Message 52 / 180 except
Byte 2 of Message 63 response shall denote the following number of input data bytes.
Message 64 / 192 shall be the same as Message 55 / 183 except Byte 2 of the Message 64
Command shall denote the number of output data bytes, plus the following output control
bytes.
2070.126 Request Module Status
The Command shall be used to request FI/O status information response.
Command/response frames are as follows:
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A33 of 107
Request Module Status Command
Description msb lsb Byte Number
(Type Number = 49) 0 0110001 Byte 1
Reset Status Bits P E K R T M L W Byte 2
Request Module Status Response
Description msb lsb Byte Number
(Type Number = 177) 1 011000 1 Byte 1
System Status P E K R T M L W Byte 2
SCC Receive Error Count Receive Error Count Byte 3
SCC Transmit Error Count Transmit Error Count Byte 4
MC Timestamp MSB MC Timestamp MSB Byte 5
MC Timestamp NMSB MC Timestamp NMSB Byte 6
MC Timestamp NLSB MC Timestamp NLSB Byte 7
MC Timestamp LSB MC Timestamp LSB Byte 8
2070.127 Status Bits
The response status bits are defined as follows:
P Indicates FI/O hardware reset
E Indicates a communications loss of greater than 2 seconds
K Indicates the Datakey has failed or is not present
R Indicates that the SCC Receive Error count byte has rolled over
T Indicates that the SCC Transmit Error count byte has rolled over
M Indicates an error with the MC interrupt
L Indicates an error in the LINESYNC
W Indicates that the FI/O has been reset by the Watchdog
2070.128 Request Module Status
Each of these bits shall be individually reset by a “1” in the corresponding bit of any
subsequent Request Module Status frame, and the response frame shall report the current
status bits. The SCC error count bytes shall not be reset. When an SCC error count rolls
over (255-0), its corresponding roll-over flag shall be set.
2070.129 MC Management
MC MANAGEMENT frame shall be used to set the value of the MC. The 'S' bit shall return
status '0' on completion or “1” on error. The 32-bit value shall be loaded into the MC at the
next 0-1 transition of the LINESYNC signal. The frames are as follows:
MC Management Command
Description msb lsb Byte Number
(Type Number = 50) 0 0 1 1 0 0 1 0 Byte 1
New MC Timestamp MSB x x x x x x x x Byte 2
New MC Timestamp NMSB x x x x x x x x Byte 3
New MC Timestamp NLSB x x x x x x x x Byte 4
New MC Timestamp LSB x x x x x x x x Byte 5
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A34 of 107
MC Management Response
Description msb lsb Byte Number
(Type Number = 178) 1 0 1 1 0 0 1 0 Byte 1
Status 0 000000S Byte 2
2070.130 Configure Inputs Commands
The Configure Inputs command frame shall be used to change input configurations. The
command-response frames are as follows:
Configure Inputs Command
Description msb lsb Byte Number
(Type Number = 51) 0 0 1 1 0 0 1 1 Byte 1
Number of Items (n) n nnnnnnn Byte 2
Item # - Byte 1 E Input Number Byte 3(I-1)+3
Item # - Byte 2 Leading edge filter (e) Byte 3(I-1)+4
Item # - Byte 3 Trailing edge filter (r) Byte 3(I-1)+5
Configure Inputs Response
Description msb lsb Byte Number
(Type Number = 179) 1 0 1 1 0 0 1 1 Byte 1
Status 0 000000S Byte 2
Block field definitions shall be as follows:
E Ignore Input Flag. "1" = do not report transitions for this input, "0" = report
transitions for this input
e A one-byte leading edge filter specifying the number of consecutive input samples
which shall be "0" before the input is considered to have entered to "0" state from "1" state
(range 1 to 255, 0 = disabled)
r A one-byte trailing edge filter specifying the number of consecutive input samples
which shall be "1" before the input is considered to have entered to "1" state from "0" state
(range 1 to 255, 0 = disabled)
S return status S = '0' on completion or '1' on input error out of range
2070.131 Poll Raw Input Data
The Poll Raw Input Data frame shall be used to poll the FI/O for the current unfiltered status
of all inputs. The response frame shall contain 8 bytes (2A) or 15 bytes (2B) of information
indicating the current status of the inputs. The frames are as follows:
Poll Raw Input Data Command
Description msb lsb Byte Number
(Type Number = 52) 0 0 1 1 0 1 0 0 Byte 1
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A35 of 107
Poll Raw Input Data Response (2070-2A)
Description msb lsb Byte Number
(Type Number = 180) 1 0 1 1 0 1 0 0 Byte 1
Inputs I0 (lsb) to I7 (msb) x x x x x x x x Byte 2
Inputs I8 to I63 x x x x x x x x Bytes 3 to 9
Timestamp MSB x x x x x x x x Byte 10
Timestamp NMSB x x x x x x x x Byte 11
Timestamp NLSB x x x x x x x x Byte 12
Timestamp LSB x x x x x x x x Byte 13
Poll Raw Input Data Response (2070-8 via 2070-2B)
Description msb lsb Byte Number
(Type Number = 180) 1 0 1 1 0 1 0 0 Byte 1
Inputs I0 (lsb) to I7 (msb) x x x x x x x x Byte 2
Inputs I8 to I119 x x x x x x x x Bytes 3 to 16
Timestamp MSB x x x x x x x x Byte 17
Timestamp NMSB x x x x x x x x Byte 18
Timestamp NLSB x x x x x x x x Byte 19
Timestamp LSB x x x x x x x x Byte 20
2070.132 Poll Filtered Input Data
The Poll Filtered Input Data frame shall be used to poll the FI/O for the current filtered
status of all inputs. The response frame shall contain 8 bytes (2A) or 15 bytes (2B) of
information indicating the current filtered status of the inputs. Raw input data shall be
provided in the response for inputs that are not configured for filtering. The frames are as
follows:
Poll Filter Input Data Command
Description msb lsb Byte Number
(Type Number = 53) 0 011010 1 Byte 1
Poll Filter Input Data Response (2070-2A)
Description msb lsb Byte Number
(Type Number = 181) 1 0 1 1 0 1 0 1 Byte 1
Inputs I0 (lsb) to I7 (msb) x x x x x x x x Byte 2
Inputs I8 to I63 x x x x x x x x Bytes 3 to 9
Timestamp MSB x xxxxxx x Byte 10
Timestamp NMSB x xxxxxx x Byte 11
Timestamp NLSB x xxxxxx x Byte 12
Timestamp LSB x xxxxxx x Byte 13
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A36 of 107
Poll Filter Input Data Response (2070-8 via 2070-2B)
Description msb lsb Byte Number
(Type Number = 181) 1 011010 1 Byte 1
Inputs I0 (lsb) to I7 (msb) x xxxxxx x Byte 2
Inputs I8 to I119 x xxxxxx x Bytes 3 to 16
Timestamp MSB x xxxxxx x Byte 17
Timestamp NMSB x xxxxxx x Byte 18
Timestamp NLSB x xxxxxx x Byte 19
Timestamp LSB x xxxxxx x Byte 20
2070.133 Poll Input Transition Buffer
The Poll Input Transition Buffer frame shall poll the FI/O for the contents of the input
transition buffer. The response frame shall include a three-byte information field for each of
the input changes that have occurred since the last interrogation. The frames are as follows:
Poll Input Transition Buffer Command
Description msb lsb Byte Number
(Type Number = 54) 0 011011 0 Byte 1
Block Number x xxxxxx x Byte 2
Poll Input Transition Buffer Response
Description msb lsb Byte Number
(Type Number = 182) 1 011011 0 Byte 1
Block Number x xxxxxx x Byte 2
Number of Entries (n) x xxxxxx x Byte 3
Item # S Input Number Byte 3(I-1)+4
Item # Timestamp NLSB x xxxxxx x Byte 3(I-1)+5
Item # Timestamp LSB x xxxxxx x Byte 3(I-1)+6
Status 0 0 0 0 C F E G Byte 3(I-1)+7
Timestamp MSB X xxxxxx x Byte 3(I-1)+8
Timestamp NMSB X xxxxxx x Byte 3(I-1)+9
Timestamp NLSB X xxxxxx x Byte 3(I-1)+10
Timestamp LSB X xxxxxx x Byte 3(I-1)+11
The entry types are depicted as follows:
Input Transition Entry
Description msb lsb Byte Number
Transition Entry Identifier S Input Number 1
Timestamp NLSB x xxxxxx x 2
Timestamp LSB x xxxxxx x 3
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A37 of 107
MC Rollover Entry
Description msb lsb Byte Number
Rollover Entry Identifier 1 111111 1 1
Timestamp MSB x xxxxxx x 2
Timestamp NMSB x xxxxxx x 3
2070.134 Active Input
Each detected state transition for each active input (see configuration data) is placed in the
queue as it occurs. Bit definitions are as follows:
S Indicates the state of the input after the transition
C Indicates the 255 entry buffer limit has been exceeded
F Indicates the transition buffer limit has been exceeded
G Indicates the requested block number is out of monotonic increment sequence
E Same block number requested, E is set in response
2070.135 The Block Number byte
The Block Number byte is a monotonically increasing number incremented after each
command issued by the CPU Module. When the FI/O Module receives this command, it
shall compare the associated Block Number with the Block Number of the previously
received command. If it is the same, the previous buffer shall be re-sent to the CPU Module
and the 'E' flag set in the status response frame. If it is not equal to the previous Block
Number, the old buffer shall be purged and the next block of data sent. If the block number
is not incremented by one, the status G bit shall be set. The block number received becomes
the current number (even if out of sequence). The Block Number byte sent in the response
block shall be the same as that received in the command block. Counter rollover shall be
considered as a normal increment.
2070.136 Set Outputs
The Set Outputs frame shall be used to command the FI/O to set the Outputs according to the
data in the frame. If there is any error configuring the outputs, the 'E' flag in the response
frame shall be set to '1'. If the LINESYNC reference has been lost, the 'L' bit in the response
frame shall be set to “1”. Loss of LINESYNC reference shall also be indicated in Module
Status Response Frame. The output bytes depend upon field I/O module. These command
and response frames are as follows:
Set Outputs Command (2070-2A)
Description msb lsb Byte Number
(Type Number = 55) 0 0 1 1 0 1 1 1 Byte 1
Outputs O0 (lsb) to O7 (msb)
Data x x x x x x x x Byte 2
Outputs O8 to O63 Data x x x x x x x x Bytes 3 to 9
Outputs O0 (lsb) to O7 (msb)
Control x x x x x x x x Byte 10
Outputs O8 to O63 Control x x x x x x x x Bytes 11 to 17
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A38 of 107
Set Outputs Command (2070-8 via 2070-2B)
Description msb lsb Byte Number
(Type Number = 55) 0 0 1 1 0 1 1 1 Byte 1
Outputs O0 (lsb) to O7 (msb)
Data x x x x x x x x Byte 2
Outputs O8 to O103 Data x x x x x x x x Byte 3 to 14
Outputs O0 (lsb) to O7 (msb)
Control x x x x x x x x Byte 15
Outputs O8 to O103 Control x x x x x x x x Byte 16 to 27
Set Outputs Response
Description msb lsb Byte Number
(Type Number = 183) 1 0 1 1 0 1 1 1 Byte 1
Status 0 0 0 0 0 0 L E Byte 2
2070.137 Configure Input Tracking Functions
The Configure Input Tracking Functions frame shall be used to configure outputs to respond
to transitions on a specified input. Each Output Number identified by Item Number shall
respond as configured to the corresponding Input Number identified by the same Item
Number. Input and Output mapping shall be one to one. If a command results in more than
8 input tracking outputs being configured, the response V bit shall be set to “1” and the
command shall not be implemented. The command and response frames are as follows:
Configure Input Tracking Function Command
Description msb lsb Byte Number
(Type Number = 56) 0 0 1 1 1 0 0 0 Byte 1
Number of Items Number of Items Byte 2
Item # - Byte 1 E Output Number Byte 2(I-1)+3
Item # - Byte 2 I Input Number Byte 2(I-1)+4
Configure Input Tracking Functions Response
Description msb lsb Byte Number
(Type Number = 184) 1 0 1 1 1 0 0 0 Byte 1
Status x x x x x x x x Byte 2
Timestamp MSB x x x x x x x x Byte 3
Timestamp NMSB x x x x x x x x Byte 4
Timestamp NLSB x x x x x x x x Byte 5
Timestamp LSB x x x x x x x x Byte 6
2070.138 Definitions are as follows:
E “1” - Enable input tracking functions for this output
“0” - Disable tracking functions for this output
I “1” - The output is OFF when input is ON, On when the input is OFF
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A39 of 107
“0” - The output is ON when input is ON, OFF when input is OFF
V “1” - The max. number of 8 configurable outputs has been executed
“0” - No error
Number of Items – the number of entries in the frame. If zero, all outputs currently
configured for input tracking shall be disabled.
2070.139 Timestamp Value
The timestamp value shall be sampled prior to the response frame.
2070.140 Outputs Tracks Inputs
Outputs which track inputs shall be updated no less than once per ms. Input to output signal
propagation delay shall not exceed 2 ms.
2070.141 Number of Item
The “Number of Item” field is valid from 0 to 16 (most that is sent at one time is 8 enables
and 8 disables). If processing a command resulting in more than 8 Input Tracking functions
being enabled, none of the command shall be implemented and response message “V” bit set
to 1. If an invalid output or input number is specified for a function, the FIOM software
shall not do that function definition. It shall also not be counted toward the maximum of 8
input tracking function allowed. The rest of the message shall be processed. When an Input
Tracking function is disabled, the output is set according to the most recently received Set
Outputs Command. When an input tracking function for an output is superseded (redefined
as either another input tracking function or as a complex output function) nothing shall be
done with the output. The most recent value remains until the new function changes it.
2070.142 Configure Complex Output Functions
The configure complex output functions frame shall be used to specify a complex output for
one to eight of any of the outputs. If a Configure Complex Output Function command
results in more than eight outputs being configured, the 'V' bit in the response message shall
be set to a '1', and the command shall not be implemented. Two output forms shall be
provided: single pulse and continuous oscillation. These output forms shall be configurable
to begin immediately or on a specified input trigger and, in the case of continuous
oscillation, to continue until otherwise configured or to oscillate only while gated active by a
specified input. If the command gate bit is active, the command trigger bit shall be ignored
and the specified input shall be used as a gate signal. The command and response frames are
as follows:
Configure Complex Output Functions Command
Description msb lsb Byte Number
(Type Number = 57) 0 011100 1 1
Number of Items Number of Items 2
Item i - Byte 1 0 Output Number 7(i-1)+3
Item i - Byte 2 Primary Duration (MSB) 7(i-1)+4
Item i - Byte 3 Primary Duration (LSB) 7(i-1)+5
Item i - Byte 4 Secondary Duration (MSB) 7(i-1)+6
Item i - Byte 5 Secondary Duration (LSB) 7(i-1)+7
Item i - Byte 6 0 Input Number 7(i-1)+8
Item i - Byte 7 P W G E J F R L 7(i-1)+9
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A40 of 107
Configure Complex Output Functions Response
Description msb lsb Byte Number
(Type Number = 185) 1 011100 1 1
Status 0 000000 V 2
Timestamp (MSB) x xxxxxx x 3
Timestamp (NMSB) x xxxxxx x 4
Timestamp (NLSB) x Xxxxxx x 5
Timestamp (LSB) x Xxxxxx x 6
2070.143 Configure Complex Outputs Bit Fields
The bit fields of the command frame are defined as follows:
E '1' - Enable complex output function for this output
'0' - Disable complex output function for this output
J '1' - During the primary duration, the output shall be written as a logic '1'
During the secondary duration, the output shall be written as a logic '0'
'0' - During the primary duration, the output shall be written as a logic '0'
During the secondary duration, the output shall be written as a logic '1'
Output Number - 7-bit output number identifying outputs
Primary Duration - For single pulse operation, this shall determine the number of
“ticks” preceding the pulse. For continuous oscillation, this shall determine the
length of the inactive (first) portion of the cycle.
Secondary Duration - For single pulse operation, this shall determine the number
of ticks the pulse is active. Subsequent to the secondary duration, the output shall
return to the state set according to the most recently received Set Outputs
command. For continuous oscillation, this shall determine the length of the
active (second) portion of the cycle. 0 = hold output state until otherwise
configured.
F '1' - The trigger or gate shall be acquired subsequent to filtering the specified input.
The raw input signal shall be used if filtering is not enabled for the specified
input.
'0' - The trigger or gate shall be derived from the raw input.
R '1' - For triggered output, the output shall be triggered by an ON-to-OFF transition of
the specified input and shall be triggered immediately upon command receipt if
the input is OFF. For gated output, the output shall be active while the input is
OFF.
'0'- For triggered output, the output shall be triggered by an OFF-to-ON transition of
the specified input and shall be triggered immediately upon command receipt if
the input is ON. For gated output, the output shall be active while the input is
ON.
Input Number - 7-bit input number identifying inputs 0 Up.
P '1'- The output is configured for single-pulse operation. Once complete, the complex
output function shall be disabled.
'0' - The output is configured for continuous oscillation.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A41 of 107
W '1' - It is triggered by the specified input. Triggered complex output shall commence
within 2 ms of the associated trigger.
'0' - Operation shall begin within 2 ms of the command receipt.
G '1' - Operation shall be gated active by the specified input.
'0' - Gating is inactive.
L '1' - The LINESYNC based clock shall be used for the time ticks.
'0' - The MC shall be used for the time ticks.
V '1' - Indicates maximum number of configurable outputs is exceeded.
'0' - No error
Number of items - The number of entries in the frame. If 0, all outputs currently configured
as complex outputs shall be disabled.
2070.144 Controlling Input Signals
Controlling input signals shall be sampled at least once per ms.
2070.145 Number of Items
The “number of items” field is valid from 0 to 16. Zero means disable all Complex Output
functions. Sixteen is the maximum because the most that is sent at one time is eight enables
and eight disables. If processing a command results in more than eight Complex Output
functions being enabled, none of the command shall be implemented and the response
message “V” bit shall be set to 1. If an invalid output or input number (the “G” or “W” bits
being set to 1) is specified for a function, that function definition is not done by the FIOM
software. It shall also not be counted towards the maximum of eight Complex Output
functions allowed. The rest of the message shall be processed. When a Complex Output
function is disabled, the output is set according to the most recently received set outputs
command. When a Complex Output function for an output is superseded, that is, redefined
as whether another Complex Output function, or as an input tracking function, nothing
special is done with the output. The most recent value remains until the new function
changes it. The “G” bit (gating) set to 1 takes precedence over the “W” bit (triggering). If
gating is ON, triggering is turned OFF, regardless of the value of the “W” bit in the
command message. If a Complex Output is configured with the “G” bit set to 1 (gating) and
the “P” bit set to 0 (continuous oscillation), the output is set to OFF (0) whenever the
specified input changes state so that the oscillation should cease (output inactive). For a
single pulse operation (“G” bit set to 1), after the secondary duration completes the Complex
Output function shall be disabled, and the output shall be set according to the most recently
received set outputs command.
2070.146 Configure Watchdog
The Configure Watchdog frames shall be used to change the software watchdog timeout
value. The Command and response frames are as follows:
Configure Watchdog Command
Description msb lsb Byte Number
(Type Number = 58) 0 011101 0 Byte 1
Timeout Value x xXxxxx x Byte 2
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A42 of 107
Configure Watchdog Response
Description msb lsb Byte Number
(Type Number = 186) 1 011101 0 Byte 1
Status 0 000000 Y Byte 2
2070.147 Timeout Value
The timeout value shall be in the range between 10 to 100 ms. If the value is lower than 10,
10 shall be assumed. If the value is greater than 100, 100 shall be assumed.
2070.148 Watchdog Timeout Value
On receipt of this frame, the watchdog timeout value shall be changed to the value in the
message and the “Y” bit set. The response frame bit (Y) shall indicate a '1' if the watchdog
has been previously set and a '0' if not.
2070.149 Controller Identification
This is a legacy message command / response for FI/O modules with Datakey resident.
Upon command, a response frame containing the 128 bytes of the Datakey See previous
sections on Request Module Status for FI/O Status Bit ‘K’ definition. If “K” bit set, only the
first two bytes shall be returned. The Command and Response frames are as follows:
Controller Identification Command
Description msb lsb Byte Number
(Type Number= 59) 0 011101 1 Byte 1
Controller Identification Response
Description msb lsb Byte Number
(Type Number = 187) 1 011101 1 Byte 1
Status 0 000000 K Byte 2
Datakey x xxxxxx x Bytes 3 to 130
2070.150 Module Identification
The Field I/O Module Identification Command frame shall be used to request the FI/O
Identification value. A value response of "1" shall Model 332 FI/O, "2" for the NEMA TS-2
Type 2, "3" is reserved for NEMA TS 2 Type 1 FI/O and "32 to 40" are reserved for ITS
Cabinets. The command and response frames are shown as follows:
I/O Module Identification Command
Description msb lsb Byte Number
(Type Number = 60) 0 011110 0 Byte 1
I/O Module Identification Response
Description msb lsb Byte Number
(Type Number = 188) 1 011110 0 Byte 1
FI/O I D byte x xXxxxx x Byte 2
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A43 of 107
SECTION VI - TYPE 2070-3D FRONT PANEL ASSEMBLY.
2070.151 General
The Type 2070-3D Front Panel Assembly (FPA) shall be delivered with a panel with Latch
assembly and two TSD #1 hinge attaching devices, assembly PCB, external serial port
connector (DB9), external Ethernet port (RJ45), CPU active LED indicator, and FP Harness
Interface. The FPA shall also provide the following features; FPA controller, two
keyboards, AUX switch, alarm bell and Display D as described below in Paragraph
2070.156.
2070.152 Keyboards
Provide two KEYBOARDS, one with sixteen keys for hexadecimal alphanumeric entry and
the other with twelve keys to be used for cursor control and action symbol entry. Engrave or
emboss each key with its function character. Each key shall have an actuation force between
1.764 ounce and 3.527 ounce and provide a positive tactile indication of contact closure.
Key contacts shall be hermetically sealed, have a design life of over one million operations,
be rated for the current and voltage levels used, and stabilize within 5 ms following contact
closure.
2070.153 Ethernet Port
The FPA shall include a standard pin out RJ-45 Ethernet port in place of the C50J RJ-45
serial port.
2070.154 FPA Layout
Alternate keyboard and display layouts are acceptable as approved by the City. However,
minimum size dimensions shall be maintained.
2070.155 CPU Active Indicator
The cathode of the CPU ACTIVE LED INDICATOR shall be electrically connected to the
CPU_ ACTIVE signal and be pulled up to +5 VDC.
2070.156 Display Liquid Crystal Display (LCD)
The Display shall consist of a Liquid Crystal Display (LCD), a backlight, and a contrast
potentiometer control. Display D shall have 16 lines of 40 characters each with minimum
dimensions of 0.104 wide by 0.167 high and either LED or EL backlight.
2070.157 Characters and Angles of Liquid Crystal Display (LCD)
Each character shall be composed of a 5 x 7 dot matrix with an underline row or a 5 x 8 dot
matrix. The viewing angle of the LCD shall be optimized for direct (90 degrees) viewing,
±35 degrees vertical, ±45 degrees horizontal. The LCD shall have variable contrast with a
minimum ratio of 4:1. The LCD shall be capable of displaying, at any position on the
Display, any of the standard ASCII characters as well as user-defined characters.
2070.158 Backlight
The backlight shall be turned on and off by the Controller Circuitry. The backlight and
associated circuitry shall consume no power when in off state. A potentiometer shall control
the LCD contrast with clockwise rotation increasing contrast. The contrast shall depend on
the angular position of the potentiometer, which shall provide the entire contrast range of the
LCD.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A44 of 107
2070.159 Cursor Display
Cursor display shall be turned ON and OFF by command. When ON, the cursor shall be
displayed at the current cursor position. When OFF, no cursor is to be displayed. All other
cursor functions (positioning, etc.) shall remain in effect.
2070.160 FPA Controller
The FPA CONTROLLER shall function as the Front Panel Device controller interfacing
with the CPU Module.
2070.161 FPA RESET
Provide a FPA RESET Switch on the Assembly PCB. The momentary CONTROL switch
shall be logic OR'd with the CPU_RESET Line, producing a FPA RESET Output. Upon
FPA RESET being active or receipt of a valid Soft Reset display command, the following
shall occur:
Auto-repeat, blinking, auto-wrap, and auto-scroll shall be set to OFF.
Each special character shall be set to ASCII SPC (space).
The tab stops shall be set to columns 9, 17, 25, and 33.
The backlight timeout value shall be set to 6 (60 seconds).
The backlight shall be extinguished.
The display shall be cleared (all ASCII SPC).
The cursor display shall be turned off.
The FPA module shall transmit a power up string through /sp6 to the CPU. Once
power is applied to the FPA, or the FPA hardware RESET BUTTON IS PUSHED.
The string is “ESC [PU”, hex value “1B 5B 50 55”.
2070.162 Keypress
When a keypress is detected, the appropriate key code shall be transmitted to SP6-RxD. If
two or more keys are depressed simultaneously, no code is to be sent. If a key is depressed
while another key is depressed, no additional code is to be sent.
2070.163 Auto-Repeat
Auto-repeat shall be turned ON and OFF by command. When ON, the key code shall be
repeated at a rate of 5 times per second starting when the key has been depressed
continuously for 0.5 second, and shall terminate when the key is released or another key is
pressed.
2070.164 AUX
When the AUX Switch is toggled, the appropriate AUX Switch code shall be transmitted to
the CPU.
2070.165 Controller Circuitry
The controller circuitry shall be capable of composing and storing eight special graphical
characters on command, and displaying any number of these characters in combination with
the standard ASCII characters. Undefined characters shall be ignored. User-composed
characters shall be represented in the communication protocol on Figure 14 of Appendix D.
P1 represents the special character number (1-8). Pn's represent columns of pixels from left
to right. The most significant bit of each Pn represents the top pixel in a column and the
least significant bit shall represent the bottom pixel. A logic ‘1’ shall turn the pixel ON.
There shall be a minimum of 5 Pn's for 5 columns of pixels in a command code sequence
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A45 of 107
terminated by an "f." If the number of Pn’s is more than the number of columns available on
the LCD, the extra Pn's shall be ignored. P1 and all Pn's shall be in ASCII coded decimal
characters without leading zero.
2070.166 Character Overwrite
Character overwrite mode shall be the only display mode supported. A displayable character
received shall always overwrite the current cursor position on the Display. The cursor shall
automatically move right one character position on the Display after each character write
operation. When the rightmost character on a line (position 40) has been overwritten, the
cursor position shall be determined based on the current settings of the auto-wrap mode.
2070.167 Auto-Wrap
Auto-wrap shall be turned ON & OFF by command. When ON, a new line operation shall
be performed after writing to position 40. When OFF, upon reaching position 40, input
characters shall continue to overwrite position 40.
2070.168 Cursor Positioning
Cursor positioning shall be non-destructive. Cursor movement shall not affect the current
display, other than blinking the cursor momentarily and periodically hiding the character at
that cursor position.
2070.169 Blinking Characters
Blinking characters shall be supported, and be turned ON and OFF by command. When ON,
all subsequently received displayable characters shall blink at the rate of 1 Hertz with a 60%
ON / 40% OFF duty cycle. It shall be possible to display both blinking and non-blinking
characters simultaneously.
2070.170 Tab Stops
Tab stops shall be configurable at all columns. A tab stop shall be set at the current cursor
position when a SetTabStop command is received. Tab Stop(s) shall be cleared on receipt of
a ClearTabStop command. On receipt of the HT (tab) code, the cursor shall move to the
next tab stop to the right of the cursor position. If no tab stop is set to the right of the current
cursor position, the cursor shall not move.
Tab stops shall be set based only upon the column (horizontal) position of the cursor; the
row position shall be ignored. Each tab that is set shall apply to all rows of the display. In
this way, tabs shall operate similarly to a typewriter or line printer. For example, if the
cursor is positioned at column 21, row 3 when a Set Tab Stop command (ESC H) is
received, a tab stop is placed at column 21 and applies to every row of the display. If the
cursor is then positioned to column 21, row 5, and a Clear Tab Stop command (ESC 0G) is
received, the tab stop on column 21 is removed and there will be no tab stop on any row of
the display at that column position.
2070.171 Auto-Scroll
Auto-scroll shall be turned ON and OFF by command. When ON, a Line Feed or new line
operation from the bottom line shall result in the display moving up one line. When OFF, a
Line Feed or new line from the bottom line shall result in the top line clearing, and the cursor
being positioned on the top line.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A46 of 107
2070.172 Displayable Characters
Display Characters shall be refreshed from the buffer at a rate of no less than 20 times per
second.
2070.173 Display Back Light Illuminate
The Display back light shall illuminate when any key is pressed and illuminate or extinguish
by command. The backlight shall extinguish when no key is pressed for a specified time.
This time shall be program selected by command, by a number in the range 0 to 63
corresponding to that number of 10-second intervals. A value of 1 shall correspond to a
timeout interval of 10 seconds. A value of 0 shall indicate no timeout.
2070.174 Command Codes
The Command Codes shall use the following conventions:
1. Parameters and Options: Parameters are depicted in both the ASCII and hexadecimal
representations as the letter 'P' followed by a lower-case character or number. These are
interpreted as follows:
Pn: Value parameter, to be replaced by a value, using one ASCII character per digit
without leading zeros.
P1: Ordered and numbered parameter. One of a listed known parameters with a
specified order and number (Continues with P2, P3, etc.)
Px: Display column number (1-40), using one ASCII character per digit without
leading zero.
Py: Display line (1-4) one ASCII character
...: Continue the list in the same fashion
Values of 'h' (0x68) and 'l' (0x6C) are used to indicate binary operations. ‘h'
represents ON (high), 'l' represents OFF (low).
2. ASCII Representation: Individual characters are separated by spaces; these are not to
be interpreted as the space character, which is depicted by SPC.
3. Hexadecimal Representation: Characters are shown as their hexadecimal values and
will be in the range 0x00 to 0x7F (7 bits).
2070.175 Controller Circuit
The Controller Circuit shall communicate via a SP6 asynchronous serial interface. The
interface shall be configured for 38.4 kilobits per second, 8 data bits, 1 stop bit, and no
parity.
2070.176 C50 ENABLE FUNCTION
C50 ENABLE function when grounded by C50 pins 1 and 5, shall be brought to Connectors
A1, pin B21 for the purpose of disabling the module channel 2, (SP4).
2070.177 Front Panel
The Front Panel shall include an electronic bell to signal receipt of ^G(hex07)). The bell
shall sound at 2,000 Hertz, with a minimum output rating of 85 dB at a distance of 4 feet for
350±100 ms upon receipt of ^G(hex07). Receipt of all other characters and ESC codes shall
continue during the time the bell sounds.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A47 of 107
SECTION VII - TYPE 2070-3D USB FRONT PANEL ASSEMBLY
2070.178 General
The 2070-3D USB Front Panel Assembly shall meet all specification presented in Section VI
with the following additions and exceptions:
2070.179 Universal Serial Bus (USB)
The FPA shall include a minimum of 2 external Type-A USB ports on front panel.
The USP ports shall be compliant to the latest AASHTO/ITE Next Generation ATC
Standard with the exception that the USB shall conform to the appropriate sections of the
USB v3.0 specification for both hardware and software operations.
2070.180 Alternate Front Panel Assembly Layout
Alternate keyboard and display layouts are acceptable as approved by the City. However,
minimum size dimension shall be maintained.
2070.181 1C-CPU USB
To facilitate the implementation of this Alternative, the City shall allow the disabling of the
USB port on the 1C-CPU front panel. However, all wiring to implement this alternative
shall be internal to the controller unit.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A48 of 107
SECTION VIII - TYPE 2070-4A POWER SUPPLY MODULE.
2070.182 Model 2070-4A Power Supply Module
Type 2070-4B power supply modules shall be provided. Type 2070-4B Power Supply
Module shall be independent, self contained Module, vented, and cooled by convection only.
The Module shall slide into the unit’s power supply compartment from the back of the
Chassis and be attached to the Backplane Mounting Surface by its four TSD #3 Devices.
2070.183 On/Off Power Switch
An "On/Off" POWER Switch, four LED DC Power Indicators, PS Receptacle POWER
Connectors, and the Incoming AC Fuse protection shall be provided on the Module Front.
The LED DC POWER Indicators shall indicate all required DC voltages meet the following
conditions: the +5 VDC and the 12 VDC are within 5% of their nominal levels.
2070.184 Input Protection
Two 0.5-Ohm, 10-watt wire-wound power resistors with a 0.2 µH inductance (one on the
AC+ Line & on the AC- Line) shall be provided. Three 20 Joule surge arrestors between
AC+ to AC-, AC+ to EG, and AC- to EG shall be provided. A 0.68 µF capacitor shall be
placed between AC+ & AC- (between the resistor & arrestors).
2070.185 +5VDC Standby Power
+5 VDC STANDBY POWER to hold up specified circuitry during the power down period
shall be provided. It shall consist of the monitor circuitry; hold up capacitors, and charging
circuitry. A charging circuit shall be provided, that under normal operation, fully charges
and float the capacitors consistent with the manufacturers’ recommendations. The Hold Up
power requirements shall be a minimum constant drain of 600 microamperes at a range of +5
VDC to +2 VDC for over 600 minutes.
2070.186 Monitor Circuitry
MONITOR CIRCUITRY to monitor incoming AC Power for Power Failure and Restoration
and LINESYNC generation shall be provided.
2070.187 ACFAIL/POWER DOWN
The AC FAIL/POWER DOWN Output Lines shall go LOW (ground true) immediately upon
Power Failure. The Lines shall transition to HIGH within 50 ms after both Power
Restoration and supply fully recovered. The Lines shall be driven separately. The
SYSRESET/POWERUP Output Lines shall transition to LOW 525 +/-25 ms after
ACFAIL/POWER DOWN transition to LOW. The Lines shall transition to HIGH 225 +/-25
ms after Power Restoration and the supply is fully recovered. The Lines shall be driven
separately.
2070.188 Monitor Circuitry Switch
The monitor circuitry shall switch the +5 VDC Standby ON immediately upon Power
Failure and isolate (OFF) the line at Power Up.
2070.189 60 Hz Square Wave LINESYNC
The 60 Hz Square Wave LINESYNC signal shall be generated by a crystal oscillator, which
shall be synchronized to the 60-Hertz VAC incoming power line at 120 and 300 degrees. A
continuous square wave signal shall be +5 VDC amplitude, 8.333 ms half-cycle pulse
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A49 of 107
duration, and 50 +/-1% duty cycle. The output shall have drive sink capability of 16 mA. A
2 K-Ohm pull-up resistor shall be connected between the output and +5 VDC. The monitor
circuit shall compensate for missing pulses and line noise during normal operation.
2070.190 LINESYNC
The LINESYNC shall continue until SYSRESET transitions LOW and begin when
SYSRESET transitions HIGH.
Power Supply Requirements.
Voltage Minimum
Load
Maximum
Load
Load
Range
Line
Reg.
Ripple &
Noise
+5 VDC 0.0 Amp 10 Amp ±5% ±1% 50mV P-P
+12 VDC Serial 0.0 Amp 0.5 Amp ±5% ±1% 50mV P
-12 VDC Serial 0.0 Amp 0.5 Amp ±5% ±1% 50mV P
+12 VDC 0.0 Amp 1.0 Amp ±5% ±1% 50mV P
2070.191 Line/Load Regulation
The Power Supply Module shall meet Line / Load Regulation for input voltage range of 90
to 135 VAC, the maximum and minimum loads called out in the table and including ripple
noise.
2070.192 Efficiency
70% minimum.
2070.193 Ripple and Noise
Less than 0.2% rms, 1% peak to peak or 50 mV, whichever is greater.
2070.194 Voltage Overshoot
No greater than 5%, all outputs.
2070.195 Overvoltage Protection
130% V out for all outputs.
2070.196 Circuit Protection
Automatic recovery upon removal of fault.
2070.197 Inrush Current
Cold Start Inrush shall be less than 25 amperes at 115VAC.Transient Response. Output
voltage back to within 1% in less than 500 µs on a 50% Load change. Peak transient not to
exceed 5%.
2070.198 Holdup Time
The power supply shall supply 30 watts minimum for 550 ms after ACFAIL going LOW.
The supply shall be capable of holding up the Unit for two 500 ms Power Loss periods
occurring in a 1.5-second period.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A50 of 107
2070.199 Remote Sense
+5 VDC compensates 250 mV total line drop. Open sense load protection required.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A51 of 107
SECTION IX - UNIT CHASSIS TYPE 2070.
2070.200 General
The Chassis consists of the metal housing, Serial Motherboard, Back-plane Mounting
Surface, Power Supply Module Supports, slot card guides, Wiring Harnesses, and Cover
Plate(s). All external screws shall be countersunk and be Phillips flat head stainless steel
type. The housing shall be treated with clear chromate and the slot designation labeled on
the back-plane mounting surface above the upper slot card guide. The Chassis shall be
cooled by convection only. The top and bottom pieces of the housing shall be slotted for
vertical ventilation.
2070.201 Serial Motherboard
Serial Motherboard shall function as support for its connectors, A1 to A5 and FP, and as the
interface between the CPU and the dedicated modules/Front Panel carrying both serial
communications, logic, and power circuits. The PCB shall be multi-layered, with one layer
plane assigned to DC Ground. A wiring harness PS2 shall be provided between the Type
2070-4 Power Supply and the Motherboard PCB (provide strain relief). Test points shall be
provided on the FPA side of the Motherboard for PS2 lines. A wiring harness FP shall be
provided, linking the Motherboard with the FPA.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A52 of 107
SECTION X - TYPE 2070 NEMA
2070.202 ATC NEMA Standard Controller Units
This specification covers two versions of 2070 / NEMA Standard Controller Units. The
versions associate with NEMA TS1/TS2 Type 2 and NEMA TS2 Type 1 Standards. They
are as follows:
Model 2070 N1 Controller Unit (TS1/TS2 Type 2)
Model 2070 N2 Controller Unit (TS2 Type-1)
2070.203 N1C Unit Consisting
The Model 2070 N1C Controller Unit consists of:
Unit Chassis
2070- 1C CPU Module
2070-2B Field I/O Module
2070-3D Front Panel Module
2070-4NA Power Supply Module
2070-8 Field I/O Module
Optional communication modules
2070.204 N2C Unit Consisting
Unit Chassis
2070-1C CPU Module
2070-2N Field I/O Module
2070-3B Front Panel Module
2070-4AN Power Supply Module
2070.205 Address
The Serial Port 5 Frame Address for 2070-2N and 2070-8 shall be “20”.
FIELD I/O MODULE
2070.206 2070-2N Field I/O Module
The 2070-2N Field I/O Module provides a TS2 Type 1 compatible SDLC interface via 2070
Serial Port 3, AC Power to the 2070 Unit and Fault Monitor LOGIC Output via SP5 on
output O78 (similar to the 2070-8) to the NEMA TS2 Malfunction Management Unit
(MMU). The communications timeout operation shall function in a manner similar to the
2070-8 (see sections 11.4.11.6 and 11.4.11.7 for details)
2070.207 Requirements Exceptions
The Module shall meet the 2070–2A Module Requirements with the following exceptions:
No C1, C11 and C12 Connectors on the front panel of the module
No 64 inputs / 64 outputs requirements
Serial Port 5 routed to the FCU MPU Device only
Serial Port 3 shall not have a disabling switch
No Watchdog output
No Muzzle Shunt
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A53 of 107
2070.208 Types
The module shall be a 4X type board/front panel with three connectors. The connectors are
10 Pin Connector A, a NEMA 5-15 Receptacle and a Port 1 DA-15S connector labeled as
either “C15S” or “Port 1”. The Port 1 (C15S) connector shall be a 15 pin metal shell DA-15
connector with female contacts. The connector shall be equipped with latching blocks and
shall intermate with a 15 pin D type connector, Amp Incorporated part number 205206-1, or
equivalent, which is equipped with spring latches, Amp Incorporated part number 745012-1,
or equivalent.
2070.209 Power
Incoming 2070 AC Power is derived from Connector A Pin C (AC+), Pin A (AC-), and Pin
H (Equipment Ground). The power is directly routed to the NEMA 5-15 Receptacle with
equipment ground also connected to the face plate. Connector A shall intermate with a
NEMA TS2 Type 1 (MS3106( )-18-1S) cable.
2070.210 Isolation
The module shall isolate 2070 Serial Port 3 from the A3 Connector and reconvert the lines to
external EIA 485 drivers/receivers which shall be terminated at C15S Connector. The Port
shall be clocked at 153.6 Kbps.
2070.211 FCU Output
An FCU output shall drive an open collector transistor whose output shall be routed to
Connector A Pin F for use as a FAULT MONITOR Output. The transistor shall be capable
of sinking 200 mA at 30 VDC.
2070.212 Connectors A, C15S pin out and functions
Connectors A and C15S pin out and functions are as follows:
CONNECTOR A
Pin Function Pin Function Pin Function
A. AC Neutral E NA I NA
B. NA F Fault Monitor J NA
C. AC Line G DCG #2
D. NA H EG (Equip Ground)
CONNECTOR C15S:
Pin Function Pin Function Pin Function
1 SP3TXD+ 6 DCG #2 11 SP3TXC-
2 DCG #2 7 SP3RXC+ 12 EG (Equip Ground)
3 SP3TXC+ 8 DCG #2 13 SP3RXD-
4 DCG #2 9 SP3TXD- 14 NA
5 SP3RXD+ 10 Port 1 Disable 15 SP3RXC-
2070.213 Serial Port 3
Serial Port 3 shall control the TS2 BIU Units using SDLC Protocol that meets the NEMA
TS2 Type 1 Frame Command / Response Standards. SP3DCD shall be allocated to Port 1
Disable where 0 VDC input on C15S pin 10 equals DCD inactive (False). SP3DCD shall be
opto-isolated from Port 1 Disable.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A54 of 107
4AN POWER SUPPLY MODULE
2070.214 4AN POWER SUPPLY MODULE
The 2070-4N Power Supply Module supports the NEMA TS 1 and TS2 Standards. The
module is identical to the 2070-4A Power Supply Requirements except for the following:
The power cord shall have a 15 inch ± 1 inch length as measured from the panel to
the plug tips.
The AC Power Fail voltage shall be 85VAC ±2VAC.
The AC Power Restore voltage shall be 90VAC ±2VAC.
The 2070-4N (A) power supply shall have proper marking Example “2070 4N (A )”.
A permanent sticker shall be an acceptable marking method.
MODEL 2070- 8 FIELD I/O MODULE
2070.215 2070-9 Module
The Module shall consist of the Module Chassis, Module Power Supply, FCU Controller,
Parallel Input/Output Ports, Serial Communications Circuits and Module Connectors. The
Module CHASSIS shall be made of 0.06 in. minimum aluminum sheet and treated with clear
chromate. All external screws, except where called out, shall be countersunk and shall be
Phillips flat head stainless steel. The matching nuts shall be permanently captive on the
mating surfaces.
2070.216 Module Front Panel
The Module Front Panel shall be furnished with the following:
1. ON/OFF POWER Switch mounted vertically with ON in the UP position.
2. LED DC Power Indicator. The indicator shall indicate that the required + 5 VDC is
within 3% and the +24 VDC is within 8%.
3. Incoming VAC fuse protection.
4. Two DB-25S COMM connectors labeled "EX1" & "EX2."
5. Four NEMA Connectors A, B, C, & D.
2070.217 Label
A permanent Label shall be affixed to the Front Panel. The label shall display the unit's serial
number. The number shall be permanent and easy to read.
2070.218 Module Power Supply
A Module Power Supply shall be provided and located on the right side of the module as
viewed from the front. The supply shall provide the necessary module internal circuitry DC
power plus 2.0 Amperes minimum of +24 VDC for external logic, detector inputs, and
output load control. The supply shall meet the following requirements:
Input Protection. Two 0.5-Ohm, 10-watt wire-wound power resistors with a 0.2 µH
inductance (one on the AC+ Line & on the AC- Line) shall be provided. Three 20 Joule
surge arrestors between AC+ to AC-, AC+ to EG, and AC- to EG shall be provided. A 0.68
µF capacitor shall be placed between AC+ & AC- (between the resistor & arrestors).
Power Supply Requirements The Power Supply shall meet the specification as listed in
Power Requirements 2070-162 through 2070-171 Supply Requirements except Input
Protection above.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A55 of 107
Tolerances. DC Voltage tolerances shall be ±3% for 5 VDC and ±8% for 24 VDC.
2070.219 Incoming AC Power
The supplied Incoming AC Power shall be derived from Connector A Pins "p" (AC+) and
"U" (AC Neutral). External +24 VDC shall be at Connector A, Pin "B" and Connector D Pin
"NN." AC Power for the 2070 receptacle shall be tapped off from the secondary side of the
ON Switch / Fuse configuration.
2070.220 Module PC Boards
All Module PC Boards shall be mounted vertically.
2070.221 POWERDOWN, NRESET, and LINESYNC
POWERDOWN, NRESET, and LINESYNC are incoming EIA-485 differential signals and
shall be routed to the module via C12S Connector. The state of the module output ports at
the time of POWERDOWN transition to LOW State and until NRESET goes HIGH shall be
an open circuit.
2070.222 Requirements
The Module shall meet all requirements under SECTION V – TYPE 2070-2 FIELD I/O
MODULE with the following exceptions:
Parallel Ports 118 Bits of Input and 102 bits of Output shall be provided. Specification for
inputs applies except the voltage is +24 in lieu of +12, Ground False ("0") exceeds 16.0
VDC, and Ground True (“1”) is less than 8.0 VDC.
Serial Communication Circuitry The module shall interface with the 2070-2B Field I/O
module via HAR 1 Harness meeting EIA-485 Requirements. HAR 1 Harness shall be 23
lines minimum with a C12P Connector on one end and soldered with strain relief on the
other. In addition to SP5 being routed to the FCU Controller interface, the SP3 EIA-485
Signal lines shall be routed only to the EX1 Connector.
2070.223 EIA-232 Serial Port
An EIA-232 Serial Port on the FCU shall be provided with baud rate selection by Shunt of
0.3, 1.2, 2.4, 4.8, 9.6, 19.2, & 38.4 Kbps asynchronous and shall be connected at EX1
Connector. This hardware is provided for future expansion capability and its use/protocol is
currently undefined.
2070.224 HAR 2 Harness
A 22-line minimum HAR 2 Harness shall be provided between EX2 Connector and Model
2070-6 Serial COMM Module in the 2070 UNIT. This provides two Modems or EIA-232
Interfaces between the 2070 UNIT and the outside world. The two EG (Equipment Ground)
lines within HAR 2 shall be connected between EX2 and the 2070-8 module chassis.
2070.225 Fault and Voltage Monitor Circuitry
NEMA TS1 Controller Fault and Voltage Monitor functions (outputs to cabinet monitor)
shall be provided.
OR Gates. Conceptually, two 3-input OR gates shall be provided. The gate 1 output shall be
connected to Connector A, Pin A (Fault Monitor) and gate 2 output shall be connected to
Connector A, Pin C. Any False state input shall cause a gate output False (+24VDC) state.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A56 of 107
FCU Output O78. The FCU output O78 shall normally change its state every 100 ms. A
module Watchdog circuit shall monitor the output. No state change for 2 ±0.1 seconds shall
cause the circuit output to generate a FALSE (+24 VDC) output (input to gates 1 and 2).
Should the FCU begin changing state, the Watchdog output shall return to TRUE (0 VDC)
state.
Operation. The module shall have a +5 VDC monitoring circuit which monitors the
module’s +5 VDC (±0.25). If the voltage exceeds the limits, the circuit output shall generate
a False output (input to gates 1 and 2). Normal operation shall return the output state to
TRUE state.
Microprocessor Output. The FCU microprocessor output shall be assigned to FAULT
Monitor (input to gate 1) and another output shall be assigned to VOLTAGE Monitor (input
to gate 2).
Message Outputs. CPU Port 5 Set Output Command Message Outputs O78 and O79 shall
be assigned to FAULT (O78) and VOLTAGE (O79). The bit logic state “1” shall be FCU
output FALSE.
CPU / FCU Operations. CPU / FCU operation at POWER UP shall be as follows:
1. FCU Comm Loss Flag set. FAULT and VOLTAGE MONITOR outputs set to
FALSE state.
2. CPU REQUEST MODULE STATUS COMMAND Message with “E” bit set is sent
to FCU to clear Comm Loss Flag and FCU responds to CPU with “E” bit reset.
3. Before the Comm Loss timer expires, the SET OUTPUT COMMAND data must be
sent. In that data, the 078 and 079 logically set to “0” will cause the FCU
microprocessor port pins assigned for FM and VM outputs to go to their TRUE
state. At this point, the signal outputs defined in the message will be permitted at the
output connectors. Any number of other messages may be sent between the
MODULE STATUS COMMAND and SET OUTPUTS COMMAND.
4. * If the above message sequence is not followed, Comm Loss Flag shall be set (or
remain) and VM & FM shall retain the FALSE output state.
5. Performs items 2 & 3 above User Software.
CPU/FCU Communications. A CPU / FCU Communications Loss during normal operation
shall cause all outputs to go blank (FALSE state) and shall set the Comm. Loss Flag. FM and
VM outputs shall be in FALSE state.
2070.226 Figures
The following figures are found in Appendix B:
Front View A11-1
Side View A11-2
ISO View A11-3
Field I/O Module, Connector A & B A11-4
Field I/O Module, Connector C & D A11-5
Field I/O Module, EX1 & EX2 Connectors A11-6
2070-2N Field I/O Module A11-7
*Notes: Module sheet metal tolerance shall be 0.015 inch or less.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A57 of 107
SECTION XI - TYPE 2070 PERIPHERAL EQUIPMENT.
2070.227 General Notes
The 2070-6x and 2070-7x modules shall provide circuitry to disable its Channel 2 and EIA-
232 control lines (TX, RX, RTS, CTS, and DCD) when a ground true state is present at
Connector A1, Pin B21 (C50 Enable). C50 Enable shall disable Channel 2 via disabling the
RS-485 signals to and from the motherboard. The disable lines shall be pulled up on these
modules.
Line drivers/receivers shall be socket mounted or surface mounted.
Isolation circuitry shall be opto- or capacitive-coupled isolation technologies. Each
module’s circuit shall be capable of reliably passing a minimum of 1.0 megabits per second.
EIA-485 drivers to the external connectors must be capable of supporting either two times
the maximum applicable baud rate for the port or 1 Mbps, whichever is less. EIA-232
drivers to the external connectors must be capable of supporting a minimum of 115,200 bits
per second.
The Communication modules shall be “Hot” swappable without damage to circuitry or
operations. A communication “glitch” occurring during insertion/removal is acceptable sine
the application program shall be able to recover/retry. Power-on and hot-swap current
surges shall not exceed a 10 ms surge at three times (3x) the maximum rating of each voltage
supply used by the module.
2070.228 Type 2070-6 A & B Async/ Modem Serial Communication Modules
Fuse Isolation. A fused isolated +5 VDC with a minimum of 100 mA power supply shall be
provided for external use.
Option – Bourns MF – MSMD020 PTC (Positive Temperature Coefficient) Resettable
Fuse, or approved equal, allowed.
Logic Switches. Two LOGIC switches per circuit shall be provided (faceplate mounted).
One logic switch shall be used to vertically switch between Half-Duplex (Down) and Full-
Duplex (Up). In Half-Duplex mode, the Transmit connections shall be used for both
Receive and Transmit. A MODEM Enable switch shall be provided such that when in the
UP Position shall enable MODEM and disable MODEM in the DOWN Position.
Circuitry. Two independent circuits, designated CIRCUIT #1 and CIRCUIT #2, shall be
provided. Both circuit functions shall be identical, except for their Serial Communications
Port and external connector (CIRCUIT #1 to SP1 [or SP3] and C2S Connector and
CIRCUIT #2 to SP2 [or SP4] and C20S Connector). Circuits #1 and Circuits #2, shall
optically isolate the FSK, C2 and C20 Serial Ports from the Motherboard SP EIA-495
signals. Each circuit shall provide full isolation from each other and the Model 2070
Motherboard.
Modem Requirements. Each CIRCUIT shall have a common power independent MODEM
with the following requirements:
Data Rate: Baud modulation of 300 to 1200 for Module 2070-6A and 0 to 9600 for
Module 2070-6B.
Modulation: Phase coherent frequency shift keying (FSK).
Data Format: Asynchronous, serial by bit.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A58 of 107
Line & Signal Requirements: Type 3002 voice-grade, unconditioned Tone Carrier
Frequencies (Transmit and Receive): MARK and SPACE: ±1% tolerance. The operating
band shall be (half power, -3 dB) between 1.0 KHz & 2.4 KHz for 2070-6A and 9.9 KHz &
18.9 KHz for 2070-6B.
Transmitting Output Signal Level: 0, -2, -4, -6, and -8 dB (at 1.7 KHz for 2070-6A & 14.7
KHz for 2070-6B) continuous or switch selectable.
Receiver Input Sensitivity: 0 to -40 dB.
Receiver Bandpass Filter: Shall meet the error rate requirement specified below and
provide 20 dB/octave, minimum active attenuation for all frequencies outside the operating
band.
Clear-to-Send (CTS) Delay: 11 +/-3 milliseconds.
Receive Line Signal Detect Time: 8 +/-2 milliseconds mark frequency.
Receive Line Squelch: 6.5 (+/-1) milliseconds, 0 milliseconds (OUT).
Soft Carrier Turn Off Time: 10 +/-2 milliseconds (0.9 kilohertz for 2070-6A and 7.8
kilohertz for 2070-6B). When the RTS is unasserted, the carrier shall turn off or go to soft
carrier frequency.
Modem Recovery Time: Capable of receiving data within 22 milliseconds after completion
of transmission.
Error Rate: Shall not exceed 1 bit in 100 kilobits, with a signal-to-noise ratio of 16 dB
measured with flat-weight over a 300 to 3,000 Hertz band.
Transmit Noise: Less than -50 dB across 600-ohms resistive load within the frequency
spectrum of 300 to 3,000 Hertz at maximum output.
Modem interface: EIA-232 Standards.
Control Switch: A CONTROL switch shall be provided on the module front panel to turn
ON (Up) / OFF (Down) all module power.
2070.229 Type 2070-7A Async Serial Comm Module
Circuitry. Two opto-isolated independent circuits, designated CIRCUIT #1 (Channel 1) and
CIRCUIT #2 (Channel 2), shall be provided. Their functions are identical, except for the
CPU Serial Communications Port and external connector (CIRCUIT #1 to SP1 [or SP3] and
Connector C21S and CIRCUIT #2 to SP2 [or SP4] and Connector C22S).
2070-7A. Each circuit shall convert its EIA-485 signal lines (RX, TX, RTS, CTS and DCD)
to / from board TTL Level Signals; isolate both signal and ground; and drive / receive
external EIA-232 devices via C21 / C22 Connectors. Connectors shall be DB-9S type.
LED Indicator. Each circuit signal TX and RX line shall have an LED Indicator mounted
on the front plate and labeled to function.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A59 of 107
SECTION XII – GLOSSARY
2070.230 Terms and Abbreviations
Wherever the following terms or abbreviations are used, the intent and meaning is
interpreted as follows:
A Ampere
AC Alternating Current
AC+ 120 Volts AC, 60 hertz ungrounded power source
AC- 120 Volts AC, 60 hertz grounded return to the power source
ANSI American National Standard Institute
ASCII American Standard Code for Information Interchange
Assembly A complete machine, structure or unit of a machine that was manufactured
by fitting together parts and/or modules
ASTM American Society for Testing and Materials
AWG American Wire Gage
C Celsius
C Language The ANSI C Programming Language
Cabinet An outdoor enclosure generally housing the controller unit and associated
equipment
Certificate of Compliance A certificate signed by the manufacturer of the material
or the manufacturer of assembled materials stating that the materials
involved comply in all respects with the requirements of the specifications
Channel An information path from a discrete input to a discrete output.
Component Any electrical or electronic device
Contractor The person or persons, Manufacturer, firm, partnership, corporation, vendor
or combination thereof, who have entered into a contract with the
DEPARTMENT, as party of the second part or legal representative
Controller Unit That portion of the controller assembly devoted to the operational
control of the logic decisions programmed into the assembly
CPU Central Processing Unit
CTS Clear To Send
DAT Program The DEPARTMENT’s Diagnostic and Acceptance Test Program
dB Decibel
dBa Decibels above reference noise, adjusted
DC Direct Current
DCD Data Carrier Detect (Receive Line Signal Detector)
DIN Deutsche Industry Norm
DRAM Dynamic random access memory. Random access means that the processor
can access any part of the memory or data storage space directly rather than
having to proceed sequentially from some starting place. DRAM is dynamic
in that it needs to have its storage cells refreshed or given a new electronic
charge every few milliseconds.
EG Equipment Ground
EIA Electronic Industries Association
EMI Electro Magnetic Interference
EPROM Ultraviolet Erasable, Programmable, Read Only Memory Device
EEPROM Electrically Erasable, Programmable, Read Only Memory Device
Equal Connectors: comply with physical dimensions, contact material, plating and
method of connection. Devices: comply to function, pin out, electrical and
operating parameter requirements, access times and interface parameters of
the specified device
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A60 of 107
ETL Electrical Testing Laboratories, Inc.
Firmware A computer program or software stored permanently in PROM, EPROM,
ROM or semi-permanently in EEPROM
FLASH A +5 VDC powered IC Memory Device with nonvolatile, electrically
erasable, programmable, 100K read/write minimum cycles and fast access
time features
FPA Front Panel Assembly
HEX Hexadecimal
Hz Hertz
IC Integrated Circuit
I.D. Identification
IEEE Institute of Electrical and Electronics Engineers
ISO Isolated
Jumper A means of connecting/disconnecting two or more conductive by
soldering/desoldering a conductive wire or by PCB post jumper
KB Kilobytes
Keyed Means by which like connectors can be physically altered to prevent
improper insertion.
Laboratory The established laboratory of the DEPARTMENT or other laboratories
authorized by the DEPARTMENT to test materials involved in the contract
LCD Liquid Crystal Display
LED Light Emitting Diode
LOGIC Negative Logic Convention (Ground True) State
LSB Least Significant Byte
lsb Least Significant Bit
MB megabyte
MSB Most Significant Byte
msb Most Significant Bit
m Milli
MCU/MPU/ IMP Micro Controller Unit, Microprocessor Unit, or Integrated
Multiprotocol Processor
MIL Military Specifications
MODEM Modulation/Demodulation Unit
Module A functional unit that plugs into an assembly
Motherboard A printed circuit connector interface board with no active or passive
components
MOS Metal-Oxide Semiconductor
MOV Metal-Oxide Varistor
MS Military Standards
N Newton: SI unit of force
N.C. Normally closed contact
N.O. Normally open contact
NA Presently Not Assigned. Cannot be used by the Manufacturer for other
purposes
NEMA National Electrical Manufacturer's Association
NETA National Electrical Testing Association, Inc.
n nano
NLSB Next Least Significant Byte
nlsb Next Least Significant Bit
NMSB Next Most Significant Byte
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A61 of 107
nmsb Next Most Significant Bit
PCB Printed Circuit Board
PDA Power Distribution Assembly
PLA/PAL Programmable Array Logic Device
Power Failure A Power Failure is said to have occurred when the incoming line voltage
falls below 92 +/- 2 VAC for 50 milliseconds. See Power Conditions.
Power Restoration Power is said to be restored when the incoming line voltage equals or
exceeds 97 +/- 2 VAC for 50 milliseconds. See Power Conditions.
Power Conditions 16.7 ms (one 60 Hertz cycle) reaction period is allowed to be included
in the 50 milliseconds timing or added to (67 milliseconds duration). The
hysteresis between power failure and power restoration voltage settings
shall be a min. of 5 VAC with a threshold drift of no more than 0.2 VAC.
ppm Parts per million
PWM Pulse Width Modulation
RAM Random Access Memory
RF Radio Frequency
RMS Root-Mean-Square
ROM Read Only Memory Device
RTS Request to Send
R/W Controller Unit Read/Write Control Line
RxD Received Data
SCI Serial Communications Interface
SDLC Synchronous Data Link Control
S Logic State
s second
Second Sourced Produced by more than one Manufacturer
SRAM Static Random Access Memory Device
SW Switch
TB Terminal Block
TOD Time Of Day Clock
Triac Silicon-Controlled Rectifier which controls power bilaterally in an AC
switching circuit
TTL Transistor-Transistor Logic
Thumb Screw Device (TSD ) A retractable screw fastener with projecting stainless steel
screw, spring and natural aluminum knob finish. (TSD No.2 shall be flat
black.)
TSD No.1 - 8-32 SOUTHCO #47-62-301-20 or equal.
TSD No.2 - 8-32 SOUTHCO #47-62-301-60 or equal.
TSD No.3 - M3 SOUTHCO #47-82-101-10 or equal.
TxD Transmitted Data
u Micro
UL Underwriter's Laboratories, Inc.
VAC Voltage Alternating Current (root mean square)
VDC Voltage Direct Current
VME Versa Module Eurocard, VMEbus Standard IEEE P1014/D1.2
x Number Value
XX Manufacturer's Option
WDT Watchdog Timer: A monitoring circuit, external to the device watched,
which senses an Output Line from the device and reacts
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A62 of 107
APPENDIX A
ELECTRICAL, ENVIRONMENTAL AND TESTING
REQUIREMENTS
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A63 of 107
APPENDIX A – ELECTRICAL ENVIRONMENTAL AND TESTING
REQUIREMENTS
A1 ENVIORNMENTAL AND TEST PROCEDURES
General A1.1
This section establishes the limits of the environmental and operational conditions in which the
first article ATC Controller Unit (CU) will perform. This section also defines the minimum test
procedures which may be used to demonstrate conformance of a CU with the provisions of the
specification.
Testing Software A1.2
Software shall be provided that contains a set of test programs to facilitate testing. This software
shall be capable of running individual tests or combinational tests. The combinational tests shall
include a single menu function that binds all of the tests into a single module. Tests may be run
either from the front panel or by an external serial port. These tests shall include but are not
limited to the items in the following outline:
A testing program shall contain the following:
1. Introduction to the Test
2. Installation Instructions
3. Starting the Software
4. Running Individual Tests
5. Test Suite Tree for combination tests
Individual Processor tests shall include:
1. DRAM Test
2. SRAM Test
3. FLASH Read/Write Test
4. Datakey Tests
5. USB Tests.
6. Ethernet Tests
Front Panel (when used) tests shall include:
1. Display Tests
2. Keyboard Tests.
I/O tests shall include:
1. I/O Loop Back Tests.
Asynchronous/Synchronous Communication Port tests shall include:
1. Loop Back Tests, Single Port and Port to Port.
2. Aggregate throughput tests as defined in Paragraph A1.3
Utility Function Tests:
Time of Day Functions
1. Display Time of Day (TOD) Clock
2. Set Time of Day (TOD) Clock
3. Enable Daylight Savings Time
4. Disable Daylight Savings Time
5. Line frequency tests
6. Clock accuracy tests
Ethernet Functions
1. Get Current IP Address
2. Set Current IP Address
3. Load IP Address from Datakey
4. Save IP Address from Datakey
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A64 of 107
5. Start Ethernet
Clear Error Log
Configure Continuous Tests
Start Application
Testing shall be performed either within an environmental chamber or on a bench. The controller
unit is not required to be installed within a cabinet during these tests.
These test procedures do not verify equipment performance under every possible combination of
environmental requirements covered by this standard. However, nothing in this testing profile
shall be construed as to relieve the requirement that the equipment provided must fully comply
with these standards/specifications under all environmental conditions stated herein.
Communication Loading Test. The communication channel loads for load testing A1.3
purposes, with no other activity present, shall be the following:
SP1, SP2, & SP8 = Continuous full-duplex, asynchronous communications at
19.2Kbps
SP4 & SP6 = Continuous full-duplex, asynchronous communications at 38.4Kbps
SP3S = Continuous full-duplex, synchronous communications at 153.6Kbps
SP5S = Continuous full-duplex synchronous communications at 614.4Kbps
All Ethernet Ports: At 10 percent loading, with 3 percent average hits to processor per
minute
No other applications or I/O activities are required to be operational during this test.
A2 Inspection
A visual and physical inspection of the CU shall verify mechanical, dimensional and assembly
conformance to all parts of this standard.
A3 Definitions of Design Acceptance Testing (DAT) and Production Testing.
Design Acceptance Testing (DAT) is performed on the first article ATC CU and is a part of the
pre-production process.
Production testing is performed on all units prior to their shipment to an agency.
A4 Environmental and Operating Requirements
The requirements (voltage, temperature, etc.) of this section shall apply in any combination.
Voltage and Frequency A4.1
1. Operating Voltage. The nominal voltage shall be 120 VAC, unless otherwise noted.
2. Operating Frequency. The operating frequency range shall be 60 hertz (+/-3.0
hertz), unless otherwise noted.
Temperature and Humidity. The Test Unit shall maintain all programmed functions A4.2
when the temperature and humidity ambient are within the specified limits defined
herein.
1. Ambient Temperature.
The operating ambient temperature range shall be from -37 degrees C to +74 degrees
C. The storage temperature range shall be from -45 degrees C to +85 degrees C.
The rate of change in ambient temperature shall not exceed 18 degrees C per hour,
during which the relative humidity shall not exceed 95 percent.
2. Humidity.
The relative humidity shall not exceed 95 percent non-condensing over the
temperature range of -37 degrees C to +74 degrees C.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A65 of 107
Above +46 degrees C, constant absolute humidity shall be maintained. This will
result in the relative humidity shown in Exhibit 3-1 for dynamic testing.
Table 1 AMBIENT TEMPERATURE VERSUS RELATIVE HUMIDITYAT
BAROMETRIC PRESSURES (29.92 In. Hg.) (NON-CONDENSING)
Ambient Temperature/
Dry Bulb (in degrees C)
Relative Humidity
(in percent)
Ambient Temperature/
Wet Bulb (in degrees C)
-37.0 to 1.1 10 -17.2 to 42.7
1.1 to 46.0 95 42.7
48.8 70 42.7
54.4 50 42.7
60.0 38 42.7
65.4 28 42.7
71.2 21 42.7
74.0 18 42.7
A5 Transients, Power Service.
The Test Unit shall maintain all defined functions when the independent test pulse levels
specified below occur on the alternating-current power service.
1. High-Repetition Noise Transients. The test pulses shall not exceed the following
conditions:
Amplitude: 300 Volts, both positive and negative polarity.
Peak Power: 2500 watts.
Repetition: 1 pulse approximately every other cycle moving uniformly over the full wave
in order to sweep across 360 degrees of the line cycle once every 3 seconds.
Pulse Rise Time: 1 microsecond.
Pulse Width: 10 microseconds.
This test is performed without protection in place or operational.
This test is considered to be a minimum test requirement for the Test Unit complying
with ANSI/IEEE C62.41. Regional conditions may warrant additional testing as
described in ANSI/IEEE C62.41. (Authorized Engineering Information)
2. Low Repetition High Energy Transients. The test pulses shall not exceed the following
conditions:
Amplitude: 600 Volts (+/-5 percent), both positive and negative polarity.
Energy Source: Capacitor, oil filled, 10 microfarads (+/-10 percent), internal surge
impedance less than 1 ohm.
Repetition: 1 discharge every 10 seconds.
Pulse Position: Random across 360 degrees of the line cycle.
This test is performed with protection in place and operational.
This test is considered to be a minimum test requirement for the Test Unit complying
with ANSI/IEEE C62.41. Regional conditions may warrant additional testing as
described in ANSI/IEEE C62.41. (Authorized Engineering Information)
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A66 of 107
A6 Nondestructive Transient Immunity.
The Test Unit (with protection in place and operational) shall be capable of withstanding a high
energy transient having the following characteristics repeatedly applied to the alternating current
input terminals (no other power connected to terminals) without failure of the test unit:
Amplitude: 2000 Volts (+/-5 percent), both positive and negative polarity.
Energy Source: Capacitor, oil filled, 15 microfarads (+/-10 percent), internal surge
impedance less than 1 ohm.
Repetition: Applied to the Test Unit once every 2 seconds for a maximum of three
applications for each polarity.
After the foregoing, the Test Unit shall perform all defined functions upon the
application of nominal alternating current power.
This test is considered to be a minimum test requirement for the Test Unit complying
with ANSI/IEEE C62.41 (100 Kilohertz Ring Wave, the 1.2/50 microseconds – 8/20
Combination Wave and the EFT Burst) at voltages and currents specified at “Location
Category B2” and at “Test Severity” level III (i.e. up to 4.0 Kilovolts, open-circuit).
Regional conditions may warrant additional testing as described in ANSI/IEEE C62.41.
(Authorized Engineering Information).
TEST FACILITIES
A7 Test Facilities
All instrumentation required in the test procedures, such as voltmeters, ammeters, thermocouples,
pulse timers, etc. shall be selected in accordance with good engineering practice. In all cases
where time limit tests are required, the allowance for any instrumentation errors shall be included
in the limit test.
Variable Voltage Source: A variable source capable of supplying 20 amperes from 100 VAC
to 135 VAC.
Environmental Chamber: An environmental chamber capable of attaining temperatures of -37
degrees C to +74 degrees C and relative humidity given in Table 1.
Transient Generators: Transient generators capable of supplying the transients outlined
above.
TEST PROCEDURE: TRANSIENTS, TEMPERATURE, VOLTAGE, AND HUMIDITY
A8 Test A: Placement in Environmental Chamber and Check-Out of Hook-Up
1. Place the test unit in the environmental chamber. Connect the test unit AC input circuit to a
variable voltage power transformer, voltmeter, and transient generator. The transient
generator shall be connected to the AC input circuit at a point at least 25 feet from the AC
power source and not over 10 feet from the input to the test unit.
2. Connect test switches to the appropriate terminals to simulate the various features
incorporated into the test unit. Place these switches in the proper position for desired
operation.
3. Verify the test hook-up. Adjust the variable-voltage power transformer to 120 VAC and
apply power to the test unit. Verify that the test unit goes through its prescribed startup
sequence and cycles properly in accordance with the operation determined by the positioning
of test switches.
Upon the satisfactory completion and verification of the test hook-up, proceed with Test B.
A9 Test B: Transient Tests (Power Service)
1. Program the test unit to dwell. Verify the input voltage is 120 VAC.
2. Set the transient generator to provide high-repetition noise transients as follows:
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A67 of 107
Amplitude: 300 Volts (+/-5 percent), both positive and negative polarity.
Peak Power: 2500 watts.
Repetition Rate: One pulse every other cycle moving uniformly over the full wave in
order to sweep once every 3 seconds across 360 degrees of line cycle.
Pulse Rise Time: 1 microsecond.
Pulse Width: 10 microseconds.
3. Apply the transient generator output to the AC voltage input for at least 5 minutes. Repeat
this test for at least two conditions of dwell for the test unit. The test unit shall continue to
dwell without malfunction.
4. Program the test unit to cycle through normal operations. Turn on the transient generator
(output in accordance with item 2) for 10 minutes, during which time the test unit shall
continue to cycle without malfunction.
5. Set a transient generator to provide high-repetition noise transients as follows:
Amplitude: 300 Volts (+/-5 percent), both positive and negative polarity.
Source Impedance: Not less than 1000 ohms nominal impedance.
Repetition: One pulse per second for a minimum of five pulses per selected terminal.
Pulse Rise Time: 1 microsecond.
Pulse Width: 10 microseconds.
Program the test unit to dwell. Verify the input voltage is 120 VAC.
6. Apply the transient generator (output in accordance with item 5) between logic ground and
the connecting cable termination of selected Field I/O input/output terminals of the test unit.
A representative sampling of selected input/output terminations shall be tested. The test unit
shall continue to dwell without malfunction.
7. Program the test unit to cycle. Turn on the transient generator (output in accordance with
item 5) and apply its output to the selected Field I/O input/output terminations. The test unit
shall continue to cycle without malfunction.
8. Reinstall protection and set a transient generator to provide low-repetition high-energy
transients as follows:
Amplitude: 600 Volts (+/-5 percent), both positive and negative polarity.
Energy Discharge Source: Capacitor, oil-filled, 10 microfarads.
Repetition Rate: One discharge each 10 seconds.
Pulse Position: Random across 360 degrees of line cycle.
9. Program the test unit to dwell. Verify the input voltage is 120 VAC.
10. Discharge the oil-filled 10-microfarad capacitor ten times for each polarity across the AC
voltage input. Repeat this test for at least two conditions of dwell. The test unit shall
continue to dwell without malfunction.
11. Program the test unit to cycle through normal operations. Discharge the capacitor ten times
for each polarity while the test unit is cycling, during which time the test unit shall continue
to cycle without malfunction.
12. During the preceding transient tests, the test unit shall continue its programmed functions.
The test unit shall not skip normal program intervals/steps or portions thereof when in
normal operation; place false inputs or produce false outputs while in dwell; disrupt normal
sequences in any manner; or change parameters.
13. Nondestructive Transient Immunity:
Turn off the AC power input to the test unit from the variable-voltage power source.
Apply the following high-energy transient to the AC voltage input terminals of the test
unit (no other power connected to terminals):
o Amplitude: 2000 +- 100V, both positive and negative polarity.
o Peak Power Discharge: Capacitor, oil-filled, 15 microfarads.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A68 of 107
o Maximum Repetition Rate: Applied to the Cabinet Assembly once every 2 seconds
for a maximum of three applications for each polarity.
Upon completion of the foregoing, apply 120 VAC to the test unit and verify that the test
unit goes through its prescribed startup sequence and cycles properly in accordance with
the programmed functions. The first operation of the over-current protective device
during this test is not considered a failure of the test unit.
NOTE—Tests C through G follow the profile indicated in Figure A1 to demonstrate the
ability of the test unit to function reliably under stated conditions of temperature, voltage, and
humidity.
Figure A1 – Test Profile
NOTES:
1. The rate of change in temperature shall not exceed 18 degrees C per hour
2. Humidity controls shall be set in conformance with the humidity given in Table 1 during
the temperature change between Test D and Test E.
3. If a change in both voltage and temperature are required for the next test, the voltage
shall be selected prior to the temperature change.
A10 Test C—Low-Temperature Low-Voltage Tests
1. Definition of Test Conditions
40
30
10
20
0
10
70
60
50
40
30
20
80
DCA+B F GE
(AMBIENT)120 VAC120 VAC100 VAC135 VAC135 VAC100 VACTEMPERATURE, in DEGREES CELSIUSSEE NOTES
1 AND 3
SEE NOTES
1 AND 2
SEE NOTES
1 AND 3
X
XX
XX
X
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A69 of 107
Environmental Chamber Door: Closed.
Temperature: -37 degrees C.
Low Voltage: 100 VAC.
Humidity Control: Off.
2. Test Procedure: While at room temperature, adjust the input voltage to 100 VAC and verify
that the test unit is still operable.
With the test unit cycling through normal operations, lower the test chamber to -37
degrees C at a rate not exceeding 18 degrees C per hour. Allow the test unit to cycle for a
minimum of 5 hours at -37 degrees C with the humidity controls in the off position. Then
operate the test switches as necessary to determine that all functions are operable.
Remove power from the test unit for a minimum period of 5 hours. Upon restoration of
power, the test unit shall go through its prescribed startup sequence and then resume
cycling.
With the test unit at -37 degrees C and the input voltage at 100 VAC, evaluate the
following item against the respective standards:
o Power Interruption Tests
On satisfactory completion of this test, proceed with Test D.
A11 Test D—Low-Temperature High-Voltage Tests
1. Definition of Test Conditions
Environmental Chamber Door: closed.
Low Temperature: -37 degrees C.
High Voltage: 135 VAC.
Humidity Controls: Off.
2. Test Procedure: While at -37 degrees C and with humidity controls off, adjust the input
voltage to 135 VAC and allow the test unit to cycle for 1 hour. Then operate the test switches
as necessary to determine that all functions are operable.
3. With the test unit at -37 degrees C and the input voltage at 135 VAC (humidity controls off),
evaluate the following items against the respective standards:
Power Interruption Tests
On satisfactory completion of this test, proceed to Test E.
A12 Test E—High-Temperature High-Voltage Tests
1. Definition of Test Conditions
Environmental Chamber Door: Closed.
High Temperature: +74 degrees C.
High Voltage: 135 VAC.
Humidity Controls: In accordance with the humidity given in Table 1.
2. Test Procedure - With the test unit cycling, raise the test chamber to +74 degrees C at a rate
not to exceed 18 degrees C per hour. Verify the input voltage is 135 VAC.
3. Set the humidity controls to not exceed 95 percent relative humidity over the temperature
range of +1.1 degrees C to +46 degrees C. When the temperature reaches +46 degrees C,
readjust the humidity control to maintain constant absolute humidity; +42.7 degrees C wet
bulb that results in the relative humidity shown in Table A1. Verify that the test unit
continues to cycle satisfactory during the period of temperature increase and at established
levels of relative humidity.
Allow the test unit to cycle for a minimum of 15 hours at +74 degrees C and 18 percent
relative humidity. Then operate the test switches as necessary to determine that all
functions are operable.
With the test unit at +74 degrees C and 18 percent relative humidity and the input voltage
at 135 VAC, evaluate the following items against the respective standards:
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A70 of 107
o Section ____ - Power Interruption Tests
On satisfactory completion of this test, proceed to Test F.
A13 Test F—High-Temperature Low-Voltage Tests
1. Definition of Test Conditions
Environmental Chamber Door: Closed.
High Temperature: +74 degrees C.
Low Voltage: 100 VAC.
Humidity Controls: 18 percent relative humidity and +42.7 degrees C wet bulb.
2. Test Procedure: Adjust the input voltage to 100 VAC and proceed to operate the test switches
to determine that all functions are operable. With the test unit at +74 degrees C and 18
percent relative humidity, +42.7 degrees C wet bulb, and the input voltage at 100 VAC,
evaluate the following items against the respective standards:
Power Interruption Tests
On satisfactory completion of this test, proceed to Test G.
A14 Test G—Test Termination
1. Program the test unit to cycle.
2. Adjust the input voltage to 120 VAC.
3. Set the controls on the environmental chamber to return to room temperature, +20 degrees C
(+/-5 degrees C), with the humidity controls in the off position. The rate of temperature
change shall not exceed 18 degrees C per hour.
4. Verify the test unit continues to cycle through normal operations properly.
5. Allow the test unit to stabilize at room temperature for 1 hour. Proceed to operate the test
switches to determine that all functions are operable.
A15 Test H—Appraisal of Equipment under Test
1. A failure is defined as any occurrence that results in other than normal operation of the
equipment. (See sub-section item b. below for details.) If a failure occurs, the test unit shall
be repaired or components replaced, and the test during which failure occurred shall be
restarted from its beginning.
2. The test unit is considered to have failed if any of the following occur:
If the test unit skips normal program intervals/steps or portions thereof when in normal
operation, places false inputs, presents false outputs, exhibits disruption of normal
sequence of operations, or produces changes in parameters beyond specified tolerances,
or
If the test unit fails to satisfy the requirements of Tests A to G, inclusive.
3. An analysis of the failure shall be performed and corrective action taken before the test unit is
retested in accordance with this standard. The analysis shall outline what action was taken to
preclude additional failures during the tests.
4. When the number of failures exceeds two, it shall be considered that the test unit fails to meet
these standards. The test unit may be completely retested after analysis of the failure and
necessary repairs have been made in accordance with item c.
5. Upon completion of the tests, visually inspect the test unit. If material changes are observed
which will adversely affect the life of the test unit, the cause and conditions shall be corrected
before making further tests.
6. Upon satisfactory completion of all of the tests described, test the unit in accordance with the
Vibration Test.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A71 of 107
A16 Vibration Test
Purpose of Test A16.1
This test is intended to duplicate vibrations encountered by the test unit (individual major
components) when installed at its field location.
Fasten the test unit securely to the vibration test table prior to the start of the test.
Test Equipment Requirements. A16.2
1. Vibration table with adequate table surface area to permit placement of the test unit.
2. Vibration test consists of:
Vibration in each of three mutually perpendicular planes.
Adjustment of frequency of vibration over the range from 5 hertz to 30 hertz.
Adjustment of test table excursion (double amplitude displacement) to maintain a
‘g’ value, measured at the test table, of 0.5g; as determined by the following
formula:
g = 0.0511df2
Where:
d = excursion in inches
f = frequency in hertz
Resonant Search A16.3
1. With the test unit securely fastened to the test table, set the test table for a double
amplitude displacement of 0.015 inch.
2. Cycle the test table over a search range from 5 hertz to 30 hertz and back within a
period of 12.5 minutes.
3. Conduct the resonant frequency search in each of the three mutually perpendicular
planes.
4. Note and record the resonant frequency determined from each plane.
In the event of more than on resonant frequency in a given plane, record the most
severe resonance.
If resonant frequencies appear equally severe, record each resonant frequency.
If no resonant frequency occurs for a given plane within the prescribed range, 30
hertz shall be recorded.
Endurance Test A16.4
1. Vibrate the test unit in each plane at its resonant frequency for a period of 1 hour at
amplitude resulting in 0.5g acceleration.
2. When more than one resonant frequency has been recorded, the test period of 1 hour
shall be divided equally between the resonant frequencies.
3. The total time of the endurance test shall be limited to 3 hours, 1 hour in each of three
mutually perpendicular planes.
Disposition of Equipment under Test A16.5
1. Examine the test unit to determine that no physical damage has resulted from the
vibration tests.
2. Check the test unit to determine that it is functionally operable in all modes of its
prescribed operation.
3. The test unit may be removed from the test table. Upon satisfactory completion of
the vibration test, proceed with the shock (impact) test.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A72 of 107
A17 Shock (Impact) Test.
Purpose of Test A17.1
The purpose of this test is to determine that the test unit is capable of withstanding the
shock (impact) to which it may reasonably be subjected during handling and
transportation in the process of installation, repair, and replacement. It is to be noted that
the test unit is not, at this time, in its shipping carton.
Fasten the test unit firmly to the specimen table. In each of its three planes the test, drop
the unit from a calibrated height to result in a shock force of 10g.
Test Equipment Requirements. A17.2
1. Shock (impact) test fixture equivalent to that suggested by the simplified sketch
shown in Figure 2.
2. The test table shall have a surface area sufficient to accommodate the test unit.
3. Calibrate the test table and the items tested as indicated. This shock test defines the
test shock to be 10g (+/-1g).
Measure calibration of the test equipment for these shock tests by three
accelerometers having fixed shock settings of 9g, 10g, and 11g. They shall be
Inertia Switch Incorporated ST-355, or the equivalent. Attach these devices
rigidly to the test table.
Calibration of the fixture for each item to be tested is as follows:
o Place a dummy load weighing within 10 percent of the test unit on the table.
o Reset the three accelerometers and drop the test table from a measured
height.
o Observe that the accelerometers indicate the following:
o Activate the 9g accelerometer.
o The 10g unit may or may not be actuated.
o The 11g unit shall not be actuated.
Figure 2
Shock Test Fixture
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A73 of 107
Repeat calibration test (a) and (b) adjusting the height of the drop until, on ten
successive drops, the following occurs:
o The 9g unit is actuated ten times.
o The 10g unit is actuated between four to eight times.
o The 11g unit is not actuated on any of the ten drops.
Test Procedure. A17.3
1. The calibration height of the drop for the particular item under test as determined in
Test Equipment Requirements shall be used in this procedure.
2. Secure the test unit to the test table surface so that the test unit rests on one of its
three mutually perpendicular planes.
3. Raise the test table to the calibrated height.
4. Release the test table from the calibrated height, allowing a free fall into the box of
energy absorbing material below.
5. Repeat the drop test for each of the remaining two mutually perpendicular planes,
using the same calibrated height for each drop test of the same test unit.
6. The observations of the accelerometer for the three tests of the test item are:
The 9g unit is actuated for all three tests. (Repeat the calibration if the unit is not
actuated.)
The 10g unit may or may not be actuated in these tests.
The 11g unit is not actuated on any drop. (If the unit is actuated, repeat the
calibration only if the test unit has suffered damage.)
Disposition of Test Unit. A17.4
1. Check the test unit for any physical damage resulting from the drop tests.
2. Check the test unit to determine that it is functionally operable in all modes of its
prescribed operation.
3. Satisfactory completion of all environmental tests, including the shock (impact) is
required.
A18 Power Interruption Tests
Conduct the following power interruption tests at low input voltage (100 VAC) and high input
voltage (135 VAC) at -37 degrees C, and +74 degrees C.
Short Power Interruption A18.1
While the Test Unit is cycling through normal operations, remove the input voltage for a
period of 475 milliseconds. Upon restoration of the input voltage, check to insure that the
Test Unit continues normal operation as though no power interruption has occurred.
Repeat this test three times.
Voltage Variation A18.2
All circuits of the Test Unit shall be subjected to slowly varying line voltage during
which the Test Unit shall be subjected to line voltage that is slowly lowered from a
nominal 120 VAC line voltage to 0 VAC at a rate of not greater than 2 Volts per second.
The line voltage shall then be slowly raised to 100 VAC at which point the Test Unit
shall resume normal operation without operator intervention. Perform this test at both -
37 degrees C and +74 degrees C, at a nominal 120 VAC line voltage. Repeat this test
three times.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A74 of 107
Rapid Power Interruption A18.3
Subject the Test Unit to rapid power interruption testing of the form that the power is off
for 350 milliseconds and on for 650 milliseconds for a period of 2 minutes. Perform
power interruption through electromechanical contacts of an appropriate size for the load.
During this testing, the controller shall function normally and continue normal
sequencing (operation) at the conclusion of the test. This test shall be performed at both -
37 degrees C and +74 degrees C, at a nominal 120 VAC line voltage. Repeat this test
three times.
The Cities of Fort Worth and Dallas, Texas
Advanced Transportation Controller Specification
February 2012 Page A75 of 107
APPENDIX B – DETAILED DRAWINGS
List of Contents
Type 2070 Unit Chassis Front View - Figure A9-1
Type 2070 Unit Chassis Rear View - Figure A9-2
Type 2070 Unit Chassis Top View - Figure A9-3
Type 2070 Unit Chassis Motherboard - Figure A9-4
Type 2070 Unit Motherboard A Connector Pinouts - Figure A9-5
Type 2070 Unit System PCB Modules, General - Figure A9-6
Type 2070-2 Field I/O Module - Figure A9-8
Type 2070-2 Field I/O Module C1 & C11 Connectors Figure A9-9
Type 2070-3 Front Panel Assembly Figure A9-10
Type 2070-3 Front Panel Assembly, Key Codes Figure A9-11
Type 2070-3 Front Panel Assembly, Key Codes Figure A9-12
Type 2070-4 Power Supply Module - Figure A9-13
Type 2070-1C CPU Module - Figure A9-15
Type 2070 Serial Port Descriptors Defaults - Figure A9-16
Type 2070 Power Failure Reactors - Figure A9-17
Type 2070-6 Async/Modem Serial Comm Module – Figure10-5-1
Type 2070-7 Serial Comm Module – Figure10-5-2
Type 2070-N1 N1Controller Unit Front View - Figure A11-1
Type 2070-N1 N1 Controller Unit Side View - Figure A11-2
Type 2070-N1 N1 Controller Unit ISO View - Figure A11-3
Type 2070-8 Field I/O Module Connector A&B - Figure A11-4
Type 2070-8 Field I/O Module Connect C&D - Figure A11-5
Type 2070-8 Field I/O Module EX1&EX2 Connector – Figure A11-6
Type 2070-2N Field I/O Module – Figure A11-7
Source: California Department of Transportation (Caltrans), California
Transportation Electrical Equipment Specifications (TEES). March 9, 2009
February 2012 Page A76 of 107
February 2012 Page A77 of 107
February 2012 Page A78 of 107
February 2012 Page A79 of 107
February 2012 Page A80 of 107
February 2012 Page A81 of 107
February 2012 Page A82 of 107
February 2012 Page A83 of 107
February 2012 Page A84 of 107
Special Note: Alternate keyboard and display layouts are acceptable as approved by the Engineer.
However, minimum size dimensions shall be maintained.
February 2012 Page A85 of 107
February 2012 Page A86 of 107
February 2012 Page A87 of 107
February 2012 Page A88 of 107
February 2012 Page A89 of 107
February 2012 Page A90 of 107
February 2012 Page A91 of 107
February 2012 Page A92 of 107
February 2012 Page A93 of 107
February 2012 Page A94 of 107
February 2012 Page A95 of 107
February 2012 Page A96 of 107
February 2012 Page A97 of 107
February 2012 Page A98 of 107
February 2012 Page A99 of 107
February 2012 Page A100 of 107
Attachment 1
Technical Specifications
Advanced Traffic Signal Controller Software
JANUARY 2012
Attachment C
Table of Contents
Local Traffic Signal Controller Software Specification
January 2012 i
TABLE OF CONTENTS
1 General and Administrative ................................................................................................................... 2
1.1 General .......................................................................................................................................... 2
1.2 Intersection Information ................................................................................................................. 2
1.3 Controller Information .................................................................................................................... 2
1.4 Software Upgrades ........................................................................................................................ 2
1.5 Copy/Paste .................................................................................................................................... 3
1.6 Save Changes ............................................................................................................................... 3
1.7 Compatibility With Existing Infrastructure ...................................................................................... 3
1.8 Industry Standard Nomenclature ................................................................................................... 3
1.9 Security .......................................................................................................................................... 3
1.10 Web Browser ................................................................................................................................. 4
1.11 Daylight Savings Time ................................................................................................................... 4
2 Configuration ......................................................................................................................................... 5
2.1 Configuration Tables ...................................................................................................................... 5
2.2 Cabinet Configuration .................................................................................................................... 5
2.3 Ring Barrier Configuration ............................................................................................................. 5
2.4 Start Up Configuration ................................................................................................................... 5
2.5 Programmed Flash Configuration .................................................................................................. 6
2.6 Manual Control Configuration ........................................................................................................ 8
3 Detection ............................................................................................................................................... 8
3.1 General .......................................................................................................................................... 8
3.2 Global Detector Parameters .......................................................................................................... 9
3.3 Detector Configuration ................................................................................................................... 9
3.4 Vehicle Detector Configuration ...................................................................................................... 9
3.5 Pedestrian Detector Configuration ............................................................................................... 11
3.6 System/Count Detector Configuration ......................................................................................... 11
3.7 Detector Input Failure .................................................................................................................. 11
3.8 Remote Reset .............................................................................................................................. 11
4 Phase Parameters .............................................................................................................................. 12
4.1 General ........................................................................................................................................ 12
4.2 Multiple Phase Parameter Tables ................................................................................................ 12
Table of Contents
Local Traffic Signal Controller Software Specification
January 2012 ii
4.3 Phase Configuration .................................................................................................................... 12
4.4 Phase Timing Parameters ........................................................................................................... 15
4.5 Global Phase Parameters ............................................................................................................ 18
4.6 Pedestrian Operation ................................................................................................................... 19
4.7 Left Turn Operation ...................................................................................................................... 20
4.8 Right Turn Operation ................................................................................................................... 20
4.9 Pedestrian Hybrid Beacon Operation .......................................................................................... 21
4.10 Phase Sequence ......................................................................................................................... 22
5 Overlaps ............................................................................................................................................. 23
5.1 General ........................................................................................................................................ 23
5.2 Overlap Configuration .................................................................................................................. 23
5.3 Overlap Timing Parameters ......................................................................................................... 25
5.4 Overlap Operations ...................................................................................................................... 26
6 Schedule ............................................................................................................................................. 28
6.1 General ........................................................................................................................................ 28
6.2 Time of Day/Day of Week Schedule (TOD/DOW) ....................................................................... 28
6.3 Holiday Schedule ......................................................................................................................... 29
6.4 Seasonal Schedule ...................................................................................................................... 30
6.5 Temporary Schedule ................................................................................................................... 30
7 Coordination........................................................................................................................................ 31
7.1 General ........................................................................................................................................ 31
7.2 Coordination Parameters ............................................................................................................. 31
7.3 Pedestrian Service ....................................................................................................................... 32
7.4 Pedestrian Service Parameters ................................................................................................... 34
7.5 Coordinated Operations (Use Cases) .......................................................................................... 34
8 Preemption ......................................................................................................................................... 36
8.1 General ........................................................................................................................................ 36
8.2 Preempt States ............................................................................................................................ 38
8.3 Preemption Priority ...................................................................................................................... 38
8.4 Railroad Preemption .................................................................................................................... 39
8.5 Emergency Vehicle Preemption ................................................................................................... 40
8.6 Normal Preempt Configuration .................................................................................................... 40
9 Transit Priority ..................................................................................................................................... 45
9.1 General ........................................................................................................................................ 45
Table of Contents
Local Traffic Signal Controller Software Specification
January 2012 iii
9.2 Full Priority Operation .................................................................................................................. 46
9.3 Partial Transit Priority .................................................................................................................. 47
9.4 Bus Priority .................................................................................................................................. 52
10 Advanced Programming ..................................................................................................................... 55
10.1 General ........................................................................................................................................ 55
10.2 Assignable Outputs ...................................................................................................................... 56
10.3 Assignable Inputs ........................................................................................................................ 57
11 Communications ................................................................................................................................. 58
11.1 General ........................................................................................................................................ 58
11.2 Center to Field Communication ................................................................................................... 59
11.3 Peer to Peer Communication ....................................................................................................... 61
11.4 Local Wireless Remote ................................................................................................................ 62
12 Advanced Operations ......................................................................................................................... 62
12.1 Traffic Responsive Operation ...................................................................................................... 62
12.2 Queue Detection .......................................................................................................................... 63
12.3 Auxiliary Field Device Operation .................................................................................................. 65
13 Diamond Interchange Sequence ......................................................................................................... 66
13.1 General ........................................................................................................................................ 66
13.2 Diamond Interchange K-Clearance .............................................................................................. 67
14 Logs .................................................................................................................................................... 72
14.1 General ........................................................................................................................................ 72
14.2 General Controller Log ................................................................................................................ 72
14.3 Conflict Monitor/MMU .................................................................................................................. 72
14.4 Front Panel Log ........................................................................................................................... 72
14.5 Controller Software Log ............................................................................................................... 72
14.6 Detector Log ................................................................................................................................ 72
14.7 Vehicle Split Log .......................................................................................................................... 72
14.8 Cycle Time Log ............................................................................................................................ 73
14.9 Coordination Log ......................................................................................................................... 73
14.10 Preempt Log ............................................................................................................................ 73
14.11 Transit Priority Log ................................................................................................................... 73
14.12 Special Event Log .................................................................................................................... 74
14.13 Advanced Operation Event Log ............................................................................................... 74
15 User Interface ..................................................................................................................................... 74
Table of Contents
Local Traffic Signal Controller Software Specification
January 2012 iv
15.1 General ........................................................................................................................................ 74
15.2 Data Entry .................................................................................................................................... 75
15.3 Status Display .............................................................................................................................. 75
16 Miscellaneous ..................................................................................................................................... 80
16.1 Special Function/Time of Day Outputs ........................................................................................ 80
16.2 Alarms ......................................................................................................................................... 80
16.3 Diagnostics .................................................................................................................................. 81
16.4 Timing Sheets .............................................................................................................................. 81
17 Desirable Features .............................................................................................................................. 82
17.1 Vehicle Detector Configuration Desirable Features ..................................................................... 82
17.2 Vehicle Detector Timing Desirable Feature ................................................................................. 82
17.3 Smooth Preempt Configuration .................................................................................................... 82
17.4 Traffic Adaptive Operation ........................................................................................................... 86
17.5 Variable Mode of Left Turn Operation .......................................................................................... 86
17.6 Variable Lagging Left Turn Splits ................................................................................................. 91
17.7 Traffic Responsive Flash Operation ............................................................................................. 92
17.8 Cycle-By-Cycle Split Adjustments ................................................................................................ 94
17.9 Auxiliary Field Device Transition Table ........................................................................................ 96
17.10 Logs for Desirable Features .................................................................................................... 97
17.11 Intersection to Vehicle Information ........................................................................................... 98
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 1 of 100
Advanced Traffic Signal Controller Software Specification
INTRODUCTION
The Cities of Fort Worth, Dallas, and Richardson Texas (the Cities) plan to transition from their existing
Model 170 local controller to the Advanced Transportation Controller (ATC). As part of the transition, the
Cities will procure new Local Controller Software that meets the existing and future needs of the Cities.
This document specifies the minimum and desirable requirements of the local controller software.
ATC SPECIAL PROVISIONS
The Cities have incorporated the ATC Standards into their ATC Special Provisions. The Cities’ ATC
Special Provisions modify and enhance the ATC Standard to meet the specific needs of the Cities. The
selected local controller software shall be fully compatible with the Cities’ ATC hardware. A copy of the
City’s ATC Special Provisions is available upon request.
CONCEPT OF OPERATIONS DOCUMENT
The Cities have defined their desired functionality for signalized intersections in its document entitled
Concept of Operation for Local Intersection Operation. This document is included in the appendix. If,
in the opinion of the selected provider, the requirements presented in this document will not provide that
functionality, it is the responsibility of the controller software provider to document and provide those
deficiencies to the Cities. The deficiencies list shall be provided to the Cities as part of the proposal.
CURRENTLY AVAILABLE SOFTWARE
The City expects that Commercially available Off-The-Shelf (COTS) software will meet, at a minimum, all of
the minimum requirements defined in this document. To be considered as COTS software, the proposed
software should be currently available and operating in the field at a minimum of 50 intersections.
CABINET TYPES
The proposed software shall be easily configurable to operate in the Type 332 family of 170 cabinets
(332/336/337), the NEMA TS1 and TS2 type 1 cabinets, and the ITS family of cabinets as defined in the
ITS Cabinet Standard v1.02.17b (or latest version).
NEMA REQUIREMENTS
Where not specifically defined in this document, the proposed local controller software shall meet or exceed
the requirements defined in Section 3 of the NEMA Standards Publication TS 2-2003 v.02.06, Traffic
Control Assemblies with NTCIP Requirements. The requirements defined in this document enhance,
expand, or are in addition to the requirements defined in the NEMA publication.
COMPLIANCE
The provided software shall be in strict adherence to the following:
Applicable National Transportation Communication for ITS Protocol (NTCIP) standards as defined
in the appendix.
The project requirements presented in this document.
If strict adherence to both conflict, compliance to the project requirements shall prevail.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 2 of 100
All Proposers must be able to demonstrate to the City’s satisfaction that their proposed controller
software is in full compliance with the provisions of this specification including all web browser interface
provisions.
FUNCTIONAL REQUIREMENTS
1 GENERAL AND ADMINISTRATIVE
1.1 GENERAL
1.1.1 The software shall provide a means for the user to define general information,
settings, and preferences.
1.2 INTERSECTION INFORMATION
1.2.1 The software shall support the following user defined intersection information
1.2.1.1 Intersection name
1.2.1.2 Intersection ID number
1.2.1.3 Street 1
1.2.1.4 Street 2
1.3 CONTROLLER INFORMATION
1.3.1 The software shall provide the following controller information
1.3.1.1 Current active software version
1.3.1.2 Available software upgrade
1.3.1.3 The software shall indicate that a new software version is available and
has been downloaded to the flash memory in the controller.
1.4 SOFTWARE UPGRADES
1.4.1 The City shall be automatically notified by the vendor when software upgrades
are available.
1.4.1.1 The automatic notice shall include a description of changes to the
software.
1.4.2 The software shall allow users to download upgrades to the local controller
software from a remote location.
1.4.3 The upgraded software shall reside in flash memory in the local controller unit
and not automatically replace the existing software in the controller unit.
1.4.3.1 If the software upgrade is considered minor, the user shall be able to
remotely replace the existing software while the controller is still operating
and shall not require a controller restart.
1.4.3.2 If the software upgrade is considered major, a controller restart shall be
required to replace the existing software.
1.4.3.3 A major upgrade shall not take place in the event of a power failure.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 3 of 100
1.4.3.4 The software provider shall submit their definition of minor and major
upgrades for City approval.
1.4.4 The software shall verify that the upgraded software was successfully
downloaded to the controller unit without errors.
1.5 COPY/PASTE
1.5.1 The software shall provide a copy and paste capability for user entered
parameters. The functionality shall be available for individual cells, rows,
columns, and full tables.
1.6 SAVE CHANGES
1.6.1 The software shall require the user to confirm any changes to the controller
database prior to accepting the change.
1.6.2 All changes shall become highlighted and be reviewable prior to acceptance.
1.6.3 Changes shall take effect upon confirmation by the user.
1.7 COMPATIBILITY WITH EXISTING INFRASTRUCTURE
1.7.1 A template shall be provided for the inputs and outputs of standard 332, 332A,
336S, 337, and 337S cabinets.
1.7.2 The software shall support monitoring of the existing conflict
monitor/malfunction monitor unit.
1.8 INDUSTRY STANDARD NOMENCLATURE
1.8.1 All names, labels, and other descriptions within the software shall use industry
standard, easily understood nomenclature. All nonstandard nomenclature shall
be approved by the City.
1.8.2 Any new software development shall follow industry standard software
development.
1.9 SECURITY
1.9.1 The software shall enable/deny access to the controller through user
passwords. User access and passwords shall be definable by the software
administrator. The user shall be required to change their password after an
amount of time in days defined by the system administrator.
1.9.1.1 Security levels shall include view only, access to change timing
parameters only, access to change configuration of phasing.
1.9.1.2 As security levels increase, the user will be able to access and change
more features in the software and each level shall include access to all
lower levels.
1.9.1.3 The software shall log the user ID, date and time of log-in and log-out and
any changes the user made.
1.9.1.4 The software shall automatically logout the last user after a user specified
amount of time has passed where there was no front panel activity or
activity from a remote connection.
1.9.2 The software shall provide access from approved remote equipment only.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 4 of 100
1.9.2.1 The user shall be able to enable/disable this feature.
1.9.2.2 The software shall maintain a “MAC Allow Table” containing the MAC
addresses of all approved equipment.
1.9.2.3 When the software identifies non-approved equipment, it shall query the
supervisory software (through an SNMP trap) in an attempt to validate the
equipment. If the equipment MAC address is validated, the equipment
shall be approved and the MAC address added to the MAC Allow Table.
1.9.2.4 The software local MAC Allow Table shall be regularly updated from the
Supervisory software.
1.9.2.5 Users with proper access privileges shall be able to enter an Equipment
MAC Address into the software via the front panel.
1.10 WEB BROWSER
1.10.1 The software shall provide a controller resident web server that exposes all
NTCIP object via a web interface.
1.10.1.1 Objects should be capable of being edited with Internet explorer 5 and
higher, Firefox 1.0 and higher, Safari 1.0 and higher Ethernet connected
web client browser.
1.10.1.2 There shall not be any step necessary to install extra software on the web
client browser. As long as the user’s web browser meets the specified
requirements, the user shall be able to view all the status objects and edit
all read/write parameter objects.
1.10.2 Web User interface object support
1.10.2.1 The web application shall support all the objects that users can set on the
controller using the controllers’ front panel User Interface. This shall
support all the standard NTCIP 1201:2005 and NTCIP 1202:2005 objects
and all manufacturer specific objects.
1.10.3 Status objects
1.10.3.1 The status objects should be refreshed by the web interface automatically
(without the need for the users to refresh pages in their web browser
manually). The refresh shall have a latency of less than 2/10 of a second
after a value change occurs.
1.10.4 Web server Mib parameters
1.10.4.1 A manufacturer specific NTCIP read/write object shall be used for
configuring the network port number which the web server listen to. The
Default Port number shall be 80.
1.11 DAYLIGHT SAVINGS TIME
1.11.1 The software shall provide the capability to automatically adjust the controller
clock to reflect daylight savings time (DST). Dates and time for the start and
end of DST shall be user programmable.
1.11.2 By default, DST shall be enabled.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 5 of 100
2 CONFIGURATION
2.1 CONFIGURATION TABLES
2.1.1 The software shall provide a minimum of five (5) tables for configuring the
software.
2.2 CABINET CONFIGURATION
2.2.1 The user shall be able to select the cabinet type.
2.2.1.1 Default configuration tables shall be provided for 332, 332A, 336S, 337,
337S, and ITS model cabinets.
2.2.2 The software shall be capable of configuring the maximum number of channel
outputs or detector inputs available in the ITS model cabinets.
2.2.3 The software shall provide a minimum of 128 user definable input pins.
2.2.4 The software shall provide a minimum of 128 user definable output pins.
2.2.5 The software shall allow the user to redirect any vehicle phase, pedestrian
phase, or overlap output by changing the pin assignment.
2.3 RING BARRIER CONFIGURATION
2.3.1 The software shall allow the user to program the ring and barrier structure.
2.3.2 The software shall provide a minimum of eight (8) concurrent rings and 12
barriers.
2.3.3 The user shall be able to program one instance of every phase in the ring and
barrier sequence.
2.3.3.1 The user shall be able to program phases even if they are not permitted.
2.3.4 The user shall be able to make changes to the active ring and barrier structure
while the software is running the traffic light.
2.3.4.1 The software shall prompt the user to put the intersection into flash or
continue.
2.3.4.1.1 If the user elects to continue without putting the intersection
into flash, the software shall provide diagnostics to evaluate
the proposed changes and determine if the controller needs
to restart to implement the proposed changes.
2.3.4.1.2 If a restart is needed, the controller shall prompt the user to
put the intersection into flash to implement changes.
The user shall be able to override the software and
continue without restart.
2.3.4.1.3 If controller is not put into flash and the user leaves the
prompt screen, the changes will be lost.
2.3.4.2 The changes shall take effect when the user confirms the changes and
the local cycle timer reaches the zero point or the last barrier is crossed.
2.4 START UP CONFIGURATION
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 6 of 100
2.4.1 The user shall be able to define the initial operation of the controller upon
startup.
2.4.2 The user shall be able to select the following startup parameters:
2.4.2.1 Primary Startup Phases
2.4.2.1.1 The primary startup phases shall display solid yellow
followed by solid all-red.
2.4.2.2 Secondary Startup Phases
2.4.2.2.1 Secondary Startup phases will serve after the primary
startup phases but prior to starting normal operation.
2.4.2.2.2 The secondary startup phases shall display green
immediately after the end of the primary startup phases.
2.4.2.3 Startup Flash
2.4.2.3.1 Enabling this feature will cause the intersection to startup in
flash.
2.4.2.4 Flash Yellow
2.4.2.4.1 The selected phases shall flash yellow during programmed
flash operation. All other phases shall flash red.
2.4.2.5 Startup All-Red Clearance
2.4.2.5.1 Enabling this feature will cause the intersection to display a
steady red indication before beginning normal operation.
2.4.2.6 Vehicle Call Disable
2.4.2.6.1 The user shall be able to identify any vehicle phase that will
not receive an automatic call upon startup.
2.4.2.6.2 By default all vehicle phases shall be receive a call upon
startup.
2.4.2.7 Pedestrian Call Disable
2.4.2.7.1 The user shall be able to identify any pedestrian phase that
will not receive an automatic call upon startup.
2.4.2.7.2 By default all pedestrian phases shall be receive a call upon
startup.
2.4.3 The user shall be able to set the following startup timing parameters. When
values are entered in the startup table for these parameters, the controller will
time these values instead of the values entered for normal operations
2.4.3.1 Primary Startup (0-25.5 sec)
2.4.3.2 Secondary Startup (0-25.5 sec)
2.4.3.3 Startup minimum green (0-255 sec)
2.4.3.4 Startup Flash (0-255 sec)
2.4.3.5 Startup All Red Clearance (0-10 sec)
2.5 PROGRAMMED FLASH CONFIGURATION
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 7 of 100
2.5.1 The user shall be able to define the programmed flash operation of the
controller.
2.5.2 The controller shall not enter flash operation unless all traffic lights are red.
2.5.3 When scheduled or commanded to change to program flash operation, the
software shall place minimum recalls on the last phases before flash. After
beginning flash operation, the controller shall remove existing vehicle and
pedestrian calls and ignore all calls during flash operation.
2.5.4 The software shall end programmed flash by providing a green light for the
selected exit phase.
2.5.5 The user shall be able to select the following programmed flash parameters by
phase:
2.5.5.1 Flash Entry Phases
2.5.5.1.1 Flash entry phase will be served before the controller enters
program flash.
2.5.5.1.2 If the flash entry phases do not end at the same time, the
controller will enter flash mode during the first all-red period
after one of the phases has been served.
2.5.5.2 Flash Exit Phases
2.5.5.2.1 Flash exit phases shall serve as the startup phases following
the end of program flash.
2.5.5.2.2 If no exit phases are selected, the secondary startup phases
shall be used.
2.5.5.3 Flash Yellow
2.5.5.3.1 The selected phases shall flash yellow during programmed
flash operation. All other phases shall flash red.
2.5.5.4 Vehicle Call
2.5.5.4.1 The user shall be able to identify any vehicle phase that will
receive an automatic call when switching from program flash
to normal operation.
2.5.5.4.2 By default all vehicle phases shall not receive a call when
exiting program flash.
2.5.5.5 Pedestrian Call
2.5.5.5.1 The user shall be able to identify any pedestrian phase that
will receive an automatic call when switching from program
flash to normal operations.
2.5.5.5.2 By default all pedestrian phases shall not receive a call
when exiting program flash.
2.5.5.6 Alternate Flash Hertz
2.5.5.6.1 The selected phase shall show red when non-selected
phases are dark and vice versa.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 8 of 100
2.5.5.7 All Red Clearance Time
2.5.5.7.1 The user shall be able to select the amount of all-red time
that will be displayed following the end of program flash.
2.5.5.7.2 The duration of the all-red clearance time shall be user
definable for 0-25.5 seconds.
2.5.5.7.3 If the all-red clearance time is 0.0 seconds, the flash exit
phases shall immediately display green.
2.6 MANUAL CONTROL CONFIGURATION
2.6.1 The user shall be able to program an alternate sequence for operation during
manual control. The user shall be able to remotely apply and remove vehicle
and pedestrian calls.
2.6.2 The software shall provide an option to enable/disable manual control.
3 DETECTION
3.1 GENERAL
3.1.1 Vehicle Detectors
3.1.1.1 The software shall support a minimum of 72 programmable vehicle
detectors per intersection.
3.1.1.2 All vehicle detectors shall be capable of collecting volume and occupancy
data.
3.1.1.2.1 Detector data shall be aggregated in 5 minute increments.
3.1.1.2.2 User shall be able to identify movements associated with
each detector.
3.1.2 Pedestrian Detectors
3.1.2.1 The software shall support a minimum of 12 programmable pedestrian
detectors per intersection.
3.1.3 System Detectors
3.1.3.1 The user shall be able to assign any detector as a system detector.
3.1.3.2 The software shall support a minimum of 16 system detectors.
3.1.4 Queue Detectors
3.1.4.1 The user shall be able to assign any detector as a queue detector.
3.1.4.2 The user shall be able to assign a minimum of eight (8) queue detectors.
3.1.5 Description
3.1.5.1 The user will be able to enter a text description of each detector. The
description field shall be at least 18 characters.
3.1.6 Multiple Detector Tables
3.1.6.1 The software shall provide a minimum of four (4) unique, user definable
detector tables.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 9 of 100
3.2 GLOBAL DETECTOR PARAMETERS
3.2.1 The software shall allow users to define the following detection parameter
values that apply to all enabled detectors.
3.2.1.1 Vehicle On Time Fail
3.2.1.1.1 The user shall be able to select the amount of time in
minutes that the detector must be in a constant on state
before it is reported failed.
3.2.1.1.2 Acceptable input value shall range from 0 to 1440 minutes.
3.2.1.2 Vehicle Off Time Fail
3.2.1.2.1 The user shall be able to select the amount of time in
minutes that the detector must be off before it is reported
failed.
3.2.1.3 Pedestrian On Time Fail
3.2.1.3.1 The user shall be able to select the amount of time in
minutes that the pedestrian detector must be in a constant
on state before it is reported failed.
3.2.1.4 Pedestrian Off Time Fail
3.2.1.4.1 Enable – the user shall select if this parameter is active in
the software.
3.2.1.4.2 The user shall be able to select the amount of time in
minutes that the pedestrian detector must be off before it is
reported failed.
3.2.1.5 Erratic Activity Fail
3.2.1.5.1 The user shall be able to select the number of actuations
(per minute) that the detector must exceed before it is
reported failed.
3.3 DETECTOR CONFIGURATION
3.3.1 The software shall be able to configure the following detector types:
3.3.1.1 Vehicle
3.3.1.2 Pedestrian
3.3.1.3 System
3.3.1.4 Queue
3.4 VEHICLE DETECTOR CONFIGURATION
3.4.1 The software shall provide the following user selected configuration
parameters for vehicle detection.
3.4.1.1 Enable
3.4.1.2 Call
3.4.1.3 Extend
3.4.1.4 Terminate
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 10 of 100
3.4.1.4.1 Detector enabled as a terminate detector shall cause the
controller to immediately end the selected phase.
3.4.1.5 Yellow Lock
3.4.1.5.1 If yellow lock is used for a left turn phase, the user shall be
able to define the permitted phases for the left turn. The
software shall not lock the call until the protected and
permitted phases for the left turn are yellow.
3.4.1.6 Red Lock
3.4.1.6.1 If red lock is used for a left turn phase, the user shall be
able to define the permitted phases for the left turn. The
software shall not lock the call until the protected and
permitted phases for the left turn are red.
3.4.1.7 Pedestrian Input
3.4.1.7.1 When enabled, the detector shall call the pedestrian phase
associated with the vehicle phases programmed for the
input.
3.4.1.8 Phase Assignment
3.4.1.8.1 The software shall allow at least eight (8) vehicle phases to
be assigned to each detector.
3.4.1.9 Overlap Assignment
3.4.1.10 Detector Disable (Type 3)
3.4.1.10.1 This parameter shall reset the phase extension timer for the
phases associated with this input until the green has been
active for the number of seconds defined by the user.
3.4.1.10.2 Once the extension timer for this detector reaches zero, the
detector shall be disabled.
3.4.1.10.3 Once a detector input is disabled it shall not become active
until the phase begins its clearance interval.
3.4.1.10.4 The phase associated with that detector.
3.4.1.11 Delay disabled when leading
3.4.1.11.1 The user shall be able to disable the detector delay for
leading left turns.
3.4.2 The software shall provide the following user definable timing parameters for
vehicle detection.
3.4.2.1 Delay
3.4.2.2 Extension
3.4.2.3 Detector Disable
3.4.2.4 Extension Time
3.4.2.5 Added Initial
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 11 of 100
3.5 PEDESTRIAN DETECTOR CONFIGURATION
3.5.1 The software shall provide the following user selected pedestrian detector
configuration parameters:
3.5.1.1 Enable
3.5.1.2 Phase Assignment
3.5.1.3 Overlap Assignment
3.6 SYSTEM/COUNT DETECTOR CONFIGURATION
3.6.1 Each detector input shall be capable of functioning as a system detector
3.6.1.1 Detectors shall accumulate volume and occupancy data on a per cycle
basis.
3.6.1.2 The user shall be able to set the time increment in minutes for the
aggregation of volume and occupancy information.
3.6.1.3 User shall be able to set the time of day/day of week to collect volume
and occupancy data.
3.6.1.4 The user can also choose to have data continuously collected.
3.7 DETECTOR INPUT FAILURE
3.7.1 In the event of a detector failure, the software shall automatically generate an
alarm and transmit the alarm to the traffic management system.
3.7.2 The software shall automatically change detector setting when a detector
linked to another detector fails.
3.7.2.1 A detector shall automatically change from call only to call and extend.
3.7.2.1.1 This shall occur when the stop detector is only used to call
the phase and the setback detector is used to call and
extend the phase. The stop detector shall change to call
and extend if the setback detector fails.
3.7.2.2 A detector shall automatically change from time before detector disable to
extend.
3.7.2.2.1 This shall occur when the stop detector has a time before
detector disable programmed and the setback detector is
used to call and extend the phase. The stop detector shall
change to call and extend if the setback detector fails.
3.7.3 The user shall be able to select any of the following modes in the event of a
detector failure:
3.7.3.1 None
3.7.3.2 Minimum Recall
3.7.3.3 Maximum 1 Recall
3.7.3.4 Maximum 2 Recall
3.7.3.5 Maximum 3 Recall
3.8 REMOTE RESET
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 12 of 100
3.8.1 The software shall allow the detectors to be reset remotely.
4 PHASE PARAMETERS
4.1 GENERAL
4.1.1 The software shall provide a minimum of 32 vehicular phases.
4.1.1.1 The user shall be able to label each vehicle phase in the phase
parameters table.
4.1.1.1.1 Each text label shall be at least six characters.
4.1.1.1.2 The vehicle phase label in a phase parameters table shall
remain blank until the user enters a label or copies a label
from another phase parameter table.
4.1.2 The software shall provide a minimum of 12 pedestrian phases.
4.1.2.1 The user shall be able to label each pedestrian phase in the phase
parameters table.
4.1.2.1.1 Each text label shall be at least six characters.
4.1.2.1.2 The pedestrian phase label in a phase parameters table
shall remain blank until the user enters a label or copies a
label from another phase parameter table.
4.1.3 All changes to phase parameters shall become active at the beginning of the
next local cycle or when the controller crossed the last barrier in the ring
structure.
4.1.4 The software shall provide configuration for Pedestrian Hybrid Signals as
described in Section 4.9.
4.2 MULTIPLE PHASE PARAMETER TABLES
4.2.1 The software shall provide a minimum of thirty-two (32) programmable tables
of phase parameters.
4.3 PHASE CONFIGURATION
4.3.1 The software shall allow the user to select the following phase configuration
parameters:
4.3.1.1 Vehicle Phase Enable
4.3.1.2 Pedestrian Phase Enable
4.3.1.3 Exclusive Vehicle Phases
4.3.1.4 Exclusive Pedestrian Phases
4.3.1.5 Restricted Phases (conflicting phases)
4.3.1.5.1 The user shall enter a pair of phases in a field. A
compatibility table does not meet this requirement.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 13 of 100
4.3.1.5.2 If the active phase is entered as a restricted phase and that
phase is active, it will prevent the other phases entered as
restricted phases from becoming active. The ring with the
other phase will red rest until the active phase ends.
4.3.1.5.3 If two restricted phases try to turn green at the same time
the controller shall select one phase, and then stop the other
phase from turning green.
4.3.1.6 Disable Minimum Yellow
4.3.1.6.1 When enabled the software shall be able to output yellow
times less than 3.0 seconds.
4.3.1.6.2 If this feature is not active, the controller shall output at least
a 3.0 second yellow.
4.3.1.7 Split Ring
4.3.1.7.1 When enabled, the software shall operate each ring
independently.
4.3.1.7.2 When enabled, this feature will disable any common barriers
between the active rings in the active ring-barrier
programming.
4.3.1.7.3 When enabled, the user shall be able to coordinate the rings
so barriers are crossed at the same time in the local cycle.
This shall not prevent one ring from crossing the barrier
even if other rings are not ready.
4.3.1.8 Every Other Cycle
4.3.1.8.1 The phase will be served every other cycle; in other words,
the phase will be omitted every other cycle.
4.3.1.8.2 The user shall be able to select if the phase is served during
odd or even cycles.
4.3.1.9 Minimum Recall 1
4.3.1.10 Minimum Recall 2
4.3.1.11 Maximum Recall 1
4.3.1.12 Maximum Recall 2
4.3.1.13 Maximum Recall 3
4.3.1.14 Soft Recall
4.3.1.14.1 Soft Recall provides a recall to the selected phases in the
absence of any other vehicle or pedestrian calls.
4.3.1.15 Conditional Service
4.3.1.15.1 Conditional Service allows selected phases to be served out
of the set sequence provided all the conditions below are
met:
4.3.1.15.2 A phase in the same ring is green and ready to terminate.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 14 of 100
4.3.1.15.3 A phase in another ring is green and has enough split time
or max time to serve the conditional service max time for the
conditional service phase.
4.3.1.16 Pedestrian Walk 1
4.3.1.17 Pedestrian Walk 2
4.3.1.18 Pedestrian Clearance 1
4.3.1.19 Pedestrian Clearance 2
4.3.1.20 Pedestrian Recall
4.3.1.21 Pedestrian Recycle
4.3.1.21.1 Pedestrian Recycle allows a late start or restart of
pedestrian service after start of vehicle green if there is
sufficient max green or split time remaining to completely
serve the walk and pedestrian clearance.
4.3.1.21.2 By default this shall be enabled.
4.3.1.22 Dual Entry
4.3.1.23 Walk Rest
4.3.1.24 Simultaneous Gap
4.3.1.25 Red Rest
4.3.1.26 Advanced Walk
4.3.1.27 Delay Walk
4.3.1.28 Last Car Passage
4.3.1.29 Phase recycle
4.3.1.29.1 The software shall allow vehicle and pedestrian phases to
be re-serviced in the cycle if enough time remains to provide
a minimum service.
4.3.1.29.2 The user shall be able to enable phase re-service by phase
and by coordination pattern.
4.3.1.29.3 The user shall define the second of the local cycle a re-
service may occur and the second of the local cycle a re-
service must be finished.
4.3.1.29.4 Vehicular phases shall be re-serviced, even if the pedestrian
phase cannot be re-served that cycle.
4.3.1.29.5 This feature shall allow the user to operate part of the
coordinated cycle in free mode.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 15 of 100
4.4 PHASE TIMING PARAMETERS
4.4.1 The software shall provide the following timing parameter ranges:
4.4.2 The software shall provide the following phase timing parameters.
4.4.2.1 Minimum Green 1
4.4.2.1.1 Minimum green 1 is the default value unless the users
specifies minimum green 2 in the active phase parameters
table
4.4.2.1.2 The software shall not violate a minimum green 1 unless
there is a request for priority or preemption.
4.4.2.2 Minimum Green 2
4.4.2.2.1 The software shall not violate a minimum green 2 unless
there is a request for priority or preemption.
4.4.2.3 Vehicle Extension
Parameter Range
(Seconds)
Increments
(Seconds)
Min Green 1 1-255 1
Min Green 2 1-255 1
Passage Time 0-25.5 0.1
Max Green 1 1-255 1
Max Green 2 1-255 1
Max Green 3 1-255 1
Conditional Service Max 1-255 1
Detector Disable 0-25.5 0.1
Yellow Clearance 0-25.5 0.1
All-Red Clearance 0-25.5 0.1
Walk 1 0-255 1
Walk 2 0-255 1
Pedestrian Clearance 1 0-255 1
Pedestrian Clearance 2 0-255 1
Advanced Walk 0-25.5 0.1
Delay Walk 0-25.5 0.1
Added Initial 0-25.5 0.1
Time to Reduce 1-255 1
Time Before Reduction 1-255 1
Minimum Gap 0-25.5 0.1
Variable Left Turn Time 0-25.5 0.1
Last Car Passage 0-25.5 0.1
Walk 2 Enable Time 0-255 1
Pedestrian Clearance 2 Enable Time 0-255 1
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 16 of 100
4.4.2.3.1 This is the base extension value. Any value in the detector
configuration table is added to this amount.
4.4.2.4 Maximum Green 1
4.4.2.4.1 Maximum green 1 shall be the default value if no other
Maximum value is entered.
4.4.2.5 Maximum Green 2
4.4.2.6 Maximum Green 3
4.4.2.7 Conditional Service Max
4.4.2.7.1 The maximum green time provided on a phase when timing
due to conditional service.
4.4.2.7.2 If the Conditional Service Max is 0 seconds, this max timer
shall have no effect. The active maximum green timer shall
apply.
4.4.2.7.3 This max green shall apply to the second time the phase is
served in a cycle. The active maximum green timer shall
apply to the first time the phase is served in a cycle.
4.4.2.8 Yellow Clearance
4.4.2.8.1 The user defined yellow shall not be less than 3.0 seconds.
If the user enters a yellow less than 3.0 seconds the
software will output 3.0 seconds unless the minimum yellow
time is disabled.
4.4.2.8.2 The software shall not output a yellow interval shorter than
the user defined value.
4.4.2.8.3 The software shall not display a yellow interval 0.01 seconds
longer than the user defined value.
4.4.2.9 All-Red Clearance
4.4.2.10 Walk 1
4.4.2.10.1 The software shall be capable of truncating the walk if there
is a request for priority or preemption.
4.4.2.10.2 The software shall not output a walk interval shorter than the
user defined value with the exception of a preemption event.
4.4.2.11 Walk 2
4.4.2.11.1 The software shall be capable of truncating the walk if there
is a request for priority or preemption.
4.4.2.11.2 The software shall not output a walk interval shorter than the
user defined value with the exception of a preemption event.
4.4.2.12 Pedestrian Clearance 1
4.4.2.12.1 The software shall be capable of truncating the pedestrian
clearance interval if there is a request for priority or
preemption.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 17 of 100
4.4.2.12.2 The software shall not output a pedestrian clearance interval
shorter than the user defined value with the exception of a
priority or preemption event.
4.4.2.12.3 The pedestrian clearance shall time with an overlap’s green
clearance and shall not extend the duration of the overlap
green clearance interval.
4.4.2.12.4 The software shall be capable of outputting the value of the
clearance interval to the countdown timer. It shall be
assumed the countdown timer is not learning the duration of
the pedestrian clearance; the software is providing this
value.
4.4.2.13 Pedestrian Clearance 2
4.4.2.13.1 The software shall be capable of truncating the pedestrian
clearance interval if there is a request for priority or
preemption.
4.4.2.13.2 The software shall not output a pedestrian clearance interval
shorter than the user defined value with the exception of a
priority or preemption event.
4.4.2.13.3 The pedestrian clearance shall time with an overlap’s green
clearance and shall not extend the duration of the overlap
green clearance interval.
4.4.2.13.4 The software shall be capable of outputting the value of the
clearance interval to the countdown timer. It shall be
assumed the countdown timer is not learning the duration of
the pedestrian clearance; the software is providing this
value.
4.4.2.14 Advance Walk
4.4.2.14.1 Entering a value in a cell in the table will activate this
feature.
4.4.2.14.2 The software shall not output an advanced walk if the output
is from a pedestrian overlap and the pedestrian interval is
active before the beginning of the phase.
4.4.2.14.3 The software shall begin the pedestrian phase during the
vehicle green even if advanced walk is programmed
provided ample phase green time is remaining on the
compatible vehicle phases.
4.4.2.15 Delay Walk
4.4.2.15.1 The software shall not output a delayed walk unless the
pedestrian phase is called before the vehicle phase begins.
4.4.2.15.2 The software shall not output a delayed walk if the output is
from a pedestrian overlap and the pedestrian interval is
active before the beginning of the phase.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 18 of 100
4.4.2.15.3 The software shall begin the pedestrian phase during the
vehicle green if the delayed walk is programmed. The
delayed walk shall not be provided if the pedestrian phase is
called and served during the vehicle green.
4.4.2.16 Volume Density – Added Initial
4.4.2.16.1 The software shall activate this feature when the user
defines the added initial and maximum initial green for a
phase.
4.4.2.17 Added Initial
4.4.2.18 Maximum Initial Green
4.4.2.19 Volume Density – Vehicle Extension
4.4.2.19.1 The software shall activate this feature when the user
defines the minimum vehicle extension, maximum vehicle
extension, time before reduction, and time to reduce for a
phase.
4.4.2.20 Minimum Vehicle Extension
4.4.2.21 Maximum Vehicle Extension
4.4.2.22 Time Before Reduction
4.4.2.23 Time To Reduce
4.4.2.24 Walk 2
4.4.2.24.1 If the pedestrian movement is an overlap, the software shall
call the walk 2 defined in the overlap table.
4.4.2.24.2 If this parameter is 0 seconds, thenWalk 1shall be output.
4.4.2.25 Walk 2 Enable Time
4.4.2.26 Pedestrian Clearance 2
4.4.2.26.1 If the pedestrian movement is an overlap, the software shall
call the pedestrian clearance 2 defined in the overlap table.
4.4.2.26.2 If this parameter is 0 seconds, the pedestrian clearance
shall be output.
4.4.2.27 Pedestrian Clearance 2 Enable Time
4.4.2.28 Variable Left Turn Time
4.4.2.29 Last Car Passage
4.5 GLOBAL PHASE PARAMETERS
If a phase is put on recall or walk rest in the Global Phase Parameters table, the phase shall be on
that recall or walk rest regardless of the active plan set table. The phases on recall or walk rest in the
global phase parameters table shall be combined with the phases on recall or walk rest in the plan
set tables. All recalls and walk rests programmed in the active plan set table shall apply regardless
of the programming in the Global Phase Parameters table; the Global Phase Parameters table shall
not prevent these recalls and walk rests from applying.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 19 of 100
4.5.1 The Global Phase Parameters shall always be active.
4.5.2 The user shall be able to define the following phase parameters:
4.5.2.1 Global Minimum Recall
4.5.2.1.1 The Global Minimum Recall shall apply to all plan set tables.
4.5.2.1.2 These recalls shall be applied in addition to existing
minimum recalls in the plan set table.
4.5.2.2 Global Maximum Recall
4.5.2.2.1 The Global Maximum Recall shall apply to all plan set
tables.
4.5.2.2.2 These recalls shall be applied in addition to existing
minimum recalls in the plan set table.
4.5.2.3 Global Pedestrian Recall
4.5.2.3.1 The Global Minimum Recall shall apply to all plan set tables.
4.5.2.3.2 These recalls shall be applied in addition to existing
minimum recalls in the plan set table.
4.5.2.3.3 One pedestrian service shall be provided per cycle; this
recall shall not cause the pedestrian service to recycle.
4.5.2.4 Global Walk Rest
4.5.2.4.1 The Global Walk Rest shall apply to all plan set tables.
4.5.2.4.2 These walk rest phases shall be applied in addition to the
existing walk rest phases in the plan set table.
4.6 PEDESTRIAN OPERATION
4.6.1 The user shall be able to assign the pedestrian movement to any pedestrian
channel.
4.6.2 The user shall be able to associate the pedestrian channel to one phase or
associate the pedestrian channel with many phases.
4.6.3 When a pedestrian call is received, the software shall place a call for all of the
pedestrian movements associated with that phase. The call for a pedestrian
movement shall remain until the walk light is displayed.
4.6.3.1 If the pedestrian movement is an overlap, a walk light displayed for that
pedestrian movement will remove the call no matter which phase was
active when the walk was output.
4.6.3.2 If the walk light is currently being displayed, the pedestrian call shall be
ignored.
4.6.3.3 If the pedestrian clearance is currently being displayed, the pedestrian
call shall not be ignored.
4.6.4 The software shall provide an alternative pedestrian interval when a condition,
programmed using the software’s logic functions, is met.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 20 of 100
4.6.4.1 The software must provide an alternative pedestrian walk interval when
the push button is depressed for a user defined amount of time in
seconds.
4.6.5 The software shall immediately begin clearing the active pedestrian phase if a
preemption input is received.
4.6.5.1 This shall not apply if a request for partial priority is received.
4.6.6 The software shall allow for an exclusive pedestrian service phase.
4.6.7 The software shall be capable of outputting a Walk Rest for any pedestrian
phase.
4.6.7.1 Walk Rest shall not delay the end of the compatible vehicle phase green.
4.6.8 The software shall allow for a pedestrian Barnes’ Dance interval.
4.6.8.1 All pedestrian movements will display a walk and all vehicle displays will
remain red.
4.6.8.2 Pedestrians may be allowed to cross diagonally.
4.6.9 The software shall allow the user to define the number of times a pedestrian
interval will be served for each pedestrian call.
4.6.9.1 The user defined number of times will also serve as the maximum number
of pending pedestrian calls. Additional pedestrian calls shall not exceed
this maximum.
4.6.9.2 The user shall be able to define this for each pedestrian movement.
4.7 LEFT TURN OPERATION
4.7.1 The software shall allow the user to vary the mode of left turn operation by
time of day/day of week.
4.7.2 The software shall allow the user to vary the mode of left turn operation within
a timing plan.
4.7.3 The software shall be capable of operating a flashing yellow arrow left turn
display or a flashing red arrow left turn display in protected only,
protected/permitted, and permitted only modes as defined in the Texas Manual
of Uniform Traffic Control Devices.
4.7.4 The software shall be capable of operating a five section left turn.
4.7.4.1 The software shall be capable of operating a Dallas Left Turn display. The
software shall provide the following modes of left turn operation.
4.7.4.1.1 Permitted Only
4.7.4.1.2 Protected/Permitted
4.7.4.1.3 Protected Only
4.8 RIGHT TURN OPERATION
4.8.1 The software shall allow the user to vary the mode of right turn operation by
time of day/day of week.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 21 of 100
4.8.2 The software shall allow the user to vary the mode of right turn operation
within a timing plan.
4.8.3 The software shall be capable of operating a flashing yellow arrow right turn
display or a flashing red arrow right turn display in protected only,
protected/permitted, and permitted only mode as defined in the Texas Manual
of Uniform Traffic Control Devices.
4.8.4 The software shall be capable of providing a green arrow for a right turn
movement unless the parallel pedestrian movement is called. If the parallel
pedestrian movement is active, the controller will output a flashing yellow
arrow to the right turn display during the pedestrian interval. After the
pedestrian interval is finished timing, the software shall provide a green arrow
for the right turn movement as long as the green arrow can be displayed for at
least the active minimum green for the overlap.
4.8.4.1 If the pedestrian phase will be serviced while the controller is outputting a
green arrow to the right turn display, the controller will immediately end
the green arrow by outputting a solid yellow arrow, and then a flashing
yellow arrow. The pedestrian walk shall not output until the right turn
overlap has finished clearing.
4.8.4.2 Right Turn Red Indication.
4.8.4.2.1 By default a steady red indication shall not be displayed if
the green arrow is clearing for a pedestrian movement
(green arrow, solid yellow arrow, flashing yellow arrow).
The software shall be capable of displaying the red
indication during the pedestrian interval if the user
chooses.
4.8.4.2.2 If the all-red is omitted, the flashing yellow arrow and walk
indication shall begin simultaneously immediately after the
solid yellow indication.
4.8.4.2.3 The user shall be able to enable the all-red duration interval
defined in the phase parameter table.
4.8.4.2.4 The user shall be able to enable displaying the red arrow
during the pedestrian interval for a user defined amount of
time in seconds.
This shall be distinct from the all-red clearance for that
right turn.
4.9 PEDESTRIAN HYBRID BEACON OPERATION
4.9.1 The software shall allow for full operation of a Pedestrian Hybrid Beacon as
described in the 2009 MUTCD, Chapter 4F.
4.9.2 The software shall operate the three-head vehicle indications (two red circular
indications set horizontally over one yellow circular indication) and standard
pedestrian heads.
4.9.3 The sequence for the Pedestrian Hybrid Beacon shall be as follows:
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 22 of 100
4.9.3.1 All vehicle heads shall remain dark until the pedestrian activates the
pedestrian push button. Pedestrian heads shall display a solid Don’t Walk
during times when the vehicle heads are not illuminated.
4.9.3.2 Vehicle heads shall flash yellow upon activation of the pedestrian push
button. Pedestrian heads shall display solid Don’t Walk indications.
4.9.3.3 Vehicle heads shall display a steady yellow indication. Pedestrian heads
shall display solid Don’t Walk indications. The will serve as the yellow
clearance interval.
4.9.3.4 Vehicle heads shall display a steady red indication in both red heads in
the three-head display. Pedestrian indications shall display a solid Don’t
Walk indication. This will serve as the all-red interval.
4.9.3.5 Vehicle heads shall display a steady red indication in both red heads in
the three-head display. Pedestrian indications shall display a Walk
indication. This will serve as the pedestrian walk interval.
4.9.3.6 Vehicle heads shall display alternating flashing red indications for the two
red heads in the three-head display. Pedestrian indications shall display
a Flashing Don’t Walk indication. This will serve as the pedestrian
clearance interval.
4.9.3.7 Following pedestrian clearance interval, the vehicular heads will all go
dark in the absence of any pedestrian service calls. The cycle will start
over at the next pedestrian service request.
4.9.4 The software shall operate the Pedestrian Hybrid Beacon in coordination with
adjacent traffic signals. The user shall be able to define the period in the local
cycle when the Pedestrian Hybrid Beacon may activate.
4.10 PHASE SEQUENCE
4.10.1 General
4.10.1.1 The user shall select the order of the phases.
4.10.1.2 The user shall be able to change the order of the phases without making
changes to the ring/barrier structure programmed.
4.10.1.3 The phase sequence defined in the active plan set shall not override other
special functions.
4.10.2 Pre-Signal Sequence
4.10.2.1 The software shall be able to output the following sequence:
4.10.2.1.1 Green
4.10.2.1.2 Yellow clearance
4.10.2.1.3 All-red clearance
4.10.2.1.4 Red flash – The software shall output a red flash while the
channel is not active.
4.10.2.1.5 Solid red
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 23 of 100
Once the pre-signal changes to solid red it shall remain
solid red until the pre-signal turns green; it cannot revert
to flashing red.
4.10.2.2 The pre-signal shall change to solid red after
4.10.2.2.1 A user defined after of time
4.10.2.2.2 A queue detector is active
4.10.2.3 The user shall be able to activate this sequence by time of day/day of
week.
5 OVERLAPS
5.1 GENERAL
5.1.1 The software shall support a minimum of 20 total overlaps.
5.1.1.1 Each of the 20 overlaps can be programmed as either a vehicle overlap or
pedestrian overlap.
5.1.2 The software shall provide a user definable text label for each overlap. The
text label shall be a minimum of 18 characters.
5.1.3 The software shall provide templates the following types of overlaps:
5.1.3.1 NTCIP normal
5.1.3.2 Dallas phasing left turn
5.1.3.3 3-Section flashing yellow arrow permissive left turn
5.1.3.4 4-Section flashing yellow arrow protective/permissive left turn
5.1.3.5 Arlington phasing left turn
5.1.3.6 3-Section flashing red arrow permissive left turn
5.1.3.7 4-Section flashing red arrow protective/permissive left turn
5.1.3.8 Right turn overlap
5.1.3.9 4-Section flashing yellow arrow protective/permissive right turn
5.1.3.10 Pedestrian overlap
5.1.3.11 Pre-signal overlap
5.1.4 The software shall allow the user to program a minimum of eight (8) overlap
tables.
5.1.4.1 A call to a pedestrian overlap shall place a call on all parent phases
associated with the pedestrian overlap.
5.2 OVERLAP CONFIGURATION
5.2.1 The software shall provide the following overlap configuration settings for each
of the 20 overlaps:
5.2.1.1 Overlap identifier
5.2.1.1.1 Identifies which overlap (1-20) is being programmed
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 24 of 100
5.2.1.2 Enable
5.2.1.3 Overlap type
5.2.1.4 Omit
5.2.1.5 Pedestrian
5.2.1.5.1 Identifies this overlap has a pedestrian movement
associated with it
5.2.1.6 Pedestrian Overlap Walk 1
5.2.1.7 Pedestrian Overlap Walk 2
5.2.1.8 Pedestrian Overlap Clearance 1
5.2.1.9 Pedestrian Overlap Clearance 2
5.2.1.10 Primary Parent Phases
5.2.1.11 Negative Parent Phases
5.2.1.11.1 Negative Parent Phases are phases that the overlap is not
allowed to time a concurrent green indication with. A
negative phase will not cause an active overlap to turn red.
5.2.1.12 Inhibit Negative Vehicle Phases
5.2.1.13 Negative Pedestrian Phases (see operational scenario 5.4.1)
5.2.1.13.1 These pedestrian phases, when active, shall prevent the
overlap from displaying a green. A pedestrian phase will be
prevented from changing to walk while the overlap is active.
5.2.1.13.2 This feature will cause the programmed overlap to
immediately begin yellow clearance if the controller is going
to immediately serve the pedestrian phase.
5.2.1.13.3 The controller shall not output a walk for the pedestrian
phase until the programmed overlap is no longer active.
5.2.1.13.4 The negative pedestrian phase will not cause an active
pedestrian phase to end.
5.2.1.14 Negative Overlaps
5.2.1.14.1 Overlap the programmed overlap is NOT allowed to time
with.
5.2.1.15 Green Omit
5.2.1.16 Overlap Suppression Phases
5.2.1.16.1 These vehicle phases, when green, will prevent the output of
the overlap green. The overlap will output green once the
phase turns yellow.
5.2.1.16.2 This feature will cause an active overlap to immediately
begin clearing.
5.2.1.17 Yellow Flash
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 25 of 100
5.2.1.17.1 Programs the overlap to flash yellow, instead of flashing red,
during programmed flash operation and startup flash
operation.
5.2.1.18 Flash-Red During Inactive
5.2.1.18.1 Enables the functionality described in 5.4.2.1.1 below.
5.2.1.19 Alternate Hertz Flash
5.2.1.19.1 Causes overlaps to flash on the alternate half cycle from
other phases and overlaps not configured for alternate flash
hertz during programmed and start up flash operation.
5.3 OVERLAP TIMING PARAMETERS
5.3.1 Minimum Green
5.3.1.1 The overlap shall not terminate while this interval is timing.
5.3.1.2 If this parameter is 0 seconds, the active minimum green for the active
compatible phase shall apply.
5.3.2 Green Extension
5.3.2.1 Maximum length of time the overlap can be extended.
5.3.3 Green Clear
5.3.3.1 Amount of time the overlap will remain green after the last parent phase
starts to terminate.
5.3.4 Yellow Clearance
5.3.4.1 The yellow clearance shall be 0.0 seconds through 25.5 seconds.
5.3.4.2 The yellow clearance programmed in the overlap table shall override the
yellow clearance programmed in the phase parameters table.
5.3.4.3 The software shall not output a yellow interval shorter than the user
defined value.
5.3.4.4 The software shall not display a yellow interval 0.1 seconds longer than
the user defined value.
5.3.5 Red Clearance
5.3.5.1 The all-red clearance shall be 0.0 seconds through 25.5 seconds.
5.3.5.2 The all-red clearance programmed in the overlap table shall override the
all-red clearance programmed in the phase parameters table.
5.3.5.3 The software shall not output an all-red interval shorter than the user
defined value.
5.3.5.4 The software shall not output an all-red interval 0.1 seconds longer than
the user defined value.
5.3.6 Pedestrian Overlap Walk 1
5.3.6.1 Length of time the walk indication will be displayed for the overlap.
5.3.6.2 The software shall be capable of truncating the walk if there is a request
for priority or preemption.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 26 of 100
5.3.6.3 The walk programmed in the overlap table shall override the walk
programmed in the phase parameter table.
5.3.7 Pedestrian Overlap Walk 2
5.3.7.1 Length of time the walk indication will be displayed for the overlap.
5.3.7.2 The software shall be capable of truncating the walk if there is a request
for priority or preemption.
5.3.7.3 The walk programmed in the overlap table shall override the walk
programmed in the phase parameter table.
5.3.8 Pedestrian Clearance 1
5.3.8.1 Length of time the pedestrian clearance will be displayed for the overlap.
5.3.8.2 The software shall be capable of truncating the pedestrian clearance
interval if there is a request for priority or preemption.
5.3.8.3 The pedestrian clearance programmed in the overlap table shall override
the pedestrian clearance programmed in the phase parameter table.
5.3.8.4 The software shall turn the input on and then off every one-half second for
the duration of the clearance interval.
5.3.8.5 The pedestrian clearance shall time with the compatible overlap’s green
clearance.
5.3.8.6 The pedestrian clearance shall not increase the length of an overlap’s
green clearance. If there is not enough time for the pedestrian interval,
the software shall delay the ending of the parent phase.
5.3.9 Pedestrian Clearance 2
5.3.9.1 Length of time the pedestrian clearance will be displayed for the overlap.
5.3.9.2 The software shall be capable of truncating the pedestrian clearance
interval if there is a request for priority or preemption.
5.3.9.3 The pedestrian clearance programmed in the overlap table shall override
the pedestrian clearance programmed in the phase parameter table.
5.3.9.4 The software shall turn the input on and then off every one-half second for
the duration of the clearance interval.
5.3.9.5 The pedestrian clearance shall time with the compatible overlap’s green
clearance.
5.3.9.6 The pedestrian clearance shall not increase the length of an overlap’s
green clearance. If there is not enough time for the pedestrian interval,
the software shall delay the ending of the parent phase.
5.3.10 Reservice
5.3.10.1 Minimum amount of red time that the overlap must display before it can
restart.
5.4 OVERLAP OPERATIONS
5.4.1 Right turn arrow overlap with pedestrian service
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 27 of 100
5.4.1.1 When a right turn overlap is in conflict with a pedestrian phase or overlap,
there shall be two possible programmable actions that can occur:
5.4.1.1.1 If a pedestrian call is received while the right turn overlap is
active, the user may select to have the right turn overlap
immediately terminate IF there is adequate time remaining to
clear the overlap and then immediately serve the pedestrian
within the parent phase time remaining without causing
transition.
5.4.1.1.2 If a pedestrian call is received while the right turn overlap is
active, the user may select to have the right turn continue for
its programmed time and the pedestrian will be served
during its next available parent’s programmed time.
5.4.2 Pre-Signal Overlap
5.4.2.1 The software shall provide the following functionality for pre-signal
overlap operation:
5.4.2.1.1 The overlap shall be capable of outputting a solid green,
solid yellow, solid red, flashing red, solid red sequence.
Green, yellow and all-red will output when the parent phases
are active; flashing red and solid red will output when the
parent phases are not active.
5.4.2.1.2 While parent phases are not active, the user shall be able to
define the number of seconds the red indications flash
before going to solid red, or shall be controlled by a queue
detector input.
5.4.2.1.3 Once the solid red is displayed the pre-signal shall display
solid red until the next green.
5.4.3 Pedestrian Overlaps
5.4.3.1 The pedestrian interval shall time with the parent phases listed in the
active overlap table. Once a pedestrian movement is programmed as an
overlap, the pedestrian walk and clearance values in the overlap table
shall be output.
5.4.3.2 If the Walk 2 Enable Time or Pedestrian Clearance 2 Enable Time is
satisfied, the Walk 2 and Pedestrian Clearance 2 programmed in the
overlap table shall be output.
5.4.3.3 The available time for the pedestrian service shall be from the beginning
of the first parent phase to the end of the last parent phase.
5.4.3.4 The pedestrian shall be serviced if a call is received while any parent
phase is active and there is enough time to clear conflicting overlaps and
serve the pedestrian before the end of the last parent phase.
5.4.3.5 The last parent phase will not be allowed to terminate until the pedestrian
clearance interval has finished. Other parent phases shall be allowed to
end early.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 28 of 100
5.4.3.6 The software shall be capable of outputting a walk rest for any pedestrian
overlap.
5.4.3.6.1 The user shall be able to select walk rest for the pedestrian
overlap.
5.4.3.6.2 This feature will ensure the walk rest time and pedestrian
clearance time fit within the parent phase times.
5.4.3.6.3 When in walk rest, the ped overlap shall run concurrently
with all vehicle parent phases without the user having to
explicitly identify walk with each parent phase.
5.4.3.7 The software shall allow the Walk 2 interval to be programmed for each
overlap.
5.4.3.7.1 The software must provide an alternative pedestrian interval
when the push button is depressed for an extended period of
time. The user will define the number of seconds required to
activate the alternative Pedestrian.
6 SCHEDULE
6.1 GENERAL
6.1.1 The software shall provide the following four schedule types:
6.1.1.1 Time of Day/Day of Week
6.1.1.2 Holiday
6.1.1.3 Seasonal
6.1.1.4 Temporary
6.1.2 The software shall automatically sort the schedule chronologically by the time
of day entry.
6.1.3 The software shall allow the enabling or disabling of any event in the schedule.
6.1.4 Each scheduled event shall completely define the current operation.
Scheduled events shall not be cumulative.
6.1.5 All schedule events shall be logged.
6.1.6 The schedule types shall be prioritized as follows (highest to lowest):
6.1.6.1 Holiday – overrides all other schedule types.
6.1.6.2 Temporary – overrides seasonal and active Time of Day/Day of Week
schedule.
6.1.6.3 Seasonal – Overrides active Time of Day/Day of Week schedule.
6.1.6.4 Active Time of Day/Day of Week.
6.2 TIME OF DAY/DAY OF WEEK SCHEDULE (TOD/DOW)
6.2.1 The software shall support at least 32 events in each schedule that can be
activated by Time of Day/Day of Week.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 29 of 100
6.2.2 The Software shall support a minimum of 16 Time of Day/Day of Week
Schedules.
6.2.3 The schedule shall allow the user to schedule, as a minimum, any of the
following operational modes:
Plan Set
Yellow Flash
All-red Flash
Free
6.2.4 Each Time of Day/Day of Week Schedule shall include the following user
defined parameters:
6.2.4.1 Enable/disable event
6.2.4.2 Event start time
6.2.4.2.1 The time of day will be in military time.
6.2.4.2.2 The user shall be able to define the hour and minute of the
event.
6.2.4.3 Day of Week
6.2.4.4 Action (i.e. Plan Set, flash, free)
6.2.4.5 Description of schedule event
6.2.4.5.1 The field will allow 48 characters for descriptive message.
6.3 HOLIDAY SCHEDULE
6.3.1 The software shall support fixed and floating holidays.
6.3.2 The user shall be able to schedule holiday events at least one year in
advance.
6.3.3 The user shall be able to define a minimum of five (5) days on either side of
the holiday as part of the holiday event.
6.3.4 The user shall be able to sort the holiday schedule by month and day
6.3.5 The holiday schedule shall provide the following user defined parameters:
6.3.5.1 Enable/disable event
6.3.5.2 Fixed holiday date
6.3.5.3 Number of days prior holiday
6.3.5.4 Number of days after holiday
6.3.5.5 Required Action (i.e. activate new TOD Schedule)
6.3.5.6 Floating holiday month
6.3.5.7 Floating holiday week
6.3.5.8 Floating holiday day
6.3.5.9 Description of schedule event
6.3.5.9.1 This field will allow a minimum of 48 characters for a
descriptive message
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 30 of 100
6.4 SEASONAL SCHEDULE
The seasonal schedule shall allow the user to disable certain events in the Time of Day/Day of Week
schedule. During the summer, when school is not in session, the City will use this feature to disable
the events in the schedule that call the signal timing plans for school.
6.4.1 The software shall allow the scheduling of a minimum of 10 seasonal events.
These events shall activate a different Time of Day/Day of Week schedule
based on the current time of the year.
6.4.2 The user shall be able to schedule seasonal events for the entire year and at
least one year in advance.
6.4.3 The seasonal schedule shall provide the following user defined parameters
6.4.3.1 Enable/disable event
6.4.3.2 Start month of seasonal schedule
6.4.3.3 Start day of seasonal schedule
6.4.3.4 End month of seasonal schedule
6.4.3.5 End day of seasonal schedule
6.4.3.6 Required Action (i.e. activate new TOD Schedule)
6.4.3.7 Description of schedule event
6.4.3.7.1 This field will allow a minimum of 48 characters
6.5 TEMPORARY SCHEDULE
6.5.1 The user shall be able to schedule events that will expire after a user defined
time period.
6.5.1.1 This feature shall be off by default.
6.5.2 Upon completion of the time period, the software shall revert back to the
default schedule and alarm the user the time period has expired.
6.5.2.1 The user shall select if the software will revert back to the default
schedule. By default the software shall revert back to the default
schedule.
6.5.2.2 The user shall select if the software will alarm the user. By default the
software shall alarm the user.
6.5.2.3 The user shall be able to extend the amount of time the temporary
schedule runs. After the extension the requirements for reverting back
and alarming the user listed above shall apply.
6.5.3 The software shall support a minimum of four (4) temporary schedule events.
These events shall activate a different Time of Day/Day of Week schedule.
6.5.4 The user shall be able to schedule any of the following operational modes:
6.5.4.1 Plan Set
6.5.4.2 Free
6.5.4.3 Yellow Flash
6.5.4.4 All-red Flash
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 31 of 100
6.5.5 Upon completion of the last time period, the user shall be able to choose if the
temporary schedule shall be deleted.
6.5.5.1 The software shall prompt the user.
6.5.6 The temporary schedule shall provide the following user defined parameters:
6.5.6.1 Start day of temporary schedule
6.5.6.2 Start Time of temporary schedule
6.5.6.3 End Day of temporary schedule
6.5.6.4 End Time of temporary schedule
6.5.6.5 Required action (i.e. activate new TOD schedule)
6.5.6.6 Description of temporary schedule
6.5.6.6.1 This field will contain a minimum of 48 characters.
7 COORDINATION
7.1 GENERAL
7.1.1 Software shall provide a minimum of 32 locally stored timing plan sets.
7.1.1.1 The user shall be able to label each timing plan; each text label shall be
at least six characters in length.
7.1.2 The software shall not activate the coordinator on start-up until the start-up
vehicle and pedestrian phases programmed by the user have been serviced.
7.1.3 Upon entry of any phase parameter, special function, internal clock update,
coordination change, or other adjustment the coordinator shall automatically
recognize the change and activate at the beginning of the next cycle.
7.1.4 The controller shall read the coordination parameters, special function,
detector settings, and overlap changes at the same time. Detection and
overlap programming changes shall occur at the beginning of the new timing
plan.
7.1.5 The offset reference point shall be user selectable,
7.1.5.1 The user shall be able to select any of the following reference points:
7.1.5.1.1 Beginning of yellow of the coordinated phases
7.1.5.1.2 Beginning of green of the coordinated phases
7.1.5.1.3 End of all-red clearance of the coordinated phases
7.1.5.2 The default offset reference point shall be the beginning of yellow for the
coordinated phases.
7.2 COORDINATION PARAMETERS
7.2.1 The user shall be able to enter the following coordination parameters.
7.2.1.1 Cycle Length
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 32 of 100
7.2.1.1.1 If the cycle length is 0 seconds, the software shall run free
while that plan is called by the daily schedule or a manual
command. If a split is entered for any phase, the value
entered by the user shall be the active maximum green time
for that phase. If the split is zero (0) seconds, the active
maximum green shall apply.
7.2.1.2 Phase Splits
7.2.1.2.1 Nominal phase split – split time active when controller is not
in transition.
7.2.1.2.2 Minimum phase split – minimum split time allowed when
controller is transitioning.
7.2.1.2.3 Maximum phase split – maximum split time allowed when the
controller is transitioning.
7.2.1.2.4 Global percent adjustment – global feature to be used in
place of minimum and maximum split times that will allow all
active phases to be adjusted by the user defined percentage
during transition.
7.2.1.3 Offset Reference Point
7.2.1.4 Offset
7.2.1.4.1 Offset value is entered in seconds.
7.2.1.5 Coordinated Phases – user identified coordinated phases
7.2.1.6 Inhibit Maximum
7.2.1.7 Transition Type
7.2.1.7.1 The user shall enter the preferred transition mode and
number of cycles to transition.
7.2.1.7.2 Transition mode options shall include: short way, long way,
dwell and auto. Auto option shall be the controller
calculated quickest way to return to coordinated operation
whether it is short way or long way.
7.2.1.7.3 The controller shall adjust faster than the programmed
number of cycles if an adjustment less than the maximum is
required.
7.2.1.7.4 The software shall proportionally reduce or increase each
split during transition within the minimum and maximum
values set for phases if the user has defined these.
7.2.1.7.5 The transition time shall be proportionally distributed to all
phases.
7.3 PEDESTRIAN SERVICE
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 33 of 100
7.3.1 Pedestrian phases shall be serviced without entering free mode even if the
pedestrian walk and clearance interval is longer than the vehicle phase split.
When the pedestrian phase is longer, the software shall provide three options:
(1) steal time from the preceding phase, (2) steal time from the subsequent
phase, or (3) the local cycle will pause. The software shall allow the user to
use all three options at once to accommodate a pedestrian phase.
7.3.1.1 The software shall allow the user to define the amount of time in seconds
stolen from the preceding phase.
7.3.1.2 The software shall allow the user to define the amount of time in seconds
stolen from the subsequent phase.
7.3.1.3 If pedestrian adjust is enabled, the local cycle shall pause at the end of
the phase associated with the pedestrian movement for the additional
amount of time needed to finish the pedestrian clearance.
7.3.1.4 If pedestrian adjust is not enabled, the additional amount of time needed
to serve the pedestrian phase shall be stolen from the subsequent
phases. The time shall be in addition to the user defined value.
7.3.1.4.1 The pedestrian phase shall not be omitted during normal
operation. A pedestrian call shall not cause the coordinated
timing plan to fail.
7.3.1.5 If the extra time is required to serve the pedestrian phase, the amount of
time stolen from other phases shall be evenly split between the preceding
and subsequent phases unless the user did not enter a high enough
number in the stolen phase parameters.
7.3.1.5.1 If the user did not enter enough time and pedestrian adjust
is enabled, the local cycle shall pause. If pedestrian adjust
is not enabled the time shall be stolen from the subsequent
phases.
7.3.2 Pedestrian Adjust
7.3.2.1 The user shall be able to enable this feature that will pause the local cycle
until the pedestrian interval has finished if the pedestrian movement is
still active after the programmed force off for the compatible vehicle
phase. The software shall immediately begin transition by shortening the
phases remaining in that cycle.
7.3.2.2 When enabled, the local cycle shall pause for the amount of time needed
to serve the pedestrian movement less the time stolen from the preceding
phase and the subsequent phase.
7.3.3 If the pedestrian phase ends the preceding phase early, the concurrent vehicle
phase shall begin early with the pedestrian phase.
7.3.4 If the pedestrian phase is not requested until the clearance interval of the
preceding phase, the pedestrian phase will still begin with the concurrent
vehicle phase.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 34 of 100
7.3.5 If the pedestrian phase requires more time than the compatible vehicle phase,
the call for the pedestrian phase must be received before the beginning of the
concurrent vehicle phase; otherwise, the pedestrian phase shall not be served
during that green.
7.3.6 If the pedestrian phase called requires less time than the compatible vehicle
phase that is currently green and will not delay the end of the phase, the
pedestrian phase, when called, shall be requested immediately and serviced
as soon as any conflicting outputs have finished clearing.
7.4 PEDESTRIAN SERVICE PARAMETERS
7.4.1 Enable pedestrian adjust
7.4.2 Time stolen from preceding phase
7.4.2.1 This value shall be zero by default.
7.4.2.2 Entering a non-zero value shall activate this feature.
7.4.3 Time stolen from the subsequent phase
7.4.3.1 This value shall be zero by default.
7.4.3.2 Entering a non-zero value shall activate this feature.
7.5 COORDINATED OPERATIONS (USE CASES)
7.5.1 Recycle left turn – software shall recycle the leading left turn phase if all of the
following conditions are met:
7.5.1.1 The oncoming through phase has received its full minimum green time,
7.5.1.2 There is time to provide a minimum service to the left turn before the end
of the permitted period, and
7.5.1.3 There is a vehicle call for that left turn phase.
7.5.1.4 This will provide a second left turn service if more vehicles arrive within
the permitted period after the initial leading left turn service has ended.
The user shall select if this feature is enabled.
7.5.2 Backup into the leading left turn
7.5.2.1 If there is no call for the leading left turn, the software shall skip the left
turn phase and serve the oncoming through traffic.
7.5.2.2 If a call for the skipped left turn is received prior to the end of the
permitted period, the software shall serve the skipped left turn phase as
long as the oncoming through movement has received its full minimum
green time.
7.5.2.3 The user shall select if this feature is enabled.
7.5.3 Optional leading left turn – software shall provide a leading left turn phase if
all of the following conditions are met:
7.5.3.1 The minor street returns to the main street early,
7.5.3.2 There is enough time remaining in the side street split to provide a full
minimum service for the main street left turn phase, and
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 35 of 100
7.5.3.3 There is a call for the main street left turn.
7.5.3.4 The user shall select if this feature is enabled.
7.5.4 Double serve side streets – when the side street returns early to the main
street, the software shall allow the minor street phases to recycle if all of the
following conditions are met:
7.5.4.1 The main street has received its full minimum service,
7.5.4.2 There is enough time remaining in the permitted period for the minor
street to serve a full minimum vehicular service, and
7.5.4.3 There is a call for the minor street phase.
7.5.4.4 The software shall operate fully actuated during the permitted period for
the minor street and shall only serve the minor street or main street
through phases.
7.5.4.5 The main street leading left turn shall not be permitted until the minor
street phase omit has been applied because the permitted window is
about to close.
7.5.4.6 The user shall select if this feature is enabled.
7.5.5 Free mode operation within the coordinated cycle
7.5.5.1 While operating in coordinated mode, the software shall provide the
option to operate a portion of the cycle in free mode.
7.5.5.2 The user shall be able to define two (2) free mode periods within one (1)
cycle.
7.5.5.3 The user shall select the beginning of the free mode operation, the end of
the free mode operation and the phases that may be active.
7.5.5.4 At the end of the free mode period, the active phases shall force off if
they are not the first coordinated phases.
7.5.6 Optional lagging left turn
7.5.6.1 The software shall allow the user to provide a lagging left turn if the active
extension time for the oncoming through is 0.0 seconds.
7.5.6.2 The user shall enter the number of seconds the oncoming through phase
may end early.
7.5.6.3 The lagging left turn shall end the same second of the local cycle that the
oncoming through would have ended.
7.5.6.4 The user shall select if this feature is enabled.
7.5.7 Phase recycle with split phase
7.5.7.1 When a minor street is split phased, the software shall allow the user to
recycle the minor street phases before returning to the main street phases
as long as there are calls for the side street phases and there is enough
time to provide a minimum split for the phase.
7.5.7.2 Once there are no longer any calls on the minor street, the user may
choose to hold in the minor street or return to the main street phases.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 36 of 100
7.5.7.3 Once the permitted window for the minor street has ended, the controller
shall return to the main street phases.
7.5.7.4 The software shall be capable of providing this operation during two
distinct periods each cycle.
7.5.8 Optional service with split phase
7.5.8.1 When a minor street is split phase and the software is programmed to
serve only one minor street phase before returning to the main street, the
software shall allow the user to serve the other minor street phase before
returning to the main street as long as there is a call and there is enough
time to provide a minimum split for the phase.
7.5.8.2 The software shall be capable of providing this operation during two
distinct periods each cycle.
8 PREEMPTION
8.1 GENERAL
8.1.1 The software shall provide a minimum of 12 unique programmable preemption
sequences.
8.1.2 The software shall provide the following types of preemption:
8.1.2.1 Railroad
8.1.2.2 Emergency Vehicle
8.1.3 The user to shall be able to program any preemption sequence as a railroad or
emergency vehicle type.
8.1.4 The user shall be able to label each unique preemption sequence.
8.1.4.1 Each label shall be at least eight (8) characters in length
8.1.5 The user shall be able to delay the preemption input.
8.1.6 The software shall be able to smoothly transition from one preemption table to
another.
8.1.7 The user shall be able to input the preemption input into the logic functions
and output the result.
8.1.8 The user shall be able to activate warning lights, blank out signs, and other
auxiliary devices during a preemption sequence.
8.1.8.1 The user shall be able to turn on and off the devices using logic function
outputs.
8.1.8.2 A minimum of eight (8) special outputs shall be provided.
8.1.8.3 The user shall be able to activate each special output at any time during
the preemption event.
8.1.8.3.1 The user will be able to assign an internal logic pin to the
special output and use the output in logic statements.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 37 of 100
8.1.8.3.2 The user will be able to assign an external logic pin to the
special output to activate field equipment while the special
pin is active.
8.1.8.3.3 The user shall be able to activate an auxiliary field device
transition table.
8.1.9 The software shall automatically reset the maximum duration timer if the
preempt input goes off and then comes back on during the dwell state.
8.1.10 The software shall not recycle the preempt entry phases. If phases defined as
entry phases are green, they shall remain green
8.1.11 The software shall not recycle the return phases. If the return phases are
green, they shall remain green.
8.1.12 The active coordinated timing plan shall continue to run in the background
during the preemption event. The coordinated timing plan shall have no effect
on the signal operation while the preemption is active.
8.1.13 The user shall be able to change the mode of operation for any traffic signal
display when a preemption input is received. This function will allow the user
to change selected overlaps to red at any time during the preemption event.
8.1.14 The software shall provide multiple preemption exit options. The user shall be
able to select the exit routine for each preemption sequence. The exit options
shall include:
8.1.14.1 The user shall be able to place calls on selected phases upon exiting
preemption.
8.1.14.2 Queue Delay Recovery - The software shall support a return to the phase
with demand the longest wait time. The user shall be able to set the
priority level for each phase.
8.1.14.3 First Phase Skipped - The software shall support a return to the first
phase skipped. A skipped phase shall also include a phase that received
a minimum green immediately preceding the preempt.
8.1.14.3.1 If the phase received more than the minimum time it will not
be considered the first phase skipped.
8.1.14.4 Exit to Coordination/Normal Operation - The software shall support an
immediate return to the place in the coordinated cycle where the software
would have been had there been no preempt.
8.1.14.4.1 Once the preemption input turns off, the software shall hold
in the active phases until the software has read the
applicable coordination parameters and checked the inputs
from the detectors.
8.1.14.4.2 The software shall not recycle the clearance phases. If the
clearance phase should be active, those phases shall
remain green.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 38 of 100
8.1.14.4.3 After the preemption the overlaps will begin following the
parent phases again and shall turn green if their parent
phase is green.
8.1.14.5 Exit to Alternate Maximum Times - The software shall support return to
alternate maximum times for each vehicle phase if the software is
operating in free mode.
8.1.14.5.1 The user shall be able to designate the duration in minutes
(0 to 60) for how long to operate the alternate maximum
times. The software shall return to normal operation at the
top of the cycle following the exit to alternate maximum time
being exceeded.
8.2 PREEMPT STATES
8.2.1 The software shall report the status of the preemption sequence using the
following states:
8.2.1.1 The preemption sequence is not active.
8.2.1.2 The minimum presence timer is active.
8.2.1.3 The preempt service delay timer is active.
8.2.1.4 The preempt service is timing the Entry 1 phases.
8.2.1.5 The preempt service is timing the Entry 2 phases.
8.2.1.6 The preempt service is timing the Dwell phases.
8.2.1.7 The preempt service is timing the exit phases.
8.2.1.8 The preempt service maximum duration timer has expired.
8.3 PREEMPTION PRIORITY
8.3.1 The software shall automatically assign a high or low priority level to each
enabled preemption event based on the preemption type.
8.3.2 For each preemption type, the user shall be able to assign an equal or lower
priority to each preemption event.
8.3.3 The software shall automatically assign the high priority level to any
preemption event enabled as a railroad type.
8.3.3.1 All railroad preemption events shall have equal priority.
8.3.4 The software shall not allow an emergency vehicle preempt event to be
programmed with a higher priority than a railroad preempt.
8.3.5 The software shall automatically assign the low priority level to any preemption
event enabled as an emergency vehicle type.
8.3.5.1 By default, all emergency vehicle preemption events shall have equal
priority.
8.3.5.2 The user shall be able to program up to four (4) emergency vehicle
preemption priority levels.
8.3.6 High priority preempts shall override low priority preempts.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 39 of 100
8.3.6.1 A request for a high priority preemption event shall immediately cancel
any active low priority preemption event and begin the high priority event.
8.3.7 Low priority preempts shall be ignored until the high priority preempt
terminates.
8.3.7.1 The low priority event shall begin running in the background. Once the
inputs for high priority event terminates the high priority event
immediately end and the low priority event shall output its current state.
8.3.7.2 Any part of the high priority event that occurs after the high priority event
input terminates shall be cancelled. The software shall immediately
output the current state of the low priority preemption sequence.
8.3.8 Equal priority preempts shall be served on a first called, first served basis.
8.3.8.1 The second preemption sequence shall begin running in the background.
Once the inputs for first preemption sequence turn off the first sequence
shall immediately end and second preemption sequence shall output its
current state.
8.3.8.2 Any part of the first preemption sequence that occurs after the first
preemption input turns off will be cancelled. The software shall
immediately output the second preemption sequence.
8.4 RAILROAD PREEMPTION
8.4.1 The software shall support the configuration of the following modes of Railroad
preemption:
8.4.1.1 Normal
8.4.1.1.1 Normal preemption mode shall terminate all active vehicle
and pedestrian phases and begin the clearance phases.
8.4.1.2 Smooth
8.4.1.2.1 Smooth preemption mode shall allow the user to define each
step in the preemption sequence. During each step the user
shall be able to define which vehicle and pedestrian phases
are permitted, called and extended.
8.4.2 The software shall accept a minimum of four (4) unique inputs from the
railroad.
8.4.3 Train preemption shall be provided when the software is running programmed
all-red and yellow-red flash.When the preemption input is received, the
software shall change the phases flashing yellow to steady green and then
begin preemption.
8.4.4 The entry phase shall not terminate until the railroad gates are in the
lowered/down position.
8.4.4.1 The entry phases shall terminate based on the following user defined
options:
8.4.4.1.1 Gate active/down input from the railroad
8.4.4.1.2 Maximum clearance time input for the entry phases.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 40 of 100
8.4.5 The user shall be able to program the intersection to operate in yellow or all-
red flash during the Dwell phase interval.
8.5 EMERGENCY VEHICLE PREEMPTION
8.5.1 The software shall support the following types of emergency vehicle
preemption systems:
8.5.1.1 Line-of-sight infrared
8.5.1.2 Global Positioning Satellite (GPS)
8.5.2 The software shall accept at least six (6) unique inputs from the Emergency
Vehicle Preemption system.
8.5.2.1 The user shall be able to configure what inputs are received from the
emergency vehicle preemption system.
8.5.2.2 The inputs shall include, at a minimum, the following:
8.5.2.2.1 Direction of travel
8.5.2.2.2 Desired route
8.5.2.2.3 Vehicle ID number
8.5.2.2.4 Estimated time of arrival
8.5.3 The software shall hold in the clearance phases and overlaps until the
preemption input turns off or the maximum preemption time is exceeded.
8.5.3.1 Software shall provide a user enabled option (on or off) for software
prevention of any occurrence of a yellow trap situation.
8.5.4 The software shall provide the current traffic demand to the emergency vehicle
preemption system. The emergency vehicle preemption system will use this
information to adapt when the preemption input is provided to the software
based on current traffic conditions.
8.5.4.1 During low traffic volumes the preemption input shall be provided as the
fire or rescue vehicle is arriving at the intersection.
8.6 NORMAL PREEMPT CONFIGURATION
Normal preemption shall activate when an advance signal has been active long enough to satisfy
any delay programmed. Any minimum green, walk, and pedestrian clearance intervals defined in the
normal preempt configuration table shall be met. The Entry 1 phases will turn green for the duration
programmed, and then the Entry 2 phases will turn green for the duration programmed. Entry 1 or
Entry 2 phases shall hold until the gate input is received and they delay end of entry phases time is
satisfied. The dwell phases will begin and hold until the gate input turns off. The software shall
follow the user defined exit mode and then return to normal operation.
8.6.1 The user shall be able to select the following minimum preemption options:
8.6.1.1 Enable
8.6.1.2 Preemption type (railroad or emergency vehicle)
8.6.1.3 Preempt lock
8.6.1.3.1 Preempt lock shall be on by default
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 41 of 100
8.6.1.3.2 Disabling preempt lock shall allow the preempt call to be
cancelled prior to reaching the dwell phases.
8.6.1.4 Override Program Flash
8.6.1.4.1 By default, a preempt call shall override program flash
8.6.1.4.2 Enabling this option will cause the preempt call to not
override program flash. The user shall be able to select this
for railroad and/or emergency vehicle preemption.
8.6.1.5 Dwell Mode
8.6.1.5.1 The user shall be able to configure the way the preempt will
operate during the dwell state.
8.6.1.5.2 The dwell mode shall include the following options:
Normal – The configured dwell phases and overlaps shall
operate normally during the dwell state.
Flash – The intersection shall operate in flash during the dwell
period.
8.6.1.6 Flash Yellow Dwell
8.6.1.6.1 User selected phases shall flash yellow during flash dwell.
All other phases shall flash red.
8.6.1.6.2 User selected overlaps shall flash yellow during dwell mode.
All other overlaps shall flash red.
8.6.1.7 Maximum Duration Time Exceeded Action
8.6.1.7.1 The user shall be able to program the action that the
controller will implement when the maximum duration time is
exceeded.
8.6.1.7.2 One maximum duration timer shall be provided for railroad.
8.6.1.7.3 One maximum duration timer shall be provided for
emergency vehicles.
8.6.1.7.4 The user shall be able to program the following actions when
the maximum duration time is exceeded:
Terminate Preempt – The preempt will terminate and not
reactivate until all preempt inputs have been cleared
Flash – The intersection shall enter all-red flash operation
until all preempt inputs have been cleared.
8.6.1.8 Return Phases
8.6.1.8.1 The return phases shall run following the end of preempt.
8.6.1.8.2 These phases shall output to the overlaps. If the phases are
parents of any overlaps, the overlaps shall turn green.
8.6.1.8.3 The phases shall remain green for at least the minimum
green defined in the active phase parameters table.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 42 of 100
8.6.1.8.4 The phases shall remain green as long as there are detector
inputs for green extensions or the maximum green timer
defined in the active phase parameter table is reached.
8.6.1.8.5 If no return phases are defined, the software shall exit
preempt via the exit mode entered.
8.6.1.9 Exit Mode
8.6.1.10 Entry 1 Phases (Railroad Preempt)
8.6.1.11 Entry 2 Phases (Railroad Preempt)
8.6.1.11.1 Entry 2 phases shall be served immediately after Entry 1
Phases.
8.6.1.12 Vehicle Dwell Phases
8.6.1.13 Pedestrian Dwell – Walk Rest phases
8.6.1.13.1 These phases shall remain in walk during the dwell interval
of the preemption.
8.6.1.13.2 Pedestrian clearance shall begin immediately after the
preemption is complete.
8.6.1.14 Pedestrian Dwell – Call phases
8.6.1.14.1 These phases shall receive one pedestrian call during the
dwell interval of the preemption.
8.6.1.14.2 If it has not already begun, the pedestrian clearance shall
begin immediately after the preemption is complete.
8.6.1.15 Entry 1 Overlap Disable
8.6.1.15.1 Overlaps identified here will be omitted during the Entry 1
interval.
8.6.1.16 Entry 2 Overlap Disable
8.6.1.16.1 Overlaps identified here will be omitted during the Entry 2
interval.
8.6.1.17 Dwell Overlap Disable
8.6.1.17.1 Overlap identified here will be omitted during the Dwell
interval.
8.6.1.17.2 The overlaps listed in Entry 2 and Dwell Overlap Disable
shall remain red when the software changes from Entry 2 to
Dwell.
8.6.1.18 Dwell Yellow Overlap Flash
8.6.1.18.1 Overlaps identified here will flash yellow if the software is in
flash operation during the dwell interval.
8.6.2 The user shall be able to enter values for the following preemption timing
parameters:
8.6.2.1 Minimum Presence Time
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 43 of 100
8.6.2.1.1 The minimum presence time is the minimum time that a
preemption call shall be present/on prior to initiating a
preempt event.
8.6.2.1.2 The range for the minimum presence time shall be from 0.0
to10.0 seconds in one-tenth (1/10) second increments
8.6.2.2 Delay Time
8.6.2.2.1 The software shall delay the initiation of the preemption
event by the delay time.
8.6.2.2.2 The delay and minimum pedestrian clearance shall time
simultaneously.
8.6.2.2.3 Even if the delay time has passed, the preemption sequence
shall not begin until the minimum pedestrian clearance time
has also passed.
8.6.2.2.4 The range shall be from 0 to 255 seconds in one (1) second
increments.
8.6.2.3 Delay End of Last Entry Phase
8.6.2.3.1 The value in the amount of time that the last Entry phase will
hold green after the gate input is received.
8.6.2.3.2 A value of zero (0) seconds will terminate the last Entry
Phase immediately.
8.6.2.3.3 The range for the delay end of last entry phase shall be from
0 to 255 seconds in one (1) second increments.
8.6.2.4 Minimum Duration Time
8.6.2.4.1 This value is the minimum time that the preempt time will be
active.
8.6.2.4.2 The range for the minimum duration time shall be from 0 to
600 seconds in one (1) second increments
8.6.2.5 Maximum Duration Time
8.6.2.5.1 The value is the maximum time that the preempt input will be
considered valid.
8.6.2.5.2 The user shall be able to program what action will be taken
if the maximum duration time is exceeded.
8.6.2.5.3 An alarm shall be generated that includes the preemption
inputs, the logical names for those inputs, and a time stamp.
8.6.2.5.4 The range for the maximum duration time shall be from 0 to
600 seconds in one (1) second increments.
8.6.2.6 Minimum Start Green
8.6.2.6.1 This value is the minimum amount of time that any active
phase must be green before it can be terminated by a
preempt input.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 44 of 100
8.6.2.6.2 A value of zero (0) will terminate the active phase
immediately. The default value shall be zero (0) seconds.
8.6.2.6.3 The software shall serve the lesser of the minimum start
green or the minimum green in the active phase parameter
table.
8.6.2.6.4 The range for the minimum start green shall be from 0 to
255 seconds in one (1) second increments
8.6.2.7 Minimum Pedestrian Walk
8.6.2.7.1 This value is the minimum amount of time that any active
pedestrian walk must serve prior to being terminated by a
preempt input.
8.6.2.7.2 A value of zero (0) will terminate the active pedestrian phase
immediately. The default value shall be zero (0) seconds.
8.6.2.7.3 The software shall serve the lesser of the minimum
pedestrian walk or the pedestrian walk time in the active
phase parameter table.
8.6.2.7.4 The range for the maximum duration time shall be from 0 to
255 seconds in one (1) second increments
8.6.2.8 Minimum Pedestrian Clearance
8.6.2.8.1 This value is the minimum amount of time that any active
pedestrian clearance must serve prior to being terminated by
a preempt input.
8.6.2.8.2 A value of zero (0) will terminate the active pedestrian phase
immediately. The default value shall be zero (0) seconds.
8.6.2.8.3 The software shall serve the lesser of the minimum
pedestrian clearance or the pedestrian clearance time in the
active phase parameter table.
8.6.2.8.4 The range for the maximum duration time shall be from 0 to
255 seconds in one (1) second increments
8.6.2.9 Entry 1 Green
8.6.2.9.1 This value is the amount of time that the Entry 1 phases will
remain green.
8.6.2.9.2 A value of zero will omit the Entry 1 phase
8.6.2.9.3 The Entry 1 Green shall only be terminated early by a valid
Gate Down input from the railroad.
8.6.2.9.4 The Entry 1 Green shall override the value for minimum and
maximum times in the active phase parameter table.
8.6.2.9.5 The range for the Entry 1 green time shall be from 0.0 to 255
seconds in one (1) second increments
8.6.2.10 Entry 2 Green
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 45 of 100
8.6.2.10.1 This value is the amount of time that the Entry 2 phases will
remain green.
8.6.2.10.2 A value of zero will omit the Entry 2 phase
8.6.2.10.3 The Entry 2 Green shall only be terminated early by a valid
Gate Down input from the railroad.
8.6.2.10.4 The Entry 2 Green shall override the value for minimum and
maximum times in the active phase parameter table.
8.6.2.10.5 The range for the Entry 2 green time shall be from 0.0 to 255
seconds in one (1) second increments
8.6.2.11 Minimum Dwell Time
8.6.2.11.1 This value is the minimum amount of time that the dwell
interval will serve.
8.6.2.11.2 The Minimum Dwell time shall not terminate prior to the
completion of the minimum duration time.
8.6.2.11.3 The range for the minimum dwell time shall be from 0 to 255
seconds in one (1) second increments.
9 TRANSIT PRIORITY
9.1 GENERAL
9.1.1 The software shall operate the transit signal displays
9.1.1.1 The bar signal sequence shall be:
9.1.1.1.1 Steady Vertical Bar (Go Indication)
9.1.1.1.2 Flashing Vertical Bar (Yellow Clearance)
9.1.1.1.3 Steady Horizontal Bar (Stop Indication)
9.1.1.1.4 Flashing Horizontal Bar (Prepare to Go Indication)
9.1.1.2 The user shall be able to define the amount of time, in seconds, the bar
indications display each of the displays in the sequence.
9.1.1.3 The vertical and horizontal bar shall flash one time per second. The bars
shall be on for one-half second then off for one-half second.
9.1.1.4 The user shall define the duration of the all-red interval. Other phases
shall be prevented from turning green while the all-red interval is active.
9.1.1.5 The train bar signals shall operate independently by direction and shall
operate such that only the direction with an approaching train shall be
activated.
9.1.1.6 The bar signal sequence shall be built into the software. Using logic
parameters to output the train bar signal as described shall not meet this
requirement.
9.1.2 The user shall be able to define the following transit signal parameters
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 46 of 100
9.1.2.1 Yellow Clearance – This is the duration, in seconds, of the flashing
vertical bar.
9.1.2.2 All-Red – This is the duration, in seconds, the steady horizontal bar shall
be displayed before any conflicting phase may turn green.
9.1.2.3 Prepare To Go – This is the duration, in seconds, of the flashing
horizontal bar.
9.1.3 The software shall be able to synchronize the end of the all-red for the train
bar signal and the end of the all-red for the vehicle and pedestrian phase.
9.1.4 The software shall provide a minimum of three (3) levels of priority, in the
following order of precedence. Preemption requests shall override all priority
requests.
9.1.4.1 Full priority operation
9.1.4.2 Partial priority operation
9.1.4.3 Bus priority operation
9.1.4.4 The hierarchy of priority is full priority is the highest, followed by partial
priority and bus priority as lowest priority.
9.1.5 High priority services shall override low priority services.
9.1.5.1 A request for a high priority service event shall immediately cancel any
active low priority service event and begin the high priority event.
9.1.6 Low priority services shall be ignored until the high priority service terminates.
9.1.6.1 The low priority event shall begin running in the background. Once the
inputs for high priority event terminates, the high priority event will
immediately end and the low priority event shall output its current
state.
9.1.6.2 Any part of the high priority event that occurs after the high priority
event input terminates shall be cancelled. The software shall
immediately output the low priority event.
9.1.7 Equal priority services shall be served on a first called, first served basis.
9.1.7.1 The second priority sequence shall begin running in the background.
Once the inputs for first priority sequence turn off the first sequence
shall immediately end and second priority sequence shall output its
current state.
9.1.7.2 Any part of the first priority sequence that occurs after the first priority
input turns off will be cancelled. The software shall immediately output
the second priority sequence.
9.2 FULL PRIORITY OPERATION
The software shall utilize the functionality required in the emergency vehicle, normal or smooth
preemption section to provide full priority. The coordinated cycle will be interrupted when a full
priority input is received and can be served.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 47 of 100
Full priority operation shall fulfill the vision in the Memorandum of Understanding for the Transit
Signal Priority System Operation and Maintenance along the Downtown Dallas Transitway mall. The
software shall also provide the functionality documented in the logical diagrams for the full priority
section in the appendix.
9.2.1 Full transit priority shall be provided for median running trains when the
controller is operating in free, flashing and coordinated modes.
9.2.2 The software shall be capable of providing an exclusive train phase.
9.2.2.1 The user shall be able to select vehicle and pedestrian movements that
are compatible with the train and may be served simultaneously.
9.2.3 Full transit priority shall be provided when the software is running programmed
yellow and all-red flash.
9.2.3.1 When a request for transit service is received, the controller shall
terminate the flash operation and return to normal operation. The
software shall provide service for the train phase, and any compatible
phases. The software shall then return to flash operation.
9.2.4 In the event that the full priority operation is terminated by the timeout
parameter, the following sequence of events will occur.
9.2.4.1 The software will provide service to all other vehicular and pedestrian
movements with calls at the intersection.
9.2.4.1.1 The user shall select the phases and pedestrian movements
served and the amount of time these phases shall remain
green.
9.2.4.2 The software will restart the timeout timer.
9.2.4.3 The software will return to the full priority mode.
9.2.4.4 An event will be logged that includes the input was on too long, the logical
name for the input, and a timestamp.
9.2.5 The software shall log events and include the following information:
9.2.5.1 Time the check in was received.
9.2.5.2 Time the check-out was received.
9.2.5.3 Time the downstream track was not clear.
9.2.5.4 Time the downstream track was clear.
9.3 PARTIAL TRANSIT PRIORITY
The software shall provide early green and extended green by direction for a train. The additional
green will be used to give the train operator a better chance to make it through the signal. The
software shall continue to operate in coordination.
Partial priority operation shall fulfill the vision in the Memorandum of Understanding for the Transit
Signal Priority System Operation and Maintenance along the Downtown Dallas Transitway Mall. The
software shall also provide the functionality documented in the logical diagrams for the partial priority
section in the appendix.
9.3.1 General
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 48 of 100
9.3.1.1 The software shall allow the user to define four full sets of partial priority
parameters, one for each direction.
9.3.1.2 A request for early green and green extension shall be priority requests
and shall not be canceled by other equal or lower priority requests.
9.3.1.3 The software shall stay in coordination with adjacent intersections while
adjusting the splits to accommodate the train. When the train is not
present, the extra green time shall be provided to movements on the
intersecting roadway.
9.3.1.4 Train indications and all compatible vehicle and pedestrian indications
shall end their clearance intervals concurrently.
9.3.1.5 The software shall hold the train phase based on the length of the train.
The software shall allow the user to define different green durations
based on the length of the train.
9.3.1.6 The software shall be capable of holding a train at the signal until the
downstream track to the next holding block and the next holding block are
both clear.
9.3.1.6.1 The software shall be able to consider two and three car
trains separately. The software shall release the train when
the downstream block long enough to hold that length of
train is clear. These will be different blocks because of the
train length.
9.3.1.6.2 The software shall be able to process detector inputs from
downstream intersections and use build in or programmable
logic to determine if the next downstream block long enough
to hold the train is not occupied.
9.3.1.7 The software shall log events and include the following information:
9.3.1.7.1 Time the check in was received, by direction.
9.3.1.7.2 Time the check-out was received by direction.
9.3.1.7.3 Time downstream was not clear.
9.3.1.7.4 Time downstream was clear.
9.3.1.7.5 Time green extension was provided.
9.3.1.8 If the train crosses the check-out detector, the clearance interval shall
begin immediately.
9.3.1.8.1 The train phase shall be able to gap out and begin clearance
immediately. Other active phases shall not prevent the train
phase from beginning the clearance interval.
9.3.1.8.2 Compatible vehicle and pedestrian phases shall operate as
follows.
9.3.1.8.3 The pedestrian phase shall begin clearing, if it has not
already done so, when the train phase gaps out.
9.3.2 Partial Priority Configuration
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 49 of 100
9.3.2.1 Compatible Phases
9.3.2.1.1 User identified vehicle and pedestrian phases compatible
the train signal. They shall be active while the train signal is
active.
9.3.2.2 Check In Detectors
9.3.2.2.1 These are the detectors that call the train phase. The call
and extension shall remain active for that transit phase until
the train is checked out from the intersection.
9.3.2.3 Check Out Detectors
9.3.2.3.1 These are the detectors that end the call for the train phase.
The train phase call and extension shall immediately end
once an input is received from one of these detectors.
9.3.2.3.2 Transit phase shall begin clearing immediately regardless of
the state of any other active phases.
9.3.2.3.3 If the checkout detector is active for a user defined number
of seconds, a new call for partial priority shall be entered
because the train is still present. The train shall checkout
once that detector turns off.
9.3.2.4 Delay Timer
9.3.2.4.1 This is the amount of time in second the detector will have to
be active before the software acknowledges it is active.
9.3.2.4.2 The default value shall be zero (0).
9.3.3 Partial Priority Timing Parameters
9.3.3.1 The software shall provide a minimum of three tables with the following
timing parameters that can be selected to be operational by time of day
and day of week.
9.3.3.2 Minimum Green – the minimum amount of time, in seconds, the vertical
bar signal shall be displayed.
9.3.3.3 Maximum Green – the maximum amount of time, in seconds, the vertical
bar signal shall be displayed.
9.3.3.4 Green Extension
9.3.3.4.1 User defined amount of time, in seconds, that the green
interval can be extended beyond its maximum or split time to
accommodate the transit priority request.
9.3.3.4.2 The user shall be able to enable green extension by
direction.
9.3.3.4.3 The green extension shall not reduce the amount of time for
the next movement to the extent that the minimum green
time cannot be served or the pedestrian interval cannot be
served.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 50 of 100
9.3.3.4.4 The user may choose to allow a pedestrian movement to be
skipped to accommodate a green extension.
9.3.3.5 Early Green
9.3.3.5.1 User defined amount of time in seconds that the software
may begin a train-compatible phase early to accommodate
the priority request. The early green shall reduce the green
time for the preceding phases.
9.3.3.5.2 The user shall be able to enable early green by direction.
9.3.3.5.3 The early green shall not reduce the amount of time for the
preceding movement such that the minimum green time or
pedestrian interval cannot be provided. Walk time shall not
be truncated to meet this requirement.
9.3.3.5.4 The user may choose to allow the pedestrian movement to
be skipped to accommodate early green.
9.3.3.6 Maximum Priority Service Time
9.3.3.6.1 User defined time, in seconds, that priority can be active.
When this value is exceeded, priority requests are cancelled
and regular, programmed operation is resumed.
9.3.3.7 Lock Out Time
9.3.3.7.1 User defined time, in seconds, that priority requests are not
acknowledged due to maximum time in priority operation.
When this time has passed, priority requests will be
acknowledged, and priority operation will resume.
9.3.3.8 Countdown Timer Time
9.3.3.8.1 The user shall enter the time, in seconds, the countdown
timer will start before the beginning of the transit phase for
that direction.
9.3.4 Partial Priority Operation
9.3.4.1 The software shall automatically select whether early green or green
extension is provided. The software will decide based on the active
phase when the train priority request is received and the anticipated
arrival time of the train.
9.3.4.1.1 The user shall be able to turn early green and green
extension off by direction and by time of day/day of week.
9.3.4.2 The software shall be able to vary the amount of green provided to the
train based on the length of the train. The detection system will provide a
distinct input for each length of train.
9.3.4.2.1 The duration of the green shall vary without disrupting the
active coordinated timing plan.
9.3.4.3 The software shall be able to determine if the track ahead of the train is
clear by using detector inputs from adjacent intersections.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 51 of 100
9.3.4.4 The train shall not be allowed to enter a block if any downstream block
between the train and the next block long enough to hold that train is not
clear. The bar signal for that direction shall remain red until the track is
clear and the local cycle is at the time when that train phase is served.
9.3.4.4.1 This feature shall prevent trains from stopping in blocks that
are shorter than the train and blocking intersections.
9.3.4.4.2 This feature shall consider the length of the train in the
decision process.
9.3.4.5 The software shall provide a countdown timer output. The countdown
timer will display the amount of time remaining until the next go indication
will be displayed.
9.3.4.5.1 The software shall be able to accommodate a 50 second
countdown.
9.3.4.5.2 The countdown timer shall begin a user defined amount of
time in seconds before the go signal and provide a constant
output during the downtown interval.
9.3.4.5.3 The software shall only output the countdown timer
information if a train is detected at the immediate
intersection.
9.3.4.5.4 The end of the countdown shall coincide with the beginning
of the transit phase.
9.3.4.5.5 The software shall be capable of providing the value of the
countdown to the timer. The format of this value shall be
accepted by at least two (2) off-the-shelf countdown timer
vendors.
9.3.4.6 The software shall deny a train priority request and not provide a go
signal under the following conditions:
9.3.4.6.1 The track between the train and the next block long enough
to hold the train is not clear. This includes the block long
enough to hold the train. The train will have to stop in a
block that is too short and will block an intersection.
9.3.4.6.2 The maximum vehicle queue length on the cross street has
been exceeded.
9.3.4.7 The user shall define the mode of operation if peer to peer communication
is lost to any intersection or detection device defined by the user. The
mode of operation shall automatically return to normal operation once
communication is restored.
9.3.4.7.1 The user shall program the controller to automatically adjust
the operation of the traffic light when communication is lost.
User defined options shall includealways providing priority,
adding recalls and changing plans. The user shall be able
to vary the response by time of day.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 52 of 100
9.3.4.7.2 An alarm will be generated that includes the communication
link that failed and the time of that failure.
9.3.4.7.3 The user shall be able to select the criterion that indicates a
communication failure including the amount of time in
seconds a link is down, the number of times a link is down
over an amount of time, and other criteria standard to the
communications industry.
9.3.4.8 The user shall define the mode of operation if detection has failed at the
intersection. The software shall determine failure using the functionality
for the vehicle detectors. The user shall be able to select the detectors to
monitor. The mode of operation shall automatically return to normal
operation once the failed detector is restored.
9.3.4.8.1 The user shall program the controller to automatically adjust
the operation of the traffic light when detection fails. User
defined options shall include always providing priority,
adding recalls and changing plans. The user shall be able
to vary the response by time of day.
9.3.4.8.2 An alarm will be generated that includes the detector that
failed and the time of that failure.
9.3.4.8.3 The software shall use the criterion already defined for the
detectors to determine failure.
9.4 BUS PRIORITY
The software shall provide early green, extended green and queue jump by direction for a bus if the
bus is on a route selected by the City and DART and the bus is behind schedule. The additional
green will be used to give the bus a better chance to make it through the traffic signal. The software
shall continue to operate the intersection in coordination.
9.4.1 General
9.4.1.1 The software shall provide a minimum of three (3) tables with the
following timing parameters that can be selected to be operational by time
of day and day of week.
9.4.1.2 The software shall receive an input from separate bus priority equipment.
The software will provide the appropriate priority sequence based on the
input from the bus priority equipment or other selected inputs. The three
responses are:
9.4.1.2.1 Early green
9.4.1.2.2 Green extension
9.4.1.2.3 Queue Jump
9.4.1.3 The software shall allow the user to define six (6) full sets of partial
priority parameters, one for each direction. These shall be unique from
the train priority inputs.
9.4.1.4 The bus priority computer shall provide unique inputs for each direction
the bus may approach the intersection.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 53 of 100
9.4.1.4.1 Two separate bus priorities shall be accommodated: early
or extended green and queue jump.
9.4.1.5 The software shall ignore a bus priority request if the software is
operating the traffic light in programmed yellow flash or all-red flash.
9.4.1.6 The software shall automatically select whether early green or green
extension is provided. The software will decide based on which phases
are active when the bus priority input is received.
9.4.1.6.1 The software shall continue to provide priority at the next
opportunity in the local cycle as long as the bus priority input
is active.
9.4.1.7 The software shall log the following data related to bus priority:
9.4.1.7.1 Type of priority request, by direction with time stamp.
9.4.1.7.2 Time priority phases initiated.
9.4.1.7.3 Time priority phases ended.
9.4.1.7.4 Action taken:
Direction receiving early green
Direction receiving extended green
Direction receiving queue jump
Extend a phase
Truncate a phase
Queue jump
9.4.2 Bus Priority Configuration
9.4.2.1 Bus priority phases
9.4.2.1.1 These are the phases that will output a green indication
during the bus priority interval.
9.4.2.1.2 These phases shall remain green until:
The priority request input has terminated.
The maximum priority time has been reached.
9.4.2.2 Bus priority overlaps
9.4.2.2.1 These are the overlaps that will output a green indication
during the bus priority interval.
9.4.2.3 Queue jump phases
9.4.2.3.1 User identified phases that will output a green indication
during the queue jump interval.
9.4.2.4 Queue jump overlaps
9.4.2.4.1 These are the overlaps that will output a green indication
during the queue jump interval
9.4.2.5 Bus priority detection input
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 54 of 100
9.4.2.5.1 Detector associated with the priority request for early green
or green extension.
9.4.2.6 Queue jump detection input
9.4.2.6.1 Detector associated with the queue jump request.
9.4.2.7 Delay Time
9.4.2.7.1 The amount of time in seconds the bus priority input must be
on before the software will acknowledge the priority request.
9.4.3 Bus Priority Timing
9.4.3.1 Green Extension
9.4.3.1.1 The amount of time, in seconds, that the software may
extend the green indication for the bus phase past the
normal phase maximum or split time.This extension will
reduce the green time for the following movement served if
running in coordinated operation.
9.4.3.1.2 The green extension shall not reduce the amount of time for
the following movements such that the minimum green time
cannot be provided or the pedestrian interval cannot be
provided.
The pedestrian interval shall only limit the green extension if a
call for the pedestrian phase is active in the controller.
9.4.3.1.3 The user may choose to allow the pedestrian movement to
be skipped.
9.4.3.2 Early Green
9.4.3.2.1 The amount of time, in seconds, that the software may begin
the compatible green phase early to serve the bus. The
early green shall reduce the green time for the preceding
phases.
9.4.3.2.2 The early green shall not reduce the amount of time for the
preceding movement such that the minimum green time or
pedestrian interval cannot be provided.
9.4.3.2.3 The user may choose to allow the pedestrian movement to
be skipped.
9.4.3.2.4 The walk or pedestrian clearance shall not be truncated to
meet this requirement.
9.4.3.3 Maximum Priority Time
9.4.3.3.1 This is the maximum amount of time in minutes the bus
priority call may remain active.
9.4.3.3.2 The software shall ignore the bus priority input once the
maximum time has been exceeded until the bus priority input
changes states.
9.4.4 Bus Priority Operation
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 55 of 100
9.4.4.1 Queue Jump
9.4.4.1.1 This is a green indication provided for the bus before the
adjacent vehicles receive a green indication. The interval
allows a bus to cross the intersection and merge into the
through lane without having to yield to other vehicles.
9.4.4.1.2 If the queue jump lane is an exclusive right turn lane, the
software shall be capable of displaying a right turn arrow to
clear motorist ahead of the bus.
9.4.4.1.3 The controller shall only provide a queue jump before the
adjacent through movement. If the bus arrives during the
green and a request for a queue jump is received it shall be
ignored until the time immediately before the beginning of
green for the adjacent through movement.
If early green time is programmed, the software shall steal time
from the preceding phase and start the queue jump phase
early.
9.4.4.1.4 The user shall be able turn this feature off by time of
day/day of week.
9.4.4.1.5 Once the bus has requested a queue jump, the software
shall not provide green extension for that direction.
10 ADVANCED PROGRAMMING
10.1 GENERAL
10.1.1 The software shall support a minimum of 64 user definable logic processor
commands
10.1.2 The software shall not limit the number of items that can be linked together in
logic statements.
10.1.2.1 The software shall process the logic commands linked together every 0.1
seconds.
10.1.3 The logic commands shall support the following Boolean gating:
10.1.3.1 OR – if either function is true, the logic channel will be true.
10.1.3.2 AND – if both functions are true, the logic channel will be true.
10.1.3.3 NOT- if the first function is NOT true, the logic channel will be true the
second function is not used for this command.
10.1.3.4 XOR- if either function is true the channel is true; if both are true the
channel will be false.
10.1.3.5 NOR – If either function is true, the logic channel will be false.
10.1.3.6 NAND – if both functions are true, the logic channel will be false.
10.1.3.7 ORNOT2 – if the first function is true OR the second function is not true,
the logic channel will be true.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 56 of 100
10.1.3.8 ANDNOT2 – if the first function is true AND the second function is not
true, the logic channel will be true.
10.1.4 The logic commands shall support the following:
10.1.4.1 LATCH – once the first function is true, the logic channel will be true until
the second function is true.
10.1.4.2 DELAY AND/OR EXTEND – once the function is true, the logic channel
shall not be true until an amount of time in seconds defined by the user
has elapsed. After the function changes from true to false, the logic
channel shall remain true until an amount of time in tenths of seconds,
seconds, minutes, or hours defined by the user has elapsed.
10.1.4.2.1 The range of the delay time shall be from 0 to 25.5 tenths of
seconds, 0 to 255 seconds, or 0 to 255 minutes, 0 to 255
hours and defined separately.
10.1.4.2.2 The range of the extend time shall be from 0 to 25.5 tenths
of seconds, 0 to 255 seconds, or 0 to 255 minutes, 0 to 255
hours and defined separately.
10.2 ASSIGNABLE OUTPUTS
10.2.1 The software shall provide the ability to program the following outputs in logic
statements:
10.2.1.1 Phase green
10.2.1.2 Phase yellow
10.2.1.3 Phase red
10.2.1.4 Phase omit
10.2.1.5 Overlap green
10.2.1.6 Overlap yellow
10.2.1.7 Overlap red
10.2.1.8 Walk
10.2.1.9 Pedestrian clear
10.2.1.10 Don’t walk
10.2.1.11 Overlap walk
10.2.1.12 Overlap pedestrian clear
10.2.1.13 Overlap don’t walk
10.2.1.14 Phase on
10.2.1.15 Phase next
10.2.1.16 Phase check
10.2.1.17 Phase hold
10.2.1.18 Virtual phase green
10.2.1.19 Virtual phase yellow
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 57 of 100
10.2.1.20 Virtual phase red
10.2.1.21 LRV green
10.2.1.22 LRV yellow
10.2.1.23 LRV red
10.2.1.24 Force off
10.2.1.25 Preempt on
10.2.1.26 Preempt entry one
10.2.1.27 Preempt entry two
10.2.1.28 Preempt dwell
10.2.1.29 Preempt off
10.2.1.30 Flash
10.2.1.31 Free
10.2.1.32 Special Function
10.2.1.33 Active plan
10.2.1.34 Special output/time of day
10.3 ASSIGNABLE INPUTS
10.3.1 The software shall provide the ability include the following inputs in logic
statements:
10.3.1.1 Vehicle detector
10.3.1.2 Pedestrian detector
10.3.1.3 Overlap detector
10.3.1.4 Overlap pedestrian detector
10.3.1.5 System detector
10.3.1.6 Queue detector
10.3.1.7 LRV detector
10.3.1.8 Terminate detector
10.3.1.9 Vehicle omit
10.3.1.10 Pedestrian omit
10.3.1.11 Overlap omit
10.3.1.12 Overlap pedestrian omit
10.3.1.13 LRV Omit
10.3.1.14 Phase hold
10.3.1.15 Overlap hold
10.3.1.16 Walk hold
10.3.1.17 Overlap walk hold
10.3.1.18 Preempt train input
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 58 of 100
10.3.1.19 Preempt emergency vehicle input
10.3.1.20 Flash sense
10.3.1.21 Manual control enable
10.3.1.22 Manual control advance
10.3.1.23 Stop time
10.3.1.24 Minimum recall
10.3.1.25 External start
10.3.1.26 Walk rest modifier
10.3.1.27 External coordination enable
10.3.1.28 Plan select enable
10.3.1.29 External time set
10.3.1.30 Door open
10.3.1.31 Force off
10.3.1.32 Red rest
10.3.1.33 Max inhibit
10.3.1.34 Max 2
10.3.1.35 Max 3
10.3.1.36 Pedestrian recycle
10.3.1.37 External plan select
10.3.1.38 Master sync input
10.3.1.39 Free select input
10.3.1.40 MMU flash
10.3.1.41 Local flash
10.3.1.42 Automatic flash
10.3.1.43 Gate down
11 COMMUNICATIONS
11.1 GENERAL
11.1.1 The software shall support the following types of external communications:
11.1.1.1 Controller to Central Supervisory Software
11.1.1.2 Masterless Peer-to-Peer between local controllers
11.1.1.3 Local Wireless Remote
11.1.2 The software shall be able to accommodate communication with all these
communication types simultaneously.
11.1.3 The software shall support the following methods of communications:
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 59 of 100
11.1.3.1 The software shall support four independent FSK modems connections
operating at speeds up to 9600 Baud
11.1.3.2 The software shall support two EAI/TIA232-E connections using a 9-pin
connector for each connection.
11.1.3.3 The software shall support a minimum of two 10/100 Ethernet connections
using standard RJ-45 connectors.
11.1.4 The software shall be able to communication either half or full duplex.
11.1.5 The local controller software shall transmit gratuitous ARP packets when first
connected to an Ethernet Network
11.1.6 The local controller software shall be able to extract VLANS from a tagged
trunk of VLANS being received from the Ethernet Network.
11.2 CENTER TO FIELD COMMUNICATION
11.2.1 The user shall be able to request a download or upload to the control system
through the front panel.
11.2.1.1 The software shall display any pages that failed.
11.2.2 The local controller software shall support the following communication
patterns:
11.2.2.1 Poll-Response
11.2.2.1.1 The software shall be capable of being polled every one (1)
second.
11.2.2.2 Exception based reporting (controller initiated event driven
communication).
11.2.3 The software shall support Central to Field (C2F) communications through the
following hardware interfaces:
11.2.3.1 EIA/TIA 232-E compliant 9-pin connector
11.2.3.2 10/100 Ethernet RJ-45 connector
11.2.3.3 FSK Modem
11.2.4 The type of field to central communication shall be configurable by the user.
11.2.5 The software shall be capable of field to central communication over a 10/100
Ethernet network.
11.2.5.1 The local controller software shall include fully integrated, native support
of the Ethernet protocol. Serial tunneling over an Ethernet network is not
acceptable.
11.2.5.2 The local controller software shall support static IP and Dynamic Host
Configuration (DHCP) IP address assignment.
11.2.5.3 The configuration of the local controller software communicating over an
Ethernet network shall include the following settings:
11.2.5.3.1 Controller name
11.2.5.3.2 IP address
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 60 of 100
11.2.5.3.3 Subnet mask
11.2.5.3.4 Gateway address
11.2.5.3.5 Domain name server
11.2.5.3.6 DHCP enable
11.2.5.4 The local controller software shall support the ICMP Protocol stack to
verify communication over an IP network.
11.2.5.5 The local controller software shall support Ethernet communications over
interconnection methods including, but not limited to the following:
11.2.5.5.1 Point to point optical fiber
11.2.5.5.2 Shared multi-drop optical fiber
11.2.5.5.3 Serial strings of wireless point to point links
11.2.5.5.4 Point to multi-point wireless links
11.2.5.5.5 Wireless mesh
11.2.5.5.6 Long latency network
11.2.5.5.7 Varying latency network
11.2.5.5.8 DOCSIS modem, shared capacity technology
11.2.5.5.9 Ethernet over traffic cable
11.2.5.5.10 Ethernet over powerline
11.2.5.5.11 Ethernet over signal cable
11.2.5.5.12 Ethernet over 9-wire cable
11.2.5.5.13 Ethernet over coaxial cable
11.2.5.5.14 10BASE2 Ethernet over copper wire (twisted pair)
11.2.5.5.15 DSL and its extensions over copper wire
11.2.5.5.16 3G commercial wireless
11.2.5.5.17 4G WiMaxcommercial wireless
11.2.5.5.18 4G LTE commercial wireless
11.2.5.5.19 4G WiMaxprivate wireless
11.2.5.5.20 4G LTE private wireless
11.2.5.6 The local controller software shall support Network Time Protocol (NTP)
for setting the controller clock.
11.2.5.7 The local controller software shall support File Transfer Protocol (FTP) for
uploading and downloading files.
11.2.6 The local controller software shall be capable of field to central communication
over a serial communication network.
11.2.6.1 The local controller software shall support EIA/TIA 232-E communications
protocol standard in a serial communication network.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 61 of 100
11.2.6.2 The local controller software shall support user definable speeds over a
serial network up to 56 kbps.
11.3 PEER TO PEER COMMUNICATION
11.3.1 The local controller software shall support peer to peer communication
between local intersection controllers exclusive of a central management
system and along the most direct and reliable path allowable by the
communication topology.
11.3.2 Peer to peer communication shall operate over an Ethernet network.
11.3.3 The local controller software shall support transmission and reception of
multiple peer messages simultaneously.
11.3.4 The local controller software shall be able to transmit peer to peer messages
to a minimum of five (5) intersections in all directions from the intersection
transmitting the messages.
11.3.5 The local controller software shall be able to receive peer to peer messages
from a minimum of five (5) intersections in all directions from the intersections
receiving the message.
11.3.6 Peer intersections shall be selectable by the user.
11.3.6.1 Peer intersection will be identified by logical name
11.3.6.2 Peer intersection will be identified by IP address
11.3.6.3 The user shall be able to select any local controller input, output, or event
to initiate a peer to peer message.
11.3.7 The receipt of a peer-to peer message shall cause the receiving intersection to
apply an internal control on the receiving peer intersection.
11.3.7.1 The user shall be able to select any internal control event available in the
software.
11.3.8 The local controller software shall have a user definable communication link
timeout feature for each peer to peer message.
11.3.8.1 The timeout value shall range from 1 second to 60 seconds in one second
increments.
11.3.8.2 The use shall be able to enable/disable the timeout feature.
11.3.8.3 Idle periods during which no peer to peer messages are being transmitted
shall not cause the link to timeout.
11.3.9 The failure of a peer to peer communication link shall initiate a communication
link failure alarm.
11.3.9.1 Failure of a communication link shall cause the receiving function to be
set to a user defined fail state
11.3.9.2 When the communication keep-alive resumes, the variable set by a
remote intersection shall return to its valid condition.
11.3.9.2.1 The user may override the defined fail state condition for
each message.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 62 of 100
11.4 LOCAL WIRELESS REMOTE
11.4.1 The user shall be able to access the local controller through a Local Wireless
Remote Client using either of the following methods:
11.4.1.1 An adapter attached to the local controller
11.4.1.2 An 802.11 a/b/g/n Access Point installed in the intersection cabinet.
11.4.2 The local wireless remote client shall be available within a 200 foot radius of
the controller cabinet.
11.4.3 The local wireless remote client connection shall use secure data
communication transmissions and shall be available to approved users and
equipment only.
11.4.4 Users shall be able to utilize the local wireless remote client from approved
laptops, smartphones, touch screen tablets, or other remote devices.
11.4.5 The local wireless remote client shall support bandwidths at a minimum of a
a/b/g/n data rate connection.
12 ADVANCED OPERATIONS
12.1 TRAFFIC RESPONSIVE OPERATION
If the Proposer has an adaptive solution the City desires a presentation of the functionality and a bid.
This requirement describes a decentralized traffic responsive operation. Traffic signals will be
grouped together and a controller will be the master for the group. The other intersections will relay
system detector information to the master controller via a peer-to-peer messaging; the master
controller will determine the plan; and the master controller will command the other intersections in
the group into the plan.
12.1.1 The software shall provide the following user defined and selectable
parameters for traffic responsive operation:
12.1.1.1 Thresholds (1-10)
12.1.1.2 Activation threshold (density)
12.1.1.3 Traffic responsive detectors (1-32)
12.1.2 The software shall provide traffic responsive operation for a user defined
intersection group
12.1.2.1 The software shall allow the selection of a single controller to serve as the
traffic responsive master controller for the intersection group.
12.1.2.1.1 The master controller shall receive data from other
controllers and transmit traffic responsive commands to the
other controllers using the peer to peer communication links.
12.1.2.2 The software shall support at least 32 user selectable detectors from any
intersection within the group for traffic responsive plan selection.
12.1.2.2.1 The software shall support weighting of the detector data by
the user for each detector (K Value).
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 63 of 100
12.1.2.3 The software shall use algorithms developed by the US Department of
Transportation for Traffic-Responsive Operation.
12.1.2.4 The software shall support up to 10 user defined traffic flow thresholds for
traffic plan selection.
12.1.2.5 Traffic Responsive Operations shall automatically select timing plans
based on defined traffic flow thresholds, defined as volume plus K times
occupancy (V+KO).
12.1.2.6 Plans eligible for traffic responsive operations shall be stored in the local
controller databases.
12.1.2.7 Plans eligible for traffic responsive operation shall be identified on a time
of day/day of week basis.
12.1.2.8 The software shall compare the processed volume and occupancy value
to the threshold values and select the timing plan that most closely
matches the processed data value.
12.1.2.9 Each intersection in the group shall verify that the command was received
and the new timing plan was implemented.
12.1.2.9.1 If the plan change fails at any intersection, the group shall
revert to the local controller time of day/day of week
schedule.
12.1.2.10 Traffic responsive operation shall end
12.1.2.10.1 When the processed volume and occupancy values satisfy
the threshold value established for traffic responsive exit.
12.1.2.10.2 A manual command is received
12.1.2.10.3 Based on the time of day/day of week schedule
12.2 QUEUE DETECTION
12.2.1 The user shall be able to define eight (8) independent responses per
intersection.
12.2.2 The user shall select the time of day/days of week the queue detection feature
is active.
12.2.2.1 This shall be for each queue detector
12.2.3 In the event of a detector failure, the queue detection response associated
with that detector shall be disabled.
12.2.4 Four levels of priority shall be provided
12.2.4.1 If a queue detector with higher priority is active, lower priority queue
detectors trying to reduce the green time for the higher priority movement
shall be ignored.
12.2.4.2 When queue detectors have equal priority and are competing for green
time, the software shall ignore both queue detectors.
12.2.5 Configuration parameters for queue detection
12.2.5.1 Enable
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 64 of 100
12.2.5.1.1 Left turn or through vehicle
12.2.5.1.2 Partial priority
12.2.5.1.3 Diamond intersections
12.2.5.2 Priority
12.2.5.2.1 For each queue detection response
12.2.5.3 Maximum Time
12.2.5.3.1 User defined in seconds
12.2.5.3.2 For each queue detection response
12.2.5.3.3 Once the maximum time is reached the queue detection
response shall turn off.
12.2.5.3.4 The maximum timer shall reset when all of the detectors for
that queue detector turn off.
12.2.6 Left turn or through vehicle queue detection
12.2.6.1 The software shall add a user defined amount of green time when user
defined detector delay or occupancy trigger points are satisfied.
12.2.6.1.1 The software shall be able to add green time to a phase
12.2.6.1.2 The software shall be able to call a phase
12.2.6.2 Configuration parameters for left turn or through vehicle queue detection
12.2.6.2.1 Detectors
12.2.6.2.2 Delay trigger point in seconds from 0 to 255.
12.2.6.2.3 Occupancy trigger point in percent from 0 to 100.
12.2.6.2.4 Green time added
12.2.6.2.5 Phase(s) green time is added to
12.2.6.2.6 Phase(s) green time is subtracted from
If more than one phase is listed, the time subtracted shall be
split evenly among the phases.
These adjustments shall not fail the coordinator.
12.2.6.2.7 Call Phase(s)
12.2.7 Partial Priority Queue Detection
If the trigger points are met, the software shall ignore requests for partial priority until the
vehicle queue length decreases or the maximum queue detection timer is exceeded.
12.2.7.1 Configuration Parameters for partial priority queue detection
12.2.7.1.1 Detectors
12.2.7.1.2 Delay trigger point
12.2.7.1.3 Occupancy trigger point
12.2.8 Diamond Intersection Queue Detection
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 65 of 100
The software shall change the diamond sequence or coordinated timing plan when the
queue detectors are active.
12.2.8.1 Configuration parameters for diamond intersection queue detection
12.2.8.1.1 Detectors
12.2.8.1.2 Delay trigger point in seconds from 0 to 255
12.2.8.1.3 Occupancy trigger point in percent from 0 to 100
12.2.8.1.4 Temporary sequence
12.2.8.1.5 Temporary timing plan
12.2.8.1.6 Amount of time in minutes that temporary sequence and/or
plan remain active after initiated. Acceptable values range
from 0 to 60 minutes.
12.2.9 The software shall log and timestamp
12.2.9.1 When a queue detection response occurs
12.2.9.2 The data that triggered the response
12.2.10 In the event of detector failure an alarm with a timestamp shall be generated
and include
12.2.10.1 The detector that failed
12.3 AUXILIARY FIELD DEVICE OPERATION
12.3.1 The software shall allow the user to program the operation of auxiliary field
devices.
12.3.2 The software shall support a minimum of eight (8) different auxiliary field
device configurations per table.
12.3.3 The software shall provide a minimum of four (4) auxiliary field device tables.
12.3.4 The auxiliary field device table shall be activated by any of the following
means:
12.3.4.1 Schedule
12.3.4.2 Manual command
12.3.4.3 Logic functions
12.3.5 The user shall be able to program the following output states of the auxiliary
field devices:
12.3.5.1 Default State
12.3.5.2 Display 1
12.3.5.3 Display 2
12.3.5.4 Display 3
12.3.6 The user shall be able to repeat any state during while the auxiliary field
device table is active (i.e. Display1 -> Display 2-> Display 1).
12.3.7 Changes in the auxiliary field device state shall be user programmable by the
following means:
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 66 of 100
12.3.7.1 Time of day
12.3.7.2 Assignable input pins
13 DIAMOND INTERCHANGE SEQUENCE
13.1 GENERAL
13.1.1 A hardcoded phase sequence, approved by the city, will run.
13.1.2 The software shall be capable of running the following diamond sequences and
shall be able to run any combination for these sequences at an intersection.
The sequence will change by time of day/day of week and/or by input from
diamond interchange queue detectors.
13.1.2.1 Figure 3 - Dual Lag
13.1.2.1.1 The user shall be able to select different splits for the
lagging left turns.
13.1.2.1.2 The user shall be able to keep the left turn and adjacent
through movement green if there is a call on only one
frontage road.
13.1.2.2 Figure 4 - TTI Phasing
13.1.2.2.1 The user shall be able to select the length of the green
clearance time for the frontage roads.
13.1.2.3 Figure 6 or 7 – Lead/Lag or Lag/Lead
13.1.2.3.1 The user shall be able omit any left turn phase.
13.1.2.3.2 The user shall be able to lead and lag any left turn
movement.
13.1.2.3.3 The user shall be able to keep the left turn and adjacent
through movement green if there is a call on only one
frontage road.
13.1.3 All diamond interchange operations shall be configurable to operate in
actuated, semi-actuated, or fixed time mode.
13.1.4 The software shall smoothly transition between sequences.
13.1.4.1 The software shall not appear to skip any movement. Even if a phase is
not technically skipped, the controller shall not service an outside
movement twice without servicing all other outside movements that have
demand.
13.1.4.1.1 The outside movement may be served twice before all other
movements are served if the movement is compatible with
another outside movement being served.
13.1.4.2 The software shall not advance to the next movement, serve that next
movement, and then back up and serve the first movement again during a
sequence change.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 67 of 100
13.1.5 The software shall be capable of running the diamond sequences listed above
with right turn overlaps on the frontage roads and arterial roads.
13.1.6 The software shall be capable of running the diamond sequences listed above
with eight (8) active pedestrian channels.
13.1.6.1 Each frontage road crossing will be independent.
13.1.6.2 The arterial road crossing will be split into two independent crossings.
13.1.7 The software shall provide templates for the following traditional diamond
operations for easy programming:
13.1.7.1 Figure 3 – dual lag
13.1.7.2 Figure 4 – TTI phasing
13.1.7.3 Figure 6 – Lead/lag
13.1.7.4 Figure 7 – Lag/lead
13.2 DIAMOND INTERCHANGE K-CLEARANCE
13.2.1 General Requirements
13.2.1.1 The feature shall allow the user to skip phases in the diamond sequence
without violating a motorist’s expectation. The expected inside interval
shall be provided to the motorist even if phases are skipped.
13.2.1.2 The software shall provide an internal clearance for traffic moving from
one side of the interchange to the other, providing full passage through
the interchange even when phases are not be served due to low volumes.
13.2.1.3 Recommending the use of the user programmable logic statement defined
in the advanced programming chapter shall not meet this requirement.
13.2.1.4 The user shall be able to skip phases during coordinated operation. In no
case shall this feature cause the coordinator to fail or cause a transition.
13.2.1.5 Right turn overlaps on the frontage and arterial roadway shall continue to
operate normally when phases are skipped.
13.2.1.6 Left turn overlaps on the arterial roadway shall continue to operate
normally when phases are skipped.
13.2.2 Figure 3 Diamond Sequence
13.2.2.1 Uncoordinated Operation
13.2.2.1.1 When changing from the arterial roadway to the frontage
road, the software shall call the appropriate inside clearance
phase(s).
If there are calls on both frontage roads, both inside clearance
phases shall be provided.
If there is only a call on frontage road one, the inside clearance
phase on the other side of the diamond shall be provided.
If there is only a call on frontage road two, the inside clearance
phase on the other side of the diamond shall be provided.
13.2.2.2 Coordinated Operation
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 68 of 100
13.2.2.2.1 Arterial roadway is coordinated
When a vehicle call is received on the frontage road the
software shall determine if there is enough time to provide the
appropriate inside clearance and provide a minimum green for
the frontage road. If there is not, the software shall skip the
frontage road that cycle.
When a pedestrian call is received on the frontage road after
the force off for the arterial phases the software shall determine
if there is enough time to provide the appropriate inside
clearance and provide the minimum pedestrian service. If
there is not, the software shall skip the frontage road that cycle.
If the pedestrian call is received on the frontage road before the
force off for the arterial phases the software shall serve the
pedestrian phase.
The software shall serve the vehicle call, if there is time, even if
the pedestrian call cannot be served that cycle.
13.2.2.3 Frontage road is coordinated
13.2.2.3.1 The software shall determine if there is enough time to serve
the arterial roadway vehicle or pedestrian phase.
13.2.2.3.2 The appropriate inside clearance shall be provided even if
the pedestrian phase was programmed to steel time from the
subsequent phase.
13.2.3 Figure 6 or 7 Diamond Sequences
13.2.3.1 Uncoordinated Operation
13.2.3.1.1 When changing from the arterial roadway to the frontage
road, the software shall call the inside clearance phase.
13.2.3.1.2 If there is a call on either frontage road the inside clearance
phase, a lagging left turn for one direction, shall be
provided. The first stage of the inside clearance shall clear
vehicles traveling in the opposite direction of the lagging left
turn. Then the first frontage road shall begin triggering the
beginning of the second stage of the inside clearance. The
second stage shall clear vehicles traveling in the same
direction as the lagging left turn.
13.2.3.2 Coordinated Operation
13.2.3.2.1 The functionality described in the Uncoordinated Operation
section shall be provided without causing a transition or
coordination failure.
13.2.3.2.2 Arterial roadway is coordinated
When a vehicle call is received on the frontage road the software
shall determine if there is enough time to provide the appropriate
inside clearance and provide a minimum green for the frontage
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 69 of 100
road. If there is not, the software shall skip the frontage road that
cycle.
When a pedestrian call is received on the frontage road after the
force off for the arterial movement in the opposite direction of the
lagging left turn the software shall determine if there is enough
time to provide the appropriate inside clearance and provide the
minimum pedestrian service. If there is not, the software shall
skip the frontage road that cycle.
If the pedestrian call is received on the frontage road before the
force off for the arterial movement in the opposite direction of the
lagging left turn the software shall serve the pedestrian phase.
The software shall service the vehicle call, if there is time, even if
the pedestrian call cannot be served that cycle.
13.2.3.2.3 Frontage road is coordinated
The software shall determine if there is enough time to serve the
arterial roadway vehicle or pedestrian phase.
The appropriate inside clearance shall be provided even if the
pedestrian phase was programmed to steel time from the
subsequent phase.
13.2.4 Figure 4 Diamond Sequence
Figure 13.2.4: Figure 4 Diamond Sequence with K-clearance
K-Clearance
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 70 of 100
13.2.4.1 Uncoordinated Operation
13.2.4.1.1 When changing from Stage 1 to Stage 4 the software shall
provide the K-clearance interval.
The northbound and westbound right turn overlap shall remain
active during the K-clearance.
The northbound and westbound right turn overlap shall remain
active for an additional amount of time equal to the duration of
the Stage 3 interval.
13.2.4.1.2 When changing from Stage 1 to Stage 5 the software shall
provide the K-clearance interval.
The westbound right turn overlap shall remain active during the
K-clearance interval.
The westbound right turn overlap shall remain active during for
an additional amount of time equal to the duration of the Stage
6 interval.
The user may choose to keep the westbound right turn overlap
active during Stage 5.
The user may choose to end the westbound right turn overlap
during Stage 5.
13.2.4.1.3 When changing from Stage 2 to Stage 5 the software shall
provide the K-clearance interval.
Northbound green clearance, Stage 3, shall not be provided.
The northbound right turn overlap shall remain active during the
K-clearance.
The northbound right turn overlap shall remain active for an
additional amount of time equal to the duration of the Stage 3
interval.
The user may choose to activate the westbound right turn
overlap during the K-clearance.
If the user activates the westbound right turn overlap during the
K-clearance, the westbound right turn shall remain active
during Stage 5.
13.2.4.1.4 When changing from Stage 2 to Stage 1 the software shall
provide not provide the K-clearance interval.
Northbound green clearance, Stage 3, shall not be provided.
The northbound right turn overlap shall remain active during
Stage 1.
13.2.4.1.5 When changing from Stage 4 to Stage 1 the software shall
provide the K-clearance interval.
The southbound and eastbound right turn overlap shall remain
active during the K-clearance.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 71 of 100
The southbound and eastbound right turn overlap shall remain
active for an additional amount of time equal to the duration of
the Stage 6 interval.
13.2.4.1.6 When changing from Stage 4 to Stage 2 the software shall
provide the K-clearance interval.
The eastbound right turn overlap shall remain active during the
K-clearance interval.
The eastbound right turn overlap shall remain active for an
additional amount of time equal to the duration of the Stage 3
interval.
The user may choose to keep the eastbound right turn overlap
active during Stage 2.
The user may choose to end the eastbound right turn overlap
during Stage 2.
13.2.4.1.7 When changing from Stage 5 to Stage 2 the software shall
provide the K-clearance interval.
Southbound green clearance, Stage 6, shall not be provided.
The southbound right turn overlap shall remain active during
the K-clearance.
The southbound right turn overlap shall remain active for an
additional amount of time equal to the duration of the Stage 6
interval.
The user may choose to activate the eastbound right turn
overlap during the K-clearance.
If the user activates the eastbound right turn overlap during the
K-clearance, the eastbound right turn shall remain active during
Stage 2.
13.2.4.1.8 When changing from Stage 5 to Stage 4 the software shall
provide not provide the K-clearance interval.
Southbound green clearance, Stage 6, shall not be provided.
The southbound right turn overlap shall remain active during
Stage 4.
13.2.4.2 Coordinated Operation
13.2.4.2.1 The functionality described in the Uncoordinated Operation
section shall be provided without causing transition or
coordination failure.
13.2.4.2.2 The software shall allow the user to select the phases that
may be skipped.
13.2.4.2.3 The software shall allow the user to select the coordinated
phases. The green for these phases shall hold until the
force off point.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 72 of 100
14 LOGS
14.1 GENERAL
14.1.1 All log entries shall be stored with a military time and date stamp.
14.1.2 All logs shall be available to the traffic management system and through the
front panel of the controller.
14.1.3 Local controller will store at a minimum all events over a seven day period.
14.1.4 The log entries shall be overwritten when full. The oldest shall be overwritten
first.
14.2 GENERAL CONTROLLER LOG
14.2.1 Power – software will log each time the controller power is turned on and off.
14.2.2 External Start – software will log each time the controller receives an external
restart from either MMU or external input.
14.2.3 Manual control – software will log the start time and end time when the
controller is operated in manual control.
14.2.4 Cabinet door – software will log the start time and end time for any occurrence
of the cabinet door being open.
14.3 CONFLICT MONITOR/MMU
14.3.1 Software shall log the start and end of each recordable fault on either the
conflict monitor or MMU.
14.4 FRONT PANEL LOG
14.4.1 Software shall log all data modifications made using the front panel.
14.4.2 Software shall log the user making modifications.
14.5 CONTROLLER SOFTWARE LOG
14.5.1 The software shall record all events and actions each day.
14.5.1.1 The software shall create a file containing the events and actions and
provide the daily file to the central system.
14.5.1.2 Using the file, the user shall be able to replay each event and action by
the software that day on a test cabinet.
14.6 DETECTOR LOG
14.6.1 The software shall support detector diagnostics that allow testing vehicle and
pedestrian detectors for no activity, maximum presence, erratic output and
communication failure.
14.6.1.1 Detector failure shall generate a log event. The log will identify the
detector number and pin assigned to that detector in the log data.
14.6.1.2 Detector restoration shall generate a log event. The log will identify the
detector number and pin assigned to that detector in the log data.
14.7 VEHICLE SPLIT LOG
14.7.1 Software shall log actual vehicle split time (in seconds) for each phase.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 73 of 100
14.7.1.1 Software shall log split times in seconds during free operation.
14.7.1.2 Software shall log split times in seconds during coordinated operation.
14.7.1.3 Software will log the sum of two services if a phase is serviced twice
during one cycle. The logged event will include an identifier that signifies
the time was split into two services.
14.7.1.4 Software will log only phases that are permitted in the controller.
14.7.1.4.1 A phase that is permitted in the controller but omitted during
a certain plan will be displayed in the log with the word omit.
14.8 CYCLE TIME LOG
14.8.1 Software shall log cycle times in seconds during free operation.
14.8.2 Software shall log cycle times in seconds during coordinated operation.
14.9 COORDINATION LOG
14.9.1 Software shall log the following events related to coordination:
14.9.1.1 Change of pattern.
14.9.1.2 Start and end of transition.
14.9.1.3 Phases skipped during transition.
14.9.1.4 Coordination failure.
14.9.1.4.1 Vehicle phase that was skipped.
14.9.1.4.2 Pedestrian phase that was skipped.
14.10 PREEMPT LOG
14.10.1 Software shall log and time stamp the following events related to preempt:
14.10.1.1 Advance input start by direction.
14.10.1.2 Advance input end by direction.
14.10.1.3 Gate input start or gates down.
14.10.1.4 Gate input end of gates down.
14.10.1.5 Start and end time of preempt, including preempt identifier (preempt
number)
14.10.1.6 Start and end time, vehicle ID number, direction, serviced provided or
denied for all emergency vehicle preemption requests.
14.10.1.7 Time special inputs received.
14.11 TRANSIT PRIORITY LOG
14.11.1 Software shall log the following events related to transit priority:
14.11.1.1 Time of request for priority and priority identifier (what priority
direction/identifier requested)
14.11.1.2 Time priority operation initiated.
14.11.1.3 End time of priority including cause for end (check-out, max time
exceeded, preempt request override)
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 74 of 100
14.11.1.4 Time priority request is denied and reason for denial.
14.11.1.5 Time denied priority request is served.
14.12 SPECIAL EVENT LOG
14.12.1 Software shall log user defined special events.
14.12.1.1 Special events will be identified by input pin number.
14.12.1.2 Software shall log the start time and end time the input pin was active.
14.13 ADVANCED OPERATION EVENT LOG
14.13.1 Advanced Operations Status Screens
14.13.1.1 Traffic Responsive Operation
14.13.1.1.1 Current value of the traffic flow threshold
14.13.1.1.2 Active plan
14.13.1.1.3 Time plan started
14.13.1.1.4 Time plan ended
14.13.1.2 Queue Detection
14.13.1.2.1 Status of each queue detector
Mode of queue detector
Is the queue detector response active
Is the queue detector response overridden
14.13.1.2.2 Current value of the volume or occupancy for each queue
detector.
14.13.1.2.3 Current value of the maximum time for each queue detector
14.13.1.2.4 Times
Time queue detector response started
Time queue detector response ended
15 USER INTERFACE
15.1 GENERAL
15.1.1 The software shall provide a user interface for data entry, status monitoring,
and management of the controller unit.
15.1.1.1 All features shall be accessible and programmable using the user
interface.
15.1.2 The user interface shall be accessible from the controller’s front panel or
remote device.
15.1.2.1 The user interface shall be automatically formatted to fit the users display
screen.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 75 of 100
15.1.3 The user interface shall ONLY display parameters that are programmed,
enabled, and/or relevant to the information being displayed. Unused phases,
data parameters (i.e. phases, detectors, overlaps, etc.) will not be displayed.
15.1.4 The software shall provide a menu-driven display format for data entry and
status information.
15.1.5 All programming must be downloadable from a remote device or the traffic
management system.
15.1.6 The software shall provide an on-screen help menu.
15.2 DATA ENTRY
15.2.1 Programming displays shall be provided in menu format to assist in data entry.
All display items shall be in English language and use standard traffic
engineering nomenclature acceptable to the City.
15.2.2 The main menu shall allow the user to select major controller functions with
submenus displayed under each major function to assist the user in identifying
all entries.
15.2.2.1 The software shall provide shortcut keys for navigating the menu
structure.
15.2.2.2 The user shall be able to return to the main menu in a single keystroke.
15.2.2.3 The user shall be able to return to the previous menu with a single
keystroke.
15.2.3 The table title and column headings shall remain visible during scrolling.
15.2.3.1 The column heading shall include at minimum the phase number.
15.2.4 The user shall be able to easily navigate to the desired cell for data entry.
15.2.5 All data entries shall be highlighted until saved into the controller’s database.
15.2.6 Information not accessible to users based on security levels shall be grayed
out or omitted.
15.3 STATUS DISPLAY
15.3.1 The software shall be able to display the real time status of the controller
operation.
15.3.2 The software shall provide a display with intersection status information
including the following:
15.3.2.1 Controller Status
15.3.2.2 Ring status
15.3.2.3 Phase Status
15.3.2.4 Coordination Status
15.3.2.5 Preemption Status
15.3.2.6 Overlap Status
15.3.2.7 Detector Status
15.3.2.8 Communication Status
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 76 of 100
15.3.2.9 Cabinet Status
15.3.2.10 Alarm Status
15.3.2.11 Advanced Operation Status
15.3.3 The Controller Status display shall include the following information
15.3.3.1 Current Date and Time
15.3.3.2 Current sync status (free, coordinated, transition)
15.3.3.3 Current plan / pattern
15.3.3.4 Flash condition (controller or cabinet)
15.3.3.4.1 Yellow flash
15.3.3.4.2 All-red flash
15.3.3.5 Current time of day / day of week pattern
15.3.3.6 Current master cycle time
15.3.3.7 Current local cycle time
15.3.3.8 Current pattern cycle
15.3.3.9 Current offset time
15.3.3.10 Special Function Output
15.3.3.11 Alarm Status
15.3.4 The Ring Status display shall include the following information for each
enabled ring.
15.3.4.1 Active phase(s) on the ring including vehicle state (Red, Yellow, Green,
Next), pedestrian state (Walk, Flashing Don't Walk, Don't Walk), vehicle
and pedestrian calls.
15.3.4.2 Minimum green timer in seconds for active phase (s)
15.3.4.3 Maximum green timer in seconds for active phase(s)
15.3.4.4 Gap or passage timer in seconds for active phase(s)
15.3.4.5 Walk timer in seconds for active pedestrian phase(s)
15.3.4.6 Flashing don’t walk timer in seconds for the active pedestrian phase(s)
15.3.4.7 Yellow clearance timer in seconds for the active phase(s)
15.3.4.8 Red clearance timer in seconds for the active phase(s)
15.3.4.9 Reason for termination of the active phases: force-off, max out, gap out.
15.3.4.9.1 The reason for termination shall remain on the display until
the next time the phase turns green.
15.3.5 The Phase Status display shall include the following information for each
enabled phase.
15.3.5.1 Phase On
15.3.5.2 Vehicle Call
15.3.5.3 Pedestrian Call
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 77 of 100
15.3.5.4 Vehicle Extension
15.3.5.5 Vehicle Red
15.3.5.6 Vehicle Yellow
15.3.5.7 Vehicle Green
15.3.5.8 Pedestrian Walk
15.3.5.9 Pedestrian Clearance
15.3.5.10 Pedestrian Don’t Walk
15.3.5.11 Phase Next
15.3.6 The Coordination Status display shall include the following information
15.3.6.1 Coordination Cycle
15.3.6.2 Coordination Sync
15.3.6.3 Free Status
15.3.6.4 Pattern Status
15.3.7 The Preemption Status display shall include the following information for each
preempt sequence
15.3.7.1 Active/Not Active
15.3.7.2 Current State
15.3.7.1 Active State or Normal or Emergency Vehicle Preempt
15.3.7.1.1 Entry One
15.3.7.1.2 Entry Two
15.3.7.1.3 Dwell
15.3.7.2 Active State of Smooth Preemption
15.3.7.2.1 Active Line
15.3.8 The Overlap Status display shall include the following information for each
enabled overlap:
15.3.8.1 Overlap Red
15.3.8.2 Overlap Yellow
15.3.8.3 Overlap Green
15.3.8.4 Overlap timers (green, yellow, red)
15.3.9 The Detector Status display shall include the following information for each
enabled detector:
15.3.9.1 Active/Not Active
15.3.9.2 Vehicle Detector Alarms
15.3.9.3 Pedestrian Detector Alarms
15.3.9.4 Delay and Extension Timers
15.3.9.5 Delay and Extension inhibit
15.3.9.6 Volume
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 78 of 100
15.3.9.7 Occupancy
15.3.9.8 Failed
15.3.9.8.1 No response programmed (always off)
15.3.9.8.2 Minimum recall
15.3.9.8.3 Maximum recall (always on)
15.3.10 The Communication Status display shall include the following information:
15.3.10.1 Field to Central (i.e. system) Communication
15.3.10.1.1 Link Status
15.3.10.1.2 Send/Receive Status
15.3.10.2 Peer-to-Peer Communication
15.3.10.2.1 Peer Link Status
15.3.10.2.2 Peer Send/Receive
15.3.11 The Cabinet Status Display shall include the following information:
15.3.11.1 Cabinet Fault Status
15.3.11.2 Channel Status
15.3.11.2.1 Channel Red
15.3.11.2.2 Channel Yellow
15.3.11.2.3 Channel Green
15.3.11.3 Assignable Input Status
15.3.11.4 Assignable Output Status
15.3.12 Advanced Operations Status Screens
15.3.12.1 Traffic Responsive Operation
15.3.12.1.1 Current value of the traffic flow threshold
15.3.12.1.2 Active plan
15.3.12.1.3 Time plan started
15.3.12.1.4 Time plan ended
15.3.12.2 Variable mode of left turn operation
15.3.12.2.1 Current mode of left turn operation by left turn
15.3.12.2.2 Current value by left turn of the volume and density data
Cycle by cycle
15 minute rolling average
15.3.12.2.3 Trigger point timers by left turn
Time to be less restrictive
Time to be more restrictive
Time between mode changes
Time of last mode change by left turn
15.3.12.3 Variable lagging left turn splits
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 79 of 100
15.3.12.3.1 Current value of the calculated left turn split for each left
turn
15.3.12.4 Traffic Responsive Flash
15.3.12.4.1 Current value of the 15 minute rolling average volumes
scaled up to a one hour volume.
Main street volume
Minor street approach volume 1
Minor street approach volume 2
15.3.12.4.2 The value of the trigger point timers
Time to be less restrictive
Time to be more restrictive
Time between mode changes
15.3.12.4.3 Current mode of operation
15.3.12.4.4 Time of last mode change
15.3.12.5 Queue Detection
15.3.12.5.1 Status of each queue detector
Mode of queue detector
Is the queue detector response active
Is the queue detector response overridden
15.3.12.5.2 Current value of the volume or occupancy for each queue
detector.
15.3.12.5.3 Current value of the maximum time for each queue detector
15.3.12.5.4 Times
Time queue detector response started
Time queue detector response ended
15.3.12.6 Cycle-by-Cycle Split Adjustments
15.3.12.6.1 Current rolling average occupancies for each phase.
15.3.12.6.2 Current splits for each phase
15.3.12.6.3 Current percentage of the cycle for each phase
15.3.12.6.4 Last change in split for each phase
15.3.12.6.5 Total change in split for each phase
15.3.12.6.6 Times
Start of adjustments
End of adjustments
15.3.12.7 Auxiliary Field Device Transition Table
15.3.12.7.1 Current Output
Default
Other Output
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 80 of 100
16 MISCELLANEOUS
16.1 SPECIAL FUNCTION/TIME OF DAY OUTPUTS
16.1.1 The controller shall provide 10 user definable special function outputs.
16.1.2 All special functions shall be capable of being activated by schedule or inputs.
16.1.3 The software shall be capable of displaying the current status (on/off) of each
special function.
16.2 ALARMS
16.2.1 The software shall support a minimum of 48 pre-defined and/or user defined
alarms.
16.2.2 All alarms shall be logged.
16.2.3 The user shall be able to configure each alarm to generate a message that will
be transmitted to the Central Supervisory System.
16.2.4 The user shall be able to trigger any physical input as an alarm.
16.2.5 All Alarms shall be classified as one of the following types.
16.2.5.1 Critical
16.2.5.2 Non Critical
16.2.5.3 Detector Fault
16.2.5.4 Coordination
16.2.5.5 Communication
16.2.5.6 Preempt
16.2.6 Critical Alarms shall include, at a minimum, the following:
16.2.6.1 Power Failure (Intersection is Dark)
16.2.6.2 Stop Time
16.2.6.3 Local Flash
16.2.6.4 MMU flash
16.2.6.5 Configuration Failure
16.2.6.6 Cycle Fail
16.2.6.7 Clock Failure
16.2.6.8 Hardware Failure
16.2.7 Non Critical Alarms shall include, at a minimum, the following:
16.2.7.1 External Start
16.2.7.2 Battery Back-up is active
16.2.7.3 Cabinet Door Open
16.2.7.4 Maximum Temperature Exceeded
16.2.7.5 Fan off
16.2.7.6 Cabinet Light Out
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 81 of 100
16.2.7.7 Local Override
16.2.8 Coordination alarms shall include, at a minimum, the following:
16.2.8.1 Coordination active
16.2.8.2 Offset transitioning
16.2.8.3 Local free
16.2.8.4 Coordination alarm
16.2.8.5 Coordination fault
16.2.8.6 Cycle fault
16.2.9 Communication alarms shall include, at a minimum, the following:
16.2.9.1 System communication fail
16.2.9.2 Peer to peer fail
16.2.10 Preempt alarms shall include, at a minimum, the following:
16.2.10.1 Railroad preempt
16.2.10.2 Emergency vehicle preempt
16.2.11 Priority alarms shall include, at a minimum, the following:
16.2.11.1 Full priority
16.2.11.2 Partial priority
16.2.11.3 Bus priority
16.3 DIAGNOSTICS
16.3.1 The software shall provide the following diagnostics:
16.3.1.1 Cabinet
16.3.1.2 Configuration
16.3.1.3 Detector
16.3.1.3.1 Defined in Section 3
16.3.1.4 Cycle
16.3.1.4.1 Yellow Clearance less than 3.0
16.3.1.5 Coordination
16.3.1.5.1 Splits not equal to cycle lengths
16.3.1.5.2 Errors in shortway transition
16.3.1.5.3 Split times less than pedestrian crossing time
16.4 TIMING SHEETS
16.4.1 The software shall provide the following types of timing sheets
16.4.1.1 Full timing sheets
16.4.1.1.1 The full timing sheets shall include all database parameters
16.4.1.2 Working timing sheets
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 82 of 100
16.4.1.2.1 Working timing sheets shall include only active or used
parameters
A template shall be created for a typical intersection with
special left turn displays.
A template shall be created for a typical diamond
intersection for the Figures 3, 4, 6, and 7.
16.4.1.2.2 Working timing sheets shall be a maximum of six (6) pages
(8 ½ inches x 11 inches)
The font shall be at least aerial narrow font size 8.
16.4.1.2.3 The working time sheet shall be printable in legal size paper.
The legal size timesheet shall have additional room in the
field for noting changes.
16.4.1.2.4 The City will approve the timesheet design for each
template.
16.4.2 The user shall be able to upload the timing sheets to the central system or
remote device.
17 DESIRABLE FEATURES
17.1 VEHICLE DETECTOR CONFIGURATION DESIRABLE FEATURES
17.1.1 Variable Lagging Left Turn Splits
17.1.1.1 Add Time Detectors
17.1.1.2 Subtract Time Detectors
17.1.2 Cycle-by-Cycle Split Adjustments
17.1.2.1 Detectors will provide occupancy data for the Cycle-by-Cycle Split
Adjustments.
17.2 VEHICLE DETECTOR TIMING DESIRABLE FEATURE
17.2.1 Variable lagging left turn split add or subtract time.
17.3 SMOOTH PREEMPT CONFIGURATION
Smooth preemption is a user defined table with several intervals. The user shall be able to define
the duration of each interval. While the table is active, the software shall operate the traffic signal in
free mode within the constraints defined by the user. On each line, the user shall define the
permitted vehicle and pedestrian phases, phases that will hold green, phases that must terminate
immediately, phases that must terminate after the minimums are satisfied, vehicle and pedestrian
phases with calls, phases with soft recalls, and special outputs that are active. If the line is not a
holding line, software shall advance to the next interval once the current interval timer has expired.
The software shall still respond to inputs from the pedestrian push buttons and vehicle detection
system if they are within the constraints defined by the user for that line. The smooth preemption
table shall be able to hold at two intervals: the first will hold on the Entry interval until the gates
active input is received and the second will hold on the Dwell interval until the gates not active is
received.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 83 of 100
17.3.1 Any of the 12 unique preempt sequences shall be configurable as a smooth
preempt type.
17.3.2 The software shall allow the user to program at least 15 intervals in the smooth
preemption sequence.
17.3.3 The smooth preemption mode shall allow the preemption sequence to omit the
clearance phase under the following conditions:
17.3.3.1 Detectors are installed, functional and capable of detection vehicles on or
approaching the railroad.
17.3.3.1.1 If a detector that detects vehicles past the presignal or on
the railroad tracks fails, track clearance will always be
provided. The input for the failed input will be always on if
the detector fail mode is maximum recall.
17.3.3.1.2 The user will select which detector inputs are required to
detect motorists on the track.
17.3.3.1.3 Vehicles are detected on the railroad tracks or between the
railroad tracks and the intersection.
17.3.4 The software shall hold in the dwell phases during track clearance. The
software shall provide track clearance if either of the following conditions are
true:
17.3.4.1 A vehicle is detected between the stop bar at the railroad tracks and the
intersection
17.3.4.2 A detector monitoring the area from the stop bar to the intersection has
failed.
17.3.5 The Entry line in the smooth preemption table will allow the use to hold in the
Dwell phases. The Dwell phases shall immediately end if a vehicle is
detected. Then the Entry phases shall begin.
17.3.5.1 If track clearance is requested, the software shall hold the track clearance
phases green as long as vehicles are detected or the gate activation input
is received.
17.3.6 The user will be able to define:
17.3.6.1 Time
This is the amount of time in seconds each interval in the smooth preemption
sequence will last.
17.3.6.2 Pedestrian Call
One call will be placed for the phases entered.
17.3.6.3 Holding Phases
Once any phases entered as a holding phase become active it shall remain
green. A hold is a continuous extension.
17.3.6.3.1 The maximum green shall not end a holding phase.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 84 of 100
17.3.6.3.2 The phase shall remain green until the software advances to
a line in the preemption table that does not have the phase
listed as a holding phase.
17.3.6.4 Advance
These phases if active will immediately end.
17.3.6.4.1 Any active vehicle phase will end immediately. Minimum
green programming is ignored.
17.3.6.4.2 Any active pedestrian phase will end immediately. The
pedestrian phase will be truncated.
17.3.6.5 Force Off
These phases if active will end as soon as all minimums are met. A
pedestrian phase will be truncated.
17.3.6.5.1 Any active vehicle phase will end after the minimum green is
provided.
17.3.6.5.2 Any active pedestrian phase will end after the vehicle phase
minimum green is provided.
17.3.6.6 Call
These phases will have a constant minimum recall.
17.3.6.6.1 Other phases permitted on that line in the smooth
preemption table shall be able to receive calls from the
detectors.
17.3.6.7 Soft Recall
These phases shall have a call only if no other permitted phases on that line
in the smooth preemption table have a call.
17.3.6.8 Permit
These phases shall be able to turn green if there is a call for the phase.
17.3.6.8.1 Phase entered in the special event table shall be allowed to
turn green even if they are omitted elsewhere in the
software.
17.3.6.8.2 These phases cannot accept extensions.
17.3.6.9 Omit Vehicle Overlap
These overlaps shall begin clearing immediately once the interval is active. If
the overlap is already red, it shall remain red.
17.3.6.10 Omit Pedestrian Phase or Pedestrian Overlap
These pedestrian phases and overlap shall not be allowed to begin.
17.3.6.10.1 Any call for these pedestrian phases and overlaps will latch
and a call will be placed for the pedestrian movements once
the omits are lifted.
17.3.6.11 Special Output
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 85 of 100
These outputs shall be used to activate auxiliary devices.
17.3.6.11.1 The special output shall remain on as the software advances
to the next interval if that special output is entered in the
next interval.
17.3.7 The permitted window for a phase in the coordinated timing plan will not cause
a phase to end while smooth preemption is active.
17.3.8 The user shall be able to select the inputs that will cause the software to hold
in a certain preemption state. There shall be two holding lines: the Entry
phase line will hold during the advance railroad inputs and the Dwell phase
line will hold during the gates down input.
17.3.8.1 The first preemption input shall activate the preemption sequence. The
software shall advance through the preemption intervals to the first
holding line and remain on that line until the first input turns off.
17.3.8.1.1 The first hold will be the entry phases.
17.3.8.1.2 The time entered for the Entry line shall not count until the
hold input turns off and the software wants to advance.
17.3.8.1.3 The software shall continue to hold on the line regardless of
the state of the second input.
17.3.8.2 Once the first input turns off and the second input is active the software
shall advance to the next line in the table. If the railroad does not turn off
the first signal when the second signal turns on, the software shall provide
the logic functions to turn off the first input.
17.3.8.2.1 The second hold will be the dwell interval.
17.3.8.2.2 The time entered for the hold shall not count until the
holding input turns off and the software wants to advance.
17.3.8.2.3 The software shall continue to hold on the second holding
line until the second input turns off.
17.3.9 Preemption shall override all priorities.
17.3.10 High priority preempts shall override low priority preempts.
17.3.10.1 A request for a high priority preemption event shall immediately cancel
any active low priority preemption event and begin the high priority
event.
17.3.11 Low priority preempts shall be ignored until the high priority preempt
terminates.
17.3.11.1 The low priority event shall begin running in the background. Once the
inputs for high priority event terminates, the high priority event
immediately end and the low priority event shall output its current
state.
17.3.11.2 Any part of the high priority event that occurs after the high priority
event input terminates shall be cancelled. The software shall
immediately output the low priority event
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 86 of 100
17.3.12 Equal priority preempts shall be served on a first called, first served basis.
17.3.12.1 The second preemption sequence shall begin running in the
background. Once the inputs for first preemption sequence turn off the
first sequence shall immediately end and second preemption sequence
shall output its current state.
17.3.12.2 Any part of the first preemption sequence that occurs after the first
preemption input turns off will be cancelled. The software shall
immediately output the second preemption sequence.
17.4 TRAFFIC ADAPTIVE OPERATION
If the Proposer has an adaptive solution the City desires a presentation of the functionality and a bid.
The controller software shall not be responsible for traffic adaptive decisions. An independent traffic
adaptive computer will be installed at each intersection in the group. The traffic adaptive computer
will process detector data, communicate with other traffic adaptive computers in the group of
intersections, and provide outputs to the controller. The controller shall, using standard controller
software features, respond to inputs sent from the traffic adaptive computer. These inputs shall be
understood by the controller without any modification to the controller software.
17.4.1 A traffic adaptive system shall provide inputs to the controller software and
those inputs shall be understood by the controller software without any
modifications to the controller software.
17.4.2 The controller software shall operate in free mode while the intersection is
operating in adaptive mode. The traffic adaptive computer shall provide inputs
for the controller software.
17.4.2.1 The controller software shall allow the user to assign an input to free
mode operation. The controller software shall operate the intersection in
free mode when the input is active.
17.4.3 The user shall define sub groups of intersections within the group. Any traffic
adaptive computer or peer-to-peer communication failure shall cause the traffic
adaptive computer to cancel free mode. The controller software shall revert
back to normal operation based on the time of day/day of the week schedule.
17.4.3.1 If the controller software loses peer-to-peer communication with another
controller in the subgroup, it will exit free mode.
17.4.3.2 The controller software shall command other intersections in the subgroup
to exit free mode.
17.5 VARIABLE MODE OF LEFT TURN OPERATION
The controller software will vary the mode of left turn operation based on the current traffic volumes
and/or detector occupancy. The user will define the mode of left turn operation the controller
software can select. The user will enable this feature for each left turn by the time of day/day of
week.
17.5.1 The software shall provide this operation for at least four (4) left turns.
17.5.2 The software shall allow the user to select the times of day/days of week that
this feature is active for each left turn.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 87 of 100
17.5.3 The user shall select the modes of operation the controller software may
choose for each left turn.
17.5.3.1 Protected only
17.5.3.2 Permitted/protected
17.5.3.3 Permitted only
17.5.4 Changes in the mode of left turn operation shall occur when all of the phases
associated with a left turn are red.
17.5.5 The software shall process the following data from the detection system for
each left turn.
17.5.5.1 The left turn volume
17.5.5.2 Opposing through volume.
17.5.5.3 Opposing left turn volume.
17.5.5.4 Opposing left turn detector occupancy
17.5.5.4.1 The detector occupancy shall be the measured during the
protected and permitted green for the oncoming left turn.
17.5.6 The software shall be capable of receiving global changes to the trigger points
from the central system. The user will make a change in one master table for
a group of intersections through the central system software and download that
change to the entire group.
17.5.7 The controller software shall calculate the product of the left turn volume and
the oncoming through volume. The software shall allow the user to define
trigger points that will be the boundary between the modes of left turn
operation.
17.5.8 The controller software shall measure the oncoming left turn volume and
occupancy. The software will allow the user to define trigger points that will be
the boundary between the modes of left turn operation.
17.5.9 Trigger Points
These are the boundaries between the modes of left turn operation. If the data crosses the
boundary, the software will want to change the mode of left turn operation.
17.5.9.1 Trigger points for the product of the oncoming through and left turn
volumes.
17.5.9.1.1 The user shall be able to enter two volume trigger points
between 10,000 and 200,000.
17.5.9.1.2 One trigger point will be the boundary between protected
only and protected/permitted
17.5.9.1.3 One trigger point will be the boundary between
protected/permitted and permitted only.
17.5.9.2 Trigger points for the oncoming left turn volumes and occupancy
17.5.9.2.1 The user shall be able to define two volume trigger points
between 0 and 1000.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 88 of 100
One trigger point will be the boundary between protected only
and protected/permitted.
One trigger point will be the boundary between
protected/permitted and permitted only.
17.5.9.2.2 The user shall be able to define two occupancy trigger
points between 0 and 100 percent.
One trigger point will be the boundary between protected only
and protected/permitted.
One trigger point will be the boundary between
protected/permitted and permitted only.
17.5.9.3 The software shall provide two ways to aggregate data and compare it to
the trigger points.
17.5.9.3.1 Cycle by cycle: the data shall cross a trigger point boundary
each cycle for at least the minimum amount of time before
the software will want to change the mode of left turn
operation.
17.5.9.3.2 15 minute rolling average: the 15 minute rolling average of
the data shall cross a trigger point boundary for at least the
minimum amount of time before the software will want to
change the mode of left turn operation.
17.5.9.4 Trigger point timer
The data shall meet a trigger point for a user defined amount of time before
the software will change the mode of left turn operation. A mode of left turn
operation shall be active for a user defined minimum amount of time before
the software will change the mode of operation.
17.5.9.4.1 Minimum Time to Be Less Restrictive
This is the amount of time in minutes that the data shall be less
than the trigger point before the software can change the mode of
left turn to a mode that is less restrictive.
There shall be a timer for each calculation for each left turn.
17.5.9.4.2 Minimum Time to Be More Restrictive
This is the amount of time in minutes that the data shall be more
than the trigger point before the software can change the mode of
left turn to a mode that is more restrictive.
There shall be a timer for each calculation for each left turn.
17.5.9.4.3 Minimum Time between Mode Changes
This is the amount of time in minutes between changes in the mode
of left turn operation.
The software shall not change the mode of left turn operation
until the minimum time between mode changes has elapsed.
The timers for the minimum time to be less restrictive and the
minimum time between mode changes shall time concurrently.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 89 of 100
The timers for the minimum time to be more restrictive and the
minimum time between mode changes shall time concurrently.
If the variable mode of left turn feature is disabled by manual
override or the time of day/day of week schedule the minimum
time between mode changes timer shall not apply.
17.5.10 The user shall be able to activate the oncoming through and oncoming left
turn calculations at the same time. When both are active, the software shall
determine the desired mode of left turn operation for each calculation.
17.5.10.1 If the calculations select different modes of left turn operation, the
software shall allow the user to select the more or less restrictive mode of
left turn operation.
17.5.11 If a detector fails, the mode of left turn operation will turn off for the effected
left turn.
17.5.11.1 The left turn shall return to the mode of operation programmed in the time
of day/day of week schedule.
17.5.11.2 An alarm will be generated that includes:
17.5.11.2.1 The left turn effected
17.5.11.2.2 The mode of operation for that left turn
17.5.11.2.3 A timestamp
17.5.12 Events shall be logged and time stamped for each left turn.
17.5.12.1 When the feature turns on
17.5.12.2 When the feature turns off
17.5.12.3 Any changes in the mode of left turn operation
17.5.12.4 The raw data for each cycle used in the calculation
17.5.12.5 The calculations for each cycle
17.5.13 Configuration parameters for variable mode of left turn operation
17.5.13.1 Enable
17.5.13.1.1 By left turn
17.5.13.1.2 For all left turns
17.5.13.1.3 Selected based on time of day/day of week schedule
17.5.13.2 Enable oncoming through calculation
17.5.13.2.1 By left turn
17.5.13.2.2 For all left turns
17.5.13.2.3 Selected based on time of day/day of week schedule
17.5.13.3 Enable oncoming left turn calculation
17.5.13.3.1 By left turn
17.5.13.3.2 For all left turns
17.5.13.3.3 Selected based on time of day/day of week schedule
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 90 of 100
17.5.13.3.4 Select volume
17.5.13.3.5 Select occupancy
17.5.13.4 Data aggregation
17.5.13.4.1 Per cycle
17.5.13.4.2 Rolling average
17.5.13.4.3 Number of minutes included in the rolling average
17.5.13.5 Minimum time to become more restrictive
17.5.13.5.1 For each left turn
17.5.13.5.2 For all left turns
17.5.13.6 Minimum time to become less restrictive
17.5.13.6.1 For each left turn
17.5.13.6.2 For all left turns
17.5.13.7 Minimum time between changes in left turn operation
17.5.13.7.1 For each left turn
17.5.13.7.2 For all left turns
17.5.13.8 Mode of left turn operation when both calculations are active
17.5.13.8.1 More restrictive mode
17.5.13.8.2 Less restrictive mode
17.5.13.9 Permitted modes of left turn operation.
17.5.13.9.1 By left turn
17.5.13.9.2 For all left turns
17.5.13.9.3 Selected based on time of day/day of week schedule
17.5.13.9.4 Modes of left turn operation
Protected only
Protected/Permitted
Permitted only
17.5.13.10 Oncoming through trigger points
17.5.13.10.1 By left turn
17.5.13.10.2 For all left turns
17.5.13.10.3 Trigger point between protected only and
protected/permitted
17.5.13.10.4 Trigger point between protected/permitted and permitted
only
17.5.13.11 Oncoming left turn calculation
17.5.13.11.1 By left turn
17.5.13.11.2 For all left turns
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 91 of 100
17.5.13.11.3 Volume trigger point between protected only and
protected/permitted
17.5.13.11.4 Occupancy trigger point between protected only and
protected/permitted
17.5.13.11.5 Volume trigger point between protected/permitted and
permitted only
17.5.13.11.6 Occupancy trigger point between protected/permitted and
permitted only
17.6 VARIABLE LAGGING LEFT TURN SPLITS
The controller will vary the split for a lagging left turn when the software is operating in coordinated
mode. The split will be determined based on the traffic in the left turn lane that cycle. The beginning
of the lagging left turn phase will be moved later and the time not used by the lagging left turn will be
added to the split for the oncoming through movement.
17.6.1 The end of the left turn shall not be adjusted by this advanced operation.
17.6.1.1 Other advanced operation features may adjust the end of the lagging left
turn.
17.6.2 The software shall provide at least a minimum split if there is a call for the
lagging left turn phase.
17.6.3 The software will delay the beginning of the lagging left turn.
17.6.3.1 The software shall delay the beginning of the lagging left turn based on
the number of vehicles in the left turn lane that cycle.
17.6.3.2 The amount of time not needed for the lagging left turn split shall be
added to the green interval for the opposing through movement.
17.6.3.3 Calculating the left turn split.
17.6.3.3.1 Each vehicle entering the left turn lane will pass through a
detection point.
Each detection will add a user defined amount of time to the left
turn split up to the maximum split for the active plan.
The software shall allow the user to define these detectors for
each left turn.
Time shall be added to the left turn split regardless of the active
phases.
17.6.3.3.2 Each vehicle exiting the left turn lane will pass through a
detection point.
Each detection will subtract a user defined amount of time from
the left turn split to the active minimum green time.
The software shall allow the user to define these detectors for
each left turn.
Time shall be subtracted from the left turn split regardless of
the active phases.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 92 of 100
The software shall not subtract time from the left turn split for a
user defined amount of time in seconds after the beginning of
the left turn phase green.
17.6.3.3.3 The software will reset the calculated left turn split to zero
(0) at the beginning of green for the left turn.
The calculated left turn split shall not be less than zero (0)
seconds.
If the left turn is served more than once per cycle, the
calculated left turn split shall be reset at the beginning of each
green for the left turn.
17.6.4 The software shall provide this operation for at least four (4) left turn
movements.
17.6.5 If the left turn is not lagging, the feature shall have no effect.
17.6.6 In the event of a detector failure the programmed split will be provided.
17.6.7 In the event of a detector failure, an alarm with a timestamp will be generated
that includes.
17.6.7.1 The left turn effected
17.6.8 Configuration Parameters
17.6.8.1 Enable
17.6.8.1.1 By left turn
17.6.8.1.2 For all left turns
17.6.8.1.3 Selected based on time of day/day of week schedule
17.6.8.2 Added and Subtracted Time
This is the time in tenths of seconds added to or subtracted from the calculated left
turn split for each vehicle.
17.6.8.3 Detectors that add time
17.6.8.3.1 If the detection is associated with more than one phase, the
time will be added to the lagging left turn phase. Other
phases will not be effected.
17.6.8.4 Detectors that subtract time
17.6.8.4.1 If the detection is associated with more than one phase, the
time will be subtracted from the lagging left turn phase.
Other phases will not be effected.
17.6.8.5 Disable Subtraction Detectors
This is the amount of time in seconds after the lagging left turn phase turns green
that time will not be subtracted from the left turn split for vehicles passing through
the subtraction detection points.
17.6.8.5.1 The user shall be able to define this amount of time for each
left turn.
17.7 TRAFFIC RESPONSIVE FLASH OPERATION
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 93 of 100
17.7.1 The software will select normal operation, yellow flash, or all-red flash based
on current traffic volumes.
17.7.2 The user shall select the time of day/days of week the software may choose
the mode of operation.
17.7.3 The software will allow the user to select trigger points for the volumes.
A trigger point is the boundary between the modes of traffic signal operation. If the data
crosses the boundary, the software will want to change the mode traffic signal operation.
17.7.3.1 Three (3) sets of trigger points will be provided. One set for each of the
three (3) volume signal warrants defined the current edition of the Manual
on Uniform Traffic Control Devices.
17.7.3.1.1 The software will allow the user to select the signal warrant
that will be used to determine the mode of traffic signal
operation.
17.7.3.2 The software shall allow the user to define a K value to scale the traffic
volume data collected by the data collection system.
17.7.3.2.1 Two K values shall be provided.
One for the major street volume.
One for the minor street volumes.
The K values shall range from at least 10 percent to 200
percent.
The user shall be able to vary the K values by Time of Day/
Day of Week.
17.7.3.3 The software shall allow the user to select one (1) to 60 minute rolling
average volume that shall be scaled up to one hour volume to determine if
the signal warrant is met.
17.7.3.3.1 If a signal warrant is met, the software will want to change to
normal operation.
17.7.3.3.2 If a signal warrant is not met, the software will want to
change to yellow-red or all-red flash operation.
17.7.3.4 Minimum Time before Changing To Normal Operation
This is the amount of time in minutes that the data shall be more than the
trigger point before the software shall change to normal operation.
17.7.3.5 Minimum Time before Changing To Flash Operation
This is the amount of time in minutes that the data shall be less than the
trigger point before the software shall change to flash operation.
17.7.3.6 Minimum Time between Changes
This is the amount of time in minutes between changes in the mode of traffic
light operation. The timers for minimum time before changing to normal
operation and minimum time before changing to flash operation shall time
concurrently. The software shall not change the mode of traffic light
operation until the minimum time between mode changes has elapsed.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 94 of 100
17.7.4 If a detector fails, the software will change operation based on the time of
day/day of week schedule.
17.7.4.1 The minimum time between changes must be satisfied.
17.7.5 In the event of a detector failure, an alarm with a timestamp will be generated.
17.7.5.1 The new mode of operation, which is based on the Time of Day/Day of
Week schedule shall be included.
17.7.6 Changes in the mode of traffic light operation shall be logged.
17.7.6.1 The mode of traffic light operation
17.7.6.2 The volumes for the main street
17.7.6.3 The volumes for each minor street approach
17.7.6.4 Timestamp
17.7.7 Configuration parameters for the variable mode of traffic light operation.
17.7.7.1 Enable
17.7.7.1.1 Selected based on time of day/day of week schedule
17.7.7.2 The number of lanes on the major street
17.7.7.2.1 One (1) lane
17.7.7.2.2 Two (2) or more lanes
17.7.7.3 The number of lanes on minor street approach one
17.7.7.3.1 One (1) lane
17.7.7.3.2 Two (2) or more lanes
17.7.7.4 The number of lanes on minor street approach two
17.7.7.4.1 One (1) lane
17.7.7.4.2 Two (2) or more lanes
17.7.7.5 K value for the major street
17.7.7.6 K value for the minor street
17.7.7.7 Active Signal Warrant
17.7.7.7.1 Warrant 1, Eight-Hour Vehicular Volume
17.7.7.7.2 Warrant 2, Four-Hour Vehicular Volume
17.7.7.7.3 Warrant 3, Peak Hour
17.8 CYCLE-BY-CYCLE SPLIT ADJUSTMENTS
While running coordination, the software will adjust the splits for all of the phases to balance the delay
at the intersection. In no case shall the feature cause the coordinator to fail.
17.8.1 The software shall adjust the green time for every active phase based on data
collected by the detection system.
17.8.1.1 The software shall collect the detector occupancy while the phase is
green.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 95 of 100
17.8.1.2 If there are multiple detectors for a movement the occupancies will be
averaged.
17.8.1.3 A rolling average of the occupancy data will be used to determine the
cycle-by-cycle split adjustments.
17.8.1.3.1 The software shall allow the user to select the amount of
time in minutes from at least one (1) to 30.
17.8.2 Cycle-by-cycle split adjustments shall be enabled by:
17.8.2.1 Time of day/day of week schedule
17.8.2.2 Manual command
17.8.3 The minimum occupancy, defined by the user, shall be exceeded by at least
the rolling average occupancy for one phase before the cycle-by-cycle split
adjustments feature will activate.
17.8.4 When a new plan is called, the software shall proportionally apply the current
adjustments to the new plan.
17.8.5 If there are multiple detectors for a phase, the occupancy shall be averaged
17.8.6 The software shall continue to run the active coordination plan while this
feature is active.
17.8.6.1 If time is added to the split for the coordinated movement, half of the
adjustment shall be added to the active offset.
17.8.6.2 If time is subtracted from the split for the coordinated movement, half of
the adjustment shall be subtracted from the offset.
17.8.7 Configuration parameters for Cycle-by-Cycle Split Adjustments
17.8.7.1 Enable
17.8.7.2 Detectors
17.8.7.2.1 Phase associated with that detector.
17.8.7.3 Number of cycles included in the rolling average.
17.8.7.4 Maximum Green Shift per Cycle
This is the maximum amount of green that shall be added or subtracted during an
adjustment.
17.8.7.4.1 For each phase
17.8.7.4.2 Percentage of the cycle
17.8.7.4.3 Amount of time in seconds
17.8.7.5 Maximum Total Green Add
17.8.7.5.1 For each phase
17.8.7.5.2 Percentage of the cycle
17.8.7.5.3 Amount of time in seconds
17.8.7.6 Maximum Total Green Reduction
17.8.7.6.1 For each phase
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 96 of 100
17.8.7.6.2 Percentage of the cycle
17.8.7.6.3 Amount of time in seconds
17.8.7.7 Minimum occupancy to activate cycle-by-cycle split adjustments
17.8.7.7.1 This feature shall turn off once the rolling average
occupancies for all phases are below the minimum
occupancy.
17.8.8 The software shall log and timestamp
17.8.8.1 The rolling average of the occupancy for each phase
17.8.8.2 The splits that were calculated by the software each cycle.
17.8.9 In the event of detector failure an alarm with a timestamp shall be generated
and include
17.8.9.1 The detector that failed
17.9 AUXILIARY FIELD DEVICE TRANSITION TABLE
These tables will be used to change the state of auxiliary field devices. For example if a lane control
sign needs to change from left only to through only, the user will program a time of day output to
activate the auxiliary field device output transition table. The first line of the table will output left only
to the lane control sign. The second line of the table will output left/through to the lane control sign.
The third line of the table will output through only to the lane control sign. The third line will also be
the holding line so the through only will be displayed as long as that time of day output is active.
When the time of day output turns off, the software shall move to the fourth line and output a
left/through to the lane control sign. Finally the fifth line of the table will output left only. Then
software will exit the table.
17.9.1 The software shall provide at least four (4) transition sequence tables for
auxiliary field devices.
17.9.2 The time of day outputs shall be linked to the assignable outputs table in the
logic functions.
17.9.3 The software shall be capable of using the time of day outputs to activate or
change the state of field equipment.
17.9.4 When the output turns off the software shall finish running the transition table.
17.9.5 The software shall be capable of outputting a default state to the auxiliary field
device when the transition table is not active.
17.9.6 Configuration parameters
17.9.6.1 Enable
17.9.6.2 Time
This is the amount of time in minutes that the line in the transition sequence
table shall remain active.
17.9.6.3 Output
This is the state of the auxiliary field device while this line in the transition
sequence table is active.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 97 of 100
17.9.6.3.1 The user shall be able to enter the state of the auxiliary
device in the table. The software shall output that state
when that line in the table is active.
17.9.6.4 Default Output
This is the state of the auxiliary device when the transition table is not active.
17.9.6.5 Holding Line
The table will hold on this line as long as the time of day output is on that
activated the table.
17.10 LOGS FOR DESIRABLE FEATURES
17.10.1 Variable mode of left turn operation
17.10.1.1 Current mode of left turn operation by left turn
17.10.1.2 Current value by left turn of the volume and density data
17.10.1.2.1 Cycle by cycle
17.10.1.2.2 Rolling average
17.10.1.3 The value of the trigger point timers by left turn
17.10.1.3.1 Time to be less restrictive
17.10.1.3.2 Time to be more restrictive
17.10.1.3.3 Time between mode changes
17.10.1.3.4 Time of last mode change by left turn
17.10.1.4 Variable lagging left turn splits
17.10.1.4.1 Current value of the calculated left turn split for each left
turn
17.10.2 Traffic Responsive Flash
17.10.2.1 Current value of the 15 minute rolling average volumes scaled up to a one
hour volume.
17.10.2.1.1 Main street volume
17.10.2.1.2 Minor street approach volume 1
17.10.2.1.3 Minor street approach volume 2
17.10.2.2 Trigger point timers
17.10.2.2.1 Time to be less restrictive
17.10.2.2.2 Time to be more restrictive
17.10.2.2.3 Time between mode changes
17.10.2.3 Current mode of operation
17.10.2.4 Time of last mode change
17.10.3 Cycle-by-Cycle Split Adjustments
17.10.3.1 Current rolling average occupancies for each phase.
17.10.3.2 Current splits for each phase
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 98 of 100
17.10.3.3 Current percentage of the cycle for each phase
17.10.3.4 Last change in split for each phase
17.10.3.5 Total change in split for each phase
17.10.3.6 Times
17.10.3.6.1 Start of adjustments
17.10.3.6.2 End of adjustments
17.10.4 Auxiliary Field Device Transition Table
17.10.4.1 Current Output
17.10.4.1.1 Default
17.10.4.1.2 Other Output
17.11 INTERSECTION TO VEHICLE INFORMATION
The software shall be capable of providing static and real time information directly to vehicles and to
the central system. The vendor shall assist the City in anticipating the information that will be
required. The Proposer shall coordinate with On Time Systems (Green Driver) and other emerging
Intersection to Vehicle standards so the software provides the needed static and real-time data in the
correct format.
17.11.1 Static Information
This information shall be automatically updated when changes are made in the field or the
central system database.
17.11.1.1 Is there a right turn signal per direction
17.11.1.2 Are right turns on red permitted per direction
17.11.1.3 Are left turns on red permitted per direction
17.11.1.4 Permitted phases
17.11.1.5 This information shall be provided per permitted phase
17.11.1.5.1 Direction associated with each phase
The user shall choose from the eight (8) cardinal
and intermediate directions.
17.11.1.5.2 Movement associated with each phase
17.11.1.5.3 U-turn, left, through, or right
17.11.1.5.4 Minimum recall
17.11.1.5.5 Maximum recall
17.11.1.5.6 Pedestrian recall
17.11.1.5.7 Walk rest
17.11.1.5.8 Dual entry
17.11.1.5.9 Coordinated phases
17.11.1.5.10 Red lock
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 99 of 100
17.11.1.5.11 Yellow lock
17.11.1.5.12 Red rest
17.11.1.5.13 Exclusive
17.11.1.5.14 Mode of left turn operation
17.11.1.5.15 Permitted only
17.11.1.5.16 Protected/permitted
17.11.1.5.17 Protected only
17.11.1.5.18 Yellow flash
17.11.1.5.19 Red flash
17.11.1.5.20 Pedestrian walk time
17.11.1.5.21 Pedestrian walk time 2
17.11.1.5.22 Pedestrian clearance
17.11.1.5.23 Pedestrian clearance 2
17.11.1.5.24 Minimum green
17.11.1.5.25 Minimum green 2
17.11.1.5.26 Vehicle Extension
17.11.1.5.27 Maximum green
17.11.1.5.28 Maximum green 2
17.11.1.5.29 Maximum green 3
17.11.1.5.30 Maximum initial
17.11.1.5.31 Time before reduce
17.11.1.5.32 Time to reduce
17.11.1.5.33 Reduce by
17.11.1.5.34 Maximum gap
17.11.1.5.35 Minimum gap
17.11.1.5.36 Yellow clearance
17.11.1.5.37 All-red clearance
17.11.1.5.38 Plan number
17.11.1.5.39 Force Offs
17.11.1.5.40 Splits
17.11.1.5.41 Lagging phases
17.11.2 Real-Time Information
The controller shall be capable of providing the current state of the parameters listed in this
section to a vehicle or the central system every second.
17.11.2.1 Time stamp
17.11.2.2 Local cycle timer (top-of-cycle)
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page 100 of 100
17.11.2.3 Current split per phase
17.11.2.3.1 Account for variable lagging left turn splits
17.11.2.3.2 Account for cycle-by-cycle split adjustments
17.11.2.4 Current mode of left turn operation by phase
17.11.2.4.1 Permitted only
17.11.2.4.2 Protected/permitted
17.11.2.4.3 Protected only
17.11.2.5 Current mode of signal operation
17.11.2.5.1 Normal
17.11.2.5.2 Yellow flash
17.11.2.6 Green phases
17.11.2.6.1 Amount of time in seconds phase will remain green
17.11.2.7 Yellow phases
17.11.2.8 Red phases
17.11.2.8.1 Amount of time in seconds phase will remain red
17.11.2.9 Vehicle calls
17.11.2.10 Active pedestrian phases
17.11.2.11 Pedestrian calls
17.11.2.11.1 If walk 1 or walk 2 will be provided
17.11.2.11.2 If pedestrian clearance 1 or pedestrian clearance 2 will
be provided
17.11.2.12 Current state of the overlaps – on/off
17.11.2.13 Active timing plan
17.11.2.14 Communication status (On-line status)
17.11.2.15 Operation status
17.11.2.15.1 Normal
17.11.2.15.2 Free
17.11.2.15.3 Preempt
17.11.2.15.4 Transition
17.11.2.15.5 All-red flash
17.11.2.15.6 Yellow flash
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page A-1
ATTACHMENT 1
APPENDIX A
National Transportation Communication for ITS Protocol (NTCIP) Compliance
1 GENERAL
The local controller software shall comply with all applicable NTCIP standards documents. Compliance
shall be to the currently approved or recommended version(s) of the relevant NTCIP standards on the date
of the initial acceptance of the software by the Cities.
It is the responsibility of the Offerors to demonstrate to the City’s satisfaction that their proposed
controller software is in full compliance with the provisions of this Appendix.
The controller must be able to implement all NTCIP messages called for in this Specification without any
additional vendor-specific proprietary statements.
1.1 DOCUMENTATION
The software shall be supplied with full documentation. Documentation shall include electronic and hard
copy. The electronic copy shall be provided on a CD-ROM. The documentation shall include all NTCIP
standard MIBs and extensions, developer-specific MIBs, and all SNMP/STMP data elements. All MIBs
shall be provided in American Standard Code for Information Exchange (ASCII) format using ASN.1
notation.
1.2 RE-DISTRIBUTION AND RE-USE RIGHTS
The Offeror shall not place any limitations on the re-distribution and re-use of the MIB. Cities licensed to
use the software shall be able to re-distribute and/or re-use the MIBs as required to provide the required
functionality defined in this specification.
1.3 MIB EXTENSIONS
The Offeror shall clearly define all MIB extensions. Primarily, all extensions shall be accomplished by the
following methods:
1.3.1 Extending the capabilities of existing standard features.
1.3.2 Defining new data elements or features under a developer-specific MIB
extension.
To the extent possible, the replacement of a partially complete feature with a complete custom feature shall
be avoided.
1.4 SUPPORT OF NTCIP STANDARDS, AMENDMENTS AND REVISIONS
The Offeror shall address any proposed revisions or draft amendments to the required NTCIP MIBs
available during the initial procurement stage and the impact on the proposed software’s NTCIP
compliance and/or ability to meet the functional requirements of this specification. The initial procurement
stage shall be extended from the date of release of this specification to one (1) year beyond the initial
acceptance of the software by the Cities.
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page A-2
In addition, the Offeror shall provide to the Cities for the life of the software, electronic and hard copies of
the MIB whenever changes are made due to changes to the standard, new software features, or bug fixes.
The electronic copies shall comply with the requirements in Section 1.1 Backward compatibility is required.
1.5 OBJECT RANGE VALUES
All objects required by these specifications shall support all values within their standardized ranges, unless
otherwise approved by the Project Engineer. A size, range, or enumerated listing indicated in the object's
SYNTAX field or through descriptive text in the object's DESCRIPTION field of the relevant standard
defines the ‘standardized range.
The Offeror shall prepare a table of object range values for each object In NTCIP Standards1201 and
1202 and identify any variances from the standard ranges that are required to meet this
specification.
2 NTCIP STANDARDS
The Offeror shall define an entre NTCIP stack and identify the NTCIP, or other standards that will be
required at each level to meet the specifications contained in this document. For each NTCIP standard,
Offerors shall complete a Profile Implementation Conformance Statement (PICS) identifying each
required object. All mandatory objects identified in the standards shall be included in the PICS.
As a minimum, the software shall comply with the following standards:
2.1 GENERAL
2.1.1 NTCIP 1101 v01.12 - NTCIP Simple Transportation Management Framework
2.1.1.1 The software shall comply with Conformance Level 2
2.1.2 NCTIP 1102: 2004 – NTCIP Octet Encoding Rules (OER)
2.1.3 NTCIP 1103 v01 - NTCIP Transportation Management Protocols (TMP)
2.1.3.1 The software shall includesupport for the “Simple Fixed Message
Protocol” (SFMP)
2.1.4 NTCIP 8004 v01 - NTCIP Structure and Identification of Management
Information (SMI)
2.2 INFORMATION LEVEL
2.2.1 NTCIP 1201v03 – NTCIP Global Objects (GO) Definitions
2.2.2 NTCIP 1202:2005 – NTCIP Object Definitions for ASC
2.2.2.1 The software shall fully implement all mandatory objects of all mandatory
and optional conformance groups defined in this standard
2.3 APPLICATION LEVEL
2.3.1 NTCIP 2303:2001 v01.06 – NTCIP AP-FTP
2.3.2 NTCIP 2301: v02 - NTCIP AP-STMF
2.4 TRANSPORT LEVEL
2.4.1 NTCIP 2201:2003 - NTCIP TP-Transportation Transport Profile
2.4.2 NTCIP 2202:2001 - NTCIP TP-Internet (TCP/IP and UDP/IP) Transport Profile
2.5 SUBNETWORK LEVEL
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page A-3
2.5.1 NTCIP 2101:2001 - NTCIP SP-PMPP/RS232
2.5.2 NTCIP 2102:2003 – NTCIP SP-PMPP/FSK
2.5.3 NTCIP 2104:2003 – NTCIP SP-Ethernet
Offerors are required to identify and comply with any additional NTCIP or other standards necessary to
meet the specifications of this document.
End of Appendix A
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-1
ATTACHMENT 1
APPENDIX B
Compliance Matrix
Instructions:
1. Offerors shall provide a response for every requirement.
2. The presented requirements are inclusive of all subheadings and descriptions included in the
requirements document. If the proposed software does not comply with all subheadings and
descriptions of a particular requirement, the requirement shall be identified as “Partially Meets
Requirements” and the Offeror shall specify in the comments area the specific subheadings or
descriptions that are not met.
Name of Offeror:______________________________________________________________________
Name of Proposed SoftwarePackage:_____________________________________________________
Current Software Version:___________________
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
1.0 GENERAL AND ADMINISTRATIVE
1.2 Intersection Information
1.2.1 User defined intersection information
1.3 Controller Information
1.3.1 Controller information
1.4 Software Upgrades
1.4.1 Automatic software upgrade notice
1.4.2 Remote software download
1.4.3 Software reside in flash memory
1.4.4 Software download verification
1.5 Copy/Paste
1.5.1 Copy and paste capability
1.6 Save Changes
1.6.1 Confirm changes prior to acceptance
1.6.2 Highlight changes
1.6.3 Changes activated by confirmation
1.7 Compatibility with Existing Infrastructure
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-2
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
1.7.1 Standard templates for 33x cabinets
1.7.2 Compatibility with CM/MMU
1.8 Industry Standard Nomenclature
1.8.1 Industry standard nomenclature
1.8.2 Industry standard software development
1.9 Security
1.9.1 Password access
1.9.2 Remote access control
1.10 Web Browser
1.10.1 Controller resident web server
1.10.2 Web user interface object support
1.10.3 Status objects
1.10.4 Web server Mib parameters
1.11 Daylight Savings Time
1.11.1 Daylight savings time programmability
1.11.2 DST default enabled
2.0 CONFIGURATION
2.1 Configuration Tables
2.1.1 Multiple configuration tables
2.2 Cabinet Configuration
2.2.1 Selectable cabinet type
2.2.2 Configurable channels for maximum ITS
cabinet
2.2.3 User definable input pins – 128
2.2.4 User definable output pins – 128
2.2.5 Redirect outputs based on pin assignment
2.3 Ring Barrier Configuration
2.3.1 Programmable ring barrier structure
2.3.2 Minimum eight rings and 12 barriers
2.3.3 One instance of phase in ring barrier sequence
2.3.4 Ability to alter ring barrier structure while
running intersection
2.4 Start-up Configuration
2.4.1 Configurable initial operation
2.4.2 Start-up parameter configuration
2.4.3 Start-up parameter timing
2.5 Programmed Flash Operation
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-3
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
2.5.1 Programmable flash operation
2.5.2 Enter program flash after all red
2.5.3 Minimum recalls entering flash operation
2.5.4 End programmed flash
2.5.5 Programmed flash parameters
2.6 Manual Control Configuration
2.6.1 Manual control alternate sequence
2.6.2 Manual control disable
3.0 DETECTION
3.1 General
3.1.1 Vehicle detectors
3.1.2 Pedestrian detectors
3.1.3 System detectors
3.1.4 Queue detectors
3.1.5 Description field
3.1.6 Four unique detector tables
3.2 Global Detector Parameters
3.2.1 Detection parameters
3.3 Detector Configuration
3.3.1 Detector type selection
3.4 Vehicle Detector Configuration
3.4.1 Vehicle detector configuration
3.4.2 Vehicle detector parameters
3.5 Pedestrian Detector Configuration
3.5.1 Pedestrian detector configuration
3.6 System/Count Detector Configuration
3.6.1 All detectors function as system detectors
3.6 Detector Input Failure
3.7.1 Detector failure alarm
3.7.2 Automated response to detector failure
3.73. Detector failure modes
3.9 Remote Reset
3.8.1 Remote reset capability
4.0 PHASE PARAMETERS
4.1 General
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-4
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
4.1.1 Minimum 32 vehicular phases
4.1.2 Minimum 12 pedestrian phases
4.1.3 Phase changes become active at beginning of
local cycle
4.1.4 Pedestrian hybrid beacon operation capability
4.2 Multiple Phase Parameters Tables
4.2.1 Minimum 32 phase parameter tables
4.3 Phase Configuration
4.3.1 Phase configuration
4.4 Phase Timing Parameters
4.4.1 Phase timing parameter ranges
4.4.2 Phase timing parameters
4.5 Global Phase Parameters
4.5.1 Global phase parameters always active
4.5.2 Global phase parameters
4.6 Pedestrian Operation
4.6.1 Pedestrian movements on any pedestrian
channel
4.6.2 Pedestrian channels assignable to phase
4.6.3 Pedestrian call operation
4.6.4 Alternative pedestrian interval
4.6.5 Immediate pedestrian clearance on preempt
4.6.6 Exclusive pedestrian service
4.6.7 Walk rest operation
4.6.8 Barnes’ Dance interval
4.6.9 Number of pedestrian services per call
definable
4.7 Left Turn Operation
4.7.1 Variable left turn operation by time of day/day
of week
4.7.2 Variable left turn operation within plan
4.7.3 Left turn indications supported
4.7.4 Five section head operation
4.8 Right Turn Operation
4.8.1 Variable right turn operation by time of day/day
of week
4.8.2 Variable right turn operation within plan
4.8.3 Right turn indications supported
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-5
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
4.8.4 Right turn / pedestrian operation
4.9 Pedestrian Hybrid Beacon Operation
4.9.1 Pedestrian hybrid beacon functionality
4.9.2 Pedestrian hybrid beacon indications
4.9.3 Pedestrian hybrid beacon operation
4.9.4 Pedestrian hybrid beacon system operation
4.10 Phase Sequence
4.10.1 Phase sequence general
4.10.2 Pre-signal sequence
5.0 OVERLAPS
5.1 General
5.1.1 Minimum 20 overlaps
5.1.2 User definable text label for each overlap
5.1.3 Templates for overlaps
5.1.4 Minimum eight distinct overlap tables
5.2 Overlap Configuration
5.2.1 Overlap configuration settings
5.3 Overlap Timing Parameters
5.3.1 Overlap minimum green
5.3.2 Overlap green extension
5.3.3 Overlap green clear 1
5.3.4 Overlap yellow clearance
5.3.5 Overlap red clearance
5.3.6 Overlap pedestrian walk 1
5.3.7 Overlap pedestrian walk 2
5.3.8 Overlap pedestrian clearance 1
5.3.9 Overlap pedestrian clearance 2
5.3.10 Overlap reservice
5.4 Overlap Operation
5.4.1 Right turn arrow overlap with pedestrian service
operation
5.4.2 Pre-signal overlap operation
5.4.3 Pedestrian overlap operation
6.0 SCHEDULE
6.1 General
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-6
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
6.1.1 Schedule types
6.1.2 Automatic schedule sort in chronological order
6.1.3 Enable/disable function
6.1.4 Completely define operation
6.1.5 Log schedule events
6.1.6 Schedule event priority
6.2 Time of Day. Day of Week Schedule
6.2.1 Minimum 32 events per schedule
6.2.2 Minimum 16 distinct schedules
6.2.3 Schedule operational modes
6.2.4 Schedule defined parameters
6.3 Holiday Schedule
6.3.1 Fixed and floating holiday functionality
6.3.2 Schedule events minimum one year in advance
6.3.3 Schedule events five days on either side of
holiday
6.3.4 Sort schedule by month and day
6.3.5 Schedule user defined parameters
6.4 Seasonal Schedule
6.4.1 Minimum 10 seasonal events
6.4.2 Schedule seasonal events minimum one year
in advance
6.4.3 Seasonal schedule parameters
6.5 Temporary Schedule
6.5.1 Schedule expiration date for events
6.5.2 Revert to scheduled event after expiration
6.5.3 Minimum of four temporary schedule events
6.5.4 Temporary operational modes
6.5.5 User define deletion of event upon expiration
6.5.6 Temporary schedule parameters
7.0 COORDINATION
7.1 General
7.1.1 Minimum 32 locally stored timing plan sets
7.1.2 Coordinator startup after startup phases
serviced
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-7
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
7.1.3 Parameter changes activated at beginning of
cycle
7.1.4 Detector and overlap changes activated at new
timing plan
7.1.5 User defined offset reference point
7.2 Coordination Parameters
7.2.1 Coordination parameters
7.3 Pedestrian Service
7.3.1 Pedestrian service operation
7.3.2 Pedestrian adjust
7.3.3 Pedestrian phase end early operation
7.3.4 Pedestrian phase call during clearance
7.3.5 Pedestrian phase call recognition for long
pedestrian service
7.3.6 Pedestrian phase call recognition for short
pedestrian service
7.4 Pedestrian Service Parameters
7.4.1 Pedestrian adjust enable
7.4.2 Time for pedestrian service taken from
preceding phase
7.4.3 Time for pedestrian service taken from
subsequent phase
7.5 Coordinated Operation (Use Cases)
7.5.1 Recycle left turn operation
7.5.2 Back up into leading left turn operation
7.5.3 Optional leading left turn operation
7.5.4 Double service for side street operation
7.5.5 Free mode operation within coordination
operation
7.5.6 Optional lagging left turn operation
7.5.7 Phase recycle with split phase operation
7.5.8 Optional service with split phase operation
8.0 PREEMPTION
8.1 General
8.1.1 Minimum 12 programmable preemption
sequences
8.1.2 Preempt types
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-8
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
8.1.3 Programmable for railroad and emergency
vehicle
8.1.4 Preempt labels
8.1.5 Delay preempt input
8.1.6 Smooth transition from one preempt to another
8.1.7 Preempt inputs available as logic identifiers
8.1.8 Ability to activate auxiliary devices as part of
preempt
8.1.9 Automatic reset of maximum timer
8.1.10 Recycle entry phases prohibited
8.1.11 Recycle return phases prohibited
8.1.12 Active plan continue to run in background
during preempt
8.1.13 Preempt input ability to change mode of
operation
8.1.14 Multiple preempt exit options
8.2 Preempt States
8.2.1 Preempt states
8.3 Preemption Priority
8.3.1 Preemption priority
8.3.2 User defined priority
8.3.3 Railroad defined as high priority
8.3.4 Emergency vehicle preemption prohibited from
higher priority than rail.
8.3.5 Emergency vehicle preemption defined as
lowest preempt priority
8.3.6 High priority preempts override low priority
preempts
8.3.7 Low priority preempts ignored during high
priority preempt activity
8.3.8 Equal priority preempts served in order calls
received
8.4 Railroad Preemption
8.4.1 Railroad preempt configuration
8.4.2 Four unique inputs for railroad preemption
8.4.3 Preemption provided during flash operation
8.4.4 Entry phases not terminated until gate down
input received
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-9
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
8.4.5 Flash operation allowed during dwell interval
8.5 Emergency Vehicle Preemption
8.5.1 Emergency vehicle preemption (EVP) types
8.5.2 Minimum six inputs for EVP
8.5.3 Hold phases remain active until call ends or
max time
8.5.4 EVP service based on traffic demand
8.6 Normal Preempt Configuration
8.6.1 Preemption configuration settings
8.6.2 Preemption timing parameters
9.0 TRANSIT PRIORITY
9.1 General
9.1.1 Software shall run transit signal displays
9.1.2 Transit signal display parameters
9.1.3 Transit signal display synchronized with
compatible vehicle and pedestrian phases
9.1.4 Three levels of priority operation
9.1.5 Higher priority services override lower priority
services
9.1.6 Lower priority services ignored until higher
priority services terminate
9.1.7 Equal priority services served in order calls
received
9.2 Full Priority Operation
9.2.1 Full transit priority for median running trains
9.2.2 Exclusive train phase functionality
9.2.3 Transit priority operational during programmed
flash
9.2.4 Full priority termination sequence
9.2.5 Priority events logged
9.3 Partial Transit Priority
9.3.1 Partial transit priority functionality
9.3.2 Partial transit priority configuration
9.3.3 Partial priority timing parameters
9.3.4 Partial priority operation
9.4 Bus Priority
9.4.1 Bus priority functionality
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-10
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
9.4.2 Bus priority configuration
9.4.3 Bus priority timing
9.4.4 Bus priority operation
10.0 ADVANCED PROGRAMMING
10.1 General
10.1.1 Minimum 64 user definable logic commands
10.1.2 No limitation to logic statement linkages
10.1.3 Logic commands
10.1.4 Logic command functions
10.2 Assignable Outputs
10.2.1 Available assignable outputs
10.3 Assignable Inputs
10.3.1 Available assignable inputs
11.0 COMMUNICATIONS
11.1 General
11.1.1 External communication support
11.1.2 Simultaneous communication
11.1.3 Communication methods supported
11.1.4 Support half and full duplex
11.1.5 ARP packet transmission upon connection to
Ethernet
11.1.6 Ability to extract VLANS
11.2 Center to Field Communications
11.2.1 Front panel capability for upload/download
with central
11.2.2 Supported communication patterns
11.2.3 Center to Field communication interfaces
11.2.4 Configurable field to central communication
11.2.5 Capability for field to central over 10/100
Ethernet network
11.2.6 Capability for field to central over serial
network
11.3 Peer to Peer Communications
11.3.1 Peer to peer communication support
11.3.2 Peer to peer over Ethernet network
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-11
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
11.3.3 Transmission and reception of multiple
messages simultaneously
11.3.4 Transmit to minimum five peers
11.3.5 Receive from minimum five peers
11.3.6 Peer intersections user selectable
11.3.7 Receipt of peer message apply local internal
control
11.3.8 Definable time out communication feature
11.3.9 Failure of peer communication generates
alarm
11.4 Local Wireless Remote
11.4.1 Remote local access methods
11.4.2 Minimum remote access range of 200 feet
11.4.3 Secure data transmission for remote access
11.4.4 Remote access devices
11.4.5 Local remote support bandwidth
ADVANCED OPERATIONS
12.1 Traffic Responsive Operation
12.1.1 Traffic responsive parameters
12.1.2 Traffic responsive operation for defined group
12.2Queue Detection
12.2.1 Minimum eight independent queue detectors
per intersection
12.2.2 Programmable by time of day/day of week
12.2.3 Detector failure will disable queue response
12.2.4 Minimum four levels of priority
12.2.5 Queue detector configuration settings
12.2.6 Left or through queue detector settings
12.2.7 Partial priority queue detection
12.2.8 Diamond intersection queue detection
12.2.9 Logged events
12.2.10 Detector failures logged
12.3Auxiliary Field Device Operation
12.3.1 Auxiliary field device operation
12.3.2 Minimum eight independent auxiliary devices
12.3.3 Minimum four independent auxiliary device
tables
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-12
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
12.3.4 Auxiliary device table activation
12.3.5 Auxiliary device output states
12.3.6 Repeat states
12.3.7 Change to device state generators
13.0 DIAMOND INTERCHANGE SEQUENCE
13.1 General
13.1.1 Sequence approved by City
13.1.2 Sequence types supported
13.1.3 Functionality as actuated, semi-actuated and
fixed time
13.1.4 Smooth transition between sequences
13.1.5 Sequences support right turn overlaps
13.1.6 Sequences support eight active pedestrian
channels
13.1.7 Templates provided
13.2 Diamond Interchange K-Clearance
13.2.1 General requirements of K clearance
13.2.2 Figure 3 diamond sequence operation
13.2.3 Figure 6 or 7 diamond sequence operation
13.2.4 Figure 4 diamond sequence operation
14.0 LOGS
14.1 General
14.1.1 All log entries time stamped in military time
14.1.2 All log entries available from front panel and
central
14.1.3 Minimum log storage of seven days of events
14.1.4 Oldest entries overwritten when log full
14.2 General Controller Log
14.2.1 Power loss log
14.2.2 External start log
14.2.3 Manual control log
14.2.4 Cabinet door log
14.3 Conflict Monitor/MMU Log
14.3.1 Conflict monitor / MMU log
14.4 Front Panel Log
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-13
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
14.4.1 Front panel modification log
14.4.2 User log
14.5 Controller Software Log
14.5.1 All events and actions logged daily
14.6 Detector Log
14.6.1 Detector diagnostics log
14.7 Vehicle Split Log
14.7.1 Vehicle split time log
14.8 Cycle Time Log
14.8.1 Cycle time log during free operation
14.8.2 Cycle time log during coordinated operation
14.9 Coordination log
14.9.1 Coordination log
14.10 Preempt Log
14.10.1 Preempt log
14.11 Transit Priority Log
14.11.1 Transit priority log
14.12 Special Event Log
14.12.1 Special event log
14.13 Advanced Operation Event Log
14.13.1 Advanced operation log
15.0 USER INTERFACE
15.1General
15.1.1 User interface for data entry, monitoring and
management
15.1.2 Accessible from front panel or remote device
15.1.3 Unused parameters not displayed
15.1.4 Menu driven format
15.1.5 All programming downloadable to remote or
central
15.1.6 On-screen help provided
15.2 Data Entry
15.2.1 Menu format, in English, using standard
nomenclature
15.2.2 Menu format with submenus
15.2.3 Titles and headings remain visible during
scrolling
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-14
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
15.2.4 Easy of navigation
15.2.5 Data changes highlighted until saved
15.2.6 Entries unavailable based on security omitted
or obscured
15.3 Status Display
15.3.1 Real time status availability
15.3.2 Real time status displays
15.3.3 Controller status detail
15.3.4 Ring status detail
15.3.5 Phase status detail
15.3.6 Coordination status detail
15.3.7 Preemption status detail
15.3.8 Overlap status detail
15.3.9 Detector status detail
15.3.10 Communication status detail
15.3.11 Cabinet status detail
15.3.12 Advanced operation status detail
16.0 MISCELLANEOUS
16.1 Special Function/Time of Day Outputs
16.1.1 Minimum ten special function outputs
16.1.2 Special function activation
16.1.3 Special function status
16.2 Alarms
16.2.1 Minimum 48 predefined alarms
16.2.2 Alarms logged
16.2.3 Alarm messages to central configurable
16.2.4 Any physical input has alarm functionality
16.2.5 Alarm classification types
16.2.6 Critical alarm types
16.2.7 Non-critical alarm types
16.2.8 Coordination alarm types
16.2.9 Communication alarms
16.2.10 Preempt alarms
16.2.11 Priority alarms
16.3 Diagnostics
16.3.1 Diagnostic support
16.4 Timing Sheets
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
January 2012 Page B-15
Local Traffic Signal Controller Software
Minimum Requirements Compliance Matrix
Minimum Requirements Meets Requirement Exceeds Requirement Partially Meets Requirements Operating in Field Requirement in Development Function not available Comments
or
Footnotes
16.4.1 Timing sheet availability
16.4.2 Timing sheets uploadable to central or remote
device
ADDITIONAL FUNCTIONALITY INLCUDED IN PROPOSED SOFTARE (DESCRIBE)
End of Appendix B
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-1
ATTACHMENT 1
APPENDIX C
Sample Timesheets
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-2
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-3
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-4
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-5
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-6
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-7
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-8
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-9
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-10
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-11
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-12
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-13
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-14
The Cities of Fort Worth and Dallas, Texas
Local Traffic Signal Controller Software Specification
December2011 Page C-15
End of Appendix C
34 41 10 - 1
TRAFFIC SIGNALS
Page 1 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
SECTION 34 41 10
TRAFFIC SIGNALS
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes :
1. LED Traffic Signal Head Assemblies
2. LED Traffic Signal Len Insert
3. Louvers
4. LED Countdown Pedestrian Signal Head Assemblies
5. Pedestrian Push Button Assemblies
6. Accessible Pedestrian Signals (APS)
7. Radar Detection Equipment and Cable
8. Hybrid Vehicle Detection System and Cable
9. Emergency Vehicle Preemption Equipment and Cable
10. Battery Back-up (BBU) System for Signal Cabinets
11. Multi-conductor Cable
12. Insulated Electrical Cable
13. Grounding Conductors
14. Ground Rod
15. Ground Boxes
16. Traffic Signal Structures
17. Foundations
18. Painting Traffic Signal Structures
19. Signal Controller
20. Controller Cabinet Assembly
21. Roadside Flashing Beacon Assembly
22. School Zone Flasher Assembly
23. Rectangular Rapid Flashing Beacon (RRFB) Assembly
24. Louvered Back Plates
25. Powder Coating Signal Structures
26. PTZ Camera and Cable
27. Communication Modems
28. Fish -eye Detection System
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the
Contract
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 2
TRAFFIC SIGNALS
Page 2 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2. Division 1 – General Requirements
3. Section 03 30 00 – Cast -in -Place Concrete
4. Section 26 05 00 – Common Work Results for Electrical
5. Section 26 05 33 – Raceways and Boxes for Electrical Systems
6. Section 31 23 16 – Unclassified Excavation
7. Section 31 24 00 – Embankments
8. Section 33 05 10 – Utility Trench Excavation, Embedment and Backfill
9. Section 33 05 30 – Location of Existing Utilities
1.2 ELECTRICAL WORK REQUIREMENTS
A. Electrical work is work performed for:
1. Roadway Illumination Assemblies
2. High Mast Illumination Assemblies
3. Performance Testing of Lighting Systems
4. Temporary Roadway Illumination
5. Conduit
6. Electrical Conductors
7. Tray Cable
8. Duct Cable
9. Electrical Service
10. Permanent Traffic Signals
11. Temporary Traffic Signals
12. Traffic Signal Cables
13. Flashing Beacon Assemblies
14. Other items that involve either the distribution of electrical power greater than 50
volts or the installation of conduit and duct banks
15. Installation of conduit and wiring associated with ground boxes
16. Foundations for Traffic Control Devices
17. Installation of the conduit system for communication and fiber optic cable
B. Electrical work does not include the installation of communications or fiber optic cable,
or the connections for low voltage and inherently power limited circuits such as
electronic or communications equipment. Assembly and placement of poles, structures,
cabinets, enclosures, manholes, or other hardware will not be considered electrical
work as long as no wiring, wiring connections, or conduit work is done at the time of
assembly and placement.
C. The work qualifications required to perform electrical work are as listed:
1. All electrical work must be directly supervised and/or performed by a certified
person that has a Traffic Signal Level II IMSA certification or other equivalent
certifications approved by Transportation Management Division.
2. Directly supervised means a certified person must be physically present during all electrical work performed by uncertified workers.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 3
TRAFFIC SIGNALS
Page 3 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1.3 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. LED Traffic Signal Head Assemblies
a. Measurement
1) Measurement for this Item shall be per each LED traffic signal head
assembly installed or replaced. b. Payment
1) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Signal Head Assembly”
installed or replaced for:
a) Various numbers of sections
c. The price bid for “Furnish/Install Signal Head Assembly” shall include:
1) Furnishing and installing LED Traffic Signal Head Assembly and
appurtenances including hinge pins, lens clips, locking devices, and gaskets
2) Housing and doors
3) Detachable visors
4) LED lamp unit 5) Mounting hardware
6) All labor, tools, equipment, and incidentals
7) Aluminum, vented one- or two-piece back plates with 2 -inch retroflective
border and mounting hardware
8) Cable inside the pole will be paid for separately
d. The price bid for “Install Signal Head Assembly” shall include:
1) Scheduling pickup of material from the City designated area
2) Pickup and transportation of material from the City designated area to the
jobsite
3) Taking precautions to ensure material is not damaged during transportation 4) Installing signal head assembly
5) Mounting hardware
6) Making all wiring terminations
7) All labor, tools, equipment, and incidentals
8) Cable inside the pole will be paid for separately
e. The price bid for “Replace Signal Head Assembly” shall include:
1) Furnishing and installing LED Traffic Signal Head Assembly and
appurtenances including hinge pins, lens clips, locking devices, and gaskets
2) Housing and doors
3) Detachable visors
4) LED lamp unit 5) Aluminum, vented one- or two-piece back plates and mounting hardware
6) Removing old signal head assembly and installing new signal head
assembly in its place
7) Mounting hardware
8) All labor, tools, equipment, and incidentals 9) Cable inside the pole will be paid for separately
2. LED Traffic Signal Len Inserts
a. Measurement
1) Measurement for this Item shall be per each traffic signal len insert retrofit.
b. Payment
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 4
TRAFFIC SIGNALS
Page 4 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Signal Len Insert” retrofit.
c. The price bid for “Signal Len Insert” shall include:
1) Furnishing, assembling, and installing the signal len insert
2) Removing old signal len insert 3) LED lamp unit
4) Cable inside the pole will be paid for separately
5) All labor, tools, equipment, and incidentals
3. Louvers
a. Measurement
1) Measurement for this Item shall be per each traffic signal louver section
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be paid for at the unit price bid per each “Louver” installed.
c. The price bid for “Signal Len Insert” shall include:
1) Furnishing, assembling, and installing the louvers
2) Adjusting louvers for best visibility for the intended approach and no
visibility for the restricted approaches 3) All labor, tools, equipment, and incidentals
4. LED Pedestrian Signal Head Assemblies
a. Measurement
1) Measurement for this Item shall be per each ped signal head assembly
installed, each ped signal ped head retrofit installed, or each ped signal
head assembly replaced.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Ped Signal Head Assembly”
or “Retrofit Ped Head Insert” installed or replaced. c. The price bid for “Furnish/Install Ped Signal Head Assembly” shall include:
1) Furnishing, assembling, and installing the pedestrian signal sections
2) Housing units
3) LED countdown pedestrian units
4) Mounting attachments and completing wiring connections
5) All labor, tools, equipment, and incidentals
6) Cable inside the pole will be paid for separately
d. The price bid for “Install Ped Signal Head Assembly” shall include:
1) Scheduling pickup of material from the City designated area
2) Pickup and transportation of material from the City designated area to the jobsite
3) Taking precautions to ensure material is not damaged during transportation
4) Installing ped signal head assembly
5) Mounting hardware
6) Making all wiring terminations 7) All labor, tools, equipment, and incidentals
8) Cable inside the pole will be paid for separately
e. The price bid for “Retrofit Ped Head Insert” shall include:
1) Furnishing, assembling, and installing the pedestrian signal sections
2) LED countdown pedestrian units
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 5
TRAFFIC SIGNALS
Page 5 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
3) Mounting attachments and completing wiring connections
4) Disposal of incandescent unit
5) All labor, tools, equipment, and incidentals
6) Cable inside the pole will be paid for separately
f. The price bid for “Replace Ped Signal Head Assembly” shall include: 1) Furnishing, assembling, and installing the pedestrian signal sections
2) LED countdown pedestrian units
3) Mounting attachments and completing wiring connections
4) Removing old ped signal head assembly and installing new ped signal head
assembly in its place
5) All labor, tools, equipment, and incidentals
6) Cable inside the pole will be paid for separately
5. Pedestrian Push Button Assemblies
a. Measurement 1) Measurement for this Item shall be per each pedestrian push button
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Ped Push Btn Station” installed for:
a) Various mounting methods
c. The price bid for “Furnish/Install Ped Push Btn Station” shall include:
1) Furnishing and installing Pedestrian Push Button Assemblies
2) Button housing
3) Button cap 4) LED indication
5) Push button signs
6) Switch
7) Built -in surge protection
8) Push Button signs 9) Push button hardware extension as needed
10) Audible notification system
11) Mounting hardware
12) All labor, tools, equipment, and incidentals
13) Cable inside the pole will be paid for separately
d. The price bid for “Install Ped Push Btn Station” shall include:
1) Scheduling pickup of material from the City designated area
2) Pickup and transportation of material from the City designated area to the
jobsite
3) Taking precautions to ensure material is not damaged during transportation
4) Installing ped push button station 5) Mounting hardware
6) Push button hardware extension as needed
7) Audible notification system
8) Making all wiring terminations
9) All labor, tools, equipment, and incidentals
10) Cable inside the pole will be paid for separately
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 6
TRAFFIC SIGNALS
Page 6 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
6. Accessibl e Pedestrian Signals (APS)
a. Measur ement
1) Measurement for this Item shall be per each audible pedestrian push button
station installed.
b. Payment 1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Audible Pedestrian
Pushbutton Station” unit of the type specified.
c. The price bid for “Furnish/Install Audible Pedestrian Pushbutton Station” shall
include:
1) Furnishing, installing, and testing the Audible pedestrian pushbutton
stations
2) Mounting hardware
3) Sign adapter
4) Pushbutton stations 5) Central control units for inside cabinet
6) Vibrotactile arrow with high visual contrast
7) Wiring harness
8) Voice message setup
9) Configuration devices or software
10) R10-3e (L/R) signs with braille
11) The signal conductor cable from the signal cabinet to the pushbutton
station shall be paid for under “3/C 14 AWG Multi-Conductor Cable”
12) Furnishing ethernet cable and terminating cable from central control unit to
communication device
13) Push button hardware extensions as needed 14) All labor, tools, equipment, and incidentals
d. The price bid for “Install Audible Pedestrian Pushbutton Station” shall include:
1) Scheduling pickup of material from the City designated area
2) Pickup and transportation of material from the City designated area to the
jobsite 3) Taking precautions to ensure material is not damaged during transportation
4) Installing and testing the audible pedestrian push button station
5) Installing central control units inside the cabinet
6) Mounting hardware
7) Push button hardware extension as needed
8) Voice message setup 9) Configuration devices or software
10) Making all wiring terminations
11) Furnishing ethernet cable and terminating cable from central control unit to
communication device
12) All labor, tools, equipment, and incidentals 13) The signal conductor cable from the signal cabinet to the pushbutton
station shall be paid for under “3/C 14 AWG Multi-Conductor Cable”
7. Radar Detection System and Cable
a. Furnish and Install Radar Detection System
1) Measurement
a) Measurement for this Item shall be per each intersection approach
furnished and installed.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 7
TRAFFIC SIGNALS
Page 7 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Furnish/Install
Radar Detection Device ” installed for:
(1) Various types 3) The price bid shall include:
a) Furnishing, assembling and installing Radar Detection Device
b) Contact closure input file cards
c) Relays
d) Set-up and diagnostic software including programming and testing of
all detection zones per signal plans. Setup must be approved by City
staff.
e) Circuits
f) Mounting hardware
g) Grounding of each device h) Central control unit in cabinet
i) Furnishing SDLC compatible cable and terminating SDLC cable
j) Furnishing ethernet cable and terminating cable from central control
unit to communication device
k) All labor, tools, equipment, and incidentals
l) Cable will be paid for separately
b. Install Radar Detection System
1) Measurement
a) Measurement for this Item shall be per each intersection approach
installed.
2) Payment a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Install Radar
Detection Device” for:
(1) Various types
3) The price bid shall include: a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing Radar Presence or Advance Device e) Relays
f) Set-up and diagnostic software including programming and testing of
all detection zones per signal plans. Setup must be approved by City
staff.
g) Circuits h) Grounding of each device
i) Furnishing SDLC compatible cable and terminating SDLC cable
j) Furnishing ethernet cable and terminating cable from central control
unit to communication device
k) All labor, tools, equipment, and incidentals
l) Cable will be paid for separately
c. Furnish and Install Radar Detection Cable
1) Measurement
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 8
TRAFFIC SIGNALS
Page 8 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Measurement for this Item shall be per linear foot of radar detection
cable furnished and installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot “Furnish/Install Radar Detection Cable” installed.
3) The price bid shall include:
a) Furnishing and installing radar detection cable
b) Making all wiring connections to radar detection devices and cabinet.
c) All labor, tools, equipment, and incidentals to install cable.
d. Install Radar Detection Cable 1) Measurement
a) Measurement for this Item shall be per linear foot of radar detection
cable installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot “Install Communication Cable” installed.
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite c) Taking precautions to ensure material is not damaged during
transportation
d) Installing radar cable
e) Making all wiring connections to radar detection devices and cabinet
f) All labor, tools, equipment, and incidentals to install cable.
8. Hybrid Vehicle Detection System and Cable
a. Furnish and Install Hybrid Vehicle Detection System
1) Measurement
a) Measurement for this Item shall be per each intersection approach furnished and installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Furnish/Install
Hybrid Detection Device ”.
3) The price bid shall include:
a) Furnishing, installing and testing hybrid detection system
b) Detector units
c) Mini-hub detector cards
d) Mounting hardware
e) Operational software f) Communication interface panel
g) Setup of all detection zones per traffic signal plans. Setup must be
approved by City staff.
h) Grounding of each device
i) Central control unit in cabinet j) Furnishing SDLC compatible cable and terminating SDLC cable
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 9
TRAFFIC SIGNALS
Page 9 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
k) Furnishing ethernet cable and terminating cable from central control
unit to communication device
l) All labor, tools, equipment, and incidentals
m) Cable will be paid for separately
b. Install Hybrid Vehicle Detection System 1) Measurement
a) Measurement for this Item shall be per each intersection approach
installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Install Hybrid
Vehicle Detection Device ”.
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing and testing all detection components
e) Setup of all detection zones per traffic signal plans. Setup must be
approved by City staff.
f) Grounding of each device
g) Furnishing SDLC compatible cable and terminating SDLC cable
h) Furnishing ethernet cable and terminating cable from central control
unit to communication device
i) All labor, tools, equipment, and incidentals c. Furnish and Install Hybrid Vehicle Detection Cable
1) Measurement
a) Measurement for this Item shall be per linear foot of hybrid detection
cable furnished and installed.
2) Payment a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot
“Furnish/Install Cat 5 Ethernet Cable”.
3) The price bid shall include:
a) Furnishing and installing hybrid detection cable
b) Making all connections to cameras and controller equipment c) All labor, tools, equipment, and incidentals to install cable.
d. Install Hybrid Vehicle Detection Cable
1) Measurement
a) Measurement for this Item shall be per linear foot of hybrid detection
cable installed. 2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot “Install
Communication Cable”.
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 10
TRAFFIC SIGNALS
Page 10 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing cable
e) Making all connections to cameras and controller equipment
f) All labor, tools, equipment, and incidentals to install cable.
9. Emergency Vehicle Preemption Equipment and Cable
a. Furnish and Install Preemption Detector
1) Measurement
a) Measurement for this Item shall be per each Preemption Detector
furnished and installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Furnish/Install
Preempt Detector ” for: (1) Various types
3) The price bid shall include:
a) Furnishing, installing and testing preemption detectors
b) Card rack
c) Phase selector d) Mounting hardware
e) All labor, tools, equipment, and incidentals
f) Cable inside the pole will be paid for separately
b. Install Preemption Detector
1) Measurement
a) Measurement for this Item shall be per each Preemption Detector installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Install Preempt
Detector ” for: (1) Various types
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing and testing preemption detector
e) Mounting hardware
f) All labor, tools, equipment, and incidentals
c. Furnish and Install Preemption Cable 1) Measurement
a) Measurement for this Item shall be per linear foot of preemption cable
furnished and installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot
“Furnish/Install Preemption Cable” installed.
3) The price bid shall include:
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 11
TRAFFIC SIGNALS
Page 11 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Furnishing and installing preemption cable
b) Making all connections to preemption detectors, phase selectors, and
controller
c) All labor, tools, equipment, and incidentals to install cable.
d. Install Preemption Cable
1) Measurement
a) Measurement for this Item shall be per linear foot of preemption cable
installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot “Install Communication Cable” installed.
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing preemption cable
e) Making all connections to preemption detectors, phase selectors, and
controller
f) All labor, tools, equipment, and incidentals to install cable.
10. Battery Back -Up (BBU) System for Signal Cabinets
a. Furnish and Install BBU System for Signal Cabinet
1) Measurement
a) Measurement for this Item shall be per each BBU System component furnished and installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Furnish/Install BBU
System” for:
(1) Various components
(2) Various types
3) The price bid shall include:
a) Furnishing, installing and testing the BBU system
b) Inverter/charger
c) Manual bypass switch d) Integrated power transfer switch or automatic bypass switch
e) Batteries
f) Self -contained external mounted cabinet if external unit
g) Mounting hardware
h) Remote communication module
i) Wiring, and all necessary hardware and software
j) Furnishing ethernet cable and terminating cable from central control
unit to communication device
k) All labor, tools, equipment, and incidentals
b. Install BBU System for Signal Cabinet 1) Measurement
a) Measurement for this Item shall be per each BBU System installed.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 12
TRAFFIC SIGNALS
Page 12 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Install BBU System”
for:
(1) Various types 3) The price bid shall inc lude:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing and testing the BBU s ystem
e) Wiring, and all necessary hardware and software
f) Furnishing ethernet cable and terminating cable from central control
unit to communication device g) All labor, tools, equipment, and incidentals
11. Mu lti-conductor Cable
a. Furnish and Install Multi-conductor Cable
1) Measurement a) Measurement for this Item shall be per each linear foot of multi-
conductor cable installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each linear foot of “Multi-
conductor Cable” installed for: (1) Various types
(2) Various sizes
3) The price bid shall include:
a) Furnishing and installing Multi-conductor Cable
b) Wiring Terminations c) Incidentals and equipment
b. Install Multi-conductor Cable
1) Measurement
a) Measurement for this Item shall be per linear foot of multi-conductor
cable installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot “Install Condr
Cable” installed for:
(1) Various types
(2) Var ious sizes 3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing Multi-conductor cable
e) Making all connections to terminals
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 13
TRAFFIC SIGNALS
Page 13 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
f) All labor, tools, equipment, and incidentals to install cable
12. Insulated Electrical Cable
a. Furnish and Install Insulated Electrical Cable 1) Measurement
a) Measurement for this Item shall be per each linear foot of Insulated
Electrical Cable installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per linear foot of “Insulated Elec
Condr Cable” installed for:
(1) Va rious types
(2) Various sizes
3) The price bid shall include:
b. Furnishing and installing Insulated Electrical Cable 1) Measurement
a) Measurement for this Item shall be per each linear foot of Insulated
Electrical Cable installed.
2) Payment
a) The work performed and materials furnished in accordance with this Item shall be paid for at the unit price bid per linear foot “Install Condr
Cable” installed for:
(1) Various types
(2) Various sizes
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing Insulated Electrical Cable e) Making all connections to terminals
f) All labor, tools, equipment, and incidentals to install cable.
13. Grounding Conductors
a. Furnish and Install Grounding Conductors
1) Measurement
a) Measurement for this Item shall be per each linear foot of Grounding
Conductors installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item shall be paid for at the unit price bid per linear foot of “Bare Elec
Condr” installed for:
(1) Various types
(2) Various sizes
3) The price bid shall include: a) Furnishing and installing Grounding conductors
b) Grounding bushes and connectors
c) All labor, tools, equipment, and incidentals to install cable.
b. Install Grounding Conductors
1) Measurement
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 14
TRAFFIC SIGNALS
Page 14 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Measurement for this Item shall be per each linear foot of Grounding
Conductors installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot “Install Condr Cable” installed for:
(1) Various types
(2) Various sizes
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing Grounding Conductors e) Grounding bushings and connectors
f) All labor, tools, equipment, and incidentals to install cable.
14. Ground Rod
a. Subsidiary 1) Measurement
a) This Item is considered subsidiary to the various Traffic Signal
Structures being installed.
2) Payment
a) The work performed and the materials furnished in accordance with
this Item are subsidiary to various Traffic Signal Structures being installed and shall be subsidiary to the unit price bid per various Traffic
Signal Structures being installed, and no other compensation will be
allowed.
b. Furnish/Install
1) Measurement a) Measurement for this Item shall be per each ground rod installed.
2) Payment
a) The work performed and the materials furnished in accordance with
this Item and measured as provided under “Measurement” shall be paid
for at the unit price bid per each “Ground Rod” furnished and installed.
3) The price bid shall include
a) Furnishing and installing ground rod
b) Grounding connectors
c) All labor, tools, equipment, and incidentals
15. Ground Boxes
a. Measurement
1) Measurement for this Item shall be per each ground box installed
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be paid for at the unit price bid per each “Ground Box” installed for:
a) Various sizes
b) Various types
c. The price bid shall include:
1) Furnishing and installing Ground Box
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 15
TRAFFIC SIGNALS
Page 15 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2) Excavation and backfill
3) Enclosures
4) Covers
5) Bolts
6) Gravel 7) Concrete apron when required
8) All labor, tools, equipment, and incidentals
16. Traffic Signal Structures
a. Furnish and Install Pedestal and Push Button Pole Assembly
1) Measurement
a) Measurement for this Item shall be per each assembly f urnished and
installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item shall be paid for at the unit price bid per each “Furnish/Install Ped or
Pushbutton Pole Ass embly” furnished and installed for:
(1) Various types
(2) Various sizes
3) The price bid shall include: a) Excavation and backfill
b) Furnishing and installing each Pedestal or Pushbutton Pole Assembly
on foundation
c) Furnishing, placement and compaction of backfill
d) Clean-up
e) Pole reinforcing collar f) Pole cap
g) Transformer base
h) Power Coating
i) Foundation will be paid separately
j) All labor, tools, equipment, and incidentals b. Install Pedestal or Pushbutton Pole Assembly
1) Measurement
a) Measurement for this Item shall be per each assembly installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Install Ped or
Pushbutton Pole Assembly” furnished and installed for:
(1) Various types
(2) Various sizes
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Excavation and backfill
e) Installing each Pedestal or Pushbutton Pole Assembly on foundation
f) Furnishing, placement and compaction of backfill
g) Clean-up
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 16
TRAFFIC SIGNALS
Page 16 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
h) Foundation will be paid separately
i) All labor, tools, equipment, and incidentals
c. Furnish and Install Signal Poles
1) Measurement
a) Measurement for this Item shall be per each signal pole furnished and installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Furnish/Install Signal
Pole” installed for:
(1) Various types
3) The price bid shall include:
a) Excavation and backfill
b) Furnishing and installing each Signal Pole Assembly on foundation
c) Luminaire arm d) LED fixture shall be paid for separately
e) Erecting assembly on concrete foundation
f) Clean-up
g) Powder Coating
h) Foundation will be paid separately
i) All labor, tools, equipment, and incidentals
d. Install Signal Poles
1) Measurement
a) Measurement for this Item shall be per each signal pole installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item shall be paid for at the unit price bid per each “Install Signal Pole”
installed for:
(1) Various types
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Excavation and backfill
e) Installing each Signal Pole Assembly on foundation f) Installing luminaire arm, fixture, and lamp if specified
g) Erecting assembly on concrete foundation
h) Clean-up
i) Foundation will be paid separately
j) Installing anchor bolts, nuts, washers, and templates k) All labor, tools, equipment, and incidentals
e. Furnish and Install Mast Arm
1) Measurement
a) Measurement for this Item shall be per each Mast Arm furnished and
installed.
2) Payment
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 17
TRAFFIC SIGNALS
Page 17 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Furnish/Install Mast
Arm” furnished and installed for:
(1) Various length intervals
(2) Various types 3) The price bid shall include:
a) Furnishing, assembling and installing Mast Arm
b) Mounting equipment
c) Vibration dampers
d) Clean-up
e) Install Mast Arm
f) Powder coating
g) All labor, tools, equipment, and incidentals
f. Install Mast Arm
1) Measurement a) Measurement for this Item shall be per each Mast Arm installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Install Mast Arm”
installed for:
(1) Various length intervals
(2) Various types
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite c) Taking precautions to ensure material is not damaged during
transportation
d) Assembling and installing Standard Mast Arm
e) Mounting equipment
f) Vibration dampers g) Clean-up
h) All labor, tools, equipment, and incidentals
17. Foundations
a. Measurement
1) Measurement for this Item shall be per each.
b. Payment
1) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Foundation” installed for:
a) Various types
c. The price bid shall include: 1) Coordination and notification
2) Exploratory excavation (as needed)
3) Excavation
4) Disposal of excess material
5) Hauling
6) Protection of the excavation
7) Forms
8) Reinforcing steel
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 18
TRAFFIC SIGNALS
Page 18 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
9) Grounding rods
10) Concrete
11) Installing F oundation
12) Furnishing and placing anchor bolts, nuts, washers, and templates
13) Clean-up 14) T estin g
15) All labor, tools, equipment, and incidentals
18. Painting Traffic Signal Structure
a. Measurement
1) Measurement for this Item shall be per each Traffic Signal Structure being
painted.
b. Payment
1) The work performed and the materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Paint Pole and Mast Arm Various Type and Size”.
c. The price bid shall include:
1) Paint material
2) Brushing/rolling paint on surface
3) Wrapping and taping signal equipment and signs as to not get paint on them
4) All labor, tools, equipment, and incidentals
19. Signal Controller
a. Furnish and Install Signal Controller
1) Measurement
a) Measurement for this Item shall be per each controller installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Furnish/Install Signal
Controller” installed for: (1) Various mounting methods
3) The price bid shall include:
a) Furnishing and installing the controller in the cabinet
b) Wiring
c) Testing
d) Furnishing ethernet cable and terminating cable from central control
unit to communication device
e) Troubleshooting
f) All labor, tools, equipment, and incidentals
b. Swap ATC Signal Controller 1) Measurement
a) Measurement for this Item shall be per each controller assembly
installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item shall be paid for at the unit price bid per each “Swap ATC Signal
Controller” installed for:
(1) Various mounting methods
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 19
TRAFFIC SIGNALS
Page 19 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Removing the controller in the cabinet and dropping off at a disposal site or at City designated area if specified to be salvaged
e) Installing the controller in the cabinet
f) Wiring
g) Testing
h) Troubleshooting
i) All labor, tools, equipment, and incidentals
c. Replace Signal Controller
1) Measurement
a) Measurement for this Item shall be per each assembly removed and
installed. 2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Replace ATC Signal
Controller” removed and furnished/installed.
3) The price bid shall include:
a) Removing the controller in the cabinet and dropping off at a disposal
site or at City designated area if specified to be salvaged
b) Furnishing and installing the controller in the cabinet
c) Wiring
d) Testing
e) Troubleshooting f) All labor, tools, equipment, and incidentals
20. Controller Cabinet Assembly
a. Furnish and Install Controller Cabinet Assembly
1) Measurement a) Measurement for this Item shall be per each assembly installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Furnish/Install
Controller Cabinet Ass embly” installed for:
(1) Various mounting methods
(2) Various types
3) The price bid shall include:
a) Furnish and installing the controller cabinet assembly on the
foundation or support
b) Power supply c) Conflict monitor
d) Load switches
e) Conduit within 6” of foundation
f) Grounding rod
g) Wiring
h) Cable within 6” of foundation
i) Terminating
j) Testing
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 20
TRAFFIC SIGNALS
Page 20 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
k) Troubleshooting
l) Foundation is paid separately
m) Installing antenna bracket and 2 antennas if required
n) Transference of any old equipment from old cabinet to new cabinet
o) All labor, tools, equipment, and incidentals b. Install Controller Cabinet Assembly
1) Measurement
a) Measurement for this Item shall be per each assembly installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Install Controller
Cabinet Assembly” installed for:
(1) Various mounting methods
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing the Controller and Cabinet Assembly on the foundation or
support
e) Conduit within 6” of foundation
f) Grounding rod
g) Wiring
h) Cable within 6” of foundation
i) Terminating j) Testing
k) Troubleshooting
l) Installing antenna bracket and 2 antennas if required
m) Transference of any old equipment from old cabinet to new cabinet
n) All labor, tools, equipment, and incidentals
21. Roadside Flashing Beacon Assembly
a. Measurement
1) Measurement for this Item shall be per each assembly installed, relocated,
or removed.
b. Payment
1) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each various type assemblies
installed for:
a) Furnish/Install Roadside Flashing Beacon Assembly
b) Relocate Roadside Flashing Beacon Assembly c) Remove Roadside Flashing Beacon Assembly
d) Various applications including signal ahead, intersection ahead, stop
ahead, etc.
c. The price bid shall include:
1) Furnish/Install:
a) Furnishing, fabricating, galvanizing, assembling, and erecting the
roadside flashing beacon assemblies.
b) Screw in Anchor Foundation
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 21
TRAFFIC SIGNALS
Page 21 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c) Anchor bolts, nuts, washers, and templates
d) Cabinet
e) Controller
f) Flasher and interface board
g) Sign h) Beacon
i) Back plate, if required
j) Solar panel, if specified
k) Solar regulator/charger, if specified
l) Batteries , if specified
m) Equipment, materials, labor, tools, and incidentals.
n) Pedestal pole base
o) Pedestal pole
p) Pole reinforcing collar
q) Pole cap r) Erecting assembly on screw in anchor foundation
2) Relocation:
a) Removing the roadside flashing beacon assembly
b) Removing existing foundation at minimum 2’ below grade
c) Installing screw in anchor foundation
d) Furnishing, fabricating, and installing any new components as required
and replacing the assembly on its new foundations with all
manipulations and electrical work
e) Salvaging materials to be returned to the City designated area
f) Disposal of unsalvageable material
g) Loading and hauling h) Equipment, material, labor, tools, and incidentals
3) Removal:
a) Removing the various roadside flashing beacon assembly components
b) Removing the foundation at minimum 2’ below grade
c) Storing the components to be reused or salvaged d) Disposal of unsalvageable material
e) Backfilling and surface placement
f) Loading and hauling
g) Equipment, materials, tools, labor, and incidentals
22. School Zone Flasher Assembly
a. Measurement
1) Measurement for this Item shall be per each School Zone Flasher assembly
installed, relocated, or removed
b. Payment
1) The work performed and materials furnished in accordance to this Item shall be paid for at the unit price bid per each various type assemblies
installed for
a) Furnish/Install School Zone Flasher Assembly
b) Relocate School Zone Flasher Assembly
c) Remove School Zone Flasher Assembly
c. The price bid shall include:
1) Furnish/Install:
a) Excavation and backfill
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 22
TRAFFIC SIGNALS
Page 22 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b) Screw in anchor Foundation
c) Pedestal pole
d) Pedestal base
e) Pole reinforcing collar
f) Mounting hardware g) Sign(s)
h) Wiring
i) Cabinet
j) Time switch
k) Cell modem
l) 12” polycarbonate traffic signal head
m) Solar array, if specified
n) Batteries , if specified
o) Flasher and interface circuit board
p) Photovoltaic controller q) Power supply and timing
r) Programming
s) Erecting assembly on screw in anchor foundation
t) Furnishing and placing anchor bolts, nuts, washers, and templates
u) Pole cap
v) Radar feedback sign
w) All labor, tools, equipment, and incidentals
2) Relocation:
a) Removing the school zone flasher assembly
b) Removing existing foundations at minimum 2’ below grade
c) Installing screw in anchor foundations d) Furnishing, fabricating, and installing any new components as required
and replacing the assembly on its new foundations with all
manipulations and electrical work
e) Salvaging materials to be returned to the City designated area
f) Disposal of unsalvageable material g) Loading and hauling
h) Equipment, material, labor, tools, and incidentals
3) Removal:
a) Removing the various school zone flasher assembly components
b) Removing the foundation at minimum 2’ below grade
c) Storing the components to be reused or salvaged d) Disposal of unsalvageable material
e) Backfilling and surface placement
f) Loading and hauling
g) Eq uipment, materials, tools, labor, and incidentals
23. Rectangular Rapid Flashing Beacon (RRFB) Assembl y
a. Measurement
1) Measurement for this Item shall be per each RRFB assembly installed,
relocated, or removed.
b. Payment
1) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each various type assemblies
installed for:
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 23
TRAFFIC SIGNALS
Page 23 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Furnish/Install RRFB Assembly
b) Relocate RRFB Assembly
c) Remove RRFB Assembly
c. The price bid shall include:
1) Furnish/Install: a) Excavation and backfill
b) Foundation
c) Pole
d) LED f lasher module
e) Mounting hardware
f) Sign (s)
g) Solar panel
h) Batteries
i) Wiring
j) Web-based monitoring k) Detection system as specified in the plans
l) Wireless communication system
m) Erecting assembly on screw in anchor foundation
n) Furnishing and placing anchor bolts, nuts, washers, and templates
o) Push button extender if needed
p) All labor, tools, equipment, and incidentals
2) Relocation:
a) Removing the rectangular rapid flashing beacon assembly
b) Removing existing foundations at minimum 2’ below grade
c) Installing screw in anchor foundations
d) Furnishing, fabricating, and installing any new components as required and replacing the assembly on its new foundations with all
manipulations and electrical work
e) Salvaging materials to be returned to the City designated area
f) Disposal of unsalvageable material
g) Loading and hauling h) Equipment, material, labor, tools, and incidentals
3) Removal:
a) Removing the various rectangular rapid flashing beacon assembly
components
b) Removing the foundation at minimum 2’ below grade
c) Storing the components to be reused or salvaged d) Disposal of unsalvageable material
e) Backfilling and surface placement
f) Loading and hauling
g) Equipment, materials, tools, labor, and incidentals
24. Louvered Back Plates
a. Measurement
1) Measurement for this Item shall be considered subsidiary to the Signal
Head Assembly pay items or each back plate installed or replaced.
b. Payment
1) The work performed and materials furnished in accordance to this Item
shall be considered subsidiary to the Signal Head Assembly pay items or to the bid item “Back Plate w/ Ref Brdr” installed or replaced for
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 24
TRAFFIC SIGNALS
Page 24 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Various Types
c. The price bid for “Furnish/Install Back Plate w/ Ref Brdr” shall include:
1) Furnishing and installing louvered back plate to signal heads with 2-inch
retroreflective border
2) Mounting hardware 3) Clean-up
4) All labor, tools, equipment, and incidentals
d. The price bid for “Replace Back Plate w/ Ref Bord” shall include:
1) Furnishing and installing louvered back plate with 2-inch retroreflective
border to signal heads
2) Removing old louvered back plate from signal head
3) Mounting hardware
4) Clean-up
5) All labor, tools, equipment, and incidentals
25. Powder Coating Signal Structures
a. Measurement
1) This Item is considered subsidiary to each Traffic Signal Structures being
furnished and installed and powder coated.
b. Payment
1) The work performed and materials furnished in accordance to this Item
shall be subsidiary to the unit price bid per each traffic signal structure
furnished and installed for: a) Various length of traffic signal poles
b) Various length of pedestal and push button poles
c) Various length of traffic signal mast arms
c. Powder coating shall include:
1) Mechanically etching surfaces by brush blasting 2) Coating material
3) Delivery to and from powder coating company
26. PTZ Camera and Cable
a. Furnish and Install PTZ Camera
1) Measurement
a) Measurement for this Item shall be per each PTZ Camera furnish and
installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Furnish/Install PTZ Camera”
3) The price bid shall include:
a) Furnishing, installing, testing, and setup the PTZ Camera
b) Mounting hardware
c) Power supply (POE injector)
d) Furnishing ethernet cable and terminating cable from central control
unit to communication device
e) Wiring all terminations to camera
f) Cable will be paid for separately
g) All labor, tools, equipment, and incidentals b. Install PTZ Camera
1) Measurement
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 25
TRAFFIC SIGNALS
Page 25 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Measurement for this Item shall be per each PTZ Camera installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Install PTZ Camera”
3) The price bid shall include: a) Installing, testing and setup the PTZ Camera
b) Mounting hardware
c) Installing Power supply (POE injector)
d) Furnishing ethernet cable and terminating cable from central control
unit to communication device
e) Scheduling pickup of material from the City designated area
f) Pickup and transportation of material from the City designated area to
the jobsite
g) Taking precautions to ensure material is not damaged during
transportation h) Wiring all terminations to camera
i) All labor, tools, equipment, and incidentals
c. Swap PTZ Camera
1) Measurement
a) Measurement for this Item shall be per each PTZ Camera swapped.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Swap PTZ Camera”
3) The price bid shall include:
a) Removing the PTZ camera and dropping off at a disposal site or at City
designated area if specified to be salvaged b) Installing PTZ Camera in same location
c) Testing and setup the PTZ Camera
d) Reconnecting all wiring and terminations to camera
e) Scheduling pickup of material from the City designated area
f) Pickup and transportation of material from the City designated area to the jobsite
g) Installing ethernet cable and terminating cable from central control unit
to communication device
h) Taking precautions to ensure material is not damaged during
transportation
i) All labor, tools, equipment, and incidentals d. Furnish and Install PTZ Camera Cable
1) Measurement
a) Measurement for this Item shall be per linear foot of PTZ Camera
cable furnished and installed.
2) Payment a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot
“Furnish/Install CAT5 Ethernet Cable”.
3) The price bid shall include:
a) Furnishing and installing PTZ camera cable
b) Making all connections to PTZ camera and communication device
c) All labor, tools, equipment, and incidentals to install cable.
e. Install PTZ Camera Cable
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 26
TRAFFIC SIGNALS
Page 26 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) Measurement
a) Measurement for this Item shall be per linear foot of PTZ Camera
cable installed.
2) Payment
a) The work performed and materials furnished in accordance with this Item shall be paid for at the unit price bid per linear foot “Install
Communication Cable” installed.
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) All labor, tools, equipment, and incidentals to install cable.
e) Making all connections to PTZ camera and communication device
27. Communication Modem
a. Furnish and Install Communication Modem
1) Measurement
a) Measurement for this Item shall be per each Communication Modem furnish and installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Furnish/Install
Communication Modem”
3) The price bid shall include: a) Furnishing, installing, and testing the Communication Modem
b) Furnishing and installing 2 antennas on cabinet
c) Power supply
d) Cable terminations to Communication Modem
b. Install Communication Modem 1) Measurement
a) Measurement for this Item shall be per each Communication Modem
installed.
2) Payment
a) The work performed and materials furnished in accordance to this Item
shall be paid for at the unit price bid per each “Install Communication
Modem”
3) The price bid shall include:
a) Installing, and testing the Communication Modem
b) Installing 2 antennas on cabinet
c) Power supply d) Cable terminations to Communication Modem
e) All labor, tools, equipment, and incidentals
f) Scheduling pickup of material from the City designated area
g) Pickup and transportation of material from the City designated area to
the jobsite
h) Taking precautions to ensure material is not damaged during
transportation
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 27
TRAFFIC SIGNALS
Page 27 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
28. Fish -Eye Detection System
a. Furnish and Install Fish -Eye Detection System
1) Measurement
a) Measurement for this Item shall be per each fish-eye detection system
furnished and installed. 2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Furnish/Install
Fisheye Detection System”.
3) The price bid shall include:
a) Furnishing, installing and testing fish-eye detection system
b) Mounting hardware
c) Operational software
d) Communication interface panel
e) Setup of all detection zones per traffic signal plans. Setup must be approved by City staff.
f) Cable will be paid for separately
g) Grounding of each device
h) Central control unit in cabinet
i) Furnishing SDLC compatible cable and terminating SDLC cable
j) Furnishing ethernet cable and terminating cable from central control
unit to communication device
k) All labor, tools, equipment, and incidentals
b. Install Fish -Eye Detection System
1) Measurement
a) Measurement for this Item shall be per each fish-eye detection installed.
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Install Fish-Eye
Detection System”. 3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation d) Installing and testing of the fisheye detection system.
e) Setup of all detection zones per traffic signal plans. Setup must be
approved by City staff.
f) Furnishing SDLC compatible cable and terminating SDLC cable
g) Furnishing ethernet cable and terminating cable from central control unit to communication device
h) All labor, tools, equipment, and incidentals
c. Furnish and Install Fish -Eye Detection Cable
1) Measurement
a) Measurement for this Item shall be per linear foot of fisheye detection
cable furnished and installed.
2) Payment
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 28
TRAFFIC SIGNALS
Page 28 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) The work performed and materials furnished in ac cordance with this
Item shall be paid for at the unit price bid per linear foot
“Furnish/Install CAT5 Ethernet Cable”.
3) The price bid shall include:
a) Furnishing and installing fisheye detection cable b) Making all connections to camera and controller equipment
c) Furnishing SDLC compatible cable and terminating SDLC cable
d) Furnishing ethernet cable and terminating cable from central control
unit to communication device
e) All labor, tools, equipment, and incidentals to install cable
d. Install Fish -Eye Detection Cable
1) Measurement
a) Measurement for this Item shall be per linear foot of fisheye detection
cable installed.
2) Payment a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per linear foot “Install
Communication Cable” installed.
3) The price bid shall include:
a) Scheduling pickup of material from the City designated area
b) Pickup and transportation of material from the City designated area to
the jobsite
c) Taking precautions to ensure material is not damaged during
transportation
d) Installing cable
e) Making all connections to camera and controller equipment f) Furnishing SDLC compatible cable and terminating SDLC cable
g) Furnishing ethernet cable and terminating cable from central control
unit to communication device
h) All labo r, tools, equipment, and incidentals to install cable
1.4 REFERENCES
A. Abbreviations and Acronyms
1. VIVDS: Video imaging vehicle detection system
2. BBU: Battery back -up system
3. LED: light emitting diode
4. APS: Accessible Pedestrian Signal
5. RRFB: Rectangular rapid flashing beacon
B. Definitions
1. Battery Back-Up (BBU) System
a. Automatic Bypass Relay
1) A unit connected between the inverter/charger, and the load, which can
automatically switch power to the controller cabinet service panel from inverter output power to utility line power, in the event of an inverter
failure.
b. Battery Back-Up System (BBU Sy stem)
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 29
TRAFFIC SIGNALS
Page 29 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) The battery back-up system includes but is not limited to a manual bypass
switch, automatic bypass switch or power transfer switch, inverter/charger,
batteries, wiring, external cabinet and all necessary hardware for system
operation.
c. Battery Back-Up System Software (BBU System software) 1) All software associated with operation, programming and functional
requirements of the BBU system.
d. Battery Monitoring Device
1) The device which monitors battery temperatures and charge rate of the
batteries used in the BBU system. Shall be an ambient sensor internal to
the inverter/charger.
e. Batteries
1) Standard 12V batteries wired in series with a cumulative minimum rated
capacity of 210 amp-hours.
f. Boost 1) When enabled, the BBU inverter/charger shall automatically switch into
this mode to raise the utility line voltage when it drops below a preset limit.
The limit may be user defined or use manufacturer default settings
(typically 100V AC).
g. Buck
1) When enabled, the unit shall automatically switch into this mode to reduc e
the utility line voltage when it rises above a preset limit. The limit may be
user defined or use manufacturer default settings (typically 135V AC).
h. External Cabinet
1) The structure which houses the complete system components for the BBU
System. i. Inverter /Charger
1) The unit which converts the DC voltage input into 120 VAC output for the
traffic signal cabinet to operate. As a minimum the inverter/charger shall
be rated for 1400 VA, 1000 watts.
j. Inverter Line Voltage 1) The power supplied from the BBU system to the traffic signal cabinet from
the BBU System inverter.
k. Manual Bypass
1) Manual switch that allows user to bypass BBU power to service system
equipment. Manual bypass switch switches utility line power directly to
cabinet. l. Signal Operation Mode
1) A signalized intersection generating a 700W load when running in normal
operation.
m. Signal Flash Mode
1) A signalized intersection generating a 300W load when running in the flash mode of operation.
n. Utility Line Voltage
1) The 120V AC power supplied to the BBU system
C. Reference Standards
1. Reference standards cited in this Specification refer to the current reference
standard published at the time of the latest revision date logged at the end of this
Specification , unless a date is specifically cited .
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 30
TRAFFIC SIGNALS
Page 30 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2. American Standard Testing Materials (ASTM)
a. ASTM B85 -57T – “Standard Specification for Aluminum-Alloy Die Castings”
b. ASTM B26 -57T – “Standard Specification for Aluminum-Alloy Sand
Castings”
c. ASTM B-209-57T – “Standard Specification for Aluminum and Aluminum-Alloy Sheet and Plate”
d. ASTM D -1535 – “Standard Practice for Specifying Color by the Munsell
System”
e. ASTM B-033 – “Standard Specification for Tinned Soft or Annealed Copper
Wire for Electrical Purposes”
f. ASTM B-8 – “Standard Specification for Concentric -Lay -Stranded Copper
Conductors, Hard, Medium-Hard, or Soft”
g. ASTM A3250-N – “High Strength Galvanized Steel Bolts”
h. ASTM A490 -N – “High Strength Galvanized Steel Bolts”
i. ASTM A123 – “Standard Specification for Zinc (Hot-Dip Galvanized) Coatings on Iron and Steel Products”
j. ASTM A153 – “Standard Specification for Zinc Coating (Hot-Dip) on Iron and
Steel Hardware”
3. Texas Manual on Uniform Control Devices (TMUTCD) a. Part IV – Traffic Signals
4. Manual on Uniform Traffic Control Devices, 2009 Edition
a. Digits
5. Federal Aviation Administration (FAA)
a. FAA L -802-B
6. Institute of Transportation Engineers (ITE):
a. Vehicle Traffic Control Signal Head – Light Emitting Diode (LED) Circular
Signal Supplemental (VTCSH), adopted June 2005.
b. Vehicle Traffic Control Signal Head Part 3: Light Emitting Diode (LED)
Arrow Traffic Signal Modules.
c. Equipment and Materials Standards, Vehicle Traffic Control Signal Heads
(VTCSH) Part 2: LED Vehicle Signal Modules. d. PTCSI LED Signal Modules Draft Version of February 2009
1) Luminous intensity, uniformity and viewing angles
2) Chr omaticity
7. Underwriter’s Laboratory Incorporate (UL)
a. Standard UL-651 – “Schedule 40 and 80 Rigid PVC Conduit and Fittings”
b. Standard UL-514B – “Conduit, Tubing, and Cable Fittings
8. American Standards Institute (ANSI)/Institute of Electrical and Electronics
Engineers (IEEE) a. Section 6.1.2 ANSI/IEEE C62.41.2 – 2002, 3KV, 2 Ω
b. Section 6.1.1 ANSI/IEEE C62.41.2 – 2002, 6KV, 30Ω
c. Transient suppression
9. MIL-STD-883 a. Test Method 2007
b. Mechanical vibration
10. MIL-STD-810F
a. Procedure 1, Rain & Blowing Rain
b. Moisture resistance
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 31
TRAFFIC SIGNALS
Page 31 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
11. National Electrical Manufacturer’s Association (NEMA)
a. Section 2.1.6 NEMA TS 2-2003
b. Section 2.1.8 NEMA TS 2-2003
c. Transient voltage protection
d. Controller compatibility
12. Federal Communications Commission (FCC)
a. Title 47 Sec 15 Sub. B
b. Electronic noise
13. International Municipal Signal Association (IMSA)
a. IMSA 5 -1
b. IMSA 7 -1
c. IMSA 20 -1
14. National Fire Protection Association (NFPA) / National Electric Code (NEC)
a. NFPA 70
b. Wiring
15. International Electrotechnical Commission (IEC)
a. Section 8.2 IEC 1000-4-5
b. Section 8.0 IEC 1000-4-12
c. Transient suppression
1.5 ADMINISTRATIVE REQUI REMENTS
A. Coordination
1. City must approve any deviation from Specification ten (10) working days prior to
installation .
B. Preinstallation Field Inspection Meetings
1. 48 hours’ Notice of Intention to establish final location of any foundations, bases,
conduit, and detectors.
2. 48 hours’ notice to Texas811, City of Fort Worth Water and Sewer (817-871-
8275), and City of Fort Worth Traffic Signals /Street Lights/Storm Drains (817-
392-8100).
C. Scheduling
1. 5 Working Days’ advanc ed approval for existing traffic signal turn off of flash operation.
2. 5 Working Days’ advanced notice of placing traffic signal into operation.
3. 5 Working Days’ notice for City provided equipment pick-up.
1.6 SUBMITTALS
A. Submittals shall be in accordance with Sec tion 01 33 00.
B. All submittals shall be approved by the City prior to delivery and/or fabrication for
specials.
1.7 ACTION SUBMITTALS/INFORMATIONAL SUBMITTA LS
A. Product Data Sheets are required for:
1. Traffic signal housing, louvered back plates, visors, louvers, LED lamps, and mounting hardware
2. Pedestrian signal housing, LED lamps, and mounting hardware
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 32
TRAFFIC SIGNALS
Page 32 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
3. Pedestrian push button assemblies
4. Accessible Pedestrian Signals
5. Conduit
6. Battery back-up systems
7. Multi-conductor cable
8. Insulated electrical cable
9. Ground boxes
10. Grounding conductor
11. Grounding rod
12. Concrete (Refer to Section 03 30 00)
13. Vibration dampers
14. Standard and Decorative Traffic Signal Structures
15. Roadside Flashing Beacon Assembly
16. PTZ Camera
17. Communication Modem
18. Vehicle Detection Systems
19. Emergency Vehicle Preemption System
20. Railroad Preemption System
21. School Zone Flasher Assembly
22. Rectangular Rapid Flashing Beacon Assembly
23. Miscellaneous ITS equipment
24. Miscellaneous items supplied
1.8 DELIVERY, STORAGE, AND HANDLING
A. Storage and Handling Requirements
1. Parts shall be properly protected so that no damage or deterioration occurs during a
prolonged delay from the time of shipment until installation.
2. Exposed anchor bolts shall be protected until pole shaft is installed.
3. Finished iron or steel surfaces not painted shall be properly protected to prevent rust
and corrosion.
4. Prevent plastic and similar brittle items from being exposed to direct sunlight and
extremes in temperature.
5. The Contractor shall secure and maintain a location to store the material in
accordance with Section 01 50 00.
B. Delivery and Acceptance
1. Inspect all City furnished materials prior to taking possession. Any damages after
taking possession shall be the responsibility of the Contractor.
2. Arrange pick up all City furnished materials and deliver them to the Site .
1.9 WARRANTY
A. Manufacturer Warranty
1. Manufacturer’s warranty shall be in accordance with Division 1.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 33
TRAFFIC SIGNALS
Page 33 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2. A 2 year warranty shall be required on all equipment furnished by the Contractor.
3. A 3 year warranty shall be required on all rectangular rapid flashing beacon
assemblies.
4. A 5 year unconditional warranty shall be required on all batteries for the battery back-
up systems furnished by the Contractor.
5. 5 year warranty shall be required on all ATC Signal Controllers
6. 5 year warranty shall be required on all Signal Controller Cabinet Assemblies
7. A 5 year warranty shall be required on all APS units.
8. School zone flasher
a. Each school zone flasher cabinet assembly shall be warranted to be free from
defects in material and workmanship for a period of five years from date of
shipment from the factory.
b. The 50/100 Ah battery shall be low self-discharging, leak proof, gelled electrolyte and maintenance free intended for photo voltaic service. The
battery shall carry a prorated warranty for a minimum of two years by the
battery manufacturer.
c. The regulator shall have a warranty of five (5) years from the date of purchase.
d. Each time switch shall be warranted to be free from defects in material and workmanship for a period of five (5) years from the date of shipment from the
factory.
B. Extended Correction Period
1. Contractor responsible for correcting any substandard workmanship and/or
materials for 24 months from the date the signal is accepted by the City .
PART 2 - PRODUCTS
2.1 PRODUCTS TO BE FURNISHED FROM THE CITY
A. Refer to Drawings and Contract Documents to determine if any Items are to be
furnished from the City and installed by the Contractor.
B. Items that the City may furnish include but not limited to:
1. Signal c ontroller
2. Controller cabinet assembly
3. Traffic signal poles
4. Traffic signal mast arms
5. Detection equipment
6. Preemption equipment
7. Signs
8. Communications device
9. Cable
10. PTZ Camera
11. Audible pedestrian signal push buttons
2.2 ASSEMBLIES , EQUIPMENT, PRODUCT TYPES , AND MATERIALS
A. Manufacturers
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 34
TRAFFIC SIGNALS
Page 34 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1. The manufacturer must comply with this Specification and related Sections.
2. Any equipment, product type, or material that is not listed in this Specification or
included on the product cut sheets on appendix or in TxDOT’s Material Producer List is considered a substitution and shall be submitted in accordance with Section
01 25 00 and not installed until approved.
a. http://www.txdot.gov/inside-txdot/division/construction/producer-list.html
3. If more than 1 unit of a given bid item is required, then the Contractor shall ensure that all units are the product of 1 manufacturer, unless otherwise directed by the
Transportation Management Manager or designee. No mix or matching will be
allowed.
B. Description
1. Regulatory Requirements
a. Traffic signal shall meet or exceed standards set forth by the Texas Manual on
Uniform Traffic Control Devices (TMUTCD), National Electric Code (NEC), Institute of Transportation Engineers (ITE), American Society for Testing and
Materials (ASTM), American Standards Institute (ANSI), and National
Electrical Manufacturer’s Association (NEMA).
2. It is the Contractor's responsibility to furnish all materials necessary to complete each traffic signal installation, whether the item is specifically mentioned or not.
All unspecified materials (i.e., electrical tape, bolts, and nuts, etc.) shall meet the
requirements of the National Electrical Code.
3. All materials supplied by the Contractor shall be of new, un-depreciated stock.
C. Traffic Signal Materials
1. LED Traffic Signal Head Assemblies
a. Vehicle Signal Housings
1) The product bid shall be manufactured by one of the following
manufacturers:
a) Econolite
b) McCain c) Other approved equivalent by City Traffic signal Engineering Manager
or Designee
2) The housing and doors of the signal head shall be made of die cast
aluminum alloy in accordance with ASTM Specification B85-57T.
3) Sandcast aluminum alloy shall be used for other parts of the signal head if
in accordance with ASTM Specification B26-57T.
4) The visors shall be fabricated from aluminum sheet conforming to the
ASTM Specification B-209-57T.
5) All miscellaneous parts such as hinge pins, lens clips, locking devices, etc.
shall be made of a non-corrosive material. 6) The housing of the signal heads shall be constructed of interchangeable
sections.
7) All exterior mating surfaces shall be flat to assure waterproof and dust-
proof assembly of sections.
8) The top and bottom of the sections will have an opening approximately 2 inches in diameter to permit the entrance of 1 ½ inch pipe nipples.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 35
TRAFFIC SIGNALS
Page 35 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
9) Each section shall have serrated openings or equivalent, for providing a
positive and locked positioning of signal sections when used with serrated
mast arm or span wire mounting brackets.
10) The door and lens housing shall be equipped with a watertight and dust-
tight molded neoprene gasket. a) The door of each signal section shall be attached to the housing in a
watertight and dust-proof manner.
b) Non-corrosive hinge pins and 2 wing screws will be furnished on each
door for opening and closing without the use of special tools.
(1) These hinges and screws shall be of such design as to allow even
gasket pressure.
11) Each signal head section shall be furnished with a detachable tunnel type
visor unless otherwise specified.
12) Visors shall be a minimum of 10 inches in length (depth) for 12 inch
signals. a) Visors shall be attached to the door assemblies in a manner that
facilitates field removal and installation.
b) Visors shall be fabricated from aluminum and shall not form a
complete circle and shall have the bottom open, unless louvers are
required.
13) Traffic signal housing shall be furnished with LED inserts that comply
with this Specification and shall be in the standard red, amber and green
configuration as specified by the most current version of the TMUTCD.
14) A screw down type terminal block shall be provided with each signal head
for facilitating field wiring.
15) The pigtail leads from the lamp receptacles shall be connected to a common terminal block within the head assembly.
16) Each terminal block will be at least a 6 position, 12 terminal strip securely
fastened at both ends to the signal housing.
17) The housing and outside sur face of the visors shall be traffic yellow (RAL
1023) in color. a) The inside surface of visors shall be a “Dull” or “Flat-black” color.
b) The outside surface shall have a minimum of 2 coats of baked chrome
yellow enamel (TT -C-595E1310), Munsell notation O.YP 47/15/3, per
FAA Specification L-802-B and ASTM D 1535.
b. LED traffic signal lamp unit
1) The product bid shall be manufactured by one of the following manufacturers:
a) GE Lighting Solutions
b) Dialight for bimodal indications only
c) Other approved equivalent approved by City Traffic Signal
Engineering Manger or Designee 2) The equipment shall conform to the applicable requirements of: the
Underwriter’s Laboratory Incorporate (UL), the American Society for
Testing and Materials (ASTM), the American Standards Institute (ANSI),
the National Electrical Manufacturer’s Association (NEMA), and other
applicable standards and specifications.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 36
TRAFFIC SIGNALS
Page 36 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
3) The LED traffic signal lamp unit shall comply at a minimum with the
Institute of Transportation Engineers (ITE) specification for Vehicle T raffic
Control Signal Head – Light Emitting Diode (LED) Circular Signal
Supplement (VTCSH); adopted June 2005, for circular indications and
Vehicle Traffic Control Signal Head Part 3: Light Emitting Diode (LED)
Arrow Traffic Signal Modules for arrow indications.
4) The LED shall have an “incandescent” look, using the minimum number of
LED’s that comply with the ITE specification.
5) If proper orientation of the LED unit is required for optimum performance,
a clear, durable and unmistakable marking shall be provided on each lens
as to its proper orientation (top or bottom).
6) The manufacturer’s name, serial number and other necessary identification
shall be permanently marked on the backside of the LED traffic signal
lamp unit. A label shall be placed on the unit certifying compliance to ITE
standards. 7) Documentation Requirements
a) Each LED traffic signal lamp unit shall be provided with the following
documentation:
(1) Complete and accurate installation wiring guide
(2) Contact name, address, and telephone number for the
representative, manufacturer, or distributor for warranty repair.
(3) A copy of a test report certified by an independent laboratory that
the LED traffic signal lamp model submitted meets all the
requirements of these Specifications in accordance with ITE
VTSCH Part 2.
(4) Schematic diagram for each unit, along with any necessary installation instruc tions
(5) For each unit submitted, the manufacturer name, brand and model
number of LEDs used shall be provided, along with the LED
manufacturer’s recommended drive current and degradation
curves. (6) Warranty information from manufacturer
(7) Quality assurance testing documentation
c. Signal head louvers
1) Louvers shall be provided for those signal sections indicated in the
Drawings.
2) All louvers shall be of such design as to provide vis ibility of the lens for the intended lane of traffic as indicated by the Drawings and block
visibility to all other lanes.
d. Mounting hardware
1) Mast Arm Mount Signal Bracket, 1-Way Cable Mount
a) The product bid shall be the mast arm mount signal bracket, 1-way cable mount, for 3 to 5 section head with 84 inches cable and 74 inches
long gusseted tube manufactured by Pelco, part no. AB-0125, or
approved equivalent.
2) Mast Arm Mount Signal Bracket, 1-Way Cable Mount, Clamp Assembly
a) The product bid shall be the mast arm clamp assembly with 84 inches
cable manufactured by Pelco, part no. AB-3009, or approved
equivalent.
3) Mast Arm Mount Signal Bracket, 2-Way Cable Mount
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 37
TRAFFIC SIGNALS
Page 37 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) The product bid shall be the mast arm mount signal bracket, cluster
cable mount, for 5 section signal head with 84 inches cable
manufactured by Pelco, part no. AB-0138, or approved equivalent.
General Specifications are below.
4) General Specifications a) Bracket shall be completely adjustable such that it is capable of
rotational adjustment about the bracket axis, vertical adjustment,
rotational adjustment about the mast arm and rotational adjustment
right & left from the vertical plane.
b) Bracket shall be provided with aircraft type stranded cable for
fastening the bracket to the supporting arm or structure.
c) Bracket shall be easily adjustable to fit all sizes of round, octagonal,
elliptical or other shaped structure without special tools or equipment.
d) Bracket shall attach to the signal in a clamping manner holding the
signal both top and bottom in order to assure maximum rigidity. (1) For the 1-way cable mount, a standard bracket shall accommodate
all major signal manufacturers’ signals from a 3 section 1-way 12
inches signal through a 5 section 1-way 12 inches signal and any
combination thereof including 3M and ICC configurations.
(2) For the 2-way cable mount, a standard bracket shall accommodate
all major signal manufacturers’ signals for a 3 section 2-way 12
inches signal and any combination thereof including 3M and ICC
configurations.
e) Upper and Lower Arms
(1) Shall be cast from 319 aluminum or equivalent
(2) The lower bracket arm shall be internally threaded to accommodate the threaded vertical support tube.
(3) The lower arm shall be furnished with ABS plastic covers, which
will slide and snap into position without the use of fasteners or
tools.
(4) All upper and lower arms shall have 72 tooth serrations cast into the arm to assure a positive lock with signal housing and shall be
secured about their rotational axis with setscrews.
(5) Both upper and lower arms shall have a tri-bolt arrangement for
attachment to the signal housing.
(6) Opening in the lower arms shall accommodate a minimum of 3, 12
conductor 14 gauge cables. f) Vertical Support Tube
(1) Shall be a double gusseted tube extruded from 6063-T6 aluminum
alloy or equivalent and have a cross section.
(2) Each tube shall be complete with a vinyl closure strip and be
threaded on 1 end to accommodate the lower arm assembly. g) Mast Arm Clamp Assembly
(1) Both male and female halves shall be cast from 713 aluminum
alloy or equivalent.
(2) The male clamp half shall be secured within the female half,
utilizing a spring steel retainer ring.
(3) Such assembly shall provide an unobstructed center of 2 3/8 inches
minimum diameter, allowing for 360 degree rotation of the clamp
assembly.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 38
TRAFFIC SIGNALS
Page 38 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(4) There shall be no internal cross bracing assembly obstructing the
center opening.
h) Aircraft Type Stranded Cable
(1) Shall be fabricated in 1 piece with a minimum diameter of 3/16
inches eithe r galvanized or stainless steel (2) The cable shall be complete with 7/16 inch stainless steel clamp
screw permanently attached to each end. Each clamp screw shall
be fitted with a stainless steel hex nut, SAE flat washer and an
aluminum-bearing washer.
(3) The clamp screw shall be flattened on 2 opposite sides for wrench
accommodation. The stranded cable shall be of sufficient length to
fasten the clamp assembly to a minimum pole diameter of 8.6
in ches .
i) Each bracket shall be complete with all necessary bolts, washers,
gaskets, etc. to allow assembly of the signal to the bracket and the bracket to the mast arm.
j) All aluminum parts shall have an Alodine (or equivalent) finish. All
steel parts shall have a traffic yellow (RAL 1023) zinc di-chromate
finish.
2. LED Countdown Pedestrian Signal Head Assemblies
a. General
1) Furnish a single, self-contained module, not requiring on-site assembly for
retrofit into existing traffic signal housings as defined in TxDOT DMS -
11130, Pedestrian Signal Heads. Ensure that installation does not require
special tools. 2) Provide LED’s rated for 100,000 hours of continuous operation over a
temperature range of -40°C to +74°C.
3) Ensure modules are rated for a minimum life of 60 months.
4) Ensure modules meet all parameters of this specification throughout this
60-month period. 5) Use LEDs manufactured using aluminum-indium-gallium -phosphide
(AlInGaP) technology or other LEDs with lower susceptibility to
temperature degradation than aluminum-gallium -arsenic (AlGaAs)
technology. AlGaAs LEDs are not allowed aluminum.
b. Housing
1) The product bid shall be manufactured by one of the following
manufacturers:
a) McCain Traffic Supply
b) Other approved equivalent by City Traffic Signal Engineering
Manager or Designee
2) Housings will not be provided for retrofit modules. 3) Housing units shall be new and unweathered.
4) Housing shall be in accordance with TxDOT DMS-11130.
5) The housing shall be fitted with an LED module that has an incandescent
look.
6) The housing shall be a 1-piece corrosion resistant aluminum alloy die-
casting with integrally cast top, bottom and sides that are weather proof
and dust-tight.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 39
TRAFFIC SIGNALS
Page 39 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
7) The housing shall be right and left drilled for clamshell attachment and
shall have top and bottom ports that are opened and capped and will
accommodate standard 1 ½ inches pipe.
8) The approximate size of housing (including body, door, and ears) shall be
16.0 inches H x 18.75 inches W x 8 inches D. 9) The door frame shall be a 1-piece corrosion resistant aluminum die-castin g.
10) The housing shall be traffic yellow (RAL 1023).
11) The housing shall have a standard 3-position terminal block, pre-wired to
receptacles to permit easy field installation of a power supply.
12) All necessary hardware shall be provided with housing. Rivets shall be
aluminum and bolts, lock washers, screws, eyebolt assembly and pins shall
be stainless steel.
c. Mounting hardware
1) Mounting hardware shall be the clamshell mount type #4805 manufactured
by McCain, or approved equivalent. 2) Mounting hardware shall be a 2-piece, cast aluminum alloy assembly.
3) The 2 separate castings shall be joined in the final assembly by the use of
stainless steel spring pins.
4) The pole half of the assembly shall be designed to adapt to a wide range of
pole configurations (4 inch minimum diameter).
5) Unit construction shall allow band-it type mounting.
6) Band -it type mounting shall be permitted by 2 recessed slots near the top
and bottom of the pole half of the assembly.
7) The pedestrian assembly shall be capable of being mounted on the pole by
lining up the mounting pins of the pole half with the mounting ears of the
pedestrian assembly and lowering it into position. 8) 3 sets of screw terminal pairs shall be located on a terminal block in the
upper third of the head half of the clamshell assembly.
9) A closed cell neoprene sponge gasket shall be provided on the mating
surfaces of the 2 halves of the assembly to compete the rain-tight
construction. d. Module
1) Modules shall comply with TxDOT DMS-11130.
2) Ensure retrofit modules are capable of replacing the optical unit.
3) The module lens may be a replaceable part without the need to replace the
complete module.
4) Ensure the walking person and hand icons (16 in. x 18 in. size only) are full (not outlines).
5) Ensure the countdown digits are made up of two rows of LEDs.
6) Ensure each digit is a minimum of 7 in. in height.
7) For each nominal message bearing surface (module) size, use the
corresponding H (height) and W (width):
Bearing Surface Module Size Icon Height Icon Width Countdown Height Countdown Width
H (16 x 18 in.) Min 7 in. 7 in. Min 9 in. 6.5 in.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 40
TRAFFIC SIGNALS
Page 40 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
8) Ensure the units do not have any attachments or options that will allow the
mode to be changed from counting the clearance cycle, to the full
walk/don’t walk cycle.
9) Provide modules that are single, self-contained devices, not requiring on-
site assembly for installation into existing traffic signal housing. 10) Ensure the power supply is designed to fit and mount inside the pedestrian
signal module.
11) Ensure the assembly and manufacturing process for the module is designed
to assure all internal LED and electronic components are adequately
supported to withstand mechanical shock and vibration from high winds
and other sources.
e. Environmental Requirements
1) Ensure the module is rated for use in the ambient operating temperature
range, measured at the exposed rear of the module, of –40°C to +74°C (–
40°F to +165°F). 2) Ensure the pedestrian module is designed to meet NEMA 250 Hose down
Test.
3) The test is to be conducted on a stand-alone unit. No protective housing
will be used.
4) Ensure the module lens is UV stabilized.
5) Ensure that the LED optical unit is dust- and moisture-proof to protect all
internal LED and electrical components.
6) Provide housing for each LED optical unit that is a sealed watertight
enclosure that prevents dirt contamination and allows for safe handling in
all weather conditions.
7) Perform moisture-resistance testing on LED signal sections in accordance with the requirements in the latest NEMA Standard 250 for Type 4
enclosures.
8) Evidence of internal moisture after testing will be cause for rejection.
f. Signal Lens
1) Ensure the lens of the LED pedestrian and countdown signal modules are polycarbonate UV stabilized and a minimum of 1/4 in. thick.
2) Ensure the exterior of the lens of the LED pedestrian and countdown signal
module are smooth and frosted to prevent sun phantom.
g. Module Identification
1) Each module must be permanently identified on the backside with the
manufacturer ’s name, model numbers, manufactured date (minimum week and year), and serial number.
2) Ensure the following operating characteristics are identified: nominal
voltage, power consumption, wattage and Volt-Ampere .
h. Photometric Requirements
1) Luminance, Uniformity & Distribution a) Ensure that for a minimum period of 60 months, the maintained
minimum luminance values for the modules under normal operating
conditions are not less than 2200 cd/m2 for the Walking Person icon
and 1400 cd/m2 for the Hand icon when measured perpendicular to the
surface of the module at nine (nine) separate points on the icon.
b) These values may decrease up to 50% of these table values beyond 15°
from the perpendicular in either to the left or right on a horizontal
plane.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 41
TRAFFIC SIGNALS
Page 41 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c) Ensure that the luminance of the module does not exceed three times
the maintained minimum luminance of the modules .
d) Ensure that the uniformity of the walking person and hand icons’
illumination meet a ratio of not more than 1 to 5 between the minimum
and maximum luminance measurements (in Cd/m2). 2) Chromaticity
a) The standard colors for the LED Pedestrian Signal Module must be
White for the walking person and Portland Orange for the hand icon
and countdown digits on a black opaque background.
b) Furnish an optical unit that remains in accordance with the
chromaticity (color) requirements in the latest Equipment and Material
Standards of the Institute of Transportation Engineers, Chapter 3:
"Pedestrian Traffic Control Signal Heads," for a minimum of 60
months over an operating temperature range of −40°F to 165°F.
i. Electrical 1) General
a) Furnish modules that are operationally compatible with traffic signal
controllers, cabinets and accessories manufactured to City
specifications.
b) Ensure that all wiring and terminal blocks meet the requirements of
Section 13.02 of the VTCSH Standard.
c) Three secured, color coded, 914 mm (36 in) long 600 V, 16 AWG
minimum, jacketed wires, conforming to the National Electrical Code,
rated for service at +105°C, are to be provided for electrical
connection.
d) Furnish LED signal modules that are designed so that there is no noticeable light output when connected to rated voltage through an
impedance of 15 Kohm (either resistive or capacitive).
e) Furnish signal modules that are designed so that, under normal
operation, an AC voltage of no greater than 10 volts RMS shall be
developed across the unit when it is connected in series with any value of impedance greater than 15 Kohms and for any applied AC voltage
between 95 and 135 volts RMS that is connected across this series
combination.
f) In addition, the signal module must be designed so that the voltage
across the module will reduce in value to less than 10 volts RMS
within 100 msec when the module is switched off by any solid state switch or switch pack having an impedance of 15 Kohms or greater.
g) Incorporate a regulated power supply engineered to electrically protect
the LEDs and maintain safe and reliable operation in each LED optical
unit.
h) Use a power supply that provides capacitor-filtered direct current (DC) regulated current to the LEDs per the LED manufacturer specification.
Designs that operate at currents greater than the LED manufacturer's
recommended drive current will not be allowed.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 42
TRAFFIC SIGNALS
Page 42 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
i) Design the power supply so that the failure of an individual component
or any combination of components cannot cause the signal to be
illuminated after alternating current (AC) power is removed. Provide a
signal module that is equipped such that each indication (i.e. walk
symbol, hand, and countdown display) is provided with a separate power supply.
2) Voltage Range
a) Ensure the LED modules operate from a 60 ± 3 Hertz AC line power
over a voltage range from 80 to 135 VAC RMS.
b) The current draw must be sufficient to ensure compatibility and proper
triggering and operation of load current switches and conflict monitors.
c) Nominal operating voltage for all measurements must be 120 ± 3 Volts
rms.
d) Fluctuations in line voltage over the range of 80Vac to 135Vac must
not affect luminous intensity by more than ± 10%. e) Ensure the LED circuitry prevents flickering at less than 100 Hz over
the voltage range stated above.
f) Provide modules that are designed and constructed so that the failure of
a single LED will not result in the loss of additional LEDs.
g) There should be no illumination of the module when the applied
voltage is less than 35 VAC RMS.
h) To test for this condition the each icon must first be fully illuminated at
the nominal operating voltage.
i) The applied voltage must then be reduced to the point where there is no
illumination.
j) This point must be greater than 35 VAC RMS. k) Turn-On and Turn-Off Time
(1) Ensure each icon of the module reaches 90% of their full
illumination (turn -on) within 75 msec of the application of the
nominal operating voltage.
(2) The modules must not be illuminated (turn-off) after 75 msec of the removal of the nominal operating voltage.
l) For abnormal conditions when nominal voltage is applied to the unit
across the two-phase wires (rather than being applied to the phase wire
and the neutral wire) the pedestrian signal unit must default to the hand
symbol.
m) Transient Voltage Protection (1) Ensure the module’s on-board circuitry includes voltage surge
protection to withstand high-repetition noise transients and low -
repetition high-energy transients as stated in Section 2.1.6, NEMA
Standard TS-2, 2003, or the latest version.
n) Electronic Noise (1) The modules and associated on-board circuitry must meet Federal
Communications Commission (FCC) Title 47, Sub Part B, Section
15 regulations concerning the emission of electronic noise.
o) Power Factor (PF) and AC Harmonics
(1) Ensure the modules provide a power factor of 0.90 or greater when
operated at nominal operating voltage, and 25ºC (77ºF).
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 43
TRAFFIC SIGNALS
Page 43 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(2) Total harmonic distortion induced into an AC power line by the
module, operated at nominal operating voltage, at 25ºC (77ºF)
shall not exceed 20%.
3) Module Functions
a) Cycle (1) The module must operate in one mode: Clearance Cycle
Countdown Mode Only.
(2) The display of the number of remaining seconds must begin only
at the beginning of the pedestrian change interval.
(3) After the countdown displays zero, the display must remain dark
until the beginning of the next countdown.
(4) Module will not have user accessible switches or controls for
modif ication of cycle.
(5) Ensure the countdown pedestrian signal displays the number of
seconds remaining until the termination of the pedestrian change interval.
(6) Countdown displays must not be used during the walk interval nor
during the yellow change interval of a concurrent vehicular phase.
b) Learning Cycle
(1) Ensure that at power on, the module enters a single automatic
learning cycle.
(2) During the automatic learning cycle, the countdown display
remains dark.
c) Cycle Modification
(1) The unit re-programs itself if it de tects any increase or decrease of
Pedestrian Timing. (2) The counting unit will go blank once a change is detected and then
take one complete pedestrian cycle (with no counter during this
cycle) to adjust its buffer timer.
d) Recycling
(1) Ensure the module allows for consecutive cycles without displaying the steady Hand icon (“Don’t Walk”) or the countdown
display.
e) Preemption
(1) Provide modules that recognize preemption events and temporarily
modify the crossing cycle accordingly.
(2) If the controller preempts during the walking man, the countdown will follow the controller's directions and will adjust from walking
man to flashing hand.
(3) It will start to count down during the flashing hand. If the
pedestrian change interval is interrupted or shortened as a part of a
transition into a preemption sequence, the countdown pedestrian signal display should be discontinued and go dark immediately
upon activation of the preemption transition.
(4) The next cycle, following the preemption event, must use the
correct, initially programmed values.
f) “Don’t Walk” Steady
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 44
TRAFFIC SIGNALS
Page 44 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(1) If the controller output displays Don’t Walk steady condition and
the unit has not arrived to zero or if both the hand and man are
dark for some reason, the unit suspends any timing and the digits
will go dark.
(2) A steady UPRAISED HAND (symbolizing DONT WALK) signal indication must be displayed during the yellow change interval and
any red clearance interval (prior to a conflicting green being
displayed).
g) Power Failures
(1) The module must maintain a consistent countdown during short
power failures (less than 1 second).
(2) A longer failure or an absence of signal greater than one (1) second
must turn off countdown display and trigger a restart system
remembering the last sequence, as it is done for the 170/2070
traffic controller.
3. Pedestrian Push Button Assemblies
a. The product bid shall be the Passport with station assembly manufactured by
Pelco, or approved equivalent by the City Traffic Signal Engineering Manager
or Designee, and shall meet the following specifications: 1) Button must be highly vandal resistant and pressure activated with
essentially no moving parts.
2) Button must be able to withstand an impact from a baseball bat or hammer.
3) Button housing must be cast aluminum powder coated traffic yellow (RAL
1023).
4) Button cap must be made of 316 stainless steel. 5) Switch must be solid state electronic Piezo switch rated for 100 million
cycles with no moving plunger or moving electrical contacts.
6) Button must have LED to give indication of button being pushed.
7) Button must give a 2 toned beep indication of button being pushed (1 tone
for push, 1 tone for release). 8) Button must have built in surge protection.
9) Button must be able to hold the call for a minimum of 5 seconds.
10) Button must operate immediately after being completely immersed in
water for 5 minutes.
11) Button must not be able to allow ice to form such that it would impede
function of button or button cap.
12) All switch electronics must be sealed within the cast aluminum housing.
13) Button must have raised ridges to protect the button from side impacts.
14) The button shall come complete with an aluminum round housing to be
mounted to the signal pole. The housing shall be cast aluminum powder
coated traffic yellow (RAL 1023). 15) R10-3e push button signs
16) All neces sary pole mounting hardware shall be supplied.
4. Accessible Pedestrian Signals (APS) a. The product bid shall be iNavigator APS™ by Polara, Pelco IntelliCross , or
approved equivalent by City Traffic Signal Engineering Manager or Designee,
and shall meet the following specifications:
1) Housing requirements
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 45
TRAFFIC SIGNALS
Page 45 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Provide a 2-piece cast aluminum housing unit consisting of a base
housing and a removable cover.
b) Shall be vandal proof and be powder coated to provide a high contrast
to the support structure for the visually impaired.
c) Made of corrosion-resistant material. The bolts used for mounting the APS housing to the support structure shall be stainless steel.
d) Shall come as a two part swivel and lock system with APS button
station and mounting plate. The mounting plate mus t have two
elongated holes for mounting to the standard of minimum 0.300” x
0.5”. One mounting hole shall be in a vertical orientation and the
second mounting hole shall be in a horizontal orientation to allow for
drill alignment errors.
e) For ease of mounting a push button height indicator will be located on
the mounting plate to assure consistent and uniform installation.
f) The swivel and lock system shall provide a minimum of plus and minus 15 degrees of rotation. A single security screw shall be used to
sec ure the APS assembly to the mounting plate for quick assembly and
disassembly.
g) The mounting plate shall provide for banding the APS assembly to a
pole with two 5/8” type steel bands.
h) The mounting plate shall provide a bend/ radius for wiring exiting from
the pole and create a natural drip loop of the wires before entering the
APS assembly.
i) Be attached to the pole with two ¼-20 screws suitable for use in tapped
holes. The mounting plate hole arrangement shall ensure that the clear
space between any two mounting holes required in the post must be at least twice the diameter of the larger hole.
j) The size and design of the APS button shall be to allow two APS
button assemblies to be mounted adjacent on a four inch diameter pole
without need for an additional adaptor or spacer.
k) Access to wiring and programming ports is provided via a separate compartment distinct from the main housing.
2) Ensure the internal components provide a pushbutton with all the electrical
and mechanical parts required for operation.
3) Supply housing or an adapter (saddle) that conforms to the pole shape,
fitting flush to ensure a rigid installation.
4) Supply adapters of the same material and construction as the housing. 5) Close unused openings with a weather-tight closure painted to matc h the
housing.
6) Provide a minimum 0.5 inch hole with an insulating bushing through the
back of the housing.
7) Ensure the manufacturers name or trademark is located on the housing. 8) The APS pushbutton shall be a solid state switch rated for at least 1 million
operations.
9) Ensure APS complies with US Access Board’s “Draft Guidelines for
Accessible Public Rights of Way” (PROWAG) Section R306.
10) Ensure that the APS complies with and provides operation consistent with
requirements of Sections 4E.09 through 4E.13 of the 2009 Edition of the
Federal Highway Administration publication Manual on Uniform Traffic
Control Devices.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 46
TRAFFIC SIGNALS
Page 46 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
11) Supply an APS (pushbutton station) that includes a pedestrian sign, a
pushbutton, vibrotactile arrow and an audible speaker contained in one unit
and with the following features:
a) Vibrating tactile arrow with high visual contrast.
b) Vibrotactile arrow shall be rotatable without disass embly of the APS enclosure. The arrow shall be adjustable by 4-degree increments.
c) Tactile arrows
(1) Raised a minimum of 0.031 inches (0.8mm) from the pedestrian
detector surface
(2) Between 1.378 inches (35mm) and 1.772 inches (45mm) in length
(3) A stroke width between 10 and 15 percent of the length of the
arrow
(4) An open arrowhead at 45 degrees to the shaft and not exceeding 33
percent of the length of the shaft
(5) Be easily removable and rotatable without APS button station disassembly
(6) Arrow affixed to the pedestrian detector face secured with security
type screws
(7) Where required a double arrow shall be provided on the pedestrian
detector
(8) Tactile arrows shall be located on the pedestrian detector, have
high visual contrast (dark on light), and shall be aligned parallel to
the direction of travel on the associated crosswalk
d) Pushbutton locator tone with a duration of 0.15 seconds or less,
repeating at 1-second intervals.
e) The pushbutton locator tones must deactivate when the traffic control signal is operating in a flashing mode.
f) The locator tones must be intensity responsive to ambient sound and be
audible (a maximum of 5 dBA louder than ambient sound) up to 6 to12
feet f rom the pushbutton or to the building line whichever is less.
g) Speech walk message for the WALKING PERSON (symbolizing WALK) indication .
h) Speech pushbutton information message.
i) Unless plans require otherwise, provide each pushbutton station with a
9” X 15” s ign. Use sheet aluminum with minimum thickness of 0.080
in. for information signs for push buttons.
j) Pedestrian detector shall: (1) Be a minimum of 2-inches (50mm) in diameter,
(2) Raised above the surrounding surface for ease of operation,
(3) The mechanism should not require more than 5 pounds (22.2 N) of
force to activate,
(4) Provide mounting for the directional tactile arrow, and (5) Provide a slot for changing the direction of the arrow through
button rotation with a blade type screwdriver.
k) Audible tone walk indications
(1) Consisting of ticks repeating at 8 to 10 times per second at multiple
frequencies with a dominant component at 880 Hz ± 20%.
(2) It must provide an audible walk indication during the walk interval
only.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 47
TRAFFIC SIGNALS
Page 47 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(3) The audible walk indication must be from the beginning of the
associated pedestrian walk phase and must have the same duration
as the pedestrian walk signal except it must be possible to limit the
accessible walk indication to the first 7 seconds of the walk
interval when the pedestrian signal rests in walk. (4) When the accessible walk indication is limited during rest in walk
a button press during the walk interval must recall the walk
interval provided the crossing time remaining is greater than the
pedestrian change interval.
12) Operational Features of system
a) Sound verification
(1) A sound verification feature shall be employed in the APS button
to prevent incorrect or erroneous sound direction indications from
reaching pedestrians.
(2) The sound verification system shall provide independent monitoring of the sounds and pedestrian signals and independent
control over the release of the sound to the pedestrian.
(3) The APS button internal program shall compare the digital sound
to be played directly with pedestrian signals monitored by the push
button station.
(4) This shall be accomplished by a separate microcontroller chip
located directly in each button station.
b) Distributed Intelligence
(1) The APS button stations shall operate independently and not
require a central control point for normal button operation.
(2) Button to button communication shall use existing field wiring. (3) The APS button stations shall not use wireless (over air)
communications for any communication requirement between
buttons.
(4) If the APS features fail in one pushbutton station the button will
still operate as a button and the other station will operate as normal.
c) Sounds
(1) The APS button station shall be capable of emitting sound cues
and voice messages during the Walk, Pedestrian Clearance, Don’t
Walk, Short and Long button presses, and on demand Train,
Emergency or Alerts requests. (2) The APS button shall provide a playlist for combing up to four
sound cues or messages. The APS button shall provide a minimum
of eight walk sounds, four button press sounds, two pedestrian
clearance sounds, and one don’t walk sound.
d) Crossing sounds concurrent or alternating (1) When buttons are used at each end of a crosswalk, the audible
“Walk” and/or “Flash Don’t Walk” (Pedestrian Clearance)
messages shall be agency configurable to emit tones that are
concurrent or alternating (when one is emitting a tone the other is
silent), for the full duration of the associated signal.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 48
TRAFFIC SIGNALS
Page 48 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(2) The concurrent/alternating mode shall be available on both the
button and overhead beacon speakers and separately settable to
commence with the Walk s ignal, Pedestrian Clearance signal or
both. The concurrent or alternating sounds shall be adjustable on-
site with the programming device. e) Audible beaconing sound during Walk
(1) The button shall provide several optional sounds for beaconing
including custom sounds/messages. This sound shall be
configurable to play through a push button speaker and/or optional
overhead speaker.
(2) The button shall provide smart detection logic to provide a way-
finding sound “on-demand”. This includes a short button press to
only ac tivate the button Walk sound/message and a long button
press to play the walk and/or pedestrian clear sound/message
through the button AND overhead beacon speaker. f) Ambient noise compensation
(1) A microphone shall be integrated at the button station to
automatically adjust the volume levels to compensate for the
ambient noise. Ambient noise shall be sampled prior to each sound
play.
g) Sound playback and sound pressure level settings
(1) Configuration for each sound shall be independently settable as
follows:
(a) Minimum sound level settable from 50dB to 110dB in 1dB
increments
(b) Maximum sound level settable from 50dB to 110dB in 1dB increments
(c) Gain (above ambient) level settable from 0dB to 20dB in 1dB
increments
(d) Period (repetition rate) settable from 0.1sec to 999sec in 0.1sec
increments (e) Playback speaker settable as; Button, Overhead (Beacon) or
both
(f) Duration of sound settable from 0sec to 999sec in 1sec
increments with default = 0 for maximum duration
(2) All sound level adjustments shall be presented in decibels (dB) and
settable in increments of 1dB. Separate sound level settings, as above, shall be provided for short and long button press.
h) Rest in walk application
(1) Fixed walk sound time – no re-service until next walk signal
(a) During the Walk signal, if the Walk sound has c ompleted due
to a fixed Duration setting, if no Pedestrian Clearance sound is programmed the Don’t Walk sound shall play by default.
(b) An APS button activation shall not replay the Walk sound after
the duration has passed while the Walk signal is still active.
(c) The APS button shall remember the activation call and at the
beginning of the Pedestrian Clearance the APS button shall
cause a contact closure to the traffic controller pedestrian input
and subsequently play the walk sound at the beginning of the
next Walk signal.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 49
TRAFFIC SIGNALS
Page 49 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(2) Fixed walk sound time – re-service on demand
(a) If a Pedestrian Clearance sound is programmed in the APS
Button, the Walk sound shall be re- serviceable within the
Walk Signal when activated.
(b) The Pedestrian Clearance sound is to ensure that there is a continuity of sound for pedestrian wayfinding in the crossing
should the Walk sound play and be terminated abruptly from a
signal change.
i) Adjustable long button press timing
(1) Configurable timing shall be available for the button to define how
long the button must be pressed to request a “Walk”
sound/message, played in accordance with the “long push setting”
for the sound message.
(2) This indication is defined as a “long button press”. An
acknowledgement tone shall be emitted when a “long button press” has been detected which is different from the short button press.
The acknowledgement tone shall be customizable and contain at
least five default choices.
j) Sound without button press
(1) Configuration shall be available on the button station to allow the
Walk sound and vibration to be activated at every Walk and
Pedestrian clearance signal without push button press requirement.
k) Signal malfunction monitoring
(1) The APS button station shall directly monitor the status of the
pedestrian signal and provide signal malfunction detection should
both walk and don’t walk signals either be steady OFF, ON. (2) In the case of a detected malfunction, the sound and vibration
functions shall be disabled until the conflict is removed for more
than approximately 1 second and the APS is in the Don’t Walk
interval.
13) Special Features (Communications Interface Unit (CUI)) a) Fault indication output to traffic controller
(1) The CIU shall monitor the health of each APS button and can be
programmed to provide a fault output to the traffic signal
controller.
(2) In the event of failure of an APS button or the CIU a contact
closure shall provide fault indication to the traffic signal controller. b) Evening sound control
(1) The CIU shall support an “Evening Maximum” sound control
hardware input which can be connected to a traffic controller time
of day control output.
(2) The Evening Maximum input, when active (must be settable as voltage ‘present’ or ‘absent’), shall cause selected APS buttons to
use the Evening Maximum sound level setting for all sounds. This
control shall be independent for each sound on each button to
achieve optimal intersection sound levels.
(3) The APS button shall support a timeout for this input to guard
against a stuck condition should the CIU fail.
c) Sound inhibit control
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 50
TRAFFIC SIGNALS
Page 50 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(1) The CIU shall support an APS button “Inhibit” control hardware
input which can be connected to a traffic controller time of day
control output.
(2) The Inhibit input, when active (must be settable as voltage
‘present’ or ‘absent’), shall cause the APS buttons to Inhibit Sound for all button speakers.
(3) The APS button shall support a timeout for this input to guard
against a stuck condition should the CIU fail.
d) Special event sounds
(1) The CIU shall s upport a “Special Event” sound control hardware
input which can be connected to a traffic controller or external
device event or time of day control output.
(2) The Special Event input, when active (must be settable as voltage
‘present’ or ‘absent’), shall cause selected APS buttons to use play
a Special Event sound playlist for that input. (3) The CIU shall support configuration of up to 11 Special event type
inputs including at a minimum; 1-Train, 5 -Emergency vehicle and
5-Alert messages.
e) Pre-timed intersection APS operation
(1) When APS buttons are installed at pre-timed (non-pedestrian
actuated) intersections they shall provide the same level of APS
service as if they were installed at a pedestrian actuated
intersection. An actuation at one APS button shall be transmitted to
the associated APS button on the same signal phase for proper
APS Button beaconing as may be required to assist pedestrians in
the crossing area. (2) The CIU shall provide a minimum of four pedestrian request
outputs that can be connected to the traffic signal controller
pedestrian inputs. The CIU pedestrian request outputs shall be
configurable to mirror APS button actuations to a minimum of four
phases. (3) The CIU pedestrian request outputs shall provide a solid-state pull
down to a TSC pedestrian input.
14) Product operating conditions
a) The APS button system shall be powered and operate from the existing
nominal 120 Vac pedestrian Don’t Walk and Walk signals only.
b) The APS button shall allow direct connection to the traffic signal pedestrian isolator inputs. The APS system shall operating in
temperatures from -37 ºC to +74 ºC (-35ºF to +165 ºF).
15) Materials and fabrication
a) Audible Signals shall be supplied with all mounting hardware for pole
and signal head mounting. b) The button station shall be die cast aluminum and shall be
weatherproof and vandal proof. The approximate dimensions are
336.55 x 127 x 88.9 mm or 13.25” x 5” x 3.5” (L x W x H).
c) The button station shall be designed to adapt to mounting on a support
structure without compromising the mechanical stability and the
environmental protection.
d) The Tactile Arrow shall be integrated into the button station housing.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 51
TRAFFIC SIGNALS
Page 51 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
e) Security screws shall be incorporated in key areas to discourage
tampering or unauthorized access.
f) Existing signage shall be used or sign and mounting bracket supplied
as follows. 5x7-3/4 sign with integrated sign holder
g) 9x12 sign with sign adapter 9x15 sign with sign adapter 16) Coating
a) The button station body shall be powder coated customers requested
color.
b) The button plunger shall be powder coated silver.
c) The Tactile arrow shall be E-coated black with clear top coat.
17) Programming requirements
a) The APS System shall allow pre-configuration or onsite configuration
of the APS attributes. The APS button can be ordered with a built in
configuration to the MUTCD 2009 standards for pedestrian poles that
are 10 feet or more apart and allow setup through a simple button press method without need of a programming device.
b) Programming device and/or software application shall be available for
configuration of all components of the APS system. The programming
device shall be compatible with Microsoft Windows 8.1, 7, Vista, XP.
c) The programmer shall allow wired and wireless programming of the
APS button and system components. It shall be possible to program
one or more APS buttons from any APS button at the intersection.
d) It shall be possible to program all push buttons from the CIU at the
traffic signal controller.
e) Wireless programming shall allow remote programming of the APS
button system within 150 feet (50m) of the traffic cabinet. f) The programming device shall allow programming of APS button
under wired and wireless conditions for; configuration, custom sounds,
firmware, HW profiles and CIU programming.
g) The programming device shall allow storage of an unlimited number of
custom templates and intersection profiles (within the storage capability of the PC).
h) IP based connection to the APS Button system for remote
programming and management shall be available.
18) Automatic volume adjustment in response to ambient traffic sound level
provided up to a maximum volume of 100 dBA.
19) Tone or voice volume measured at 3 ft. from the pushbutton station shall be 2 dB minimum and 5 dB maximum above ambient noise level and shall
be responsive to ambient noise level changes.
20) The pushbutton must be Americans with Disabilities Act compliant and
activate both the walk interval and accessible pedestrian signal.
21) Actuation indicator-tone and pedestrian acknowledge light. The light shall remain on until the next walk cycle has started.
22) Extended button press which can be used to request a louder WALK signal
and locator tone for subsequent clearance interval.
23) Internal speaker
a) Weather-resistant speaker protected by a vandal resistant screen.
b) Nominal 15w speaker that shall provide audible feedback in the form
of various signaling sounds
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 52
TRAFFIC SIGNALS
Page 52 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c) The button housing shall provide speaker ports to direct the sound in
front and behind the button station in line with the button sign face.
d) The APS button shall provide for the installation of speaker baffles to
block sound from the front or back as may be required for special
applications. 24) Pedestrian Button Feedback
a) Have a functional pushbutton that activates the pedestrian walk signal
whenever actuated, even if the audible speech walk message, the
pushbutton information message, the pushbutton locator tone, and the
vibrating surface features are disabled.
b) Have a pushbutton that when actuated activates the pedestrian walk
signal's timing during an APS attribute failure.
25) Power Interface Module (PIM)
a) A PIM shall be used to provide a low power interface to the APS
button station (nominal 12-15 VDC). b) The PIM shall be installed in the Pedestrian Signal head or in an
electrical box as required. The PIM shall be UL approved and bear
necessary markings.
c) The PIM shall meet NEMA TS2-2003 (or latest release)
Environmental and Electrical requirements.
26) Overhead Beaconing Capability
a) The APS button station shall have the option of driving an external
overhead (pedestrian signal or pole mounted) speaker with independent
audio amplifier and audio controls.
b) This may be used where:
(1) Crosswalks are longer than 70 feet (22m), unless they are divided by a median that has another accessible pedestrian signal with a
locator tone;
(2) Crosswalks that are skewed;
(3) Intersections with irregular geometry, such as more than four legs;
(4) Crosswalks where audible beaconing is requested by an individual with visual disabilities; or
(5) Other locations where a study indicates audible beaconing would
be beneficial.
c) The overhead beaconing is used to assist pedestrians with orientation
in the crossing area. Overhead beacons have been shown to improve
directional information and safety for visually impaired and sighted pedestrians. NCHRP Document 117A: Accessible Pedestrian Signals:
A Guide to Best Practices.
27) Capable of operating at, as a minimum, up to 1000 ft (AWG #12) cable run
from signal cabinet.
28) Pushbutton station and Central control unit shall be rated for the following temperature range:
a) Pushbutton station: -30°F to +155°F.
b) Central Control Unit: -30°F to +165°F
29) APS units shall be operationally compatible with TS1, TS2, 170 and 2070
controllers and cabinet assemblies, currently used by the City and any other
Texas government entities.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 53
TRAFFIC SIGNALS
Page 53 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
30) Unless specified otherwise in the plans, supply a central control unit (CCU)
for the pushbutton stations that resides in the Traffic Signal Controller
Cabinet.
a) Provide a CCU capable of controlling up to 4 pedestrian phases and 12
Pushbutton stations. b) Ens ure that all inputs and outputs on the CCU have Transient Voltage
Protection.
31) If plans specify that the APS will require no additional space or wiring in
the cabinet, provide one control unit per push button station capable of
mounting in the pedestrian signal housing.
32) If a special device or software is required to configure the APS operation,
provide a minimum of one device or copy of software per signal cabinet
along with any required connectors, unless required otherwise by the plans.
33) Provide any wiring harnesses, connectors, interface cables, terminal blocks,
etc. required for connecting the pushbutton station or CCU to the traffic signal controller assembly and making the Pushbutton stations operational.
5. Radar Detection Equipment and Cable
a. Radar presence detection
1) The product bid shall be the SmartSensor Matrix™ by Wavetronix, or approved equivalent approved by City Traffic Signal Engineering Manager
or Designee, and shall meet the following specifications.
2) General
a) Sensor Outputs
(1) Radar detector shall transmit real-time presence data from up to 10
lanes, depending on mounting location and lane widths. (2) The radar detector shall support a minimum of eight detection
zones.
(3) The radar detector shall support a minimum of eight detector
channel outputs and have user -selectable channel assignments.
(4) The radar detector shall use ’OR’ or ‘AND’ logic gates to map a single zone to multiple channel outputs, and shall have channel
output extend and delay functionality.
(5) The radar detector algorithms shall mitigate detections from
wrong-way or cross traffic.
(6) The radar detector system shall have fail-safe mode capabilities for
contact closure outputs if communication is lost. Contact closure
will occur on all programmed detector channels associated with the
interface module when the failsafe is triggered and will remain in
this state until communication is re-established between the
interface module and the radar vehicle sensor.
b) Detectable Area (1) The radar detector shall be able to detect and report presence in
lanes wit h boundaries as close as 6 feet from the base of the pole
on which the detector is mounted. The detector shall be able to
detect and report presence in lanes located within the 140 feet arc
from the base of the pole on which the RPD is mounted.
(2) The detector shall be able to detect and report presence for vehicles
within a 90 degree field of view.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 54
TRAFFIC SIGNALS
Page 54 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(3) The detector shall be able to detect and report presence in up to 10
lanes.
(4) The detector shall be able to detect and report presence in curved
lanes and areas with islands and medians.
c) System Hardware (1) Preassembled back plate
(a) Each detector shall have a traffic cabinet preassembled back
plate with the following:
• AC/DC power conversion
• Surge protection (Lightning and surge protection will be provided for power connections and communications
links to the radar RVDS meeting or exceeding EN
61000-4-5 class specifications.)
• Terminal blocks for cable landing
• Communication connection points (b) The preassembled back plate for the detector shall be a cabinet
side mount or rack mount.
(2) Contact Closure Input File Cards
(a) The detector shall use contact closure input file cards with 2 or
4 channel capabilities.
(b) The contact closure input file cards for the detector shall be
compatible with industry standard detector racks.
(3) Radar design
(a) Frequency Stability
• The circuitry shall be void of any manual tuning
elements that could lead to human error and degraded
performance over time.
• All transmit modulated signals shall be generated by
means of digital circuitry, such as a direct digital
synthesizer, that is referenced to a frequency source that
is at least 50 parts per million (ppm) stable over the specified temperature range, and ages less than 6 ppm
per year.
• Any upconversion of a digitally generated modulated
signal shall preserve the phase stability and frequency
stability inherent in the digitally generated signal.
• The detector shall not rely on temperature compensation
circuitry to maintain transmit frequency stability.
• The bandwidth of the transmit signal of the detector
shall not vary by more than 1% under all specified
operating conditions and over the expected life of the
detector.
(b) Antenna Design
• The detector antennas shall be designed on printed
circuit boards.
• The vertical beam width of the detector at the 6dB points
of the two-way pattern shall be 65 degrees or greater.
• The antennas shall cover a 90 degree horizontal field of
view.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 55
TRAFFIC SIGNALS
Page 55 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
• The sidelobes in the RPD two-way antenna pattern shall
be -40dB or less.
(c) The detector shall transmit a signal with a bandwidth of at least
245 MHz, which provides for a resolution of 2 feet.
(d) The detector shall provide at least 8 RF channels so that
multiple units can be mounted in the same vicinity without
causing interference between them.
(e) The detector shall have a self-test that is used to verify correct
hardware functionality.
(f) The detector shall have a diagnostics mode to verify correct system functionality.
(4) Physical Properties
(a) The detector shall not exceed 4.2 pounds in weight.
(b) The detector shall not exceed 13.2 in. by 10.6 in. by 3.3 in.
(33.5 cm x 26.9 cm x 8.4 cm) in its physical dimensions. (c) All external parts of the detector shall be ultraviolet-resistant,
corrosion-resistant, and protected from fungus growth and
moisture deterioration.
(d) Enclosure
• The detector shall be enclosed in a Lexan, Makrolon, or
other approved polycarbonate material.
• The enclosure shall be classified “f1” outdoor
weatherability in accordance with UL 746C.
• The detector shall be classified as watertight according
to the NEMA 250 Standard.
• The detector enclosure shall conform to test criteria set
forth in the NEMA 250 standard for type 4X enclosures.
• Test results shall be provided for each of the following
type 4X criteria: External Icing (NEMA 250 clause 5.6),
Hose -down (NEMA 250 clause 5.7), 4X Corrosion
Protection (NEMA 250 clause 5.10), Gasket (NEMA 250 clause 5.14).
• The detector shall be able to withstand a drop of up to 5
feet without compromising its functional and structural
integrity.
• The detector enclosure shall include a connector that meets the MIL-C-26482 specification.
• The MIL-C-26482 connector shall provide contacts for
all data and power connections.
(e) Power
• The detector shall consume less than 10 W.
• The detector shall operate with a DC input between 9
VDC and 28 VDC.
(f) Communications Ports
• The detector shall have two communication ports, and
both ports shall communicate independently and simultaneously.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 56
TRAFFIC SIGNALS
Page 56 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
• The detector shall support the upload of new firmware
into the detector’s non-volatile memory over either
communication port.
• The detector shall support the user configuration of the
following: Response delay and Push port.
• The communication ports shall support at least a 9600
bps baud rate.
b. Radar advanced detection
1) The product bid shall be the SmartSensor Advance™ by Wavetronix, or
approved equivalent approved by City Traffic Signal Engineering Manager
or Designee, and shall meet the following specifications .
2) General
a) All materials furnished, assembled, fabricated, or installed under this
Item will be new, corrosion resistant, and in strict accordance with the
details shown on the plans and in this Special Specification. b) The detector will be non-intrusive, easy to install, remotely accessible,
and provide multiple connectivity options for easy integration into
legacy systems .
(1) The detector will have a method for automatically calibrating the
detection device; this method will be executed in the detector’s internal processor. This auto-calibratio n method will automatically
determine detection thresholds.
c) Sensor Performance
(1) The detector will accurately and continuously detect Estimated
Time of Arrival (ETA), speed, and range data for vehicles, or
clusters of vehicles simultaneously moving within 100 feet to 500 feet from the sensor in the selected direction of travel.
(2) The detector will be mounted in a forward-fire position, looking
into either approaching or departing traffic for the selected
direction of travel.
(3) The detector will filter the ETA data, speed data, and range data based upon minimum and maximum constraints to produce alerts,
customizable for safe and efficient dilemma zone protection,
congestion management, and other operational goals.
(4) The detector will maintain accurate performance in all weather
conditions, including rain, freezing rain, snow, wind, dust, fog, and
changes in temperatures and light.
(5) The device will not rely on temperature compensation circuitry and
will be capable of continuous operation over and ambient
temperature range from -40° C to 75° C, and a relative humidity
range from five percent to 95 percent (non-condensing).
(6) Detector operation will continue in rain or snow up to 10 cm per hour, and the device will not experience degraded performance
when encased in 1/2 inch of ice.
(7) Speed data will be accurate for individual vehicle measurement
when there are no adjacent vehicles traveling in the same direction.
(a) Eighty-five percent of all measurements will be within 5 mph
of truth when vehicles are not changing speed.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 57
TRAFFIC SIGNALS
Page 57 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(b) Speed accuracy will be verified with radar gun, by video speed
trap using the frame rate as a time reference, or equivalent
method.
(8) Range data will be accurate for individual vehicle measurement
when there are no adjacent vehicles traveling in the s ame direction. (a) Eighty-five percent of all measurements will be within ten feet
of the distributed length of the vehicle when vehicles are not
changing speed. Range accuracy will be verified with: LIDAR
gun, by video using visual markers as a distance reference and
frame rate as a time reference, or equivalent method.
(9) ETA data will be accurate for individual vehicle measurements
when there are no adjacent vehicles traveling in the same direction.
(a) ETA is the estimated time of arrival as calculated by dividing
the vehicles range from the stop bar by the speed of the
vehicle. (b) ETA is calculated for purposes of safely and efficiently
protecting vehicles within the decision dilemma zone, which is
nominally defined to exist for motorists with an ETA between
2.5 and 5.5 seconds from the stop bar who are driving faster
than 35 mph when the light turns yellow.
(c) Eighty-five percent of all measurements will be within one
second of truth for all vehicles not changing speed within the
decision dilemma zone.
(d) ETA accuracy will be verified with: LIDAR gun, or by video
using visual markers as a distance reference and frame rate as a
time reference. d) Lightning surge protection that meets or exceeds the EN 61000-4-5
Class 4 specifications will be installed no farther th an 40 feet along the
detector cable from the detector unit. To ensure the continued
operation of the detector in the presence of electrical surges, all
connections to the detector will be protected, including power, RS-232, RS-485 communication lines and ground.
e) Communication
(1) The detector will provide two or more communication ports that
can be accessed simultaneously using any detector-supported
protocol.
(2) This will enable multiple operators to collect data from the detector at the same time without interrupting or interfering with each
other.
(3) The detector will provide RS-232 and RS-485 serial
communication ports; each communication port will support all of
the following baud rates: 9600, 19200, 38400, 57600 and 115200. (4) The RS -232 port will be full-duplex and will support true
RTS/CTS hardware handshaking for interfacing to various
communication devices.
f) Power
(1) The detector will consume less than 10 watts with a DC input
between 12 VDC and 28 VDC.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 58
TRAFFIC SIGNALS
Page 58 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(2) The equipment will be designed such that the failures of the
equipment will not cause the failure of any other unit of
equipment.
(3) Automatic recovery from power failure will be within 15 seconds
after resumption of power. g) Windows® and PocketPC® -based Software
(1) The detector will also include graphical user interface software that
displays all configured zones and provides visual representation of
all detected vehicle clusters. The detected range, speed, arrival
time, and identification number will be viewable on the visual
representation of all detected vehicle clusters. The graphical
interface will operate on Windows 98, Windows 2000, Windows
NT 4.0, Windows XP Pro and Windows PocketPCs equivalent to
the Dell Axim X50v. The software will automatically select the
correct baud rate. (2) The graphical user interface will also display all configured alerts
and provide visual representation of their actuation. The operator
will have the ability to configure alerts using minimum and
maximum constraints on the detected ETA, speed, and range of
vehicles.
(3) The operator will have the ability to save the configuration
information to a file, or reload the detector configuration from a
file, using the graphical user interface software. Using the
installation software, the operator will be able to easily change the
baud rate on the sensor by selecting baud rates from a drop-down
list, as well as add response delays for the communication ports. Additionally, the operator will have the ability to switch between
data pushing and data polling, and change the detector’s settings
for Flow Control from none to RTS/CTS and vice versa.
(4) The operator will be able to upload new firmware into the
detector’s non-volatile memory over any supported communication channel.
h) RF Design
(1) All microwave circuitry within the detector will be designed
utilizing active control that dynamically adjusts to compensate for
temperature and age variations in component performance. This
eliminates most opportunities for human error or age degradation in circuits that contribute to product performance. The circuitry
will be void of any manual tuning elements that could lead to
human error and degraded performance over time.
(2) All transmit modulated signals will be generated by means of
digital circuitry, such as a direct digital synthesizer, that is referenced to a frequency source that is at least 50 ppm stable over
the specified temperature range, and ages less than six ppm per
year. Any up-conversion of a digitally generated modulated signal
will preserve the phase stability and frequency stability inherent in
the digitally generated signal. These specifications ensure that
during operation the detector strictly conforms to FCC
requirements and that the radar signal quality is maintained for
precise algorithmic quality.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 59
TRAFFIC SIGNALS
Page 59 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(3) The detector antennae will be designed on printed circuit boards,
eliminating the need for RF connectors and cabling that result in
decreased reliability. Printed circuit antennae are less prone to
physical damage due to their extremely low mass.
(4) The antennae parameters will meet the following criterion to ensure quality performance:
(a) 3 dB Elevation Beam Width: > 65 degrees
(b) 3 dB Azimuth Beam Width: < 15 degrees
(c) Side Lobes: < -20 dB
i) Enclosure
(1) The detector will be enclosed in a Lexan polycarbonate, ultraviolet
resistant material and will be classified as watertight according to
the NEMA 250 Standard. The enclosure will be classified "f1"
outdoor weatherability in accordance with UL 746C.
(2) The detector will be able to withstand a drop of up to 5 feet without compromising its functional and structural integrity.
j) Input file cards
(1) The detector manufacturer will provide an optional input file card
compatible with 170, 2070, NEMA TS1 and NEMA TS2 input file
racks. The input file card will translate per vehicle data packets or
actuation packets from the detector into corresponding contact
closure outputs. Operators will be able to assign any contact
closure output channel to any configured alert. These settings will
be saved in non-volatile memory on the input file card for
complete recovery in case of power failure.
(2) The input file card will support Dual Loop (Speed Trap) emulation, as well as the following modes of operation:
(a) Actuation (true presence filtered by conditional alert
constraints output in real time with 2.5 ms resolution)
(b) Pulse (a single 125 ms output pulse for each vehicle)
(c) Presence (an output pulse corresponding to the duration of each vehicle cluster in the detection zone with a resolution of
2.5 ms)
(d) Single Loop Speed (duration of the pulse corresponds directly
to the speed of the vehicle, speed (mph) = 13.64/duration in
seconds)
(3) The input file card will receive data packets over an RS -485 bus at any of the following baud rates: 9600, 19200, 38400, 57600 and
115200. Also, the input file card will auto-baud and auto-detect a
detector over wired and wireless communication channels that
have a maximum latency of 500 ms.
(4) The input file card will comply with the NEMA TS2-1998 Traffic Controller Assemblie s with NTCIP Requirements, Section 2.8
specification. Documentation and results of the NEMA TS2-1998
test will be provided.
(5) The input file card will also provide failsafe operation, so that in
the event of failure of communication from the sensor, a constant
call will be placed on all contact closure channels.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 60
TRAFFIC SIGNALS
Page 60 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(6) The input file card will comply with the EN 61000-4-5 Class 4
lightning surge protection test specification. Documentation and
results of the EN 61000-4-5 Class 4 test will be provided.
k) FCC
(1) Each det ector will be Federal Communications Commission (FCC) certified under CFR 47, Part 15, section 15.245 as a field
disturbance sensor, or section 15.249 as an intentional radiator.
This certification will be displayed on an external label on each
device acc ording to the rules set out by the FCC.
(2) The detector will transmit in the 10.50 – 10.55 GHz or 24.00 –
24.25 GHZ frequency band and will meet the power transmission
requirements specified under sections 15.245 and 15.249 of CFR
47.
(3) The manufacturer will provide documentation proving compliance
to all FCC specifications. c. Radar Detection Cable
1) The cable end connector shall meet the MIL-C-26482 specification and
shall be designed to interface with the appropriate MIL-C-26482
connector.
2) The connector back shell shall be an environmentally sealed shell that
offers excellent immersion capability.
3) All conductors that interface with the connector shall be encased in a single
jacket, and the outer diameter (O.D.) of this jacket shall be within the back
shell’s cable O.D. range to ensure proper sealing.
4) The back shell shall have a strain relief with enough strength to support the
cable slack under extreme weather conditions. 5) The cable shall conform to the following specifications:
6) The RS-485 conductors shall be a twisted pair.
7) The RS-485 conductors shall have nominal capacitance conductor to
conductor of less than 71pF/Ft at 1 KHz.
8) The RS-485 conductors shall have nominal conductor DC resistance of less than 16.5 ohms/ (304.8 m) at 68°F (20°C).
9) The power conductors shall be one twisted pair with nominal conductor
DC resistance of less than 11.5 ohms/ (304.8 m) at 68°F (20°C).
10) Each wire bundle or the entire cable shall be shielded with an
aluminum/mylar shield with a drain wire.
11) The wire shall be a single continuous home-run cable with no splices allowed and terminated only in the junction box provided by the
manufacturer and in the traffic signal cabinet at the other end.
12) The cable O.D. shall not exceed 0.4 inches.
13) The cable length shall not exceed 2000 feet for the operational baud rate of
RS -485 communications (9.6 Kbps). 14) If 12 VDC is being supplied for the detector then the cable length shall not
exceed 90 feet.
15) If 24 VDC is being supplied for the detector then the cable length shall not
exceed 500 feet.
16) Both c ommunication and power conductors can be bundled together in the
same cable as long as the above-mentioned conditions are met.
6. Hybrid Vehicle Detection System and Cable
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 61
TRAFFIC SIGNALS
Page 61 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a. The product bid shall be the Iteris Vantage Vector Hybrid™ system, or
approved equivalent approved by City Traffic Signal Engineering Manager or
Designee, and shall meet the following specifications.
b. The multi-sensor system shall utilize two different sensors of different
technologies, video imaging and radar, to detect and track lic ensed and unlicensed vehicles at distances up to 600 feet.
c. The sensor system shall fuse vehicle information from the two sensors to
provide highly accurate and precise detection for special or advanced
applications .
d. The multi-sensor system shall use a primary detector rack mounted processor
to interface with the traffic control cabinet. The module shall process
information from both video imaging and radar sensors simultaneously in real-
time.
e. System configurations
1) The multi-sensor detection system (MSDS) s hall consist of up to two video cameras and radar units, detection processors (DP) capable of processing
from one to two intersection approaches, output extension modules, surge
suppressors, a setup tool and a pointing device.
2) Available system configurations
a) The MSDS will be deployed at locations where site conditions and
roadway geometry vary. The MSDS system may also be deployed at
locations where existing cabinets or equipment exist. Existing site
configurations will dictate the availability of cabinet space and MSDS
usage.
b) The proposed MSDS shall be available in various configurations to
allow maximum deployment flexibility. Each configuration shall have an identical user interface for system setup and configuration. The
communications protocol to each configuration shall be identical and
shall be hardware platform independent. The proposed MSDS shall
have multiple configurations available for deployment as described in
Table 1.
Table 1. MSDS Configuration
Description
No. of
Multi -Sensor
Inputs
No. Video Outputs Mounting Configuration Power Supply Requirements
Single -Channel
Rack Mounted 1 1
Rack Mount
(Type 170 or
NEMA TS -1,
TS-2 Racks)
12 or 24 VDC
Power From
Rack
Dual-Channel
Rack Mounted 2 1
Rack Mount
(Type 170 or
NEMA TS -1,
TS-2 Racks)
12 or 24 VDC
Power From
Rack
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 62
TRAFFIC SIGNALS
Page 62 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
f. System software
1) The system shall include software that detects vehicles in multiple lanes.
Video imaging detection zones shall be defined using only an on-board
video menu and a pointing device to place the zones on a video image. Up
to 24 video detection zones per camera view shall be available. Two additional trigger zones for the radar sensor shall be available and be
configurable by using the same system setup menu on the DP. A separate
computer shall not be required to program the detection zones. A portable
setup tool shall be available for sensor alignment and adjustment of
camera’s field of view and focus.
g. Materials
1) Multi-Sensor Detection System Hardware
a) The MSDS hardware shall consist of the following four elements:
(1) Video imaging camera sensor
(2) Radar sensor (3) Sensor data combiner
(4) Detection processor
b) The MSDS shall be made in the U.S.A. in compliance with FTA “Buy
America” regulations.
2) Video Imaging Camera Sensor
a) To accommodate deployment flexibility, the MSDS c amera sensor
shall be compatible will all DP platforms identified in Table 1. The
MSDS camera sensor shall be supplied by the MSDS manufacturer.
b) The advanced camera enclosure shall utilize Indium Tin Oxide (ITO)
technology for the heating element of the front glass. The transparent
coating shall not impact the visual acuity and shall be optically clear. c) Cable terminations at the data combiner for video and power shall not
require crimping or special tools.
d) The camera sensor shall allow the user to set the focus and field of
view via Wi-Fi connectivity.
e) The camera shall produce a useable video image of the bodies of vehicles under all roadway lighting conditions, regardless of time of
day. The minimum range of scene luminance over which the camera
shall p roduce a useable video image shall be the minimum range from
nighttime to daytime, but not less than the range 1.0 lux to 10,000 lux.
f) The camera electronics shall include automatic gain control (AGC) to
produce a satisfactory image at night. g) The imager luminance signal to noise ratio (S/N) shall be more than 50
dB with the automatic gain control (AGC) disabled.
h) The imager shall employ three dimensional dynamic noise reduction
(3D-DNR) to remove unwanted image noise.
i) The camera imager shall employ wide dynamic range (WDR) technology to compensate for wide dynamic outdoor lighting
conditions. The dynamic range shall be greater than 100 dB.
j) The camera shall be digital signal processor (DSP) based and shall use
a CCD sensing element and shall output color video with resolution of
not less than 550 TV lines.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 63
TRAFFIC SIGNALS
Page 63 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
k) The camera sensor shall include an electronic shutter control based
upon average scene luminance and shall be equipped with an auto-iris
lens that operates in tandem with the electronic shutter. The electr onic
shutter shall operate between the ranges of 1/1 to 1/10,000th second.
l) The camera sensor shall utilize automatic white balance. m) The camera sensor shall include a variable focal length lens with
variable focus that can be adjusted, without opening up the camera
housing, to suit the site geometry by means of a portable interface
device designed for that purpose and manufactured by the detection
system supplier.
n) The horizontal field of view shall be adjustable from 4.6 to 53.6
degrees. This camera configuration may be used for the majority of
detection approaches in order to minimize the setup time and spares
required by the user. The lens shall be a 12x zoom lens with a focal
length of 3.7mm to 44.0mm. o) The lens shall also have an auto-focus feature with a manual override
to facilitate ease of setup.
p) The camera shall incorporate the use of preset positioning that store
zoom and focus positioning information. The camera shall have the
capability to recall the previously stored preset upon application of
power.
q) The camera shall be housed in a weather -tight sealed enclosure
conforming to IP-67 specifications. The housing shall allow the camera
to be rotated to allow proper alignment between the camera and the
traveled road surface.
r) The camera enclosure shall be equipped with a sunshield. The sunshield shall include a provision for water diversion to prevent water
from flowing in the camera's field of view.
s) The camera enclosure shall be design so that the pan, tilt and rotation
of the camera assembly can be accomplished independently without
affecting the other settings. t) The camera enclosure shall include a proportionally controlled Indium
Tin Oxide heater design that maximizes heat transfer to the lens. The
output power of the heater shall vary with temperature, to assure
proper operation of the lens functions at low temperatures and prevent
moisture condensation on the optical faceplate of the enclosure.
u) The glass face on the front of the enclosure shall have an anti-reflective coating to minimize light and image reflections.
v) When mounted outdoors in the enclosure, the camera shall operate in a
temperature range from -34 °C to +74 °C and a humidity range from
0% RH to 100% RH. Measurement of satisfactory video shall be
based upon DP system operation. w) The camera sensor shall acquire its power from the sensor data
combiner.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 64
TRAFFIC SIGNALS
Page 64 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
x) Recommended camera placement height shall be 18-33 feet (or 6-10
meters) above the roadway, and over the traveled way on which
vehicles are to be detected. For optimum detection the camera should
be centered above the traveled roadway. The camera shall view
approaching vehicles at a distance not to exceed 350 feet for reliable detection (height to distance ratio of 10:100). Camera placement and
field of view (FOV) shall be unobstructed and as noted in the
installation documentation provided by the supplier.
y) The video signal shall be fully isolated from the camera enclosure and
power cabling
z) A weather -proof protective cover shall be provided to protect all
terminations at the camera.
3) Radar Sensor
a) The radar sensor shall operate in the 24 GHz frequency band and shall
operate on 1 of 7 available enumerated channels that is user selectable. b) The radar detection range shall be 600 feet minimum, +/- 5%.
c) The radar sensor shall be able to track up to 20 independent objects
simultaneously.
d) Object speed detection shall be within a range of 0 to 150 miles per
hour +/- 1.0 miles per hour.
e) The radar sensor shall be able to detect vehicles in 1 to 4 traffic lanes.
f) The radar sensor shall be housed in a weather -tight sealed enclosure
conforming to IP-67 specifications. The housing shall allow the radar
to be adjusted to allow proper alignment between the sensor and the
traveled road surface.
g) When mounted outdoors in the enclosure, the radar shall operate in a temperature range from -34 °C to +74 °C and a humidity range from
0% RH to 100% RH.
h) The radar sensor shall communicate with the sensor data combiner.
i) The radar sensor shall acquire its power from the sensor data combiner.
4) Multi-Sensor Assembly a) Both camer a and radar sensors shall be housed in an overall, single
enclosure assembly.
b) The overall size of the multi-sensor enclosure shall not exceed 14
inches x 15 inches x 17 inches.
c) The overall weight of the multi-sensor unit shall not exceed 11 pounds.
d) The effective projected area (EPA) shall not exceed 2.0 square feet. e) The maximum power consumption for the multi-sensor assembly shall
be less than 10 watts typical, 20 watts peak.
5) Sensor Data Combiner
a) A sensor data combiner that combines sensor information from both
video and radar sensors shall be employed. b) The sensor data combiner shall supply primary power to each sensor
unit.
c) The sensor data combiner shall facilitate digital communications
between the sensor data combiner and each of the sensor units.
d) The sensor data combiner shall get its primary power from an AC
power source using industry standard 3-conductor cabling.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 65
TRAFFIC SIGNALS
Page 65 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
e) The sensor data combiner shall communicate with the detection
processor using a single coax cable. Both video imaging and radar
data shall use the single coax cable.
f) The sensor data combiner shall also employ industry standard Wi-Fi
connectivity for remote sensor system setup using a mobile programming device such as a netbook or tablet computer. Video
camera and radar sensor shall be able to be configured independently.
g) The sensor data signal shall be fully isolated from the mechanical
enclosure and power cabling
h) Cable terminations at the sensor data combiner shall not require
crimping tools.
i) The sensor data combiner shall be housed in a weather -tight sealed
enclosure conforming to IP-67 specifications.
6) Detector Processor (DP)
a) Each sensor input shall accept RS170 (NTSC) or CCIR (PAL) signals from an external video source. The interface connector shall be BNC
type and shall be located on the front of the processing unit. The
sensor input shall have the capability to be terminated into 75-ohms or
high impedance (Hi-Z) using dip switches or software control from the
user menu. The sensor input shall also facilitate the data from the
radar sensor.
b) A LED indicator shall be provided to indicate the presence of the
sensor signal. The LED shall illuminate upon valid sensor
synchronization and turn off when the presence of a valid sensor signal
is removed.
c) One video output shall be provided. The video output shall be RS170 or CCIR compliant and shall pass through the input video signal.
d) For multi-channel video input configurations, a momentary push-
button shall be provided on the front panel to cycle through each input
video channel. In the absence of a valid sensor signal, the channel
shall be skipped and the next valid sensor signal shall be switched. The real time video output shall have the capability to show text and
graphical overlays to aid in system setup. The overlays shall display
real-time actuation of detection zones upon vehicle detection or
presence. Overlays shall be able to be turned off by the user. Control
of the overlays and sensor switching shall also be provided through the
serial communications port. The video output interface connector shall be positive locking BNC type. Friction type (e.g. RCA type)
connectors shall not be allowed.
e) A serial communications port shall be provided on the front panel. The
serial port shall compliant with EIA232 electrical interfaces an d shall
use a DB9 type connector mounted on the front panel of the DP. The serial communications interface shall allow the user to remotely
configure the system and/or to extract calculated vehicle/roadway
information. The interface protocol shall be doc umented or interface
software shall be provided. The interface protocol shall support multi-
drop or point-to-multipoint communications. Each MSDS shall have
the capability to be addressable. The DP shall support data rates of
1200 bps to 230,400 bps, inclusive.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 66
TRAFFIC SIGNALS
Page 66 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
f) Open collector (contact closure) outputs shall be provided. Four (4)
open collector outputs shall be provided for the single or dual channel
rack-mount configuration. Additionally, the DP shall allow the use of
extension modules to provide up to 24 open collector contact closures
per camera input. Each open collector output shall be capable of sinking 30 mA at 24 VDC. Open collector outputs will be used for
vehicle detection indicators as well as discrete outputs for alarm
conditions. The DP outputs shall be compatible with industry standard
detector racks assignments.
g) Logic inputs such as delay/extend or delay inhibit shall be supported
through the appropriate detector rack connector pin or front panel
connector in the case of the I/O module. For DPs and extension
modules, 4 inputs shall be supported via detector rack interface. The
I/O module shall accommodate eight (8) inputs through a 15-pin “D”
connector. h) Detection status LEDs shall be provided on the front panel. The LEDs
shall illuminate when a contact closure output occurs. Rack-mounted
detection processors shall have a minimum of four (4) LEDs. Rack-
mounted extension modules shall have two (2), four (4) or eight (8)
LEDs (depending upon extension module type) to indicate detection.
i) The front panel of the DP shall have detector test switches to allow the
user to manually place calls on each DP output channel. The test
switch shall be able to place either a constant call or a momentary call
depending on the position of the switch.
j) A USB mouse port shall be provided on the front panel of the rack
mount detection processing unit. The mouse port shall not require special mouse software drivers. The mouse port shall be used as part
of system setup and configuration. A mouse shall be provided with
each detection processor.
k) Extension modules shall be connected to the DP by an 8-wire twisted -
pair cable with modular RJ45 connectors. DP and EM communications shall be accommodated by methods using differential signals to reject
electrically coupled noise.
l) Extension modules (EM) shall be available to eliminate the need of
rewiring the detector rack, by enabling the user to plug an extension
module into the appropriate slot in the detector rack to provide
additional open collector outputs. The extension module shall be available in both 2 and 4 channel configurations. EM configurations
shall be programmable from the DP. A separate I/O module with 32
outputs through a 37-pin “D” connector on the front panel and 8 inputs
through a 15-pin “D” connector using an external wire harness for
expanded flexibility shall also be available. m) The DP and EM shall be specifically designed to mount in a standard
detector rack, using the edge connector to obtain power, provide
contact closure outputs and accept logic inputs (e.g. delay/extend). No
adapters shall be required to mount the DP or EM in a standard
detector rack. Detector rack rewiring shall not be required.
n) The DP shall utilize non -volatile memory technology to store on-board
firmware and operational data.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 67
TRAFFIC SIGNALS
Page 67 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
o) The DP shall enable the loading of modified or enhanced software
through the EIA232 or USB port (using a USB thumb drive) and
without modifying the DP hardware.
p) The DP and EM shall be powered by 12 or 24 volts DC. DP and EM
modules shall automatically compensate for either 12 or 24 VDC operation. DP power consumption shall not exceed 7.5 watts. The EM
power consumption shall not exceed 3 watts.
q) The DP shall operate satisfactorily in a temperature range from -34 °C
to +74 °C and a humidity range from 0%RH to 95%RH, non-
condensing as set forth in NEMA specifications.
r) An Edco CX-06M video surge suppresser shall be provided for each
sensor input. The surge suppresser shall be appropriately grounded to
the cabinet ground rod using 14 AWG minimum.
7) System Software
a) Detection zones shall be programmed via an on board menu displayed on a video monitor and a pointing device connected to the DP. The
menu shall facilitate placement of detection zones and setting of zone
parameters or to view system parameters. A separate computer shall
not be required for programming detection zones or to view system
operation.
b) The DP shall store up to three different detection zone patterns in non-
volatile memory. The DP can switch to any one of the three different
detection patterns within 1 second of user request via menu selection
with the pointing device. Each configuration shall be uniquely labeled
and able to be edited by the user for identification. The currently
active configuration indicator shall be displayed on the monitor. c) The DP shall detect vehicles in real time as they travel across each
detection zone.
d) The DP shall accept new detection patterns from an external computer
through the EIA232 port when the external computer uses the correct
communications protocol for downloading detection patterns. A Windows™-based software designed for local or remote connection
and providing video capture, real-time detection indication and
detection zone modification capability shall be provided with the
system.
e) The DP sys tem shall have the capability to automatically switch to any
one of the stored configurations based on the time of day which shall be programmable by the user.
f) The DP shall send its detection patterns to an external computer
through the EIA232 port when requested when the external computer
uses the appropriate communications protocol for uploading detection
patterns. g) The DP shall default to a safe condition, such as a constant call on each
active detection channel, in the event of unacceptable interference or
loss of the sensor signal.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 68
TRAFFIC SIGNALS
Page 68 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
h) The system shall be capable of automatically detecting a low -visibility
condition such as fog and respond by placing all effected detection
zones in a constant call mode. A user -selected alarm output shall be
active during the low -visibility condition that can be used to modify
the controller operation if connected to the appropriate controller input modifier(s). The system shall automatically revert to normal detection
mode when the low -visibility condition no longer exists.
i) Up to 24 detection zones per camera input shall be supported and each
detection zone can be sized to suit the site and the desired vehicle
detection region.
j) The DP shall support 2 independent trigger points for radar outputs for
dilemma zone applications.
k) The DP shall provide up to 24 open collector output channels per
sensor input using one or more extension modules.
l) A single detection zone shall be able to replace multiple inductive loops and the detection zones shall be OR'ed as the default or may be
AND'ed together to indicate vehicle presence on a single approach of
traffic movement.
m) Placement of detection zones shall be done by using only a pointing
device, and a graphical interface built into the DP and displayed on a
video monitor, to draw the detection zones on the video image from
each video camera. No separate computer shall be required to program
the detection zones.
n) When a vehicle is detected within a detection zone, a visual indication
of the detection shall activate on the video overlay display to confirm
the detection of the vehicle for the zone. o) Detection shall be at least 98% accurate in good weather conditions,
with slight degradation possible under adverse weather conditions (e.g.
rain, snow, or fog) which reduce visibility.
p) Detection accuracy is dependent upon site geometry, camera
placement, camera quality and detection zone location, and these accuracy levels do not include allowances for occlusion or poor video
due to camera location or quality.
q) The DP shall provide dynamic zone reconfiguration (DZR). DZR
enables normal operation of existing detection zones when one zone is
being added or modified during the setup process. The new zone
configuration shall not go into effect until the configuration is saved by the operator.
r) Detection zone setup shall not require site specific information such as
latitude and longitude to be entered into the system.
s) The DP shall process the video input from each camera at 30 frames
per second. Multiple camera processors shall process all video inputs simultaneously.
t) The DP shall output a constant call during the background learning
period of no more than 3 minutes.
u) Detection zone outputs shall be configurable to allow the selection of
presence, pulse, extend, and delay outputs. Timing parameters of
pulse, extend, and delay outputs shall be user definable between 0.1 to
25.0 seconds.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 69
TRAFFIC SIGNALS
Page 69 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
v) Up to six video detection zones per sensor input shall have the
capability to count the number of vehicles detected. The count value
shall be internally stored for later retrieval through the EIA232 port.
The zone shall also have the capability to calculate and store average
speed and lane occupancy at bin intervals of 10 seconds, 20 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes and 60 minutes. One radar
sensor zone shall also count vehicles, calculate, and store the average
speed and lane occupancy across the approach.
w) In addition to the count type zone, the DP shall be able to calculate
and/or acquire average speed and lane occupancy using both video and
radar s ensors. These values shall be stored in non-volatile memory for
later retrieval.
x) The DP shall have an “advance” zone type where detection outputs to
the traffic controller is compensated for angular occlusion and
distance. y) The DP shall employ color overlays on the video output.
z) The DP shall have the ability to show phase status (green, yellow, or
red) for up to 8 phases. These indications shall also be color coded.
aa) The user shall have the ability to enable or disable the display of the
phase information on the video output.
bb) The DP shall have the capability to change the characteristics of a
detection zone based on external inputs such as signal phase. Each
detection zone shall be able to switch from one zone type (i.e.
presence, extension, pulse, etc.) to another zone type based on the
signal state. For example, a zone may be a “count” zone when the
phase is green but change to a “presence” zone type when the phase is not green.
cc) Another application would be zone type of “extension” when the signal
phase is green and then “delay” when red.
dd) For alpha numeric user inputs, the DP shall utilize a virtual keyboard
on the video overlay system to ease user input. The virtual keyboard shall use the standard QWERTY keyboard layout.
ee) The DP shall aid the user in drawing additional detection zones by
automatically drawing and placing zones at appropriate locations with
only a single click of the mouse. The additional zone shall utilize
geometric extrapolation of the parent zone when creating the child
zone. The process shall also automatically accommodate lane marking angles and zone overlaps.
ff) When the user wishes to modify the location of a zone, the DP shall
allow the user move a single zone, multiple zones or all zones
simultaneously.
gg) When the user wishes to modify the geometric shape of the zone, the DP shall allow the user to change the shape by moving the zone corner
or zone sides.
hh) On screen zone identifiers shall be modifiable by the user. The user
shall be allowed to select channel output assignments, zone type, input
status, zone labels or zone numbers to be the identifier.
ii) For multiple camera input DPs, the user shall have the ability to enable
automatic video output switching. The dwell time for each sensor
input shall be user programmable.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 70
TRAFFIC SIGNALS
Page 70 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
jj) For radar sens or zones, the output can be triggered by presence of a
vehicle only or by presence of a vehicle above a user-defined speed
threshold.
7. Emergency Vehicle Preemption Equipment and Cable
a. The product bid shall be the Opticom™ system by Global Traffic
Technologies, or approved equivalent approved by City Traffic Signal
Engineering Manager or Designee, and shall meet the following specifications.
b. Provide new, corrosion resistant materials.
c. Emergency Preemption Phase Selector
1) Shall be a plug-in two channel, dual priority, encoded signal device.
2) Shall have the capability to be installed directly into the input file of Type
170 traffic controllers equipped with priority phase selection software.
3) Shall recognize and discriminate among three distinct emitter frequency
rates via Emergency Preemption Detectors: Command Priority, Advantage Priority and probe vehicles.
4) When Emergency Preemption Detector signals are recognized as a valid
call, the Emergency Preemption Phase Selector shall cause the signal
controller to advance to and/or hold the desired traffic signal display. This
is accomplished by utilizing Emergency Preemption Phase Selector circuitry in conjunction with normal internal controller functions .
5) The Emergency Preemption Phase Selector shall be capable of ass igning
priority traffic movement to one of two channels on a first come, first serve
basis. Each channel shall be connected to select a particular traffic
movement from those normally available within the controller.
6) Once a call is recognized, "commit to green" circuitry in the Emergency Preemption Phase Selector shall function so that the desired green
indication will be obtained even if optical communication is lost. After
serving a priority traffic demand, the Emergency Preemption Phase
Selector shall r elease the controller to follow normal sequence operation.
7) The phase selector shall not change the timing of the following intervals for any normal controller phase: minimum green, walk, pedestrian
clearance, yellow change, or red clearance.
8) Emergency Preemption Phase Selector shall also have the following
features: two auxiliary detectors per channel, compatible with encoded
signal and non-encoded emitters, computer-based interface (RS232
communications front port, and rear backplane, customizable ID code
validation), crystal controlled circuitry, optically isolated outputs, front
panel switches and diagnostic indicators for testing, and multi-function test
switch.
9) Phase selector shall be powered from AC mains and shall provide 24-volt
DC output for its ass ociated detectors. 10) Emergency Preemption Phase Selector shall utilize solid state and relay
circuitry to interface between the Emergency Preemption Detector and the
traffic signal controller .
11) Emergency Preemption Phase Selector shall supply power to and rec eive
electrical signals from the Emergency Preemption Detector .
12) Emergency Preemption Phase Selector shall be tested to NEMA electrical
test specifications .
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 71
TRAFFIC SIGNALS
Page 71 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
13) Emergency Preemption Phase Selector shall operate at a voltage range of
89 to 135 VAC +10% and 60Hz + 3Hz .
14) Provide equipment that is not affected by the transient voltages, surges and
sags normally experienced on commercial power lines. It is the
Contractor's responsibility to check the local power service to determine if any special design is needed for the equipment. Any extra cost, if required,
is subsidiary to this Item.
15) Install appropriate surge protectors in the cabinet for the Emergency
Preemption Phase Selector and Emergency Preemption Detector.
16) Provide equipment that meets the requirements of Sec . 2.1.6, “Transients,
Power Service” of the NEMA Standard TS2-1992, and/or the latest
revision .
17) Provide all wiring to the requirements of the NEC. Cut all wires to proper
length. Provide cable slacks to facilitate removal and replacement of
assemblies, panels, and modules. Do not double back any wires to take up slack. Neatly lace wires into cable with nylon lacing or plastic straps.
Secure cables with clamps .
18) Provide diodes or other protective devices across the coils of all DC relays,
solenoids, and holding coils for transient suppression.
19) Furnish equipment with readily accessible, manually re-settable or
replaceable circuit protection devices (such as circuit breakers or fuses) for
equipment and power source protection.
20) Design the equipment such that the failures of the equipment shall not
cause the failure of any other unit of equipment.
21) Equipment furnished shall be modular in design to allow major portions to
be readily replaced in the field. 22) Emergency Preemption Phase Selector shall have mechanically key
modules of unlike functions to prevent insertion into the wrong socket or
connector.
23) Clearly identify all modules and assemblies with name, model number,
serial number, and any other pertinent information required to facilitate equipment maintenance.
24) A c ard rack shall be supplied with every Emergency Preemption Phase
Selector .
a) Shall be a metallic enclosure with a dedicated card slot for one phase
selector with either two or four channel units .
b) The front panel of the card rack shall include a terminal strip for connecting the detectors, as well as a 9-pin circular connector and
harness to connect the phase selector’s inputs and outputs.
c) T he card rack shall be subsidiary to the Emergency Preemption Phase
Selector.
d. Emergency Preemption Detector 1) Furnish Emergency Preemption Detector that shall seamlessly operate with
the vehicle emitters used in the project area.
2) Detector s hall transform the optical energy detected from an approaching,
vehicle mounted emitter to an electrical signal. The electrical signal s hall
be transmitted along an Emergency Preemption Detector Cable to the
Emergency Preemption Phase Selector for processing.
3) Detectors shall permit a direct, unobstructed line-of-sight to vehicle
approaches.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 72
TRAFFIC SIGNALS
Page 72 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
4) Detector shall have a cone of detection of not more than 13 degrees. The
Emergency Preemption Detector and/or Emergency Preemption Phase
Selector shall not sense a pre-emption signal from an emitter outside this
cone.
5) Detector shall have solid state circuitry and advanced electrical transient immunity.
6) Detectors shall have a range of 200 feet and is adjustable up to 2,500 feet.
7) Detector shall operate at an electrical voltage of 24 to 28 VDC, 50 MA
minimum.
8) Detectors shall operate at a temperature range of -30 degrees F to 165
degrees F.
9) Detector shall include mounting hardware, as specified, for mast arm
mounting, span wire mounting, pole-side mounting, mounting on top of a
signal head, or mounting on top of a pipe or pedestal.
10) Detector shall have an adjustable turret configuration to accommodate skewed approaches.
11) Detector housing shall be of light weight, durable, high-impact
polycarbonate material having stainless steel and brass fittings.
12) Detector shall operate at a humidity of 5% to 95% relative.
e. Emergency Preemption Detector Cable
1) Shall be Model 138 Opticom™ cable, or approved equivalent, and shall be
compatible with all other equipment used in this specification.
2) Cable s hall be individually tinned copper strand three-conductor cable with
yellow, orange, and blue conductor wires. It shall also have a bare shield
drain wire .
3) Cable shall be AWG #20 (7x28), stranded with conductor insulation of 600 volt, 75°C (167°F).
4) Cable shall have a DC resistance not to exceed 11.0 ohms per 1000 ft.
5) The capacitance from one conductor to other 2 conductors and shield shall
not exceed 48 pf./ft.
6) Cable jacket shall be rated for 600 volts, 80 degrees C (176 degrees F), and minimum average wall thickness of 0.045 in.
7) Finished O.D. of 0.3 in. maximum.
8. Battery back -up (BBU) S ystem for Signal Cabinets
a. The product bid shall be the Alpha FXM 2000 model, or approved equivalent
approved by Traffic Signal Engineering Manager or Designee for external
battery backup system.
b. The internal battery backup system shall be Zinc 5, or approved equivalent
approved by City Traffic Signal Engineering Manager or Designee.
c. Shall meet the following specifications.
d. Functionality 1) Standby Mode
a) The BBU shall be provided with a standby mode.
b) The utility AC power shall be passed directly to the output.
c) The system will transfer to Backup mode at user defined, low and high
cutoff voltage level transfer points that are adjustable between 90 and
135 VAC.
d) The BBU shall automatically apply a 5VAC difference for the return
transfer points.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 73
TRAFFIC SIGNALS
Page 73 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
e) When the BBU is in Standby mode (Buck/Boost Disabled), the BBU
shall bypass the utility line power whenever the utility line voltage is
outside the transfer set points (±2 VAC).
2) Low Restore
a) In cases of low or absent utility line voltage, when the utility line voltage has been restored at or above 5 VAC ±2 VAC of the low
transfer set point for more than 20 seconds, the BBU shall transfer
from Backup Mode to Utility Line Mode.
3) High Restore
a) In cases of high utility line voltage, when the utility line voltage has
been restored at or above 5 VAC ±2 VAC of the high transfer set point
for more than 20 seconds, the BBU shall transfer from Backup Mode
to Utility Line Mode.
4) Buck/Boost Line – Interactive Mode
a) The BBU shall include Buck/Boost Functionality. b) The Buck/Boost mode shall have a minimum range of 90-150 VAC.
c) There shall not be any user definable transfer set points for the buck
boost mode.
d) Whenever Buck/Boost mode is selected, the output of the system shall
be regulated between 100-130VAC.
e) When the output of the system can no longer be maintained with this
range, the BBU shall transfer to Backup Mode.
5) Line Qualify Time
a) The BBU shall have a user definable line qualify time.
b) The user shall be able to select a minimum of three (3) possible
settings. c) The minimum setting shall be 3, 20, and 30 seconds.
d) The default line qualify time shall be 30 seconds.
6) Battery Charger
a) The BBU shall have an integral charger.
b) The charger shall be a 3-step charger using bulk, absorption and float charging techniques, appropriate for the battery type.
c) The integral 3-Step Charger shall use temperature compensation.
d) The charging system shall compensate over a range of 2.5-4.0mV/°C
per cell.
e) A temperature probe which plugs into the front panel of the BBU shall
be used to monitor the internal temperature of the batteries. f) The Temperature sensor shall be of sufficient length to properly reach
the center battery and yet not too long to cause an inaccurate reading.
g) The batteries shall not be recharged whenever the battery temperature
exceeds 50°C.
h) The recharge time for the batteries from “protective low -cutoff” to 80 percent or more of full charge capacity shall not exceed 12 hours.
e. Operation
1) The BBU system shall provide the following operational modes when
operating on battery power: full operation of all traffic signal devices, flash
operation, and combination of full and flash operation.
2) The BBU shall provide a minimum of 2.0 hours of full time operation and
3.0 of flash operation for a traffic signal utilizing LED only vehicle and
pedestrian indications.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 74
TRAFFIC SIGNALS
Page 74 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
3) The BBU shall be compatible with all City cabinet and controller types ;
and all cabinet components for full time operation.
4) The BBU shall provide a minimum of 1500W/1800VA@25°C active
output capacity with 85 percent minimum inverter efficiency.
5) When operating in backup mode, the BBU output shall be 120VAC±5VAC, pure sine wave output, ≤3%THD, 60Hz ± 0.05 Hz.
6) The BBU DC system voltage shall be 48VDC.
7) The maximum transfer time allowed, from disruption of normal utility line
voltage to stabilized inverter line voltage from batteries, shall be 40
milliseconds (ms). The same maximum allowable time shall also apply
when switching from the inverter line voltage to utility-line voltage.
Transfers to and from battery operation shall not interfere with the
operation of the other equipment in the intersection.
8) The BBU and all components shall operate without performance
degradation over a temperature range of -37°C to +74°C. Additionally, all components and parts used shall, at the minimum, be rated for this
temperature range.
9) In the event the AC service feeding the BBU is severed, or there is a utility
blackout, the AV voltage measured at the AC inputs to the BBU (line to
neutral) shall be less than 1 VAC.
10) The BBU shall have lightning surge protection compliant with IEEE/ANSI
C.62.41 and must be able to withstand 2000 volt surges applied 50 times
across line and neutral. These surges shall not cause the BBU to transfer to
Backup mode.
11) The AC input and output shall be panel mounted plug/receptacles that
allow no possibility of accidental exposure to dangerous voltages. The AC Input shall be a male receptacle and the AC Output shall be a female
receptacle. The receptacles shall utilize some form of locking mechanism
or hold down clamps that prevent accidental disconnects.
12) The DC connection shall be a recessed one or two pieces Anderson Style
receptacle. 13) The Power Transfer relay control and the battery temperature sense inputs
shall be heavy duty panel-mounted style connectors.
14) All connections shall provide mechanically and electrically secure
connections without the use of a screwdriver. The only exception is the
Relay Terminal Block.
15) The BBU must be able to shut down in order to protect against internal damage in the event of an overload at the output.
16) The BBU shall provide a time-of-day schedule. The time-of -day schedule
shall allow the user to schedule operational modes.
17) The BBU shall automatically change operational modes based on the time-
of -day schedule. 18) The BBU shall not switch from Flash Operation to Full Operation mode
when the remaining battery capacity is ≤40 percent.
19) The BBU shall prevent a malfunction feedback to the cabinet or from
feeding back to the utility service. In the event of BBU failure
(inverter/charger or battery) or complete battery discharge, the power
transfer relay shall revert to Normally Closed (de-energized) state where
utility line power is connected to the cabinet.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 75
TRAFFIC SIGNALS
Page 75 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
20) The BBU shall initiate an automatic shutdown when battery output reaches
42DVC.
21) The BBU shall be equipped with an integral system to prevent the battery
from destructive discharge or overcharge.
f. Power Transfer Switch 1) Rating
a) The BBU shall include a Power Transfer Switch rated at 120VAC/50
amps minimum.
2) Manual Bypass Switch
a) The Power Transfer Switch shall include a manual bypass switch.
Placing the manual bypass switch in “Bypass” mode shall cut AC
power to the Inverter/charger and route it directly to the traffic signal
cabinet.
b) In this condition, power to the inverter is disconnected, and battery
power from the inverter is disconnected. c) The inverter can then be powered off without affecting normal
intersection operation.
d) With the inverter turned off, the batteries can be safely disconnected
from the inverter.
3) Indicator light
a) The Power Transfer Switch shall include a bypass indicator light that
automatically illuminates when the Manual bypass switch is in Bypass
position.
4) Status Relay
a) The Power Transfer Switch shall include a bypass status relay with
normally open, dry contacts that automatically close when the Manual bypass switch is in Bypass position.
5) Power Transfer Relay
a) The Power Transfer Switch shall include a 50 Amp power transfer
relay controlled by the inverter to cause the Power Transfer Switch to
switch between AC power from the utility and battery power from the inverter.
6) Integrated Switch
a) The manual bypass switch and the power transfer relay shall be
integrated together within the Power Transfer Switch allowing the
manual bypass switch to be rated at 15 Amp and to be integrated with
the bypass indicator light and bypass status relay. 7) Terminal Blocks
a) The Power Transfer Switch shall have terminal blocks capable of
accepting #6 AWG wiring with #6 AWG internal to the Power
Transfer Switch as required for 50 Amp operation.
g. Displays, Controls, Diagnostics and Maintenance 1) The BBS inverter/charger unit shall include a backlit LCD display for
viewing all status and configuration information. The screen shall be
easily viewable in both bright sunlight and in darkness.
2) Screen size
a) The screen shall be large enough to display the following information:
(1) Operating mode (standby, buck/boost)
(2) Utility input voltage
(3) BBU output voltage
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 76
TRAFFIC SIGNALS
Page 76 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(4) Charger status
(5) Percent battery charge
(6) BBU status (standby, backup, buck, boost)
(7) Any alarms and faults
3) The BBU inverter/charger unit shall include a keypad for configuring system parameters and navigating system information.
4) Communications
a) The BBU shall be equipped with an industry standard RS-232 serial
connection for user configuration and management.
b) The serial port shall be an EIA-232 (DB9-Female) connector.
c) The BBU shall have an Ethernet communication interface for user
configuration and management. The Ethernet Port shall be an RJ -45,
EIA 568B Pin Out Connector.
d) The BBU shall be include remote monitoring & alarms transmission
capabilities through the Ethernet RJ45 IP Addressable Port, using SNMP protocol. Other means of communication will be considered.
e) All BBU configuration and System menus shall be accessible and
programmable from the RS-232 and Ethernet Port.
f) The BBU shall support TCP and UDP over IP protocol
communications.
g) The BBU shall support FTP, Telnet, and HTTP.
h) The BBU shall be SNMP compliant.
5) Web-based interface
a) The BBU shall be provided with a web-based-interface for user
configuration and management through a web browser.
b) The BBU shall allow the user to do the following through the web browser:
(1) View logs
(2) Change modes of operation
(3) Configure email alarms
(4) Adjust line qualify time (5) Program relay contacts
(6) Configure network parameters
6) Status LEDs
a) The BBU shall have discrete status LED indications on the front of the
inverter/charger.
(1) Green output LED (a) This LED will be ON any time that the output of the BBU is
modified, either by backup Mode or by Buck//Boost Modes.
(2) Red fault LED
(a) This LED will be ON any time that there are any faults in the
system. (3) Yellow Alarm LED
(a) The LED will be ON any time that there are any alarms in the
system.
(4) Event log
(a) The BBU shall maintain an event log containing a minimum of
200 of the most recent events recorded by the BBU. At a
minimum, the event log shall record the following: date/time
stamp, current operating mode, what the event was.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 77
TRAFFIC SIGNALS
Page 77 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
(b) The Event log shall be viewable through the LCD display,
EIA-232 port, and the Ethernet Interfaces.
(5) Counters
(a) The BBU shall keep track of the following: the number of
times that the unit was in backup, buck, and boost modes. h. Programmable Relay Contacts
1) The BBU shall provide the user six (6) programmable dry relay contacts.
As a minimum, the programmable options shall be On Battery, Low
Battery, Timer, Alarm, Fault, and Off.
2) Relay Contact Terminals
a) The relay contacts shall be made available on the front panel of the
BBS via an 18-position, screw hold-down, printed circuit board
mounted terminal block.
3) Contacts
a) Each relay shall have their own common and their own set of normally open (NO) and normally closed (NC) terminals. The terminals for
each relay shall be oriented as NO-C-NC on the terminal block.
4) Labeling
a) The contacts on the terminal block shall be labeled 1-18, left to right.
Additionally, each set of contact shall be labeled with the NO-C-NC
designation, as well as C1…C6 from left to right. All additional
contacts on the terminal block shall be labeled as “spare”.
5) Rating
a) The relay contacts shall be rated at a minimum of 1 amp @125 VAC.
6) Display
a) When a relay is energized, it shall be displayed on the LCD screen. 7) On Battery Relay Contact
a) The dry relay contacts that are configured for “on battery” shall only
energize when the Inverter is operating in Backup Mode.
8) Time Relay Contacts
a) The BBU shall include a timer that will energize the “timer” configured dry relay contact after the user configured time has elapsed.
b) The timer is started when the BBU enters Backup Mode.
c) The user can configure the timer from 0 – 480 minutes in 15 minute
increments.
9) Low Battery Relay Contact
a) The BBU shall have an adjustable low battery relay setting. b) This setting shall be adjustable so that the user can set the point at
w hich the low battery relay contact is energized.
i. Batteries
1) Provide batteries from the same manufacturer/vendor of the BBU system.
2) Individual batteries shall be 12V. 3) Batteries shall be comprised of extreme temperature, float cycle, GEL
VRLA (Valve Regulated Lead Acid).
4) Battery amp-hour rating shall be 105 amp-hour maximum.
5) Batteries shall be easily replaced and commercially available off the shelf.
6) Battery string
a) Batteries used for the BBU shall consist of a 4 battery string with a
cumulative minimu m rated capacity of 210 amp-hours
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 78
TRAFFIC SIGNALS
Page 78 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
7) Batteries shall be sized and rated to operate a 700W load for 4 hours
(normal operation) followed by a 300W load for 2 hours (flash operation)
for a total of 6 hours.
8) Operating temperature
a) The battery system shall consist of one or more strings of extreme temperature; float cycle GEL VRLA (Valve Regulated Lead Acid)
batteries.
b) Batteries shall be certified to operate at extreme temperatures from –
40°C to +74°C
9) Construction
a) Battery construction shall include heavy-duty, inter -cell connections
for low -impedance between cells, and heavy-duty plates to withstand
shock and vibration.
10) Top cover
a) The top cover shall use tongue and groove construction and shall be epoxied or heat-sealed to the battery case for maximum strength and
durability.
11) Ability to function
a) The battery shall function if laid on its side without leakage of
chemicals and be so designed.
b) An integral lifting handle should be provided on the batteries for ease
of removal/installation.
12) Interconnect wiring
a) All batteries shall be provided with the appropriate interconnect wiring
and corrosion-resistant mounting trays and/or brackets appropriate for
the cabinet into which they will be installed. j. System Housing
1) EIA Standard
a) The internal cabinet shall come with installed EIA rails.
b) All references made to EIA rail or EIA 19” rack shall conform to
Electronic Industrial Standards EIA-310-B, Racks, Panels, and associated equipment with 10-32 “Universal Spacing” threaded holes.
c) The BBU shall be installed in an external cabinet adjacent to or
connected to the Traffic Controller cabinet
2) Inverter/Charger Mounting
a) The Inverter/Charger Unit shall be shelf or rack mounted on a standard
EIA19” rack. 3) Power Transfer Switch Mounting
a) The Power Transfer switch shall be mounted on EIA Rail.
4) Interconnect wiring
a) All interconnect wiring shall be provided and shall be UL Style 1015
CSA TEW. 5) BBU replacement
a) The BBU equipment and batteries shall be easily replaced and shall not
require and special tools for installation.
6) The BBU inverter and batteries shall be hot swappable. There shall be no
disruption to the Traffic Signal when removing the inverter or batteries for
maintenance.
7) All inverter and battery connections shall be of the quick disconnect type
for ease of maintenance.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 79
TRAFFIC SIGNALS
Page 79 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
8) All necessary installation hardware (bolts, fasteners, washers, shelf angles,
racks, etc.) shall be included.
9) Cabinet shall have a cabinet white LED light that is wired to turn on when
the cabinet door is open.
10) The external cabinet shall be capable of housing batteries, inverter/charger unit, power transfer switch, control panels, wiring, wiring harnesses, and
all other ancillary equipment.
11) Cabinet Types
a) TYPE 1: Pole mounted external cabinet (for 336 type cabinet
locations)
b) TYPE 2: Sid e mounted external cabinet - Side mounted (attached to
the side of the model 332, 336, 350i, 352i, or 357i Cabinets )
c) TYPE 3: Base mounted external cabinet - Freestanding (for all type
cabinet locations). The base mounted external cabinet shall have a
minimum 8” riser for easy cable entrance. 12) All external cabinets shall be NEMA 3R rated.
13) The external cabinet shall be ventilated through the use of louvered vents,
filter, and one thermostatically controlled fan.
a) The External fan cabinet shall be AC or DC operated from the same
line output of the Power Transfer Switch that supplies power to the
traffic controller cabinet.
b) A 2 -postion terminal block shall be provided on the fan panel
14) The external cabinet shall come provided with all bolts washers, nuts,
cabinet-cabinet coupler fitting, shelves, wiring, and all other hardware
necessary for mounting and connecting the external cabinet.
k. Documentation 1) Cabinet wiring diagrams and equipment manuals must be provided for
each cabinet.
2) Detailed directions/instructions for installation, programming and
maintenance for each BBU unit must be included.
9. Multi -conductor cable
a. All cable shall be multi-conductor capable of operating at 600 volts maximum,
and suitable for use at conductor temperatures not exceeding 75 degrees C (167
degrees F).
b. Multi-conductor cable shall be either stranded IMSA 20-1, #14 AWG, stranded
copper wire.
c. The copper wire (before insulating) shall meet the requirements of the latest
American Society for Testing and Materials (ASTM) standards for uncoated wire.
d. Ensure fillers are non-metallic, moisture resistant, non -wicking material.
e. Supply cables that clearly show the name of the manufacturer and the IMSA
specification number applied at approximate 2 foot intervals to the outer surface of the jacket by indent printing.
10. Insulated electrical cable
a. Power lead-in cable shall be stranded RHW copper wire and suitable for A/C electric service.
b. The cable shall be capable of operating at 600 volts maximum and suitable for use
at conductor temperatures not exceeding 167 degrees Fahrenheit (75 degrees
Celsius ).
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 80
TRAFFIC SIGNALS
Page 80 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c. Material and construction shall be in accordance with the applicable requirements
of IMSA and NEC standards.
d. Conductors shall be stranded, anneal coated copper.
e. Copper wire before insulating or stranding, s hall meet the requirements of the
latest edition of ASTM B-033 (for coated wire). f. Stranding shall be class B, in accordance with the latest edition of ASTM B-8.
g. Insulation shall be THHN and comply with Federal Specification A-A-59544 and
all applicable AS TM standards.
11. Grounding conductor
a. The grounding conductor shall be a #8 AWG solid copper wire.
b. The conductor shall be bonded to all ground rods.
12. Ground rod
a. Ground rod electrodes shall be copper-bonded steel being at least 5/8 inch in diameter.
b. All ground rods shall be a minimum of 8 feet.
c. All ground rods shall be a minimum of 6 feet in ground.
13. Ground Boxes a. All boxes shall meet all test requirements of the latest SCTE 77 “Specification
of Underground Enclosure Integrity” for Tier 22 applications.
b. Bottom edge of box or extension shall be footed with a minimum 1 ¼” flange.
c. Cover lift eye shall be molded with cover.
d. Cover lettering shall be 1” incised letters reading “Danger High Voltage Traffic
Signal.”
e. Cover shall include the City of Fort Worth logo in upper left-hand corner.
f. Cover must be secured with “Penta Head”, stainless steel, self -cleaning bolts
and nuts.
g. Provide security bolts if indicated in the Drawings. h. The top surface of the ground box cover shall have a minimum co-efficient of
friction of 0.5.
i. Boxes shall be stackable for extra height.
j. Boxes shall be manufactured from Reinforced Polymer Concrete (RPM)
composed of borosilicate glass fiber, a catalyzed polyester resin and an aggregate.
Side walls may be reinforced polymer.
k. The size and dimensions of the required ground boxes shall be shown in
standard detail 34 41 10 – D601.
14. Traffic Signal Structures
a. Design 1) Structures shall be designed in accordance with 1994 AASHTO “Standard
Specifications for Structural Supports for Highway Signs, Luminaires, and
Traffic Signals” for 80 MPH wind zone.
2) Refer to the City’s Standard or Decorative Traffic Signal standard detail
sheets for additional details. b. Markings
1) All pole shafts and mast arms for this project shall be marked with the
identification numbers from the drawings to facilitate assembly of these
items in the field.
2) For Projects with multiple intersections, the pole shafts and mast arms shall
be identified by intersection.
c. Vibration dampers
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 81
TRAFFIC SIGNALS
Page 81 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) Steel mast arms ranging above 28 feet in length shall be provided with
aluminum vibration dampers.
d. Structure Finish
1) Standard
a) The traffic signal poles and mast arms shall be galvanized in accordance to ASTM A123. Each component must be completely
coated in a single dip. No double dipping will be allowed. All
miscellaneous hardware shall be galvanized per ASTM A153.
2) Decorative
a) As shown in the plans.
e. High strength galvanized steel bolts
1) The allowable working stresses for A325 bolts shall be given in the
AASHTO Streetscape Structure Specifications for Structural Joints using
ASTM A3250-N or A490-N bolts.
f. Powder Coating 1) After galvanizing, the steel and aluminum products shall be blasted to an
SSPC-SP7 commercial blast.
2) All galvanized parts shall be pre-baked to ensure all gasses are released
from the coating surface prior to powder coating.
3) Finish with 1 coat of UMC super TGIC thermosetting powder coating 3-5
mils (D.F.T.) and baked in accordance with powder manufacturer’s
recommendations.
4) Top coating is electrostatically applied and oven baked at 400 degrees
Fahrenheit and cured for a minimum of 10 minutes.
5) Top coat color shall be black (RAL 9017) unless otherwise selected by the
City. g. Terminal block
1) Terminal shall be Pelco 12 -Circuit terminal block assembly, or approved
equal. Rated at 85 AMP 600V
h. Mast arm pole shaft
1) Each traffic signal mast arm pole shall be fabricated from a 1 piece high strength steel sheet, and shall have no more than 2 longitudinal full length
high frequency resistance welded joints and no horizontal welded joints
except at the base of the pole.
2) Welds shall have a smooth and consistent external surface appearance.
3) All welds shall be performed by an American certified structural steel
welder. 4) Traffic signal poles shall have a uniform taper.
5) Poles shall have a minimum of 50,000 PSI yield strength.
6) Cold working the steel to attain the 50,000 PSI required yield strength is
not acceptable.
7) The certifications from the vendor on the steel must indicate a minimum of 50,000 PSI yield strength after fabrication.
i. Mast arm
1) Each traffic signal mast arm shall be constructed from a 1 piece high
strength, steel sheet with guaranteed minimum yield strength of 50,000
PSI.
2) Arms over 40 feet may be 2 piece but shall arrive at the Site and City yard
as welded 1 piece.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 82
TRAFFIC SIGNALS
Page 82 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
3) The certifications from the vendor on the steel must indicate a minimum of
50,000 PSI yield strength after fabrication.
4) Cold working the steel to attain the 50,000 PSI required yield strength is
not acceptable.
5) Mast arms shall have no more than 2 longitudinal full length high frequency resistance welded joints.
6) Welds shall have a smooth and consistent external surface appearance.
7) All mast arms shall have a uniform taper.
j. Luminaire Arm
1) Luminaire arms shall be fabricated in accordance with the Drawings.
k. Pedestal Structures
1) Pedestal structures for mounting pedestrian signals or median-mount traffic
signals shall be furnished with a transformer base, pole cap, and all
necessary hardware for proper installation.
2) Height of pole shall be set in the Drawings, but shall not exceed 15 feet. l. All other hardware necessary for complete installation of traffic signal
structures, i.e., simplex plates, pole caps, transformer bases, anchor bolts, etc.
shall be hot dipped galvanized and conform to the design, dimension, and
strength requirements of said items as indicated on the Drawings.
m. All hardware shall be packed on a per pole basis.
15. Foundations
a. All foundations shall be built in accordance with Section 03 30 00 and the
requirements stated in the Drawings.
16. Hardware Signal Pole Paint
a. Primer coating shall be Kwal Paint #5810 G-Prime Premium Acrylic Universal
Primer or approved equivalent. This is a 100 percent acrylic primer for all
types of surfaces, including galvanized finishes.
b. Finish coating
1) The flat finish coat shall be Kwal pain t #6300 Accupro 100 percent Acrylic Exterior Flat Finish or approved equivalent. This is a 100 percent acrylic
finish that is durable and chalk resistant.
2) The semi-gloss finish coat shall be Kwal paint #3910 Accupro 100 percent
Acrylic Exterior Semi-Gloss Finish or approved equivalent. This is a 100
percent acrylic finish that is durable and chalk resistant.
c. Finish coat colors that are permissible within the City include:
1) Black: RAL #9017
2) Stockyards Oxide Red: RAL #3099
17. Signal Controller a. The traffic signal controller shall be Intelight ATC controller or approved
equivalent approved by City Traffic Signal Engineering Manager or Designee,
and shall meet the specifications as shown in Specification Attachment “B”.
b. Traffic signal controller shall be capable of running latest version of Intelight’s
Maxtime controller software and shall meet the following specifications as shown in Specification Attachment “C”.
18. Controller Cabinet Assembly
a. The traffic signal controller cabinet shall be McCain ATC type cabinet, or
approved equivalent approved by City Traffic Signal Engineering Manager or
Designee, and shall meet the specifications as shown in Specification
Attachment “A”.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 83
TRAFFIC SIGNALS
Page 83 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
19. Roadside Flash ing Beacon Assembly
a. Provide flasher control assembly in accordance with TxDOT DMS 11160,
“Flasher Control Assembly.”
b. Provide pedestal pole bases in accordance with TxDOT DMS -11140, “Pedestal
Pole Base.” c. When shown on Drawings, provide solar powered flasher controller assemblies
in accordance with TxDOT DMS 11150, “Solar Power Flasher Controller
Assembly.”
20. School Zone Flasher Assembly
a. Reverse flashing beacons shall be installed on the back side of traffic signal
mast arms at signalized intersections within the school zone.
b. Cabinet
1) The cabinet shall have a hinged panel for mounting the time switch, the
flasher and interface board, and the solar regulator. This hinged panel shall be in front of the battery compartment. The cabinet shall be designed to
mount a time switch with dimensions of 10 3/8"h x 4 7/8"w x 4"d with the
CPC connector.
2) The cabinet shall be fabricated of .125 inch sheet aluminum. The cabinet
shall be weatherproof using a neoprene gasket and shall be supplied with a standard #2 Corbin lock and key. The cabinet shall be of sufficient size to
house one (1) 100-amp hour battery. The outside dimensions of the
cabinet shall be a minimum of 17"h x 18.5"w x 14.75"d. The outside of
the cabinet shall be the natural aluminum finish.
3) The cabinet shall have a rain flap designed to cover the top of the cabinet
door. The rain flap shall extend the width of the cabinet and shall be 1.75” deep. The rain flap shall have a slight down angle and extend past the door
of the cabinet when the door is closed to allow rain water to drip past the
opening of the cabinet door.
4) In order to allow battery gasses to escape, the cabinet shall be equipped
with vents on the left and right side of the cabinet. The vents shall be covered on the inside of the cabinet with a screen to prevent insects and
other debris from entering the cabinet. The battery compartment shall have
1/2" foam on bottom, sides and back to properly insulate the battery. The
battery compartment shall be of sufficient size to house one (1) 100-amp
hour (Group 31) battery.
5) The flasher cabinet shall be supplied with appropriate hardware for
mounting to a 4 1/2" o. d. pedestal pole using Pelco SE-1100.
c. Flasher and Interface Circuit Board
1) The flasher cabinet assembly shall include a flasher and interface boar d. A
two (2) circuit 12VDC flasher shall be integral to the flasher and interface
board. The flasher shall be of all solid state construction and shall be rated at a minimum of 6.0 Amps per circuit. The flasher shall utilize zero-
voltage turn-on and turn-off of current thus eliminating electromagnetic
interference.
2) The flasher and interface board shall have two terminal blocks for
connecting the wiring of the cabinet. Barrier type terminal blocks shall be
used to terminate all wires. The terminal blocks shall terminate the
following functions:
1. Solar Panel + 1. Time switch relay common
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 84
TRAFFIC SIGNALS
Page 84 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2. Solar Panel - 2. Time Switch relay normally open
3. Battery + 3. DC + power to time switch
4. Battery - 4. DC – to time switch
5. Confirmation light +
6. Confirmation light - 7. Load-1 from the flasher
8. Load-2 from the flasher
9. DC common from flasher
10. DC common from flasher
3) The above functions shall be clearly silk screened on the circuit board
adjacent to the appropriate terminal.
4) The flasher and interface board shall be pre-wired for connection to a solar
regulator. The wires connecting the flasher and interface board to the solar
regulator shall be a minimum of 16AWG and shall be permanently
soldered to the flasher and interface board. 5) The flasher and interface board shall be pre-wired with a 16-position, CPC
type, quick disconnect connector to accommodate a time switch. The time
switch connector shall be wired as follows:
Pin 4: Relay common
Pin 10: Relay normally open
Pin 13: DC common
Pin 15: DC +
6) The flasher and interface board shall include 3 separate fuses to protect the
solar array, the battery and the load. The fuses shall be easily replaceable
from the front of the board with the use of a standard fuse removal tool.
7) It shall be possible to configure the flasher and interface board to operate as a 24 hour flasher with the use of standard tools.
8) The flasher cabinet shall be supplied with appropriate hardware for
mounting to a 4 1/2" o. d. pedestal pole using Pelco SE-1100.
d. Battery
1) Group 31 a) Each battery shall be Valve-Regulated, Gelled -Electrolyte, with a
nominal voltage of 12 volts and rated at 108Ah (100 hour test method).
Each battery shall conform to the following:
(1) Operating temperature range: -76°F (-60°C) to 140°F (60°C)
(2) Resistance: 4.0 Milliohms full charge
(3) Plate Alloy: Lead Calcium (4) Vents: Pressure relief self -sealing (2PSI operation) vents
permanently attached
(5) Case: Polypropylene
(6) Terminals: Forged with opening for ¼” bolt
(7) Maximum size: L-13.0” x W-7” x H-9.75” (8) Weight: 69.5 lbs.
(9) Non-Spillable: ICAO, IATA & DOT standards
(10) Group Size Rating: Group 31
(11) Cycle Life vs. DOD: 5000 or greater @ +25°C (77°F) BCI 2-
Hour Capacity
2) Group 22
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 85
TRAFFIC SIGNALS
Page 85 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Each battery shall be Valve-Regulated, Gelled -Electrolyte, with a
nominal voltage of 12 volts and rated at 58.2Ah (100 hour test
method). Each battery shall conform to the following:
(1) Operating Temperature Range: -76°F (-60°C) to 140°F (60°C)
(2) Resistance: 4.0 Milliohms full charge (3) Plate Alloy: Lead Calcium
(4) Vents: Pressure relief self -sealing (2PSI operation) vents
permanently attached
(5) Case: Polypropylene
(6) Terminals: Forged with opening for 1/4" bolt
(7) Maximum Size: L-9.38" x W-5.5" x H-9.25"
(8) Weight: 37.0 lbs.
(9) Non-Spillable: ICAO, IATA & DOT Standar ds
(10) Group Size Rating: Group 22
(11) Cycle Life vs. DOD: 5000 or greater @ +20°C (77°F) BCI 2-Hour Capacity
e. Photovoltaic Controller (Solar Regulator/Charger)
1) The flasher cabinet shall include a Photovoltaic Controller (Solar
Regulator/Charger) that uses Pulse Width Modulation (PWM) type
technology. The PWM controller shall be 100% solid state and be
designed for use as a battery charge regulator in photovoltaic (solar) energy
systems.
2) The PWM controller will allow maximum solar panel current to flow into
the battery throughout the battery charge cycle and once full charge is
reached; the regulator will continually allow small current pulses to
maintain a full charge. The PWM type controller shall allow a true 0 to 100% duty charging cycle without having over-c urrent to the battery.
3) The photovoltaic controller shall have terminals to accept up to 10AWG
wire.
4) The solar regulator shall have the following LED status indications :
Charging Status LED
Color Indication Operating State
None Flickers “on” Night (LED flickers every 5 sec)
Green Solid: flickers “off” Charging (LED flickers every 5 sec)
Red Flashing Error
-Solar array current too high disconnect -High Voltage disconnect
-High temperature disconnect
Red Solid: flicker “off” Critical error
-Temp sensor damaged (for battery
charging) -Heat sink temp damage (for internal
heat level)
-MOSFIT damage
-Firmware error
Battery Status LEDs (3)
Led Indication Battery Status Load Status
Green 2 flash per sec Full Battery (N/U for Gel Cell) Regulator “LOAD” output good
Green 1 flash per second Final stage of charge Regulator “LOAD” output good
Green Solid Battery nearly full charge Regulator “LOAD” output good
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 86
TRAFFIC SIGNALS
Page 86 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
Green 1 flash per 2 seconds maintaining full charge Regulator “LOAD” output good
Yellow Solid Battery half full state Regulator “LOAD” output good
Red 1 flash per second Battery low “LOAD” good near disconnect
Red Solid Battery state critical Low Voltage Disconnect (LVD)
(No Field Indications) LVD occurs at 11.5 VDC
Reconnects “LOAD” at 12.6 VDC
5) Amperage Rating
a) The amperage rating of the solar regulator shall be a minimum of 125% greater than the amperage supplied by the solar array.
b) The solar regulator shall be configurable to work with both sealed and
flooded batteries. It shall be possible to switch between sealed and
flooded with the use of simple tools or by use of switch setting.
c) Operating temperature: -40 to 60° (C)
f. Time Switch
1) This specification sets forth the minimum acceptable design requirements
for a two (2) circuit solid state time switch. It is intended for use in
industrial applications and traffic control systems, and shall be of all solid
state construction except for the 2 relay outputs. All components shall be
made available to the purchaser for servicing for five years after expiration of the manufacturer's warranty, or shall be so identified that they may be
purchased from industrial electronics suppliers. The time switch shall use
day plan programming with the annual exception method for ease of
programming.
2) Physical
a) The time switch shall be equipped with a means for mounting to a
suitable back plane. Mounting holes that provide clearance for at least
a No. 10 sc rew will be acceptable.
b) The time switch shall not exceed 8 3/8"h x 4 7/8"w x 2"d without
harness and 10 3/8"h x 4 7/8"w x 2"d with harness. A case shall be provided to protect the time switch circuitry from dust. The unit shall
fasten securely to the cas e and must be easily removable from the case
with the use of simple tools.
c) Interface to the power source (AC or DC) and to the controlled device
shall be provided by means of a quick disconnect connector with a 48"
mating harness. The AC and DC power inputs shall be protected with
a fuse and MOV.
3) Power Supply and Timing
a) The time switch shall operate on either 12 Volt DC +/-2VDC or an AC
power source between 95 and 135 VAC and from -30 to +74 degrees
C. b) The AC & DC power supply shall be an integral part of the time switch
circuit board for operation in AC powered or solar DC powered
systems. A separate 12VDC power supply module, similar to those
used for calculators and battery chargers, is not acceptable.
c) No time shall be gained or lost during changeover from AC power to the back-up system and back to AC power.
4) Programming
a) All programming shall be accomplished via a 16 key positive action
push button keyboard which is an integral part of the unit. Prompt
messages shall be displayed during the programming process to guide
the operator as the data is being entered.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 87
TRAFFIC SIGNALS
Page 87 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b) The time of day shall be able to be set to one second.
c) Time of day, day of week, date, year and the operation of the 2 relay
outputs shall be able to be easily set from the integral keyboard. The
functions of the keys shall be clearly marked on the keypad. Prompt
messages shall be displayed during the programming process to guide the operator as the data is being entered. All data required to properly
set and program the unit and review the stored program shall be clearly
displayed without the use of auxiliary devices.
d) Changeover from standard time to daylight savings time or vice versa
shall be accomplished automatically. The operator shall have the
capability of entering the daylight savings time information from the
keyboard thus eliminating the need for a PROM change should the
current U.S. law change. The daylight savings time feature shall be
able to be defeated from the keyboard. Leap year compensation shall
be automatic. e) When the user is programming the unit, the display shall provide for
verification of each piece of data prior to its being entered. Provision
shall be made for correction of any incorrect data prior to entering it. It
shall be possible to alter any individual program step without
disturbing any other step in the program.
f) When an instruction is given to turn the output/s on or off, that
instruction time shall be able to be set to one minute, and the change
shall take place at the zero second of that minute.
g) A set of cle ar operating instructions shall be furnished with each time
switch .
h) A software package shall be available that will allow the operator to upload programming and download programming to the time switch
from a table top central computer or laptop. The programming shall
include all day plans, week plan, annual plans and a unique name
assigned by the operator. The software shall be able to store the
programming for an unlimited number of time switches. 5) Day Plan Programming
a) Each time switch shall have ten (10) day plans. One of the Day Plans
shall be used for holidays throughout the school year. The other nine
Day Plans shall be capable of programming 16 program steps per plan.
Each day plan program step shall include the following:
(1) Time of day in: Hours, Minutes, AM or PM (2) ON/OFF Commands: ON, OFF
b) One day plan shall be reserved for programming a normal school day
and the other 8 day plans are programmed for any school flasher
schedule other than the normal school day such as an early out
schedule. c) Means shall be provided to allow the operator to clear the
programming of a single Day Plan or all of the Day Plans by simple
keystrokes.
6) Week Plan Programming
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 88
TRAFFIC SIGNALS
Page 88 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) Each time switch shall have a Week Plan. The Week Plan is the
normal Monday through Friday school program. The time switch shall
automatically assign Saturday and Sunday to no Day Plan, and
Monday through Friday to the Normal Day Plan. The operator shall
have the ability to reprogram any day of week in the Week Plan to any other Day Plan.
7) Annual Plan Programming
a) The time switch shall be capable of executing thirty-six (36) separate
Annual Plans. The Annual Plan programming shall use the exception
day method where the time switch automatically runs its Week Plan
until an Annual Plan program instructs it to run a different day plan.
b) Programming for the Annual Plans shall be accomplished through the
integral keyboard. Each Annual Plan shall be programmed by entering
a Day Plan number and the beginning date (month/date/year) and the
ending date for which the time switch is to run that Day Plan. The time switch shall be capable of running a Day Plan as short as one (1)
day or as long as six (6) months. It shall be possible to begin an
Annual Plan in one calendar year and end that same Annual Plan in the
next c onsecutive year.
c) It shall not be necessary to enter the Annual Plans in chronological
order.
d) Means shall be provided to allow the operator to clear all of the data in
the Annual Plans without affecting the operation of the time switch.
e) A means shall be provided to review the Annual Plans without
affecting the normal operation of the time switch. The display shall
include the Annual Plan number, the Day Plan number, and the beginning and ending dates.
8) Program Transfer
a) It shall be possible to program any time switch, and transfer that
program to any other like time switch by means of a simple unit-to-unit
cable. Upon completion of the program transfer, an electronic check shall be activated to insure an accurate transfer of data. In the event an
invalid tra nsfer occurs, an error message shall be displayed alerting the
operator. The transfer cable connection shall be accessible from the
front of the time switch.
9) Manual Operation
a) The time switch shall have the capability of manually turning on or off the two relay outputs from the integral keyboard. The manual
operation shall remain in effect until the next valid program step
occurs. At that point the time switch will release from manual control
and revert to its internal program.
b) The main display of the time switch shall indicate when the unit is under manual control.
10) Display
a) Integral with the time switch shall be an easy to read, 2 line, 16
characters per line, alphanumeric Liquid Crystal Display (LCD). This
display shall provide a clear indication of the time of day
(HH:MM:SS), AM or PM, day of week, date (MM/DD/YY) and the
status of the output relays. Time shall be entered on a 12 hour format
with a clear indication of AM or PM.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 89
TRAFFIC SIGNALS
Page 89 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b) The operator shall be able to display the current status of the time
switch with simple keystrokes. This status screen shall include which
Day Plan and Annual Plan numbers are in effect.
c) A means shall be provided to review the program in the unit's memory,
and such means shall be integral with the time switch. Such program revie w shall not affect the current operation of the time switch.
11) Back -up System
a) A means shall be provided to maintain timekeeping when the line
power source (115VAC) is not available. This back-up system shall
maintain timekeeping for not less than 7 years at 25C. Upon
resumption of the line power, the unit shall automatically resume
normal operation.
b) A means shall be provided to maintain the time switch program when
the line power source (115VAC) is not available. This back-up system
shall maintain all prog rammed steps intact for not less than 7 years at 25C. Upon resumption of the line power, the unit shall automatically
resume normal operation.
c) Should the timekeeping or the program of the time switch be erased
during an AC power outage, the unit shall dis play an indication of the
loss. The display shall be an easy to read LCD and shall be able to be
reset from the integral keyboard.
d) When the time switch is operating on the back-up system, the displays
shall be blanked and the output disabled to conserve back-up power.
12) Outputs
a) The time switch shall have two (2) single-pole, double-throw relay
output with a contact rating of at least 15 amps at 115 VAC resistive load.
g. 12” Polycarbonate Traffic Signal Head
1) The purpose of this specification is to set forth minimum design and
operating requirements for a 12" adjustable face polycarbonate traffic
signal head which can house a 12” 12VDC LED. 2) General
a) The performance of each signal shall conform to the standard for
Adjustable Face Vehicular Traffic Control Signal Head, Technical
Report No. 1, of the Institute of Transportation Engineers, as most
recently revised.
b) The signal shall be sectional in construction, requiring one lens per section. Sections shall be of such design and construction as to fit
together rigidly and securely, to prevent the entrance of dirt or
moisture and prevent the rotation of misalignment of the individual
sections.
3) Housing a) The housing for the individual sections shall be injection molded from
ultraviolet and heat stabilized flame retardant permanently colored
polycarbonate resins.
b) All parts shall be clean, smooth, and free from flaws, cracks,
blowholes, and other imperfections.
c) The top and bottom of each section shall be molded with a 5 serrated
boss and reinforcing ribs.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 90
TRAFFIC SIGNALS
Page 90 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
d) Openings in the top and bottom of the signal shall accommodate
standard bracket arms.
e) A cast boss shall be provided for mounting a 5 or 6 position terminal
strip.
4) Door a) The doors for each section shall also be injection molded from similar
material to that used for the main section housing.
b) Two integrated hinge lugs shall be mounted to the housing with two
stainless steel hinge pins.
c) Positive latching shall be achieved with stainless steel eyebolts and
wingnut assemblies.
d) The inside of the door shall have a groove to accommodate a pliant
gasket resulting in a completely weatherproof and dustproof assembly
when the door is in the closed position.
e) The door shall be equipped with four metal threaded inserts molded in for added strength to the visor attachment screws.
5) Visor
a) All signal head shall have a tunnel visor for each section.
b) The visor shall be one piece made of molded permanently colored
polycarbonate resins and have twist-on attaching ears.
6) Hardware
a) All screws, latching bolts, and hinge pins shall be 300 series stainless
steel to prohibit rust and corrosion.
7) Terminal Block
a) The traffic signal shall be equipped with a 2 or 3 section #12 terminal
barrier strip; one side with a quick disconnect terminal for socket leads. The opposite set of terminals with a screw clamp terminal for field
wiring.
8) Signal Closure Kit
a) A signal closure kit will be furnished with each signal head unless
otherwise noted. The closer kit shall be designed to seal the signal head at either top or bottom without use of special tools. The closer
cap shall be molded ABS plastic having the same color as the signal
head with UV stabilizers and having a durometer neoprene gasket.
The adapter bar used to secure the closure kit to the head shall
compensate for varying thickness of the signal heads. Two screws
shall be provided to fit any manufacturers signal. h. Signal Mounting Hardware
1) The purpose of this specification is to set forth minimum design and
specification requirements for a signal mounting bracket assembly to attach
an 8" & 12" polycarbonate traffic signal head to a 4 1/2" pole.
2) Materials a) The bracket shall consist of a hollow aluminum cast arm with circular
tri-bolt signal centering bosses, drilled and tapped 1/4" x 20 for
attachment of a traffic signal head and on pole end cast openings for
3/8" U-bolt.
b) All associated hardware needed to attach signal head to a 4 1/2" pole
shall be supplied with the bracket.
c) No special tools required.
d) The hollow aluminum arm shall have a 1 1/2" wire raceway.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 91
TRAFFIC SIGNALS
Page 91 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
e) The casting shall be free of voids, pits, dents, molding sand and
excessive foundry grinding marks.
f) The exterior finish shall be free of molding fins, cracks and other
blemishes.
g) All design radii shall be smooth and intact. h) Minimum aluminum ingot requirements :
(1) Aluminum alloy: 319
(2) Yield strength: 18
(3) Tensile strength: 27
(4) Brinell hardness: 75
(5) Elongation (% in 2”): 2%
3) Finish
a) Bracket arm: alodine finish
b) Hardware: zinc di-chromate
i. Pedestal Base 1) The pedestal base shall be 13 3/4" square and 15" high.
2) The base shall be cast aluminum with natural finish and minimum weight
of 20 lbs.
3) The pedestal base shall be fabricated from new aluminum billet with the
following minimum requirements:
a) Aluminum alloy: 319
b) Tensile strength, KSI: 34
c) Yield strength, KSI: 19
d) Elongation (% in 2"): 2.5
e) Brinell hardness: 85
f) Shearing strength, KSI: 23 4) No scrap material shall be used in the fabrication process.
5) The pedestal base shall be free of voids, pits, molding sand and excessive
foundry grinding marks.
6) All design radii shall be smooth and intact.
7) The top of the pedestal base shall be threaded to receive a 4" NPT pedestal pole.
8) The pedestal base shall be designed to be fastened to a concrete foundation
by means of 3/4" anchor bolts located 90 degrees apart on the bottom of
the base.
9) The base shall have slots in the bottom 1 1/2" wide and 2 1/2" long
measured along the circumference of the bolt circle, allowing a proper fit even if the bolts are placed slightly off center.
10) The base shall accommodate bolt circles from 12" to 14 1/2".
11) Each pedestal base shall be supplied with a set of 4 anchor bolts, 3/4"
diameter by 18" length, galvanized per ASTM-A-572. Each anchor bolt
shall have a hex nut and flat washer. 12) The pedestal base shall have an 8 1/2" square door opening that is free of
burrs and sharp edges.
13) Each pedestal base shall be supplied with a removable 8 1/2" square door.
The door shall be attached to the base by using one socket button head
screw at the top and two injection molded lugs with slots at bottom.
14) The door shall be injection molded ABS plastic that is free of burrs and
sharp edges and shall conform to the following minimum requirements:
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 92
TRAFFIC SIGNALS
Page 92 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
ASTM Method Value
Tensile @ yield (1/8”) D638 6,600 psi
Flexural @ yield D790 11,000 psi
Rockwell Hardness D785 101 (R Scale)
Nothched Izod D256 5 ft. lb./in.
15) The door shall have reinforcing ribs and shall have an edge thickness of
.25" and a minimum thickness of .156".
16) The door shall contain a fire retardant meeting or exceeding Underwriters
Laboratories UL94 test H.B. and ultra-violet inhibitors and stabilizers for
protection against U.V. degradation.
17) The color of the door shall be gray aluminum tone. All surfaces shall be
flat and straight without blisters, buckling or warping.
j. Pedestal Pole 1) The pedestal pole shall be 15' in length.
2) The pedestal pole shall be extruded with the following minimum
requirements:
a) Aluminum alloy: 6063-T6
b) Tensile strength, KSI: 30 c) Yield strength, KSI: 25
d) Elongation: 10%
e) Minimum wall thickness: 0.237”
f) Outside diameter: 4.5”
3) The pedestal pole shall be threaded and deburred 4" on one end only per
NPT specification. 4) The pedestal pole shall have a rough surface texture consisting of a
uniform grain pattern that is perpendicular to the axis of the pole for the
full length of the pole.
5) The pedestal pole shall be free of heat discoloration, holes, ridges, cracks
or other surface defects. k. Pole Reinforcing Collar
1) The reinforcing collar shall be designed to reinforce a pedestal pole at the
point where the threads enter the pedestal base.
2) The reinforcing collar shall be three piece cast aluminum with the
following minimum requirements:
a) Aluminum alloy: 319
b) Tensile strength, KSI: 27
c) Yield strength, KSI: 18
d) Elongation: 2
e) Brinell Hardness: 70
f) Finish: Alodine 1200 g) Minimum wall thickness: 5/8"
h) Minimum mounted height: 4 3/8"
3) The reinforcing collar shall clamp around the top of a pedestal base with
six (6) 5/16" socket head bolts.
4) Each reinforcing collar shall be supplied with a 5/16" x 3/4" roll pin for
holding the collar securely in place. The collar shall have an opening to be
used for drilling a pilot hole for the roll pin.
l. Anchor Bolts
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 93
TRAFFIC SIGNALS
Page 93 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) A set of four (4) anchor bolts shall be furnished with four (4) washers and
four (4) hex nuts.
2) The anchor bolts shall be ¾” x 18” in length as measured from inside of the
bend to the threaded end of the anchor bolt.
3) The anchor bolt shall be threaded ¾”-10NC for a minimum length of 3-¼” inches of thread.
4) The “L” bend shall be a minimum of 3 inches as measured from the inside
of the anchor bolt shaft to the end of the bend.
5) The anchor bolt material shall conform to ASTM A-529 Grade 50
specifications, with minimum yield strength of 50 KSI and minimum
tensile strength of 70 KSI.
6) The material shall be of domestic origin (manufactured in the USA).
7) The anchor bolt shall be hot dipped galvanized per ASTM A-153 their full
length and the threads brushed or rethreaded to remove any excess
galvanize on the threads. 8) The material for the hex nuts shall conform to ASTM A-563 Grade DH
specifications.
9) The nut shall be hot dipped galvanized per ASTM A-153 and rethreaded to
remove any excess galvanize on the threads.
10) The material for the washer shall conform to ASTM F-844 specifications.
11) The washer shall be hot dipped galvanized per ASTM A-153.
12) All galvanized runs, drips, icicles and bare spots shall be properly treated.
m. Cell Modem for 2-way communications with CPR2102 or AAP22 Time
Switch
1) Frequency Band
a) Hepta -band 850/900/AWS 1700/1900/2100 MHz 2) Physical
a) The cell modem shall be housed in an aluminum enclosure with a
means for mounting. A mounting bracket shall be supplied with eac h
modem for attaching to a time switch.
b) The cell modem shall not exceed 3.17” H (3.816” including connectors) x 2.45” W x 1.16” D. The cell modem shall be
approximately 8.8 ounces in weight.
3) Connectors
a) The RF antenna connector shall be a SMA female and be marked
CELL. The serial connector shall be a DB9 female and the power shall
be a 2.5mm miniature screw -on connector and both will be located on same end.
b) SIM (Subscriber Identification Module) shall be a Mini SIM.
4) Cable Harness
a) Each cell modem shall be supplied with a cable harness with the
appropriate connectors to connect the cell modem to the time switch. The cable harness shall connect 12 VDC power, serial data in, serial
data out and ground from the time switch to the cell modem. The DC
power shall be supplied from the time switch over this cable harness.
5) Electrical
a) The cell modem shall be capable of operating on a DC power source
between +7 to +32 VDC and shall be designed to operate from -40 to
+85 degrees C. The unit must be powered directly from the time
switch.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 94
TRAFFIC SIGNALS
Page 94 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b) A separate power supply module, similar to those used for calculators
and battery chargers, is not acceptable.
6) Antenna
a) Antenna configurations must be provided to insure a RSSI level
necessary for dependable communications to the remote unit. The antenna required will be determined at the time of installation by
testing the signal strength at each individual location. Any necessary
cabling and mounting hardware will be provided.
b) An omni antenna and coax cable designed for the frequency band of
the cell network shall be supplied with the cell modem. The coax cable
shall be a minimum of 24” long with connectors necessary to connect
the antenna to the cell modem. The omni antenna shall have a nominal
impedance of 50 ohms and shall have a gain of 0 – 2 dB.
7) Indicators
a) The cell modem shall have LED indicators to display the following: (1) Power -When the cell modem has power applied
(2) Tr- When the cell modem is in the process of transmitting data
(3) CD- When the cell modem has acquired connection to the cell
network
(4) LS - Link Status
(5) Signal- Signal strength
8) SIM Card
a) Each cell modem shall be equipped with a SIM card that is pre-
provisioned by the supplier for data through a 3G service provider.
b) The cell modem shall have a slot designed for receiving the SIM card.
The slot shall be accessible from the outside of the cell modem enclosure and shall hold the SIM card firmly in place.
9) Cell Modem Configuration
a) The cell modem shall have the ability to receive commands from the
centr al computer using standard modem “AT” commands. When an
AT command is received, the modem shall respond by sending the appropriate response to the central computer. These commands shall
allow the operator to determine or execute the following:
(1) Unattended daily validation
(2) Relay status
(3) Low battery voltage
(4) Signal strength (5) Last download
(6) Last power -up
(7) Data acquisition command for AP22 or CPR2102 from the time
switch
b) Each cell modem shall have a serial connector that is pre-configured to work with Model CPR2102 and Model AP22 Time Switches. The pre-
configuration of the serial port shall include the baud rate, data bits,
stop bit, parity and flow control.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 95
TRAFFIC SIGNALS
Page 95 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
21. Rectangular Rapid Flashing Beacon (RRFB) Assembly
a. Cabinet
1) The cabinet shall be manufactured of 0.125” sheet aluminum. Nominal
cabinet dimensions shall be 22” H x 12.0” W x 8.0” D. The cabinet shall be
a one (1) compartment type. The cabinet shall have screen covered louvers on each side for ventilation. On the bottom of the cabinet there shall be two
screened insect proof drain holes. The cabinet shall be weather resistant,
providing a degree of protection from falling rain or sleet and shall be
undamaged by the formation of ice on the enclosure.
2) The cabinet door shall be a single unit with a continuous piano hinge
riveted to the door and the cabinet. The hinge shall be an A730S,
constructed with a 304 stainless steel hinge pin. The door shall incorporate
a neoprene gasket which forms a snug weather tight seal when the door is
closed. The door lock shall be a standard Police lock.
3) Each cabinet shall be equipped with a mounting bracket for 4.5” OD pole mounting. All necessary hardware for proper mounting shall be included.
b. Control Panel
1) The systems electronic components including a solar charge controller,
solid state flasher, countdown timer and radio shall be mounted on a
modular control panel. The control panel shall mount in the cabinet using
standoffs and a self -retaining, spring loaded thumb screw for quick and
easy removal. The solar panel input, battery input and system load output
shall be fused for short circuit and overload protection and to provide ease
of system maintenance.
2) The solar panel, beacons and battery shall be connected to the control panel
through a main wiring harness via a circular pin connector (CPC). 3) Solar Charge Controller
a) The solar charge controller shall be fully automatic charger using four
stages of charging for rapid, efficient and safe battery charging. Stage
1: Full Charge, with 100% of available solar energy. Stage 2: Pulse-
Width Modulation (PWM) constant voltage regulation to prevent heating and excessive battery gassing. Stage 3: Float Charge, after
battery is fully recharged, reduces to a float or trickle charge with
transition dependent on battery history. Stage 4: Equalize Charge, a
boost charge that depends on elapsed time and battery history.
Flooded cells receive a vigorous equalization, sealed batteries a smaller
boost to bring uneven cells into balance and extend battery life. Gel cells are not equalized.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 96
TRAFFIC SIGNALS
Page 96 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b) The solar charge controller shall have a low voltage load disconnect
(LVD) of 11.4 VDC and shall automatically reconnect after LVD when
the voltage reaches 12.6 VDC. The charge controller shall have a high
voltage disconnect (HVD) of 15.3VDC. A liquid crystal display (LCD)
shall be provided on the front of the charge controller to display battery voltage, solar charge current, and load current. In addition, colored
LED’s will indicate charging state and battery status. The green
charging LED shall be on when charging and off when not charging.
Battery status LED’s indicate battery state, showing a blinking green
LED during PWM charging, a solid green LED when battery is near
full charge, a solid amber LED indicating battery at middle capacity,
blinking red LED indicating low charge, or a solid red LED indicating
load disconnected (LVD).
c) A multifunction manual disconnect push button shall be provided to
allow disconnect of the Load or both Load and Solar. When the button is pushed the red Led inside the button will light. In addition, the Load
of both the Load and Solar will display ‘OFF’ in the digital meter to
indicate the disconnected state.
d) The solar charge controller will be capable of operating in a
temperature range of -40 degrees C and +60 degrees C.
e) Wire terminations to the solar charge controller shall be accomplished
via Euro style terminations.
f) The solar charge controller shall be Morningstar Corporation’s Prostar
15 with LCD display or approved equal.
4) Solid State DC Flasher
a) The flasher shall be solid state, 2 circuit device which controls the wig-wag and rapid flashing sequence of the yellow indications on each side
and end of the RRFB.
b) The flasher shall allow an input voltage range of 11 to 25 VDC,
support a maximum power load of 50W per output and be capable of
operating in a temperature range of -40°C and +75° C. The flasher shall be an ELTEC FS -2B or approved equal.
5) Countdown Timer
a) The countdown timer shall be a multi-function, multi-range, multi-
voltage electronic timer with DPDT relay output and LED status
indicator. The timer shall operate upon system activation to control the
flash duration of the RRFB. The timer shall provide seven field selectable ranges of timing providing 0.1s to 100h activation duration.
b) The timer shall conform to the following minimum specifications:
(1) Operating Voltage: 12VDC Nominal (10.2V – 14.4V)
(2) Max Power Consumption: 0.6W
(3) Repetition Accuracy: +/- 0.5% (4) Operating Temp Range: -20° C to +60°
(5) Relay Output Rating: 10A – 250V
(6) Fixing: Plug -in Base: 11 -pin
6) Wireless Communications
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 97
TRAFFIC SIGNALS
Page 97 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
a) The units on each side of the road shall communicate wirelessly. No
trenching or boring is necessary. The radio transmitter and receiver
shall use Frequency Hopping Spread Spectrum (FHSS) technology to
ensure reliable data delivery within the unlicensed Industrial, Scientific
and Medical (ISM) band. b) The communication system radios shall conform to the following
minimum specifications:
(1) Operating Voltage: 10VDC – 30VDC
(2) Operating Current: Typ - <100mA, Max – <200mA at 12VDC
(3) Operating Frequency: 900 MHz
(4) RF Transmit Power: 1 Watt
(5) Network Identification: MAC ID Binding
(6) Antenna Impedance: 50Ω
c) The initiation of the signal for the flashers to commence flashing will
be by pedestrian push button. Activation from pedestrian shall trigger the system countdown timer to operate the crossing indications for the
programmed duration. Each time a pedestrian pushes a button, the
countdown timer will reset and repeat to the preset flashing beacon
cycle.
d) The wireless communication system must be an ELTEC 730247-GW
or an approved equal.
c. Solar Panel
1) The solar panel shall be constructed of high efficiency, multi-crystal silicon
solar cells that are laminated within a pottant of ethylene vinyl acetate
(EVA) and encapsulated between a tempered glass cover plate and a back
sheet. The entire laminate shall be secured within an anodized aluminum frame for structural strength, ease of installation, and to protect the cells
from the most severe environmental conditions. The panel shall be self -
cleaning, impact resistant, highly transmissive, tempered glass superstate.
The panel module frame shall be made of extruded, polymer coated
aluminum alloy or similar approved construction. The panel module junction box shall be a UV resistant, weatherproof wire termination system
which handles #18 AWG - #8 AWG wiring. The typical wattage of the
solar panel shall be 40 watts. The appropriate wattage of the solar panel
shall be verified with a system sizing report based upon location and
specific system configuration and operating parameters.
2) A mounting rack for the solar panel shall be included with the solar panel. The mounting rack shall mount to a 4 ½” OD pole.
d. Battery
1) The system battery shall be valve regulated, recombinant, starved
electrolyte, sealed lead acid absorbed glass mat (AGM) 12 volt DC battery.
The battery self -discharge rate shall be 1% per month or less (at 68 degrees F). The battery will utilize T881 terminals. The positive terminal will be
covered with a rubber boot to protect the battery from accidental shorting.
The typical battery capacity shall be 55 amp-hours. The appropriate
battery size shall be verified with a system sizing report based upon
location and specific configuration and operating parameters .
e. Rectangular Rapid Flashing Beacon (RRFB) Light Bar
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 98
TRAFFIC SIGNALS
Page 98 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) The RRFB shall comply with FHWA Interim Approval Memorandum
dated July 16, 2008 and all subsequent official interpretation letters
provided as clarification. The RRFB shall contain 5 rectangular rapid-
flashing yellow indications; two on each side, and one in the end visible to
pedestrians in the cross walk. The indications facing the motorists shall be approximately 5” wide by 2” high, and shall be yellow indications, Whelen
500 Series TIR6 50AA3ZCR, split lightheads featuring a six Super-LED
panel with a cle ar outer lens providing wide-angle visibility and high
intensity output. The LED used on the end of the light bar facing the
pedestrian shall be round.
2) Indications facing the motorists shall meet SAE J595 Class 1 peak
luminous output requirements. The vendor shall submit third party
certification of SAE J595 Class 1 compliance.
3) The RRFB flash pattern with be the WW+S (Wig-Wag plus Simultaneous)
as approved by the FHWA on July 25, 2014. The beacons shall flash at a rate of 75 flashes per minute.
4) The RRFB housing shall be constructed of 0.125” brushed sheet
aluminum. The housing shall be powder coated Federal Yellow.
5) The RRFB will be assembled and wired as a unit. The unit’s two piece
housing shall include a keyed quick disconnect plug between the wiring
harness of each side to allow for ease of installation and maintenance. The
housing shall mount to 2-3/8” or 4-1/2” OD poles with integral universal
mounting bracket and a U-bolt.
f. Night Dimming
1) Automatic night dimming may be enabled on the RRFB FS-2B flasher.
The dimming function shall employ an external photocell to detect ambient light. The flasher shall initiate the night dimming function when detected
light conditions reach the ambient light level as defined by the Federal
Aviation Administration (FAA).
g. Pole and Base
1) The pole shall be a schedule 40 spun aluminum 4” ID (4.5” OD) x 16’ H. The base shall be an AASHTO Certified square aluminum breakaway base,
Pelco PB-5340 or equal. A set of 4 anchor bolts shall be provided. The
anchor bolts shall be ¾” x 16” and be similar to Pelco part number PB-
5306. A two-piece aluminum pole collar assembly with standard stainless
steel fasteners shall be provided.
h. Signage 1) Two (2) W11-2 (36” x 36”) signs shall be provided for each pole location
and shall be mounted on each side of the pole just above the light bar. Two
(2) W16-7p (24” x 12”) shall be provided for each pole location. One left
pointing down arrow mounted below the light bar on one side and one right
pointing down arrow mounted below the light bar on the other side of the pole. Signs shall be constructed using 3M diamond grade reflective
fluorescent yellow -green sheeting.
2) Back to back sign mounting hardware for mounting the signs on a 4.5” OD
pole shall be included.
i. Pedestrian Push Button
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 99
TRAFFIC SIGNALS
Page 99 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) A pedestrian push button shall be provided to activate the flashing beacons.
The button shall be an ADA compliant push button with H-frame mount
incorporating a plaque on the push button reading ‘PUSH BUTTON TO
TURN ON WARNING LIGHTS’.
22. Louvered Back Plates
a. Material
1) Aluminum or acrylonitrile -butadiene-styrene (ABS).
2) One-piece for 3- and 4-section heads
3) Two-piece for 5-section heads
b. Finishes
1) Aluminum: powder coat
2) ABS, integrally molded
c. Color(s)
1) Face: flat black 2) Back: flat black
d. A 2 -inch wide fluorescent yellow AASHTO Type BFL or CFL retroreflective
border shall be added to aluminum plates.
e. Shall be vacuum formed.
f. Aluminum plates shall be louvered. g. ABS sheet material shall conform to ASTM D1788.
23. Powder Coating Traffic Signal Structures
a. Powder Coating
1) After galvanizing, the steel and aluminum products shall be blasted to an
SSPC-SP7 commercial blast.
2) All galvanized parts shall be pre-baked to ensure all gasses are released
from the coating surface prior to powder coating.
3) Finish with 1 coat of UMC super TGIC thermosetting powder coating 3-5
mils (D.F.T.) and baked in accordance with powder manufacturer’s
recommendations. 4) Top coating is electrostatically applied and oven baked at 400 degrees
Fahrenheit and cured for a minimum of 10 minutes.
5) Top coat color shall be black (RAL 9017) unless otherwise selected by
the City.
b. Additional Color(s)
1) Stockyards RAL #3099 Oxide Red
2) Other colors may be approved by the City.
24. PTZ Camera and Cable
a. The PTZ camera shall be Spectra Enhanced 7 Series IP or approved equivalent approved by City Traffic Signal Engineering Manager or Designee.
b. Items must include:
1) Wal mount
2) IP Dome camera, PTZ 2MP 30x Zoom Pend Dome
3) Pole Mount Adapter 4) POE injector, 75 Watt Single Port 100-240VAC
c. The rubber straps shall have the following specifications:
1) Size shall conform to field conditions of pole diameter and PTZ camera
mount.
2) Shall be weather, water, abrasion, oil, and UV resistant, 60A, adhesive
backing type, black
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 100
TRAFFIC SIGNALS
Page 100 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
3) Size shall be 2”Width x 3ft Length x 0.25” Thick, 300% elongation
d. Cable shall be
1) Shielded, gel filled, waterproof, direct burial UV rated.
2) 24 AWG Solid Copper
3) 350MHz, Non-PVC UV Jacket 4) Shielded with drain (Ground) wire
5) CMX flame rated
6) UL or ETL listed and RoHS compliant
25. Communication Modem
a. The product bid shall be the WR44R by DIGI, or approved equivalent
approved by City Traffic Signal Engineering Manager or Designee, and shall
meet the following specifications.
1) Shall transmit on a minimum 4G LTE broadband platform.
2) Shall have a minimum of 4 ethernet ports.
3) Shall have an integrated Wi-Fi (B/G/N) access point and 5 VPN Tunnels features.
4) Housing shall be constructed with rugged enclosure to withstand a harsh
environment.
5) Shall include AC power supply supporting minimum of 18VDC, extended
temp. NEMA 5-15P (US) to 4-pin connector.
6) Shall have advanced routing, security, and firewall features.
7) Dual SIM compatibilities
8) LTE North America Multi-Carrier (700/850/1700(AWS)/1900 MHz)
9) Enterprise Software Package
10) Extended temperature 11) Remote manager device license
b. Communication Modem shall include two Wi-Fi antennas and two low profile
robust cellular antennas from panorama part #: LPB-7-27-2SP or approved
equivalent approved by City Traffic Signal Engineering Manager or Designee.
Antenna must meet the following specifications:
1) Threaded bold, black, and between 6-10’ pigtail.
2) RSMARV: 2.4/5.8GHz (Wi-fi)
3) 700-2700 MHz 2m SMAP (Cellular)
2.3 SOURCE QUALITY CONTROL
A. Battery back-up system
1. The City reserves the right to do testing on BBU systems to ensure Quality
Assurance on unit before installation and random sampling of units being provided
to the City. BBU systems that fail will be taken off the City’s Qualified Products
List.
2. The City testing procedures will check compliance with all the criteria of this
Specification Section including the following:
a. Event logging for fault/alarm conditions .
b. Demonstrated use of 1 or more of the operating methods described in this
Specification.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 101
TRAFFIC SIGNALS
Page 101 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c. Testing of ability to power a 700W load for 4 hours, transfer to flash mode and
power a 300W load for 2 additional hours, at an ambient temperature of +25
degrees Celsius .
d. Testing of all components in environmental chamber (temperature ranges from
-30 degrees Celsius to +74 degrees Celsius ) following NEMA TS2 2003 standards, section 2 and Advanced Transportation Controller (ATC) Standard,
Version 5.2b, Section 9.
3. Each BBU shall be manufactured in accordance with a written manufacturer’s
Quality Assurance program. The QA program shall include, as a minimum,
specific design and production QA procedures.
4. The Inverter manufacturer s hall be ISO 9001or ISO 9002 certified.
5. The manufacturer, or an independent testing lab hired by the manufacturer, shall
perform qualification testing on BBU Systems offered to the City. Testing
procedures shall conform to testing procedures defined by the standard TxDOT or
City procedure. Testing data shall be submitted to the City for review.
PART 3 - EXECUTION
3.1 EXAMINATION
A. Verification of Conditions
1. The Contractor shall verify by exploratory excavation, if needed, that existing
underground utilities are not in conflict with proposed foundations and conduit
bores.
a. All exploratory excavations shall be in accordance with Section 33 05 30.
3.2 PREPARATION
A. Protection of In-Place Conditions
1. The Contractor shall assume full responsibility for the preservation of existing
lands caping (sod, shrubbery, trees, and etc.), sprinkler systems, and/or other private
property at the Site during the installation of the traffic signal. Damaged landscaping, sprinkler systems, and/or other private property shall be replaced
within a reasonable time, by the Contractor at his own expense, to the satisfaction
of the Inspector.
2. No trees or shrubbery shall be cut except upon the specific authority of the Inspector.
3. Removal of mail boxes in the way of construction requires 48 hours advance notice to
the post office.
3.3 INSTALLATION
A. Special Techniques
1. LED Vehicle and Pedestrian Signal Head Assemblies
a. Assembly
1) Assemble individual signal sections in multi-section faces in accordance
with the manufacturer’s recommendations to form a rigid signal face. 2) Assemble and mount signal heads as shown on the plans.
3) Close any openings in an assembled signal head with a plug of the same
material and color as the head.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 102
TRAFFIC SIGNALS
Page 102 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
4) Remove only the existing lens, reflector, and incandescent lamp when
installing a retrofit replac ement LED traffic signal or pedestrian signal
lamp unit into an existing signal housing; fit the new unit securely in the
housing door; and connect the new housing unit to the existing electrical
wiring or terminal block by means of simple connectors. b. Wiring
1) Wire each optical unit to the terminal block located in that signal section
by means of solderless wire connectors or binding screws and spade lugs.
2) Wire all sections of a multi-section signal face to the section terminal
blocks in which the traffic signal cable is terminated.
3) Maintain the color coding on leads from the individual optical units
throughout the signal head, except for the traffic signal cable.
4) Use solderless wire connectors or binding screws and spade lugs for
connections to terminal blocks. Use binding screws and spade lugs for field
wiring. c. Signal and pedestrian heads shall be securely tightened immediately after
signal head assembly has been installed.
d. If any signal head assembly is found to be loose or asymmetrical in any
manner, t he Contractor shall be required to remove and rebuild the signal head
assembly to the satisfaction of the Inspector.
e. The Contractor shall mount signal heads level and plumb.
f. The Contractor shall position and secure the signal heads so they are visible as
stipulated, in Section 4E.05 of the 2009 MUTCD.
g. All connection screws shall be tight and snug.
h. All signal heads or parts of heads not in operation shall be covered with burlap
or fabric material until placed into operation. i. When the signal heads become operational, all existing heads no longer
required shall be removed immediately.
j. Pedestrian head assemblies installed such that the wiring to each head shall
pass from the mast arm through the signal head bracing or attachment hardware
to the signal head. k. No exposed cable or wiring will be permitted.
l. Installation of a pedestrian signal retrofit module into an existing pedestrian
signal housing shall only require the removal of the existing optical unit
component, i.e., lens, lamp module, gaskets, and reflector; will be weather tight
and fit securely in the housing; and shall connect directly to existing electrical
wiring.
2. Pedestrian Push Button Assemblies
a. Meet the requirements of the TMUTCD when installing push-buttons.
b. Wire the push-button according to manufacturer’s installation instructions.
c. Close unused housing openings with a weather-tight closure painted to match the housing.
d. Verify that each button is communicating and fully functional.
e. Do not use terminal connec tions or splice wire leads except at approved
locations.
f. Attach wires to terminal posts with solderless terminals unless otherwise
advised by manufacturer’s recommendations.
g. Attach terminals to the wires with a ratchet-type compression crimping tool
properly sized to the wire.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 103
TRAFFIC SIGNALS
Page 103 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
h. Mount a pedestrian push button sign near each push button as shown on the
plans.
3. Accessible Pedestrian Signals (APS) a. Meet the requirements of the TMUTCD when installing APS Stations.
b. Wire the APS Stations according to manufacturer’s installation instructions.
c. If a controller unit is required by the plans, integrate the pedestrian controller
unit into the traffic signal controller cabinet assembly.
d. Remove any burrs or rough edges on any holes drilled for wire entry to APS
pushbuttons.
e. Ensure pushbutton stations are mounted at the proper height and orientation.
f. Provide a neat workmanship in the installation of any wiring harnesses, control
units, wiring panels, push button stations.
g. Follow manufacturer’s recommendations regarding installation and weatherproofing.
h. Documentation
1) Each APS shall be provided with the following documentation:
2) Complete and accurate installation wiring guide.
3) Contact name, address, and telephone number for the representative, manufacturer, or distributor for warranty repair.
4) If requested supply schematics for all electronics. One schematic diagram
shall be provided for pushbutton stations, panels, central control units or
control units, along with any necessary installation instructions.
4. Radar Detection Equipment and Cable
a. Manufacturing
1) Radar detection equipment and cable shall follow manufacture installation
requirements and city construction details.
2) Radar detection shall connect the controller to central control unit through
SDLC compatible c able. 3) Radar detection shall connect the communication modem to central control
unit through ethernet cable.
4)
b. Support
1) The radar detector manufacturer shall provide both training and technical
support services .
c. Documentation
1) Radar detector documentation shall include an instructional training guide
and a comprehensive user guide as well as an installer quick-reference
guide and a user quick-reference guide. 2) The radar detector manufacturer shall supply the following documentation
and test results at the time of the bid submittal:
a) FCC CFR 47 certification (frequency compliance)
b) IED 6100-4-5 class 4 test report (surge)
5. Hybrid Vehicle Detection System and Cable
a. Hybrid vehicle detection equipment and cable shall follow manufacture
installation requirements and city construction details.
b. The hybrid detection system shall connect the controller to central unit through
SDLC compatible cable.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 104
TRAFFIC SIGNALS
Page 104 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c. The hybrid detection system shall connect the communication modem to central
control unit through ethernet cable.
d. The supplier of the video detection system must supervise the installation and
testing of the video and computer equipment. A factory certified representative
from the supplier must be on site during installation. e. Install the detector in accordance with the manufacturer’s recommendations in
order to achieve the detection areas as shown on the Drawings.
f. The detector mounts shall be neat and plumb.
g. Hybrid detection c ables shall be installed in the conduit system at the same
time as the other signal cables.
6. Emergency Vehicle Preemption Equipment and Cable
a. Emergency vehicle preemption system equipment required in the Drawings
will be furnished and installed by the Contractor.
b. Where practical, emergency vehicle preemption receiver units shall be mounted to a rigid metal arm and banded to the mast arm pole upright on the
intersection corner designated on the Drawings.
c. The Inspector shall determine if the roadway sight line permits this type of
emergency vehicle preemption installation.
d. The emergency vehicle preemption receiver units shall be mounted on the mast arms for the intersection approaches as designated on the Drawings.
e. Use stainless steel for all external screw s, nuts, and locking washers; do not use
any self -tapping screws unless approved by the Engineer or City.
f. All equipment shall be installed and wired in a neat and orderly manner in
conformance with the manufacturers’ instructions.
g. Emergency Preemption Detector Cables shall be installed continuous with no splices between the Emergency Preemption Detector and the cabinet.
h. All connections from the Emergency Preemption Phase Selector to the cabinet
wiring shall be made at the termination panel. The termination panel shall have
AC+ Lights, AC -, and a switched logic ground. The switched logic ground
feeds all the pre-empt inputs to the Emergency Preemption Phase Selector. When switched off by the pre-emption disconnect switch, the traffic controller
shall not be affected by pre-empt calls from the optical pre-emption system. A
minimum of two test buttons shall be provided. If there are more than two pre-
empt runs, a button for each shall be installed. A chart or print out, indicating
the program steps and settings shall be provided along with the revised cabinet
wiring diagrams.
7. Battery Back -up (BBU) System for Signal Cabinets
a. Mount the BBU system as shown in the plans.
8. Multi -Conductor Cable
a. Cables shall be installed in conduit unless indicated as an "overhead" cable run.
1) All conduits must be in accordance with Section 26 05 33.
2) Conduit must be continuous, reasonably dry, completely free of debris, and
without sharp projections, edges, or short bends. b. If required by the Inspector, the Contractor shall demonstrate that the conduit is
dry and free of debris by pulling a swab and/or mandrel through the conduit.
The conductors shall be installed in a manner so as to ensure against harmful
stretching of the conductors or damage to the insulation.
c. Installation methods shall conform to the recommendations of the cable
manufacturer.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 105
TRAFFIC SIGNALS
Page 105 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
d. The Contractor shall furnish, at the request of the Transportation Management
Manager or designee a copy of the manufacturer's recommendations, which
shall include methods of attaching pull cable, pulling tension per conductor
size and per radius of conduit bend, and the type of lubricant to be used.
e. All cables in a given conduit run shall be pulled at the same time and the conductors shall be assembled to form 1 loop in such a manner that the pulling
tension is equally distributed to all the cables.
f. Long, hard pulls will necessitate the use of pulling eyes.
g. For short runs, the cables may be gripped directly by the conductors by
forming them into a loop to which the pull wire or rope can be attached.
h. The insulation on each conductor shall be removed before the loop is formed.
i. The method used will depend on the anticipated maximum pulling tension in
each case.
j. In existing conduit where new cables are to replace existing cables, the existing
cables may be used to pull in the new cables. k. At locations where, new cables are to be added to existing cable runs, the
existing cables shall first be pulled out, the new cables are to be added to the
existing cables to form 1 cable pull (no slipping if any wires).
l. Installation and removal shall be done in such a way as to prevent damage to
the existing and/or new cables.
m. In the event of damage, the Contractor shall bear the responsibility of providing
the material and labor for replacement of defective cables at no extra cost to the
City.
n. All conduit runs shall be measured accurately and precisely for determining
cable lengths to be installed.
o. A conduit run measurements shall take place in the presence of the Inspector. p. The Inspector shall record all cable measurements and include the distances on
an as -built drawing.
q. In locations where new cables are to replace existing cables, the Contractor
may use the removed cables as a measuring device to determine the lengths of
the new cables to be installed. r. However, this does not relieve the Contractor of his responsibility to record
accurate measurements of all cable lengths.
s. The manufacturer's recommended maximum pulling tensions shall not be
exceeded under any circumstances.
t. The cable shall be fed freely off the reel into the conduit without making a
reverse curve. u. At the pulling end, the pull wire and cables shall be drawn from the conduit in
direct line with the c onduit.
v. Sheaves or other suitable devices shall be used as required to reduce any
hazards to the cable during installation.
w. The cables shall be adequately lubricated to reduce friction and further minimize possible damage.
1) Such lubricants shall not be the grease or oil type used on lead sheathed
cables, but shall be 1 of several commercially available wire pulling
compounds that are suitable for PVC sheathed cables.
2) They shall consist of soap, talc, mica, or similar materials and shall be
designed to have no deleterious effect on the cables being used.
x. Cables shall be neatly trained to their destinations.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 106
TRAFFIC SIGNALS
Page 106 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
y. The Contractor shall adhere to the cable manufacturer's recommended values
for the minimum bending radii to which cables may be bent for permanent
training during installation.
1) These limits do not apply to conduit bends, sheaves, or other curved
surfaces around which these cables may be pulled under tension while being installed.
2) Larger radius bends are required for such conditions.
z. Wire and Cable
1) All wire and cable shall conform to the requirements shown in the
Drawing s, except wire and cable specifically covered by other Items of this
Contract.
aa. Controller Cabinet Wiring
1) Wiring for the controller cabinet shall consist of connecting (1) signal
wires, (2) loop detector wires, (3) power wires, (4) ground wires, and (5)
pedestrian push button wires to their respective terminals in the cabinet. 2) In the controller cabinet, stranded signal conductors from the field shall be
stripped back and a solderless terminal connector (spade lug) shall be
attached by means of a crimping tool.
3) These terminal Connectors shall be inserted under the binder head screw
and tightened securely.
4) Other wiring for the controller shall be completed as shown on the wiring
diagrams and in the instructions furnished with the controller by the
manufacturer.
5) All field wiring in cabinets shall be neatly installed. Incoming cables shall
be trained to their destination and neatly laced together.
a) All spare wires shall be trimme d and neatly coiled with the ends taped. b) Detector lead-in cables shall have their insulation jackets removed
from their terminal strip connection to the bottom of the cabinet.
6) Pedestrian push buttons shall have a ground wire that is completely
isolated a nd independent from all other ground wires.
a) This wire shall be connected to the designated terminal in the controller cabinet.
b) A pedestrian isolation board shall be in place.
bb. Signal Head Wiring
1) No splicing of cable shall be allowed.
2) Conductors shall run as follows:
a) An unbroken 20-conductor cable and 1 bare #8 shall run from the controller cabinet to each pole pier.
b) An unbroken 7 conductor, #14 AWG (or larger) cable shall run from
the signal pole base to each signal head (5-section, 4-section and 3-
section) an unbroken 4 conductor, #14 AWG cable to each pedestrian
signal head. 3 conductor, #14 AWG (or larger) shall run to each pedestrian push button or APS unit.
c) Each cable shall be identified as referenced on the pole wir ing detail
sheet provided in the Drawings with permanent marking labels
(Panduit type PLM standard single marker tie, Thomas and Betts type
548M or equivalent) at each ground box, pole base and controller.
cc. Luminaire Wiring
1) 3 #10 XHHW cables shall run from service disconnect in parallel around
the intersection as on the Drawings .
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 107
TRAFFIC SIGNALS
Page 107 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2) Luminaire wiring connection may be made in the nearest ground box to the
traffic signal pole; such connection shall be placed in a water tight seal.
a) If more than 3 wires are splice together in the traffic signal cabinet then
a Kearney connector (or approved equivalent) shall be used as
required. 3) Run 2 #8 cables from terminal panel in signal pole to luminaire.
dd. Terminals
1) The ends of all stranded wires from the controller cabinet and from the
signal h eads shall be twisted at least 3 turns and wire nut applied in the
base of the signal structure.
ee. Identification of Signal Wires and Cables
1) IMSA color coded signal cable shall be used for all signal systems.
a) Colors shall be continuous from the point of origin to the point of
termination.
2) Each signal cable, detector lead-in cable and communication cable shall be designated with permanent marking labels or (Panduit type PLM, Thomas
and Betta type 548M standard single marker type or equivalent) and color
coded tape at each pull box and in the controller cabinet.
9. Insulated Electrical Cable a. Perform work in accordance with the details shown on the plans.
10. Ground Conductors
a. Perform work in accordance with the details shown on the plans.
11. Ground Rod
a. Properly install and connect a ground rod for each controller cabinet, power
drop and signal pole pier to reduce any extraneous voltage to a safe level.
b. The ground rod shall be located so as to minimize the length of the grounding-
conductor run. c. For pole mounted cabinets a grounding rod and grounding conductor shall be
installed at the nearest foundation or ground box.
d. All grounding circuits shall be s ubstantial and permanent and shall be
electrically continuous with an ohms -to-ground resistance not to exceed 10
ohms when tested by volt-ohm-meter.
e. UFER grounding shall be used for illumination poles.
f. Grounding Connectors and Electrodes
1) When the location precludes driving a single ground rod to a depth of 8
feet (2.4 m), or when a multiple ground rod matrix is used to obtain the
required resistance to ground, ground rods shall be spaced at least 6 feet
apart and bonded by a minimum No. 6 AWG copper wire. 2) Connection of grounding circuits to grounding electrodes shall be by devices
which will ensure a positive, fail-safe grip between the conductor and the
electrode (such as lugs or pressure connectors).
a) No splice joint will be permitted in the grounding c onductor.
3) Each grounding rod shall be driven into the ground to a depth sufficient to provide the required resistance (10 ohms) between electrodes and ground.
12. Ground Boxes
a. Use established industry and utility safety practices when installing or
removing ground boxes located near underground utilities. Consult with the
appropriate utility company before beginning work.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 108
TRAFFIC SIGNALS
Page 108 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b. Fabricate and install ground boxes in accordance with the details, dimensions,
and requirements shown on the plans. Install ground box to approved line and
grade.
c. Lube bolts, clean out cover rim, and clean ground box inside and out prior to
final inspection. d. Removal
1) Remove existing ground boxes and concrete aprons. Uncover conduit to a
sufficient distance so that 90-degree bends can be removed and conduit
reconnected. Clean the conduit in accordance with Item 618, “Conduit.”
Replace conduit within 5 ft. of the ground box. Remove old conductors and
install new conductors as shown on the plans. Backfill area with material
equal in composition and density to the surrounding area. Replace
surfacing material with similar material to an equivalent condition.
13. Traffic Signal Structures a. The Contractor shall install all traffic signal structures in accordance with the
Drawings.
1) Deviation from the Drawings because of physical obstructions, such as
overhead utilities or in appropriate mast arm length to fit a relocated
foundation, shall be worked out with the Inspector and approved prior to installation.
2) Stake the traffic signal pole locations for verification by the City.
b. Poles shall have nuts on top and bottom of the pole base plate.
1) Anchor bolts for mast arm signal poles shall be set so that 2 are in tension
and 2 are in compression.
2) The exposed length of the anchor bolt between the top of the f oundation and the bottom of the leveling nut should not exceed one bolt diameter.
c. The traffic signal pole heights and mast arm lengths shown on the Drawings
and in the material summary are to be used for bidding purposes only.
d. Prior to fabrication, the Contractor, in cooperation with the Inspector, shall
make field measurements to determine the actual pole height necessary to ensure a vertical clearance of 17 feet minimum and 19 feet maximum from the
roadway surface to the bottom of the lowest point on the signal head assembly
or mast arm and to determine the mast arm lengths required to mount the traffic
signal heads over the traffic lanes.
1) The masts arms shall be straight and level in the area where the signal
heads are attached.
2) These field measurements and evaluations shall be determined from the
actual field location of the pole foundations, considering all above and
below ground utilities and the existing roadway elevations and lane widths.
e. Transformer bases for pedestal poles shall be leveled and tightly secured to the
foundation before the structure is placed on the base. 1) If shims are required for leveling, total shim height shall not exceed 1/2
inches.
2) Foundation anchor bolts shall extend a minimum of 1 inch through each
nut in the base.
f. Exc ept as modified herein, erection of traffic signal structures shall be in
accordance with the applicable Specifications and standards of the AISC
Manual of Steel Construction.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 109
TRAFFIC SIGNALS
Page 109 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) Erecting equipment shall be suitable for the Work and shall be in proper
working condition.
2) Where parts cannot be assembled or fitted properly as a result of errors in
fabrication or deformation due to handling or transportation shall be
reported immediately to the Inspector. 3) Straightening of plates and angles or other shapes shall be done by
approval of the manufacturer.
4) No corrections will be allowed that will void the manufacturer's warranty.
5) A letter from the manufacturer approving the corrections shall be required
or the material may be rejected by the Inspector.
g. Use established industry and utility safety practices when working near
underground or overhead utilities. Consult with the appropriate utility
company before beginning such work.
h. Erect structures after foundation concrete has attained its design strength.
i. The s teel structure frame shall be lifted as shown in the manufacturer's specifications and all match marking shall be followed.
1) Temporary bracing shall be used wherever necessary to support all loads to
which the structure may be subjected, including equipment, operation, and
material loading.
2) Such bracing shall be left in place as long as may be required for safety.
3) The various members, after being assembled, shall be aligned and adjusted
accurately before being fastened.
4) Fastening of splices on compression members shall be done after the
abutting surfaces have been brought completely into contact.
5) No welding or bolting shall be done until the structures have been properly
aligned. j. Bearing surfaces and surfaces which will be in permanent contact with each
other shall be cleaned before the members are assembled.
1) Bearing plates shall be set in exact position and shall have a full and even
bearing upon the concrete.
2) As erection progresses, the Work shall be bolted to take care of all dead load, wind and erection stresses.
3) All erection bolts used in welded construction may be tightened securely
and left in place.
4) If removed, the holes shall be filled with plug welds.
k. Field bolting shall be in accordance with the requirements specified for shop
fabrication. 1) Untrue holes shall be corrected by reaming.
2) Where the surface of a bolted part has a slope of more than 1:20, a beveled
washer shall be used to compensate for the lack of parallelism.
3) Bolt heads and nuts shall be drawn tight against the Work with a suitable
wrench not less than 15 inches long. 4) Bolt heads shall be tapped with a hammer while the nut is being tightened.
l. Field Painting of Structures
1) Surfaces where the shop coat of paint has been damaged shall be retouched
after installation.
a) The cleaning, pretreatment, and priming of welds and the areas
adjacent thereto shall be done promptly after the acceptance of the
weld.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 110
TRAFFIC SIGNALS
Page 110 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b) Care shall be taken to properly mask signals heads, signs, pedestrian
pushbuttons and their mounting hardware to keep paint from splashing
onto these components.
c) Masking shall be removed after completion of the painting process.
d) A sufficient number of paint coatings shall be applied to each structure to result in a uniform finish once completed.
e) All structures shall be air blasted using high pressure air to remove
peeled paint and dust prior to application of new paint.
m. Bolted parts shall fit solidly together when assembled and shall not be
separated by gaskets or any other interposed compressible material.
1) When assembled, all joint surfaces, including those adjacent to the bolt
heads, nuts, or washers, shall be free of scale, except tight mill scale, and
shall also be free of burrs, dirt, and other foreign material that would
prevent solid seating of the parts.
2) Each fastener shall be tightened to at least the minimum bolt tension as recommended by the pole manufacturer using ASTM A325 or A490 bolts
for the size of fastener used.
3) Threaded bolts shall be tightened with properly calibrated wrenches or by
the "turn-of-nut" method.
4) Bolts may be installed without hardened washers when tightening takes
place by the "turn-of-bolt" method. Any bolt tightened by the calibrated
wrench method (or by torque control) shall have a hardened washer under
the element (nut or bolt head) turned in to a point not closer than 7/8 of the
bolt diameter from the center of the washer.
n. Grouting
1) The Contractor shall perform all Work required to complete the grout work associated with installing the signal structure and furnish all supplementary
items necessary for its proper installation.
o. Where signal poles and/or mast arms exist on raised foundations that are to be
removed and installed on new foundations, the Contractor shall store these
poles, mast arms, street lights, and wiring until they can be installed on their new foundations.
p. Vibration dampers
1) Dampers shall be installed using Astro Sign Brac or Signfix Aluminum
Channel or approved equivalent.
q. Signs
1) The Contractor shall furnish, install and relocate existing signs as shown in the Drawings.
2) Mast -arm signs shall be mounted with Astro-sign Brac or Signfix
aluminum channel or equivalent as approved by the Engineer.
3) Metro street name signs shall be mounted level with the ground as shown
on the City’s Standard Details.
14. Foundations
a. All foundations shall be staked by the Contractor and approved by the
Inspector prior to excavation.
1) While staking the pole locations, the Contractor, along with the Inspector,
shall be cognizant of pedestrian needs by verifying the location of the push
buttons and the pedestrian heads.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 111
TRAFFIC SIGNALS
Page 111 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
b. Concrete foundations for signal structures shall be located so that the closest
face is a minimum of 3 feet from the face of the nearest vertical curb.
1) Before excavating foundations probe to determine the location of utilities
and structures.
2) Foundations shall be paid for once, however, payment for additional work due to unforeseen conditions will be negotiated based on number of labor
hours and materials used.
3) Furnish all supplementary items necessary for proper foundation
installation.
c. Excavation for all foundations shall be done in accordance with lines and
depths indicated on the Drawings .
1) All loose material shall be remove d from the excavation before concrete is
placed.
2) Any water shall be removed by pumping or bailing.
3) The use of explosives will not be permitted. d. Foundations shall be constructed to the dimensions shown on the Drawing s.
1) The Contractor is required to make certain that the top of the finished
foundation is level and formed.
2) Anchor bolts and conduits shall be held rigidly in place by a template until
the concrete is set.
e. A mechanical vibrator shall be used for compacting and working the concrete.
After the concrete has been placed and the top struck off, it shall be covered
with wet cotton or burlap mats or other appropriate form of curing, for not less
than 96 hours.
f. All bracing and templates for anchor bolts shall remain in place for 96 hours
after the concrete is poured. 1) During that time, the anchor bolts and conduit shall not be subjected to any
applied strain.
g. Backfill shall be tamped with mechanical tamps in 6 inches layers to the
density of the surrounding ground.
1) Where excavation is made in the roadway shoulder, the shoulder shall be replaced with material equivalent to the original composition.
h. All excavated material, not required for backfill, shall be promptly removed
and disposed of by the Contractor, outside the limits of the Project .
1) The Work Site shall be kept clean and neat at all times.
i. No concrete shall be placed when the atmospheric temperature drops below 40
degrees Fahrenheit (temperature reading taken in the shade away from artificial heat) unless permission to do so is given by the Inspector.
1) Refer to Section 03 30 00.
j. The City shall supply to the Contractor the controller cabinet anchor bolts and
specific cabinet templates , when the City furnishes the controller cabinet.
k. The cabinet door shall open to the north. Controller face plate shall also face north. Field terminations shall be done on the south side of the cabinet.
l. Pole anchor bolts shall be aligned to be parallel to the tangent of the street curb
that the pole is intended to serve.
m. Tubing used to form pole foundations shall not be visible and all exposed
concrete shall be finished with vinyl concrete patch mix to provide a smooth
quality finish with all voids filled and no aggregate exposed.
n. The cost of the Work shall be included in the unit bid price for this item.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 112
TRAFFIC SIGNALS
Page 112 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
15. Hardware Signal Pole Paint
a. Requirements for poles and railings
1) Cleaning
a) The entire surface shall be cleaned free of dirt, grime and oils before
applying the primer coat. b) Use vinegar wash applied with a sponge or cloth over the entire
surface.
2) Sanding
a) Spot sanding may be required in order to remove flaking paint and to
provide a smooth surface.
3) Priming
a) Primer coat shall be applied with a brush or roller.
b) The entire surface shall be covered, even over existing painted or
galvanized surfaces.
c) Spraying is not permissible. 4) Finish coat
a) Finish coat shall be applied with a brush or roller.
b) The entire surface shall be covered, even over existing painted or
galvanized surfaces.
c) Spraying is not permissible.
5) Parking meter housings, luminaire heads, signal heads, photo control eyes,
pedestrian push buttons and sign faces shall be protected for paint splash.
6) Controller cabinets and circuit boxes mounted to poles shall be painted to
match the color of the pole.
7) The ambient temperature s hall be 40 degrees Fahrenheit and rising and dry
conditions. b. Requirements for traffic signal heads
1) Traffic signal heads should be cleaned by wiping it with a damp sponge or
rag to remove all the dust and dirt.
2) Lens and back plate should be masked off.
3) The outside of the traffic signal head should be painted traffic yellow (RAL 1023) and the inside of the lens visors should be painted flat black.
4) The outside of pedestrian signal head should be painted traffic yellow
(RAL 1023).
5) The ambient temperature shall be 40 degrees Fahrenheit and rising and dry
conditions.
16. Signal Controller
a. Each controller cabinet shall be modified for use at a specific intersection in
accordance with the instructions included in the Drawing s.
1) Each cabinet shall be prepared and tested for on-the-street use
b. Connect all field wiring s to the controller-cabinet assembly. 1) T he City will program the controller, the conflict monitor, and other
equipment in the controller cabinet and turn on the traffic signals.
c. All wiring modifications made in conjunction with preparing the cabinet for
use at a specific intersection shall be documented on the cabinet prints for that
intersection.
17. Roadside Flashing Beacon Assembl y
a. Installation
1) Install in locations as shown in Drawings .
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 113
TRAFFIC SIGNALS
Page 113 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2) Stake the pole location for approval by City or Engineer.
3) Install pole, breakaway base, connectors, wiring, signal beacons, sign and
foundation as shown on the Drawings or as directed.
4) Install the flasher control assembly on the electrical service pole.
5) Install watertight breakaway electrical fuse holders in all line and neutral conductors at breakaway base.
6) Use established industry and utility safety practices to erect assemblies
near overhead or underground utilities.
7) Consult with the appropriate utility company prior to beginning such work.
b. Relocation
1) Disconnect and isolate the electrical power supply prior to removal of the
assembly.
2) Remove existing assembly as directed.
3) Unless otherwise directed, salvage existing components such as sign,
beacons, pole, and base. 4) Repair or replace lost or damaged components as directed.
5) Relocate existing assembly to the location shown on the plans or as
directed.
6) Install existing assembly at new foundations.
7) Remove existing foundations.
8) Accept ownership of unsalvageable materials and dispose of in accordance
with federal, state, and local regulations.
c. Removal
1) Disconnect and isolate existing electrical power supplies prior to removal
of the assembly.
2) Remove existing sign panel, beacons, pole, and base from existing assembly.
3) Store items to be reused or salvaged without damaging.
4) Store sign panels above the ground in a vertical position at locations shown
on the plans or as directed.
5) Accept ownership of unsalvageable materials and dispose of in accordance with federal, state, and local regulations.
6) Unless otherwise shown on the plans, remove abandoned foundations,
including steel, to 2 ft. below the finished grade.
7) Backfill with material equal in composition and density to the surrounding
area, and replace any surfacing, such as asphalt pavement or concrete
riprap, with like material to equivalent condition.
18. School Zone Flasher Assembly
a. Installation
1) Install in locations as shown in Drawings.
2) Stake the pole location for approval by City or Engineer. 3) Install pole, breakaway base, connectors, wiring, signal beacons, controller,
modem, sign and foundation as shown on the Drawings or as directed.
4) Install watertight breakaway electrical fuse holders in all line and neutral
conductors at breakaway base.
5) Use established industry and utility safety practices to erect assemblies
near overhead or underground utilities.
6) Consult with the appropriate utility company prior to beginning such work.
b. Relocation
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 114
TRAFFIC SIGNALS
Page 114 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) Disconnect and isolate the electrical power supply prior to removal of the
assembly.
2) Remove existing assembly as directed.
3) Unless otherwise directed, salvage existing components such as sign,
beacons, pole, and base. 4) Repair or replace lost or damaged components as directed.
5) Relocate existing assembly to the location shown on the plans or as
directed.
6) Install existing assembly at new foundations.
7) Remove existing foundations.
8) Accept ownership of unsalvageable materials and dispose of in accordance
with federal, state, and local regulations.
c. Removal
1) Disconnect and isolate existing electric al power supplies prior to removal
of the assembly. 2) Remove existing sign panel, beacons, pole, and base from existing
assembly.
3) Store items to be reused or salvaged without damaging.
4) Store sign panels above the ground in a vertical position at locations shown
on the plans or as directed.
5) Accept ownership of unsalvageable materials and dispose of in accordance
with federal, state, and local regulations.
6) Unless otherwise shown on the plans, remove abandoned foundations,
including steel, to 2 ft. below the finished grade.
7) Backfill with material equal in composition and density to the surrounding
area, and replace any surfacing, such as asphalt pavement or concrete riprap, with like material to equivalent condition.
19. Rectangular Rapid Flashing Beacon (RRFB) Assembly
a. Installation
1) Install in locations as shown in Drawings. 2) Stake the pole location for approval by City or Engineer.
3) Install pole, breakaway base, connectors, wiring, control panel, solar panel,
battery, light bar, signage, pedestrian push button, and foundation as shown
on the Drawings or as directed.
4) Install watertight breakaway electrical fuse holders in all line and neutral
conductors at breakaway base.
5) Use establis hed industry and utility safety practices to erect assemblies
near overhead or underground utilities.
b. Relocation
1) Disconnect and isolate the solar panels prior to removal of the assembly.
2) Remove existing assembly as directed. 3) Unless otherwise directed, salvage existing components such as sign, light
bar , solar panel, pole, and base.
4) Repair or replace lost or damaged components as directed.
5) Relocate existing assembly to the location shown on the plans or as
directed.
6) Install existing assembly at new foundations.
7) Remove existing foundations.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 115
TRAFFIC SIGNALS
Page 115 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
8) Accept ownership of unsalvageable materials and dispose of in accordance
with federal, state, and local regulations.
c. Removal
1) Disconnect and isolate solar panel prior to removal of the assembly.
2) Remove existing sign panel, light bar, solar panel, pole, and base from existing assembly.
3) Store items to be reused or salvaged without damaging.
4) Store sign panels above the ground in a vertical position at locations shown
on the plans or as directed.
5) Accept ownership of unsalvageable materials and dispose of in accordance
with federal, state, and local regulations.
6) Unless otherwise shown on the plans, remove abandoned foundations,
including steel, to 2 ft. below the finished grade.
7) Backfill with material equal in composition and density to the surrounding
area, and replace any surfacing, such as asphalt pavement or concrete riprap, with like material to equivalent condition.
20. Powder Coating Traffic Signal Structures
a. All galvanized exterior surfaces shall be coated with a Urethane or Triglycidyl
Isocyanurate (TGIC) Polyester Powder to a minimum film thickness of 2.0 mils (0.002”).
b. Prior to application, the surfaces to be powder coated shall be mechanically
etched by brush blasting (Ref. SSPC-SP7) and the zinc coated substrate
preheated to 450 degrees for a minimum of one hour in a gas fired convection
oven.
c. The coating shall be electrostatically applied and cured in a gas fired convection oven by heating the zinc coated substrate to a minimum of 350
degrees Fahrenheit and a maximum of 400 degrees Fahrenheit.
d. The thermosetting powder resin shall provide both intercoat as well as substrate
fusion adhesion that meets 5A or 5B classifications of ASTM D3359.
21. PTZ Camera and Cable
a. Assembly
1) Shall assemble individual sections of PTZ camera assembly in accordance
with the manufacture’s installation manual specifications.
2) Assemble, mount, and orient PTZ camera assembly as per the plans.
b. Wiring
1) CAT5E cable shall exit the metal pole thru a CBG liquid tight outlet
bushing.
2) Loop cable for water drainage before entering the PTZ camera assembly.
3) CAT5E cable shall be terminated on each end of the cable with RJ45 connectors wired specifically for T568B. Both ends must use the same
standard.
4) When terminating RJ45 connectors, the outer most insulation jacket shall
be inserted fully into the connector to only allow a maximum of 0.5 inches
untwisted pair allowable per ANSU/TIA 568B. 5) The ferrite provided by the manufacture shall be installed as close as
possible to the cameras RJ45 port.
6) Prior to mounting the PTZ camera after terminating each end of the
CAT5E cable, cable shall be tested and pass by appropriate network cable
tester.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 116
TRAFFIC SIGNALS
Page 116 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
c. Mounting
1) Two (2) rubber insulation shall be used on pole prior to mounting PTZ
Camera wall mount bracket.
22. Communication Modem and Antenna
a. Communication modem shall
1) Be installed inside the traffic signal cabinet.
2) Be instead in a neat and serviceable manner.
3) Plug the power supply to the Controller unit receptor or clean power panel.
b. Antennas shall
1) Be installed on the top of the cabinet on the sloped sections or on bracket.
2) Follow manufacture instruction carefully to water seal the antenna to
prevent water leaking.
3.4 FIELD QUALITY CONTROL
A. Field Tests and Inspections
1. Initial testing of all materials, construction items, or products incorporated in the
Work will be perform ed at the direction of the City.
a. Embankment construction shall conform to 31 24 00.
b. All backfill of structures shall conform to 33 05 10. c. Excavation s hall conform to 31 23 16.
2. The failure to require tests of materials by the Inspector shall in no way relieves the
Contractor of his responsibility of furnishing materials conforming to these
Specification s.
3. Tests, unless otherwise specified, shall be made in accordance with the latest methods
of the ASTM or other approved test methods.
a. The Contractor shall provide such facilities, as the Inspector may require, for
the collecting and forwarding of samples and shall not use the materials represented by the samples until tests have been made.
b. The Contractor shall furnish adequate samples without charge.
4. Signal cables
a. The Transportation Management Manager or designee may require that all cables shall be checked for insulation resistance upon installation and prior to
termination. The tests shall be made with a test set operating at a minimum of
500 volts DC applied to the conductors.
b. Each conductor in the multi-conductor signal cables shall be tested for insulation
resistance relative to each other and to the outer covering of the cable. The
minimum acceptance value for insulation resistance shall be 1 megohm.
5. Controller cabinet
a. If the controller cabinet is to be supplied by the Contractor for this Project , the
cabinet shall be tested at a facility located within the Dallas/Fort Worth area. b. The Contractor shall notify the Inspector or his representative a minimum of 3
Working Days prior to beginning the test period of his intent to test a cabinet or
group of cabinets.
c. At this point, the City may schedule an inspection team and notify the Contractor
of the earliest date and time the team can visit. d. Each cabinet shall be tested with a controller unit for a minimum of 24 continuous
hours.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 117
TRAFFIC SIGNALS
Page 117 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
1) The cabinet test will include conflict monitor functions, detector unit
function and load switch operation for conformance with cabinet hardware
specifications, etc.
2) The cabinet must successfully pass all items o therwise the test is restarted
for another 24-hour period.
B. Non-Conforming Work
1. In the event that a material, construction item, product incorporated in the Work,
embankment, backfill, excavation or any other item tested, fails to satisfy the
minimum requirements of the initial test described above, appropriate prove-out tests
shall b e made as directed by the Inspector to determine the extent of the failure and to
verify that corrective measures have brought the Item up to Specification
requirements.
a. The cost of all testing necessary to determine the extent of the failure and the
adequacy of the corrective measures shall be the responsibility of the
Contractor.
3.5 SYSTEM STARTUP
A. The Contractor shall coordinate with the Inspector to have a qualified technician on the Site when the traffic signal is placed into operation.
B. During the 30 day test period, the contractor shall be responsible for any trouble calls and
shall make all necessary action to repair the problem. The City will be responsible for
traffic signal timing operation only.
C. The Contractor shall provide a local telephone number (not subject to frequent changes)
where trouble calls are to be received on a 24-hour basis.
D. The Contractor's response time to reported calls shall be within a reasonable travel time,
but not more than 2 hours maximum.
E. Appropriate repairs shall be made within reasonable time.
1. If, after further diagnosing the problem, the qualified technician determines the
problem is in the equipment supplied by others, the Contractor shall notify the
Inspector.
F. 30 days test period will restart after completing each signal failure due to workmanship
G. No extra compensation will be allowed for fulfilling the requirements stated above.
3.6 CLOSEOUT ACTIVITIES
A. Prior to final acceptance by the City, the Contractor is responsible for removal,
replacement and reinstallation of any damaged material at the Contractor's expense.
B. Whenever the Work provided for and contemplated under the Contract has been found by
the Inspector to be completed to his / her satisfaction on any individual signalized
intersection, or interconnected system of signalized intersections, as shown in the
Drawing s, final cleaning up of said signalized intersection has been performed and the
traffic signal equipment supplied by the or has operated continuously for a minimum of 30 days in a satisfactory manner, the Contractor will be released from further maintenance on
that particular intersection.
1. Such partial acceptance will be made in writing and shall in no way void or alter
any terms of the Contract.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 118
TRAFFIC SIGNALS
Page 118 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
2. If equipment fails, a new 30-day test period will start when the equipment has been
repaired or replaced.
3.7 PROTECTION
A. Prevent any property damage to property owner's poles, fences, landscaping,
mailboxes, etc., and repair any damages.
B. Provide access to all driveways during construction.
C. Protect all underground and overhead utilities, including sprinkler systems, and repair any
damages .
3.8 MAINTENANCE
A. While performing Work under this Contract, the Contractor bears the sole risk of loss
for damages to or destruction of any traffic signal equipment or appurtenances, on
equipment that was not to be replaced or installed under this Contract, but which was
damaged or destroyed through the fault or negligent acts of the Contractor.
B. The Contractor shall replace such damaged or destroyed equipment, etc., at no cost to
the City, regardless of whether or not the damaged or destroyed equipment, etc., was a
part of this Contract or any warranties under this Contract.
C. The Contractor's responsibility shall cease under this paragraph upon written
acceptance of an intersection by the City.
D. The Contractor's responsibility for full operation and maintenance of all traffic signal
equipment shall begin when he starts any type of Work which effects active intersection
control at the first intersection and shall extend through the period of final Project
acceptance of each intersection.
E. This maintenance responsibility includes existing controllers/masters, existing
interconnect and cabling systems, existing signal indications, existing vehicle detectors,
new controllers/masters, new signal hardware, new cabling systems, and other hardware
elements which are considered part of either the existing or the new traffic signal system.
F. It is recognized that the City may continue to make a first response to any trouble call.
Action on such response will, however, be limited to placing the intersection on flash,
replacing load switches or detector amplifiers, erecting temporary control devices, requesting immediate traffic control by uniformed police officer, or other such action
deemed necessary to provide a safe operation.
1. Such action will in no way relieve the Contractor of his operation and maintenance
responsibility .
G. The Contractor shall be required to notify the Inspector or Transportation Management
Division at least 24 hours in advance of any planned controlled change-outs or any other
operational procedures.
H. Battery Back-up System
1. The BBU shall provide voltmeter standard probe input-jacks (+) and (-) to read the
exact battery voltage drop at the inverter input.
2. The BBS shall be equipped with both Input and Output AC circuit breakers, and
with either a DC circuit breaker or fused battery harness.
3. All components, terminations, terminal blocks, relays, etc. shall be fully accessible.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 10 - 119
TRAFFIC SIGNALS
Page 119 of 119
CITY OF FORT WORTH Insert Project Name
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS City Project No. XXXXX
Revised March 11, 2022
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
11/19/2015 S. Arnold Various revisions and additions
3/11/2022 S Hobbs &
A Rahman
• Added electrical work requirements as section 1.2 and adjusted other sections
numbering
• Various additions/revisions added into section 1.3 including measurement,
payment, and new bid items
• Added/revised manufacturer warranty requirements under section 1.9
• Added products required for product submittals under section 1.7
• Revised and added product specifications under section 2.2
• Added installation requirements for new bid items under section 3.3
• Revised references and organization names to reflect current references and
names throughout document
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 1
ARTERIAL LED ROADWAY LUMINAIRES
Page 1 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
SECTION 34 41 20.01
ARTERIAL LED ROADWAY LUMINAIRES
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Roadway illumination assemblies
2. Roadway illumination foundations
3. Removal of roadway illumination assemblies
4. Relocation of roadway illumination assemblies
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
3. Section 03 30 00 – Cast-in-Place Concrete
4. Section 33 05 10 – Utility Trench Excavation, Embedment and Backfill
5. Section 33 05 30 – Location of Existing Utilities
6. Section 34 41 10 – Traffic Signals
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Roadway Illumination Assemblies
a. Measurement
1) Measurement for this Item shall be per each Roadway Illumination Assembly
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Rdwy Illum Assmbly” installed for:
a) Various types
c. The price bid shall include:
1) Furnishing Roadway Illumination Assembly, if required
2) Assembling and installing each Roadway Illumination Assembly
3) Poles
4) Arms
5) Anchor bolts
6) Fixtures
7) Internal electrical conductors
8) Connection and mounting hardware
9) Bases
10) Lamps
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 2
ARTERIAL LED ROADWAY LUMINAIRES
Page 2 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
11) Preparing submittals
12) Exploratory excavation (as needed)
13) Coordination and notification
14) Assembly and transportation of all items
15) Excavation, hauling, disposal of excess material
16) Protection of the excavation
17) Clean-up
18) Testing
2. Ornamental Illumination Assemblies
a. Measurement
1) Measurement for this Item shall be per each Ornamental Assembly installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Ornamental Assmbly” installed for:
a) Various types
c. The price bid shall include:
1) Furnishing Ornamental Illumination Assembly, if required
2) Assembling and installing each Ornamental Assembly
3) Poles
4) Arms
5) Anchor bolts
6) Fixtures
7) Internal electrical conductors
8) Connection and mounting hardware
9) Bases
10) Lamps
11) Preparing submittals
12) Exploratory excavation (as needed)
13) Coordination and notification
14) Assembly and transportation of all items
15) Excavation, hauling, disposal of excess material
16) Protection of the excavation
17) Clean-up
18) Testing
3. Lighting Fixtures
a. When a pay item for Illumination Assembly exists:
1) Measurement
a) This Item is considered subsidiary to Illumination Assembly installation.
2) Payment
a) The work performed and materials furnished in accordance with this Item are
subsidiary to the unit price bid per each “Rdwy Illum Assmbly” or “Ornamental
Assmbly” bid, and no other compensation will be allowed.
b. When a pay item for Illumination Assembly does not exist:
1) Measurement
a) Measurement for this Item shall be per each Lighting Fixture installed.
2) Payment
a) The work performed and materials furnished in accordance with this Item shall
be paid for at the unit price bid per each “Lighting Fixture” installed for:
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 3
ARTERIAL LED ROADWAY LUMINAIRES
Page 3 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
(1) Various types
(2) Various power
3) The price bid shall include:
a) Furnishing Lighting Fixture, if required
b) Assembling Lighting Fixture
c) Wiring connections
d) Disposal of any unused or replaced materials
e) Clean-up
4. Roadway Illumination Foundations
a. Measurement
1) Measurement for this Item shall be per each Roadway Illumination Foundation
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Rdwy Illum Foundation” installed for:
a) Various types
c. The price bid shall include:
1) Installing each Roadway Illumination Foundation
2) Reinforcing steel
3) Exploratory excavation (as needed)
4) Grounding rods
5) Coordination and notification
6) Excavation, hauling, disposal of excess material
7) Protection of the excavation
8) Clean-up
9) Testing
5. Contact Enclosure
a. Measurement
1) Measurement for this Item shall be per each Contact Enclosure installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Contact Enclosure” installed for:
a) Various mounting methods
c. The price bid shall include:
1) Furnishing and installing Contact Enclosure
2) Mounting materials
3) Clean-up
6. Furnishing and Installing Wood Light Pole
a. Measurement
1) Measurement for this Item shall be per each 40’ Wood Light Pole furnished and
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Furnish/Install 40’ Wood Light Pole”.
c. The price bid shall include:
1) Excavation
2) Furnishing and installing each 40’ Wood Light Pole
3) Furnishing, placement and compaction of backfill
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 4
ARTERIAL LED ROADWAY LUMINAIRES
Page 4 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
4) Clean-up
7. Furnishing and Installing Wood Light Pole Arm
a. Measurement
1) Measurement for this Item shall be per each 8’ Wood Light Pole Arm furnished and
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Furnish/Install 8’ Wood Light Pole Arm”.
c. The price bid shall include:
1) Furnishing and installing each 8’ Wood Light Pole Arm
2) Clean-up
8. Aluminum Electrical Conductors
a. Measurement
1) Measurement for this Item shall be per linear foot of Aluminum Electrical
Conductor installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item and
measured as provided under “Measurement” will be paid for at the unit price bid
per linear foot of “Alum Elec Conductor” installed for:
a) Various Sizes
c. The price bid shall include:
1) Furnishing and installing Aluminum Electrical Conductor
2) Testing
9. Conductor Reconnection
a. Measurement
1) Measurement for this Item shall be per each conductor reconnected.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Reconnect Conductor”.
c. The price bid shall include:
1) Reconnection of conductors using City approved method
2) Testing of connection
10. Street Light Pole Removal and Salvage
a. Measurement
1) Measurement for this Item shall be per each Street Light removed and salvaged.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Salvage Street Light Pole” performed.
c. The price bid shall include:
1) Removal and salvage of Street Light Pole
2) Maintain existing street light circuit including new ground box and reconnection of
circuits (if required by City)
3) Removal of existing street light pole foundation 2’ below grade, back fill with like
surrounding material
4) Delivery of salvaged materials to appropriate location
5) Clean-up
11. Street Light Pole Relocation
a. Measurement
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 5
ARTERIAL LED ROADWAY LUMINAIRES
Page 5 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
1) Measurement for this Item shall be per each Street Light Pole removed and
salvaged.
b. Payment
1) The work performed and materials furnished in accordance with this Item shall be
paid for at the unit price bid per each “Relocate Street Light Pole” performed.
c. The price bid shall include:
1) Removal and salvage of Street Light Pole
2) Delivery of salvaged materials to appropriate location
3) Replacement of pole to new location
4) Furnishing, placement and compaction of backfill material
5) Clean-up
1.3 REFERENCES
The publications listed below form a part of this specification to the extent referenced.
Publications are referenced within the text by their basic designation only. Versions listed shall
be superseded by updated versions as they become available.
A. American National Standards Institute (ANSI)
1. C136.2-2004 (or latest), American National Standard for Roadway and Area Lighting
Equipment—Luminaire Voltage Classification
2. C136.10-2010 (or latest), American National Standard for Roadway and Area Lighting
Equipment - Locking-Type Photocontrol Devices and Mating Receptacle Physical and
Electrical Interchangeability and Testing
3. C136.15-2011 (or latest), American National Standard for Roadway and Area Lighting
Equipment – Luminaire Field Identification
4. C136.22-2004 (R2009 or latest), American National Standard for Roadway and Area
Lighting Equipment – Internal Labeling of Luminaires
5. C136.25-2009 (or latest), American National Standard for Roadway and Area Lighting
Equipment – Ingress Protection (Resistance to Dust, Solid Objects and Moisture) for
Luminaire Enclosures
6. C136.31-2010 (or latest), American National Standard for Roadway Lighting Equipment
– Luminaire Vibration
7. C136.37-2011 (or latest), American National Standard for Roadway and Area Lighting
Equipment - Solid State Light Sources Used in Roadway and Area Lighting
B. American Society for Testing and Materials International (ASTM)
1. B117-09 (or latest), Standard Practice for Operating Salt Spray (Fog) Apparatus
2. D1654-08 (or latest), Standard Test Method for Evaluation of Painted or Coated
Specimens Subjected to Corrosive Environments
3. D523-08 (or latest), Standard Test Method for Specular Gloss
4. G154-06 (or latest), Standard Practice for Operating Fluorescent Light Apparatus for UV
Exposure of Nonmetallic Materials
C. Council of the European Union (EC)
1. RoHS Directive 2002/95/EC, on the restriction of the use of certain hazardous substances
in electrical and electronic equipment
D. Federal Trade Commission (FTC)
1. Green Guides, 16 CFR Part 260, Guides for the Use of Environmental Marketing Claims
E. Illuminating Engineering Society of North America (IESNA or IES)
1. DG-4-03 (or latest), Design Guide for Roadway Lighting Maintenance
2. HB-10-11 (or latest), IES Lighting Handbook, 10th Edition
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 6
ARTERIAL LED ROADWAY LUMINAIRES
Page 6 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
3. LM-50-99 (or latest), IESNA Guide for Photometric Measurement of Roadway Lighting
Installations
4. LM-61-06 (or latest), IESNA Approved Guide for Identifying Operating Factors
Influencing Measured Vs. Predicted Performance for Installed Outdoor High Intensity
Discharge (HID) Luminaires
5. LM-79-08 (or latest), IESNA Approved Method for the Electrical and Photometric
Measurements of Solid-Sate Lighting Products
6. LM-80-08 (or latest), IESNA Approved Method for Measuring Lumen Maintenance of
LED Light Sources
7. RP-8-00 (or latest), ANSI / IESNA American National Standard Practice for Roadway
Lighting
8. RP-16-10 (or latest), ANSI/IES Nomenclature and Definitions for Illuminating
Engineering
9. TM-3-95 (or latest), A Discussion of Appendix E - "Classification of Luminaire Lighting
Distribution," from ANSI/IESNA RP-8-83
10. TM-15-11 (or latest), Luminaire Classification System for Outdoor Luminaires
11. TM-21-11 (or latest), Projecting Long Term Lumen Maintenance of LED Light Sources
F. Institute of Electrical and Electronics Engineers (IEEE)
1. IEEE C62.41.2-2002 (or latest), IEEE Recommended Practice on Characterization of
Surges in Low-Voltage (1000 V and less) AC Power Circuits
2. ANSI/IEEE C62.45-2002 (or latest), IEEE Recommended Practice on Surge Testing for
Equipment Connected to Low-Voltage (1000 V and Less) AC Power Circuits
G. National Electrical Manufacturers Association (NEMA)
1. ANSI/NEMA/ANSLG C78.377-2008 (or latest), American National Standard for the
Chromaticity of Solid State Lighting Products
H. National Fire Protection Association (NFPA)
1. 70 – National Electrical Code (NEC)
I. Underwriters Laboratories (UL)
1. 1449, Surge Protective Devices
2. 1598, Luminaires
3. 8750, Light Emitting Diode (LED) Equipment for Use in Lighting Products
J. Definitions
1. Lighting terminology used herein is defined in IES RP-16. See referenced documents for
additional definitions.
i. Exception: The term “driver” is used herein to broadly cover both drivers and
power supplies, where applicable.
ii. Clarification: The term “LED light source(s)” is used herein per IES LM-80 to
broadly cover LED package(s), module(s), and array(s).
1.4 ADMINISTRATIVE REQUIREMENTS
A. Coordination
1. Notify City at (817) 392-7738 a minimum of 7 days before beginning Work on the Project.
2. Notify Inspector prior to pouring roadway illumination assembly foundations.
3. Coordinate with Traffic Services Inspector for pole types, template dimensions and anchor
bolts, and any questions about installing the foundations and conduit.
4. For location of City underground street luminaire cable and conduit call (817) 392-7738 or
(817) 392-8100.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 7
ARTERIAL LED ROADWAY LUMINAIRES
Page 7 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
5. Obtain and pay for all permits as required to Work in parkway.
B. Preinstallation Meetings
1. Attend pre-construction meeting.
1.5 LIGHTING SYSTEM PERFORMANCE
A. Energy Conservation
1. Connected Load
a. Luminaires shall have maximum nominal luminaire input wattage as specified for each
luminaire type in Appendix A.
2. Lighting Controls
a. See separate controls specification identified in section 1.2 above, if applicable.
b. See section 2.1-B below for driver control interface and performance requirements.
c. See section 2.1-K below for photocontrol receptacle requirements.
B. Photometric Requirements
1. Luminaires shall meet the general criteria provided in the body of this specification and the
particular criteria for each luminaire type defined in Appendix A.
1.6 REQUIRED SUBMITTALS FOR EACH LUMINAIRE TYPE DEFINED IN APPENDIX A
A. General submittal content shall include
1. Completed Appendix E submittal form
2. Luminaire cutsheets
3. Cutsheets for LED light sources
4. Cutsheets for LED driver(s)
a. If dimmable LED driver is specified, provide diagrams illustrating light output and
input power as a function of control signal.
5. Cutsheets for surge protection device, if applicable
6. Instructions for installation and maintenance
7. Summary of luminaire recycled content and recyclability per the FTC Green Guides,
expressed by percentage of luminaire weight
B. LM-79 luminaire photometric report(s) shall be produced by the test laboratory and include
1. Name of test laboratory
a. The test laboratory must hold National Voluntary Laboratory Accreditation Program
(NVLAP) accreditation for the IES LM-79 test procedure or must be qualified, verified,
and recognized through the U.S. Department of Energy’s CALiPER program. For more
information, see http://ts.nist.gov/standards/scopes/eelit.htm or
www.ssl.energy.gov/test_labs.html.
2. Report number
3. Date
4. Complete luminaire catalog number
a. Provide explanation if catalog number in test report(s) does not match catalog number
of luminaire submitted
1) Clarify whether discrepancy does not affect performance, e.g., in the case of
differing luminaire housing color.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 8
ARTERIAL LED ROADWAY LUMINAIRES
Page 8 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
2) If nominal performance of submitted and tested products differ, submit additional
LM-79 report(s) and derivation as indicated in Appendix C.
5. Description of luminaire, LED light source(s), and LED driver(s)
6. Goniophotometry
7. Colorimetry
C. Calculations and supporting test data per Appendix B indicating a lumen maintenance life of not
less than 50,000 operating hours
D. Computer-generated point-by-point photometric analysis of maintained photopic light levels as
per Appendix A
1. Calculations shall be for maintained values, i.e. Light Loss Factor (LLF) < 1.0, where LLF
= LLD x LDD x LATF, and
a. Lamp Lumen Depreciation (LLD)
1) Shall be 0.85 (L70) for all luminaires.
2) Shall be the percentage of initial output calculated in section 1.6-C.
b. Luminaire Dirt Depreciation (LDD) = 0.90, as per IES DG-4 for an enclosed and
gasketed roadway luminaire installed in an environment with less than 150 µg/m3
airborne particulate matter and cleaned every four years.
c. Luminaire Ambient Temperature Factor (LATF) = 1.00
2. Use of IES HB-10 mesopic multipliers
a. Shall be disallowed herein, by assuming an S/P ratio of 1.00 for all luminaires.
3. Calculation/measurement points shall be per IES RP-8.
E. Summary of Joint Electron Devices Engineering Council (JEDEC) or Japan Electronics and
Information Technology Industries (JEITA) reliability testing performed for LED packages
F. Summary of reliability testing performed for LED driver(s)
G. Written product warranty as per section 1.7 below
1.7 CLOSEOUT SUBMITTALS
A. Warranty Documentation
1. Provide manufacturer warranty information to the City.
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE
A. Before approval and purchase, Supplier shall provide at the Owner’s request luminaire
sample(s) identical to product configuration(s) submitted for inspection at the Supplier’s
expense. Owner shall request IES LM-79 testing of luminaire sample(s) to verify performance
is within manufacturer-reported tolerances and Photometric reports and .ies files, per IES LM-
63. The Photometric file must match the luminaire being submitted.
B. After installation, Owner may perform IES LM-50 field measurements to verify performance
requirements outlined in Appendix A, giving consideration to measurement uncertainties
outlined in IES LM-61.
1.10 DELIVERY, STORAGE, AND HANDLING
A. Storage and Handling Requirements
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 9
ARTERIAL LED ROADWAY LUMINAIRES
Page 9 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
1. Parts shall be properly protected so that no damage or deterioration occurs during a
prolonged delay from the time of shipment until installation.
2. Exposed anchor bolts shall be protected until pole shaft is installed.
3. Prevent plastic and similar brittle items from being exposed to direct sunlight and extremes
in temperature.
4. The Contractor shall secure and maintain a location to store the material in accordance with
Section 01 50 00.
B. Delivery and Acceptance
1. Contactor and Inspector shall visually inspect roadway illumination assemblies after
removal to determine the condition of the hardware.
2. Contractor shall protect all salvable material during transport to City specified storage
facility.
3. Delivered material must be in the same condition after removal, as agreed upon by
Contractor and Inspector after removal.
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY
A. Provide a minimum ten-year warranty covering maintained integrity and functionality of
1. Luminaire housing, wiring, and connections
2. LED light source(s)
a. Negligible light output from more than 10 percent of the LED packages constitutes
luminaire failure.
3. LED driver(s)
B. Warranty period shall begin 90 days after date of installation.
PART 2 - PRODUCTS
2.1 LUMINAIRE REQUIREMENTS
A. General Requirements
1. Luminaires shall be as specified for each type in Appendix A.
2. Luminaire shall have an external label per ANSI C136.15
3. Luminaire shall have an internal label per ANSI C136.22 to include date of manufacture.
4. Luminaire shall be rated for a minimum of IP65 per ANSI C136.25.
5. Nominal luminaire input wattage shall account for nominal applied voltage and any
reduction in driver efficiency due to sub-optimal driver loading.
6. Luminaires shall start and operate in -20°C to +50°C ambient.
7. Electrically test fully assembled luminaires before shipment from factory
8. Effective Projected Area (EPA) and weight of the luminaire shall not exceed the values
indicated in Appendix A.
9. Luminaires shall be designed for ease of component replacement and end-of-life
disassembly.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 10
ARTERIAL LED ROADWAY LUMINAIRES
Page 10 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
10. Luminaires shall be rated for the ANSI C136.31 Vibration Level indicated in Appendix A.
11. LED light source(s) and driver(s) shall be RoHS compliant.
12. Transmissive optical components shall be applied in accordance with OEM design
guidelines to ensure suitability for the thermal/mechanical/chemical environment.
13. Luminaires shall have 4 bolts for mounting to 1-1/4” to 2-3/8” Tenon arm for leveling and
securing of luminaire to tenon arm. 2-Bolt connections shall not be permitted.
14. Luminaires shall come standard with 7-pin photocontrol dimming receptacle meeting ANSI
C136.41 requirements.
B. Driver
1. Rated for minimum of 50,000 hours.
2. Shall be specified with 0-10V dimmable driver to accept input from 7-pin photocell
receptacle.
3. Rated case temperature shall be suitable for operation in the luminaire operating in the
ambient temperatures indicated in section 2.1-A above.
4. Shall accept the voltage or voltage range indicated in Appendix A at 50/60 Hz, and shall
operate normally for input voltage fluctuations of plus or minus 10 percent.
5. Shall have a minimum Power Factor (PF) of 0.90 at full input power and across specified
voltage range.
6. Control signal interface
a. Luminaire types indicated “Required” in Appendix A shall accept a control signal as
specified via separate controls specification referenced in section 1.2 above, e.g., for
dimming.
b. Luminaire types indicated “Not Required” in Appendix A need not accept a control
signal.
C. Electrical immunity
1. Luminaire shall meet the “Basic” requirements in Appendix D. Manufacturer shall indicate
on submittal form (Appendix E) whether failure of the electrical immunity system can
possibly result in disconnect of power to luminaire.
D. Electromagnetic interference
1. Shall have a maximum Total Harmonic Distortion (THD) of 20% at full input power and
across specified voltage range.
2. Shall comply with FCC 47 CFR part 15 non-consumer RFI/EMI standards.
E. Electrical safety testing
1. Luminaire shall be listed for wet locations by an OSHA NRTL.
2. Luminaires shall have locality-appropriate governing mark and certification.
F. Painted or finished luminaire components exposed to the environment
1. Shall exceed a rating of six per ASTM D1654 after 1000hrs of testing per ASTM B117.
2. The coating shall exhibit no greater than 30% reduction of gloss per ASTM D523, after 500
hours of QUV testing at ASTM G154 Cycle 6.
G. Thermal management
1. Mechanical design of protruding external surfaces (heat sink fins) for shall facilitate hose-
down cleaning and discourage debris accumulation.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 11
ARTERIAL LED ROADWAY LUMINAIRES
Page 11 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
2. Liquids or other moving parts shall not be permitted.
H. IES TM-15 limits for Backlight, Uplight, and Glare (BUG Ratings) shall be as specified for
each luminaire type in Appendix A.
1. Calculation of BUG Ratings shall be for initial (worst-case) values, i.e., Light Loss Factor
(LLF) = 1.0.
2. Luminaires shall not be tilted for calculations.
I. Minimum Color Rendering Index (CRI): 70.
J. Correlated Color Temperature (CCT)
1. If nominal CCT specified in Appendix A is listed in Table 1 below, measured CCT and Duv
shall be as listed in Table 1.
Table 1. Allowable CCT and Duv (adapted from NEMA C78.377)
Manufacturer-Rated
Nominal CCT (K)
Allowable LM-79 Chromaticity Values
Measured CCT (K) Measured Duv
2700 2580 to 2870 -0.006 to 0.006
3000 2870 to 3220 -0.006 to 0.006
3500 3220 to 3710 -0.006 to 0.006
4000 3710 to 4260 -0.005 to 0.007
4500 4260 to 4746 -0.005 to 0.007
5000 4745 to 5311 -0.004 to 0.008
5700 5310 to 6020 -0.004 to 0.008
6500 6020 to 7040 -0.003 to 0.009
2. If nominal CCT specified in Appendix A is not listed in Table 1, measured CCT and Duv
shall be as per the criteria for Flexible CCT defined in NEMA C78.377.
K. The following shall be in accordance with corresponding sections of ANSI C136.37
1. Wiring and grounding
a. All internal components shall be assembled and pre-wired using modular electrical
connections.
2. Mounting provisions
a. Specific configurations are indicated in Appendix A
3. Terminal blocks for incoming AC lines
4. Photocontrol receptacle
5. Latching and hinging
6. Ingress protection
2.2 PRODUCT MANUFACTURERS
A. Any manufacturer offering products that comply with the required product performance and
operation criteria may be considered.
B. Note if a field installed house side shield is available.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 12
ARTERIAL LED ROADWAY LUMINAIRES
Page 12 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
2.3 MANUFACTURER SERVICES
A. Manufacturer or local sales representative shall provide installation and troubleshooting support
via telephone and/or email.
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
6/15/2015 F. Griffin Revise to LED type luminaires
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 13
ARTERIAL LED ROADWAY LUMINAIRES
Page 13 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
APPENDIX A
APPLICATION-BASED SYSTEM SPECIFICATION
LUMINAIRE TYPE “A” – ARTERIAL TYPICAL
SITE PARAMETERS
ROADWAY DATA: Lane width 12 ft
Number of lanes, total on both sides of median 6
Shoulder width, drivelane to edge of pavement 5 ft
Median width 10 ft
IES pavement class. R1 R2 R3 R4
Posted speed limit ≤ 25 mph > 25 mph
SIDEWALK DATA: Sidewalk width 6 ft
Edge of sidewalk to edge of roadway pavement 4 ft
LIGHT POLE DATA: Luminaire mounting height 40 ft
Arm length, horizontal 9 ft
Luminaires per pole 2
Pole set-back from edge of pavement 5 ft
In-line pole spacing (one pole cycle) 200 ft
Layout One side Opposite Staggered Median
PERFORMANCE CRITERIA: APPLICATION
ROADWAY
PHOTOPIC
ILLUMINANCE:
Maintained average horizontal at pavement 0.9 FC
Avg:min uniformity ratio 3:1
PHOTOPIC
LUMINANCE:
Maintained average luminance n/a
Avg:min uniformity ratio n/a
Max:min uniformity ratio n/a
SIDEWALKS
PHOTOPIC
ILLUMINANCE:
Maintained average horizontal at pavement 0.2 FC
Avg:min uniformity ratio (horizontal) n/a
Maintained min. vertical illum. at 4.9 ft, in directions of travel 0.1 FC
PERFORMANCE CRITERIA: LED LUMINAIRE
INPUT POWER: Max. nominal luminaire input power 150W
NOMINAL CCT: Rated correlated color temperature 3000 K
CUTOFF CLASS: Max. nominal backlight-uplight-glare ratings FULL CUTOFF
VOLTAGE: Nominal luminaire input voltage 120-277V
FINISH: Luminaire housing finish color Gray
WEIGHT: Maximum luminaire weight 30 lb
EPA: Maximum effective projected area 0.9 ft2
MOUNTING: Mtg. method Post-top Side-arm Trunnion/yoke Swivel-tenon
Tenon nominal pipe size (NPS) 1-1/4 inches
And 2-3/8 inches
VIBRATION: ANSI test level Level 1 (normal) Level 2 (bridge/overpass)
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 14
ARTERIAL LED ROADWAY LUMINAIRES
Page 14 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
DRIVER: Wireless control
compatible 350mA 530mA 700mA
Appendix B
Estimating LED Lumen Maintenance
IES TM-21 allows for extrapolation of expected lumen maintenance from available test data. The extent
of such extrapolation is limited by the duration of testing completed and the number of samples used in
the testing. The TM-21 methodology shall be used by the manufacturer to determine lamp lumen
depreciation (LLD) at end of lumen maintenance life per section 1.6-C.
The applicant may estimate lumen maintenance in one of two ways:
Option 1: Component Performance
Under this compliance path, the applicant must submit calculations per TM-21 predicting lumen
maintenance at the luminaire level using In Situ Temperature Measurement Testing (ISTMT) and
LM-80 data. To be eligible for the Component Performance option, ALL of the conditions below
must be met. If ANY of the conditions is not met, the component performance option may not
be used and the applicant must use Option 2 for compliance.
1. The LED light source(s) have been tested according to LM-80.
2. The LED drive current specified by the luminaire manufacturer is less than or equal to the
drive current specified in the LM-80 test report.
3. The LED light source(s) manufacturer prescribes/indicates a temperature measurement
point (TS) on the light source(s).
4. The TS is accessible to allow temporary attachment of a thermocouple for measurement of
in situ temperature. Access via a temporary hole in the housing, tightly resealed during
testing with putty or other flexible sealant is allowable.
5. For the hottest LED light source in the luminaire, the temperature measured at the TS
during ISTMT is less than or equal to the temperature specified in the LM-80 test report
for the corresponding drive current or higher, within the manufacturer’s specified
operating current range.
a. The ISTMT laboratory must be approved by OSHA as a Nationally Recognized
Testing Lab (NRTL), must be qualified, verified, and recognized through DOE’s
CALiPER program, or must be recognized through UL’s Data Acceptance Program.
b. The ISTMT must be conducted with the luminaire installed in the appropriate
application as defined by ANSI/UL 1598 (hardwired luminaires), with bird-fouling
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 15
ARTERIAL LED ROADWAY LUMINAIRES
Page 15 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
appropriately simulated (and documented by photograph) as determined by the
manufacturer.
Option 2: Luminaire Performance
Under this compliance path, the applicant must submit TM-21 calculations based on LM-79
photometric test data for no less than three samples of the entire luminaire. Duration of
operation and interval between photometric tests shall conform to the TM-21 criteria for LED
light sources. For example, testing solely at 0 and 6000 hours of operation would not be
adequate for the purposes of extrapolation.
Between LM-79 tests, the luminaire test samples must be operated long-term in the appropriate
application as defined by ANSI/UL 1598 (hardwired luminaires). The test laboratory must hold
NVLAP accreditation for the LM-79 test procedure or must be qualified, verified, and recognized
through the U.S. Department of Energy (DOE)’s CALiPER program. The extent of allowable
extrapolation (either 5.5 or 6 times the test duration) depends on the total number of LED light
sources (no less than 10 and preferably more than 19) installed in the luminaire samples, as per
TM-21.
This compliance path poses a greater testing burden to luminaire manufacturers but
incorporates long-term testing of other components in the system, such as drivers.
Under either compliance path, values used for extrapolation shall be summarized per TM-21 Tables 1
and 2. Submitted values for lumen maintenance lifetime and the associated percentage lumen
maintenance shall be “reported” rather than “projected” as defined by TM-21. Supporting diagrams are
requested to facilitate interpretation by Owner.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 16
ARTERIAL LED ROADWAY LUMINAIRES
Page 16 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
APPENDIX C
PRODUCT FAMILY TESTING
LM-79 AND ISTMT
It is recognized that due to the time and cost required for product testing, it would not be realistic to
expect manufacturers offering a multitude of unique luminaire configurations to test every possible
configuration. Therefore, the “product families” method may be utilized for LM-79 and ISTMT, whereby
manufacturers identify a set of representative products for which test data can be used to demonstrate
the accuracy of interpolated or extrapolated performance of product configurations lacking test data.
Precedent for this approach can be found in LM-80.
If the particular luminaire configuration submitted has not been tested, the performance may be
conservatively represented by test data for another luminaire configuration having:
The same intensity distribution (typically only applies to LM-79)
The same or lower nominal CCT
The same or higher nominal drive current
The same or greater number of LED light source(s)
The same or lower percentage driver loading and efficiency
The same or smaller size luminaire housing.
A more accurate estimate of performance can be obtained by linear interpolation between two or more
tests differing in terms of the six parameters listed above. For example, consider a hypothetical
luminaire offered in a single size housing, and having the following parameters:
Three intensity distributions: IES Type II, III, or IV
Three CCTs: 4000, 5000, and 6000K
Three drive currents: 350, 525, and 700 mA
Four LED quantities: 20, 40, 60, or 80 LEDs.
Table C.1 illustrates a set of tests which could allow for accurate interpolation between tested
configurations, given a single luminaire housing size and essentially constant driver efficiency; these 10
tests may provide representative data for the 108 possible product configurations. Note that
normalized intensity distribution must not be affected by the other three parameters.
Table C.1. Representative testing of a single luminaire housing size
Tests Intensity distribution CCT Drive current # of LEDs
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 17
ARTERIAL LED ROADWAY LUMINAIRES
Page 17 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
(IES Type) (K) (mA)
1, 2, 3 II, III, IV 4000 700 80
4, 5 IV 5000, 6000 700 80
6, 7 IV 4000 325, 525 80
8, 9, 10 IV 4000 700 20, 40, 60
For example, the manufacturer could detail interpolation as shown in Table C.2, applying the following
multipliers to the base test #2 to model a configuration with Type III intensity distribution, 5000K CCT,
525 mA drive current, and 40 LEDs:
Ratio of test #4 lumens to test #3 lumens
Ratio of test #7 lumens to test #3 lumens
Ratio of test #9 lumens to test #3 lumens.
Table C.2. Multipliers for Test #2 to yield: Type III , 5000K, 525mA, 40 LEDs
Test # Intensity distribution
(IES Type)
CCT
(K)
Drive current
(mA)
# of LEDs Multiplier
(lumens ratio)
2 III 4000 700 80 n/a
3 IV 4000 700 80 n/a
4 IV 5000 700 80 #4 / #3
7 IV 4000 525 80 #7 / #3
9 IV 4000 700 40 #9 / #3
Interpolation between minimal LM-79 and ISTMT data is more difficult if housing size increases with
increasing wattage; it may not be clear whether the lowest-wattage configuration would be expected to
“run cooler” than the highest-wattage configuration. In these circumstances, the adequacy of
submitted data is subject to Owner approval.
At this time, the “successor” method cannot be used; luminaires tested must utilize the LED light
source(s) characterized by the submitted LM-80 report.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 18
ARTERIAL LED ROADWAY LUMINAIRES
Page 18 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
APPENDIX D
ELECTRICAL IMMUNITY
Test Procedure
Electrical Immunity Tests 1, 2 and 3, as defined by their Test Specifications, shall be performed on an
entire powered and connected luminaire, including any control modules housed within the
luminaire, but excluding any control modules mounted externally, such as a NEMA socket connected
photo-control. A shorting cap should be placed across any such exterior connector.
The luminaire shall be connected to an AC power source with a configuration appropriate for
nominal operation. The AC power source shall have a minimum available short-circuit current of
200A. The luminaire shall be tested at the nominal input voltage specified in Appendix A, or at the
highest input voltage in the input voltage range specified in Appendix A.
Electrical Immunity test waveforms shall be superimposed on the input AC power line at a point
within 6 inches (15cm) of entry into the luminaire using appropriate high-voltage probes and a
series coupler/decoupler network (CDN) appropriate for each coupling mode, as defined by
ANSI/IEEE C62.45-2002. The test area for all tests shall be set up according to ANSI/IEEE C62.45-
2002, as appropriate.
Prior to electrical immunity testing a set of diagnostic measurements shall be performed, and the
results recorded to note the pre-test function of the luminaire after it has reached thermal
equilibrium. These measurements should include at a minimum:
a) For all luminaires, Real Power, Input RMS Current, Power Factor and THD at full power/light
output
b) For luminaires specified as dimmable, Real Power, Input RMS Current, Power Factor and THD at
a minimum of 4 additional dimmed levels, including the rated minimum dimmed level
Tests shall be applied in sequential order (Test 1, followed by Test 2, followed by Test 3). If a failure
occurs during Test 3, then Test 3 shall be re-applied to a secondary luminaire of identical
construction.
Following the completion of Tests 1, 2, and 3, the same set of diagnostic measurements performed
pre-test should be repeated for all tested luminaires, and the results recorded to note the post-test
function of the luminaire(s).
A luminaire must function normally and show no evidence of failure following the completion of
Test 1 + Test 2 + Test 3 (for a single tested luminaire), or the completion of Test 1 + Test 2 on a
primary luminaire and Test 3 on a secondary luminaire. Abnormal behavior during testing is
acceptable.
A luminaire failure will be deemed to have occurred if any of the following conditions exists
following the completion of testing:
a) A hard power reset is required to return to normal operation
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 19
ARTERIAL LED ROADWAY LUMINAIRES
Page 19 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
b) A noticeable reduction in full light output (e.g. one or more LEDs fail to produce light, or become
unstable) is observed
c) Any of the post-test diagnostic measurements exceeds by ±5% the corresponding pre-test
diagnostic measurement.
d) The luminaire, or any component in the luminaire (including but not limited to an electrical
connector, a driver, a protection component or module) has ignited or shows evidence of
melting or other heat-induced damage. Evidence of cracking, splitting, rupturing, or smoke
damage on any component is acceptable.
Test Specifications
NOTE: L1 is typically “HOT”, L2 is typically “NEUTRAL” and PE = Protective Earth.
Test 1) Ring Wave: The luminaire shall be subjected to repetitive strikes of a “C Low Ring Wave” as
defined in IEEE C62.41.2-2002, Scenario 1, Location Category C. The test strikes shall be applied as
specified by Table D.1. Prior to testing, the ring wave generator shall be calibrated to simultaneously
meet BOTH the specified short circuit current peak and open circuit voltage peak MINIMUM
requirements. Note that this may require that the generator charging voltage be raised above the
specified level to obtain the specified current peak. Calibrated current probes/transformers designed for
measuring high-frequency currents shall be used to measure test waveform currents.
Test waveform current shapes and peaks for all strikes shall be compared to ensure uniformity
throughout each set (coupling mode + polarity/phase angle) of test strikes, and the average peak
current shall be calculated and recorded. If any individual peak current in a set exceeds by ±10% the
average, the test setup shall be checked, and the test strikes repeated.
Table D.1: 0.5 µS – 100Hz Ring Wave Specification
Parameter Test Level/Configuration
Short Circuit Current Peak 0.5 kA
Open Circuit Voltage Peak 6 kV
Source Impedance 12
Coupling Modes L1 to PE, L2 to PE, L1 to L2
Polarity and Phase Angle Positive at 90° and Negative at 270°
Test Strikes 5 for each Coupling Mode and Polarity/Phase Angle
combination
Time between Strikes 1 minute
Total Number of Strikes = 5 strikes x 4 coupling modes x 2 polarity/phase angles
= 40 total strikes
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 20
ARTERIAL LED ROADWAY LUMINAIRES
Page 20 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
Test 2) Combination Wave: The luminaire shall be subjected to repetitive strikes of a “C High
Combination Wave” or “C Low Combination Wave”, as defined in IEEE C62.41.2-2002, Scenario 1,
Location Category C. The test strikes shall be applied as specified by Table D.2. The “Low” test level shall
be used for luminaires with Basic Electrical Immunity requirements, while the “High” test level shall be
used for luminaires with Elevated Electrical Immunity requirements. Prior to testing, the combination
wave generator shall be calibrated to simultaneously meet BOTH the specified short circuit current peak
and open circuit voltage peak MINIMUM requirements. Note that this may require that the generator
charging voltage be raised above the specified level to obtain the specified current peak. Calibrated
current probes/transformers designed for measuring high-frequency currents shall be used to measure
test waveform currents.
Test waveform current shapes and peaks for all strikes shall be compared to ensure uniformity
throughout each set (coupling mode + polarity/phase angle) of test strikes, and the average peak
current shall be calculated and recorded. If any individual peak current in a set exceeds by ±10% the
average, the test setup shall be checked, and the test strikes repeated.
Table D.2: 1.2/50µS – 8/20 µS Combination Wave Specification
Parameter Test Level/ Configuration
1.2/50 µS Open Circuit Voltage Peak Low: 6 kV High: 10kV
8/20 µS Short Circuit Current Peak Low: 3 kA High: 10kA
Source Impedance 2
Coupling Modes L1 to PE, L2 to PE, L1 to L2
Polarity and Phase Angle Positive at 90° and Negative at 270°
Test Strikes 5 for each Coupling Mode and Polarity/Phase Angle
combination
Time Between Strikes 1 minute
Total Number of Strikes = 5 strikes x 4 coupling modes x 2 polarity/phase angles
= 40 total strikes
Test 3) Electrical Fast Transient (EFT): The luminaire shall be subjected to “Electrical Fast Transient
Bursts”, as defined in IEEE C62.41.2 -2002. The test area shall be set up according to IEEE C62.45-2002.
The bursts shall be applied as specified by Table D.3. Direct coupling is required; the use of a coupling
clamp is not allowed.
Table D.3: Electrical Fast Transient (EFT) Specification
Parameter Test Level/ Configuration
Open Circuit Voltage Peak 3 kV
Burst Repetition Rate 2.5 kHz
Burst Duration 15 mS
Burst Period 300 mS
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 21
ARTERIAL LED ROADWAY LUMINAIRES
Page 21 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
Coupling Modes L1 to PE, L2 to PE, L1 to L2
Polarity Positive and Negative
Test Duration 1 minute for each Coupling Mode and Polarity combination
Total Test Duration = 1 minute x 7 coupling modes x 2 polarities
= 14 minutes
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20.01 - 22
ARTERIAL LED ROADWAY LUMINAIRES
Page 22 of 22
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised June 15, 2015
APPENDIX E
PRODUCT SUBMITTAL FORM
Luminaire Type1
Manufacturer
Model number
Housing finish color
Tenon nominal pipe size (inches)
Nominal luminaire weight (lb)
Nominal luminaire EPA (ft2)
Nominal input voltage (V)
ANSI vibration test level Level 1 (Normal) Level 2 (bridge/overpass)
Nominal BUG Ratings
Make/model of LED light source(s)
Make/model of LED driver(s)
Dimmability Dimmable Not dimmable
Control signal interface
Upon electrical immunity system failure Possible disconnect No possible disconnect
Thermal management Moving parts No moving parts
Lumen maintenance testing duration (hr)
Reported lumen maintenance life (hr) 2
Warranty period (yr)
Parameter Nominal value Tolerance (%)
Initial photopic output (lm)
Maintained photopic output (lm)
Lamp lumen depreciation
Initial input power (W)
Maintained input power (W)
Initial LED drive current (mA)
Maintained LED drive current (mA)
Drive current used
In-situ LED Tc (°C)
CCT (K)
Additional product description
1 See Appendix A, and attach supporting documentation as required.
2 Value shall be no less than as specified in section 1.6-C, and shall not exceed six times the testing duration
indicated in the row above. Value shall be consistent with values submitted in the rows below for maintained ligh t
output, maintained input power, and maintained drive current.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 1
ROADWAY ILLUMINATION ASSEMBLIES
Page 1 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
SECTION 34 41 20
ROADWAY ILLUMINATION ASSEMBLIES
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Roadway illumination assemblies
2. Roadway illumination foundations
3. Removal of roadway illumination assemblies
4. Relocation of roadway illumination assemblies
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
3. Section 03 30 00 – Cast-in-Place Concrete
4. Section 33 05 10 – Utility Trench Excavation, Embedment and Backfill
5. Section 33 05 30 – Location of Existing Utilities
6. Section 34 41 10 – Traffic Signals
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Roadway Illumination Assemblies
a. Measurement
1) Measurement for this Item shall be per each Roadway Illumination
Assembly installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Rdwy Illum Assmbly”
installed for:
a) Various types
c. The price bid shall include:
1) Furnishing Roadway Illumination Assembly, if required
2) Assembling and installing each Roadway Illumination Assembly
3) Poles
4) Arms
5) Anchor bolts
6) Fixtures
7) Internal electrical conductors
8) Connection and mounting hardware
9) Bases
10) Lamps
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 2
ROADWAY ILLUMINATION ASSEMBLIES
Page 2 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
11) Preparing submittals
12) Exploratory excavation (as needed)
13) Coordination and notification
14) Assembly and transportation of all items
15) Excavation, hauling, disposal of excess material
16) Protection of the excavation
17) Clean-up
18) Testing
2. Ornamental Illumination Assemblies
a. Measurement
1) Measurement for this Item shall be per each Ornamental Assembly
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Ornamental Assmbly”
installed for:
a) Various types
c. The price bid shall include:
1) Furnishing Ornamental Illumination Assembly, if required
2) Assembling and installing each Ornamental Assembly
3) Poles
4) Arms
5) Anchor bolts
6) Fixtures
7) Internal electrical conductors
8) Connection and mounting hardware
9) Bases
10) Lamps
11) Preparing submittals
12) Exploratory excavation (as needed)
13) Coordination and notification
14) Assembly and transportation of all items
15) Excavation, hauling, disposal of excess material
16) Protection of the excavation
17) Clean-up
18) Testing
3. Lighting Fixtures
a. When a pay item for Illumination Assembly exists:
1) Measurement
a) This Item is considered subsidiary to Illumination Assembly
installation.
2) Payment
a) The work performed and materials furnished in accordance with this
Item are subsidiary to the unit price bid per each “Rdwy Illum
Assmbly” or “Ornamental Assmbly” bid, and no other compensation
will be allowed.
b. When a pay item for Illumination Assembly does not exist:
1) Measurement
a) Measurement for this Item shall be per each Lighting Fixture installed.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 3
ROADWAY ILLUMINATION ASSEMBLIES
Page 3 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
2) Payment
a) The work performed and materials furnished in accordance with this
Item shall be paid for at the unit price bid per each “Lighting Fixture”
installed for:
(1) Various types
(2) Various power
3) The price bid shall include:
a) Furnishing Lighting Fixture, if required
b) Assembling Lighting Fixture
c) Wiring connections
d) Disposal of any unused or replaced materials
e) Clean-up
4. Roadway Illumination Foundations
a. Measurement
1) Measurement for this Item shall be per each Roadway Illumination
Foundation installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Rdwy Illum Foundation”
installed for:
a) Various types
c. The price bid shall include:
1) Installing each Roadway Illumination Foundation
2) Reinforcing steel
3) Exploratory excavation (as needed)
4) Grounding rods
5) Coordination and notification
6) Excavation, hauling, disposal of excess material
7) Protection of the excavation
8) Clean-up
9) Testing
5. Contact Enclosure
a. Measurement
1) Measurement for this Item shall be per each Contact Enclosure installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Contact Enclosure” installed
for:
a) Various mounting methods
c. The price bid shall include:
1) Furnishing and installing Contact Enclosure
2) Mounting materials
3) Clean-up
6. Furnishing and Installing Wood Light Pole
a. Measurement
1) Measurement for this Item shall be per each 40’ Wood Light Pole furnished
and installed.
b. Payment
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 4
ROADWAY ILLUMINATION ASSEMBLIES
Page 4 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Furnish/Install 40’ Wood
Light Pole”.
c. The price bid shall include:
1) Excavation
2) Furnishing and installing each 40’ Wood Light Pole
3) Furnishing, placement and compaction of backfill
4) Clean-up
7. Furnishing and Installing Wood Light Pole Arm
a. Measurement
1) Measurement for this Item shall be per each 8’ Wood Light Pole Arm
furnished and installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Furnish/Install 8’ Wood
Light Pole Arm”.
c. The price bid shall include:
1) Furnishing and installing each 8’ Wood Light Pole Arm
2) Clean-up
8. Aluminum Electrical Conductors
a. Measurement
1) Measurement for this Item shall be per linear foot of Aluminum Electrical
Conductor installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
and measured as provided under “Measurement” will be paid for at the unit
price bid per linear foot of “Alum Elec Conductor” installed for:
a) Various Sizes
c. The price bid shall include:
1) Furnishing and installing Aluminum Electrical Conductor
2) Testing
9. Conductor Reconnection
a. Measurement
1) Measurement for this Item shall be per each conductor reconnected.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Reconnect Conductor”.
c. The price bid shall include:
1) Reconnection of conductors using City approved method
2) Testing of connection
10. Street Light Pole Removal and Salvage
a. Measurement
1) Measurement for this Item shall be per each Street Light removed and
salvaged.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Salvage Street Light Pole”
performed.
c. The price bid shall include:
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 5
ROADWAY ILLUMINATION ASSEMBLIES
Page 5 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
1) Removal and salvage of Street Light Pole
2) Maintain existing street light circuit including new ground box and
reconnection of circuits (if required by City)
3) Removal of existing street light pole foundation 2’ below grade, back fill
with like surrounding material
4) Delivery of salvaged materials to appropriate location
5) Clean-up
11. Street Light Pole Relocation
a. Measurement
1) Measurement for this Item shall be per each Street Light Pole removed and
salvaged.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Relocate Street Light Pole”
performed.
c. The price bid shall include:
1) Removal and salvage of Street Light Pole
2) Delivery of salvaged materials to appropriate location
3) Replacement of pole to new location
4) Furnishing, placement and compaction of backfill material
5) Clean-up
1.3 REFERENCES
A. Reference Standards
1. Reference standards cited in this Specification refer to the current reference
standard published at the time of the latest revision date logged at the end of this
Specification, unless a date is specifically cited.
2. National Electric Code (NEC)
3. Texas State Law, Article 1426C
1.4 ADMINISTRATIVE REQUIREMENTS
A. Coordination
1. Notify City at (817) 392-7738 a minimum of 7 days before beginning Work on the
Project.
2. Notify Inspector prior to pouring roadway illumination assembly foundations.
3. Coordinate with Traffic Services Inspector for pole types, template dimensions and
anchor bolts, and any questions about installing the foundations and conduit.
4. For location of City underground street luminaire cable and conduit call (817) 392-
7738 or (817) 392-8100.
5. Obtain and pay for all permits as required to Work in parkway.
B. Preinstallation Meetings
1. Attend pre-construction meeting.
1.5 SUBMITTALS
A. Shop Drawings will be required for each Illumination Assembly and shall include:
1. Material Data
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 6
ROADWAY ILLUMINATION ASSEMBLIES
Page 6 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
2. Pole dimensions and data
3. Luminaire arm dimensions and data
4. Attachment details
5. Fixtures
6. Base details
7. Anchor bolt data
8. Wall thickness
9. Permissible loading and allowable stress
B. Product Data submittals shall be in accordance with Section 01 33 00.
C. All submittals shall be approved by the Engineer or the City prior to delivery and/or
fabrication for specials.
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
A. Product Data Sheets
1. Submit product data sheets for roadway illumination assemblies to City for
approval prior to ordering materials.
1.7 CLOSEOUT SUBMITTALS
A. Warranty Documentation
1. Provide manufacturer warranty information to the City.
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING
A. Storage and Handling Requirements
1. Parts shall be properly protected so that no damage or deterioration occurs during a
prolonged delay from the time of shipment until installation.
2. Exposed anchor bolts shall be protected until pole shaft is installed.
3. Prevent plastic and similar brittle items from being exposed to direct sunlight and
extremes in temperature.
4. The Contractor shall secure and maintain a location to store the material in
accordance with Section 01 50 00.
B. Delivery and Acceptance
1. Contactor and Inspector shall visually inspect roadway illumination assemblies
after removal to determine the condition of the hardware.
2. Contractor shall protect all salvable material during transport to City specified
storage facility.
3. Delivered material must be in the same condition after removal, as agreed upon by
Contractor and Inspector after removal.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 7
ROADWAY ILLUMINATION ASSEMBLIES
Page 7 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY
A. Manufacturer Warranty
1. Manufacturer’s warranty shall be in accordance with Division 1.
PART 2 - PRODUCTS
2.1 PRODUCTS TO BE PURCHASED FROM THE CITY
A. Refer to Drawings and Contract Documents to determine if any Items are to be
purchased from the City and installed by the Contractor.
B. Items eligible for purchase from the City include:
1. Roadway Illumination poles
2. Contactors
2.2 ASSEMBLIES, EQUIPMENT, PRODUCT TYPES, AND MATERIALS
A. Manufacturers
1. Only the manufacturers as listed in the City’s Standard Products List will be
considered as shown in Section 01 60 00.
a. The manufacturer must comply with this Specification and related Sections.
2. Any product that is not listed on the Standard Products List is considered a
substitution and shall be submitted in accordance with Section 01 25 00.
B. Description
1. Regulatory Requirements
a. All Work related to the installation of roadway illumination assemblies shall be
in compliance with the National Electric Code (NEC).
2. Roadway Illumination Assemblies
a. Poles, arms, light fixtures and lamps shall conform to City Standard Details.
b. Ornamental Assemblies
1) Refer to Drawings for ornamental pole specifications.
c. Lighting Fixtures
1) Refer to Drawings for lighting fixture specifications.
d. Foundations
1) Concrete shall conform to Section 03 30 00.
e. Wood Light Poles
1) Wood Poles for electrical service shall be ANSI Class 5 treated timber.
a) For other applications, Class 2 treated timber is allowed.
2) All treated wood poles shall be free from pith holes.
a) Trimmed scars are allowable up to a depth of 2-inches in poles up to 10
inches in diameter.
b) Scars 1/5 of the pole diameter at the scar location will be allowable for
wood poles larger than 10-inches.
3) Wood poles shall not deviate from straight more than 1 inch in 10 feet of
length.
a) Only a single sweep shall be permitted.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 8
ROADWAY ILLUMINATION ASSEMBLIES
Page 8 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
b) A straight line adjoining the midpoint of the pole at the butt with the
midpoint of the pole at the top shall not at any intermediate pass
through the external surface of the pole.
c) Only a single twist of spiral grain will be permitted.
4) Butt slivering due to felling shall be permitted if the distance from the
outside circumference is not less than ¼ inch and the height is not more
than 1 foot.
5) Timber shall be treated for preservation in accordance with AWPA C4
pressure treatment methods.
a) The poles shall have the minimum net retention of preservative
treatment shown in the following table:
Treatment
Minimum Retention
(pounds per cubic foot)
Creosote 9.0
Pentachlorophenol 0.45
ACA/CCA 0.6
6) Pole Markings
7) All markings shall be in accordance with the following table:
a) The bottom brand shall be placed squarely on the face of each pole 10
feet from the butt.
Marking Description of Marking
PTC Supplier’s code or trademark (ie. Pole Treating
Company)
F-01 Plant location and year of treatment (ie. Forestville,
2001)
SPC Species and preservative code (ie. southern pine,
creosote)
5-35 Class-length (ie. Class 5, 35-foot pole)
8) A treatment certification will be required with each shipment of treated
timber poles including:
a) Name of treatment company
b) Location of treatment plant
c) Applicable product standard (AWPA C4)
d) Charge number
e) Date of treatment
f) Contents of charges (poles)
g) Preservative treatment
h) Measured preservative retention values
f. Wood Light Pole Arms
1) Refer to City Standard Detail Drawings for light pole arm specifications.
g. Aluminum Electrical Conductors
1) Refer to Drawings for conductor sizes
2) Use stranded insulated conductors that are rated for 600 volts
3) Approved for wet locations
4) Marked in accordance with UL, NEC, and CSA requirements
3. Roadway illumination pole foundations
a. Foundations shall be Class C (3000 PSI) concrete.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 9
ROADWAY ILLUMINATION ASSEMBLIES
Page 9 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
1) Refer to Section 03 30 00.
b. Foundation shall be 24 or 30 inches in diameter unless shown otherwise in the
Drawings.
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL
A. Tests and Inspections
1. Notify the Traffic Services Division Inspector 24 hours in advance (between 8:00
am and 5:00 pm) of all concrete pours at (817) 392-7738.
a. Inspector must be present when concrete is placed on the Project Site.
PART 3 - EXECUTION
3.1 EXAMINATION
A. Verification of Conditions
1. Contractor shall verify by exploratory excavation, if needed, that existing
underground utilities are not in conflict with proposed foundations.
a. All exploratory excavation shall conform to Section 33 05 30.
2. Contractor shall contact the following entities at least 48 hours in advance of
excavation:
a. DIG TESS
b. City of Fort Worth Water Department
c. City of Fort Worth T/PW Department
3. No additional payment will be made for relocation of any foundations or conduit
due to location of existing utilities.
4. The Engineer may shift an assembly’s location, if necessary, to avoid conflict with
utilities.
3.2 PREPARATION
A. Protection of In-Place Conditions
1. Contractor shall be responsible for the following at no additional cost to the City:
a. Prevent any property damage to property owner's poles, fences, shrubs,
mailboxes, etc. Any damaged property will be restored as directed by
Engineer.
b. Adjust and repair any existing landscaping and the sprinkler systems as directed
by the Engineer to allow for the placement of all roadway illumination
equipment. This shall be done in a manner equal to or better than the areas
adjacent to the damaged areas.
c. Provide access to all driveways during construction, unless authorized by the
inspector.
d. Protect all underground and overhead utilities and repair any damages.
3.3 INSTALLATION
A. Foundations
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 10
ROADWAY ILLUMINATION ASSEMBLIES
Page 10 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
1. Dimensions shown on Drawings for locations of street light foundations, conduit
and other items may be varied to meet local conditions; subject to approval of
Engineer.
2. Foundation piers shall be drilled plumb.
3. The top of foundation shall be poured level.
4. The top 3 inches of the exposed pier (height) above finished grade shall have the
sonotube removed.
5. Anchor bolts shall extend above the top of the foundation concrete as shown on
Anchor Bolt Detail.
6. Anchor bolts, ground rod, reinforcing, and conduit shall be in place before pouring
concrete in pier foundations.
7. Pier foundations shall have 1 continuous concrete pour.
8. Foundations shall have a chamfered edge (beveled) at the top.
9. Top of foundation shall be 3 inches above the finished grade unless shown different
on Drawings.
10. Foundations in medians shall be placed in the center of the median between the 2
curbs.
11. Foundations shall not be drilled within 3 feet of a water line or fire hydrant.
12. In residential areas foundations shall be placed in the street right of way (R.O.W.)
in line with the property line between lots and at the break of the radius point of the
street curb at street intersections.
13. Foundations shall not be placed in sidewalks (or location of future sidewalks) or
sidewalk ramps.
14. No street light poles shall be placed on foundations prior to 7 days following
pouring of concrete.
B. Roadway Illumination Assemblies
1. Roadway Illumination Assemblies
a. Use established industry and utility safety practices when installing poles
located near overhead or underground utilities. Consult with the appropriate
utility company before beginning work.
b. Prevent scarring or marring of poles, mast arm, and fixtures.
c. Stake, install, and align each assembly as shown on the plans.
d. Do not use screw-in type foundations.
e. Install anchor bolts and coat anchor bolt threads.
f. Erect structures after foundation has attained its design strength as required in
Section 03 30 00.
g. Tighten anchor bolts for poles with shoe bases.
h. Do not place grout between base plate and foundation.
i. Test installed roadway illumination assembly with City inspector present.
2. Wood Light Pole
a. All light pole installations should be coordinated with all appropriate utility
companies prior to Work beginning.
b. Drill holes for setting poles shall be a minimum of 1.5 diameters of the pole
butt.
c. Poles shall be set plumb, unless otherwise specified on the Drawings.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 11
ROADWAY ILLUMINATION ASSEMBLIES
Page 11 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
d. Unless otherwise shown in Drawings, poles should be set to the minimum
depths shown in the following table:
Pole Length
(feet)
Minimum Setting Depth
(feet)
≤ 25 4.5
26-30 5.0
31-35 5.5
36-40 6.0
41-45 6.5
46-50 7.0
e. Backfill the hole around the pole thoroughly by tamping 6-inch lifts of backfill
material until reaching natural grade.
1) Once grade is met, apply a last 6-inch lift in a cone shape around the pole to
allow for settling.
2) Backfill in accordance to Section 33 05 10.
f. Repair and clean-up surrounding area to a condition that is equal to or better
than its condition prior to installation.
3.4 REPAIR / RESTORATION [NOT USED]
3.5 RELOCATION AND REMOVAL
A. Relocation
1. Disconnect and remove conductors from abandoned circuits.
2. Remove abandoned circuit or ducts to a point 6 inches below final grade.
3. Reconnect conduit, ducts, conductors to be reused.
4. Replace damaged conduit, ducts, and conductors.
5. Do not use screw-in type foundations.
6. Install existing structures on new foundations.
7. Do not place grout between base plate and foundation.
8. Furnish and install new internal conductors, fused and unfused connectors, and
fixtures.
9. Test installed roadway illumination assembly with City inspector present
10. Accept ownership of unsalvageable materials and dispose of in accordance with
federal, state, and local regulations.
B. Removal
1. Remove roadway illumination assembly components in accordance with
established industry and utility safety practices.
2. Remove transformer bases from transformer base poles.
3. Remove luminaires and mast arms from the pole shaft.
4. Stockpile pole shafts, mast arms, and assembly hardware at a location designated
by the City.
5. Pole shafts, mast arms, and assembly hardware will remain City property unless
otherwise shown on the plans or directed.
6. Disconnect and remove conductors from abandoned circuits.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 20 - 12
ROADWAY ILLUMINATION ASSEMBLIES
Page 12 of 12
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised December 20, 2012
7. Remove abandoned conduit and ducts to a point 6 inches below final grade.
8. Destroy existing transformer bases to prevent reuse.
9. Remove abandoned concrete foundations to a point 2 ft. below final grade.
10. Backfill the hole with material that is equal in composition and density to the
surrounding area.
11. Replace surfacing material with similar material to an equivalent condition.
12. Accept ownership of unsalvageable materials and dispose of in accordance with
federal, state, and local regulations.
3.6 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
3.7 SYSTEM STARTUP [NOT USED]
3.8 ADJUSTING [NOT USED]
3.9 CLEANING
A. Contractor shall clean up and remove all loose material resulting from construction
operations.
3.10 CLOSEOUT ACTIVITIES [NOT USED]
3.11 PROTECTION [NOT USED]
3.12 MAINTENANCE [NOT USED]
3.13 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 1
ALUMINUM SIGNS AND SIGN POSTS
Page 1 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
SECTION 34 41 30
ALUMINUM SIGNS AND SIGN POSTS
PART 1 - GENERAL
1.1 SUMMARY
A. Section Includes:
1. Aluminum signs installed on mast arms, signal poles, or steel posts.
B. Deviations from this City of Fort Worth Standard Specification
1. None.
C. Related Specification Sections include, but are not necessarily limited to:
1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
2. Division 1 – General Requirements
1.2 PRICE AND PAYMENT PROCEDURES
A. Measurement and Payment
1. Furnishing and Installing Mast Arm or Signal Pole Mounted Aluminum Signs
a. Measurement
1) Measurement for this Item shall be per each sign installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Furnish/Install Alum Sign
Mast Arm Mount” installed for:
a) Various types
c. The price bid shall include:
1) Fabricating the aluminum sign
2) Treatment of sign panels required before application of background
materials
3) Application of the background materials and messages to the sign panels
4) Furnishing and fabricating frames, windbeams, stiffeners, or required joint
backing strips
5) Furnishing bolts, rivets, screws, fasteners, clamps, brackets, and sign
support connections
6) Assembling and erecting the signs
7) Preparing and cleaning the signs
2. Installing Mast Arm or Signal/Street Light Pole Mounted Aluminum Signs
a. Measurement
1) Measurement for this Item shall be per each sign installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid for each “Install Alum Sign Mast Arm
Mount” installed.
c. The price bid shall include:
1) Installing each Aluminum Sign
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 2
ALUMINUM SIGNS AND SIGN POSTS
Page 2 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
2) Furnishing and fabricating frames, windbeams, stiffeners, or required joint
backing strips
3) Furnishing bolts, rivets, screws, fasteners, clamps, brackets, and sign
support connections
4) Assembling and erecting the signs
5) Preparing and cleaning the signs
3. Furnishing and Installing Ground Mounted Aluminum Sign and Post Assemblies
a. Measurement
1) Measurement for this Item shall be per each assembly furnished and
installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid for each “Furnish/Install Alum Sign
Ground Mount” installed for:
a) Various types
c. The price bid shall include:
1) Fabrication of signs and posts
2) Treatment of sign panels required before application of background
materials
3) Application of the background materials and messages to the sign panels
4) Scheduling utility line locates
5) Furnishing and fabricating frames, windbeams, stiffeners, or required joint
backing strips
6) Furnishing bolts, rivets, screws, fasteners, clamps, brackets, and sign
support connections
7) Assembling and erecting the signs and posts
8) Preparing and cleaning the signs
4. Installing Ground Mounted Aluminum Sign and Post Assemblies
a. Measurement
1) Measurement for this Item shall be per each assembly installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid for each “Install Alum Sign Ground
Mount” installed.
c. The price bid shall include:
1) Scheduling utility line locates
2) Assembling and erecting the signs and posts
3) Preparing and cleaning the signs
5. Furnishing and Installing Aluminum Signs Mounted on Existing Poles
a. Measurement
1) Measurement for this Item shall be per each sign furnished and installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Furnish/Install Alum Sign
Ex. Pole Mount” furnished and installed.
c. The price bid shall include:
1) Furnishing and installing the aluminum sign
2) Furnishing and fabricating frames, windbeams, stiffeners, or required joint
backing strips
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 3
ALUMINUM SIGNS AND SIGN POSTS
Page 3 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
3) Furnishing bolts, rivets, screws, fasteners, clamps, brackets, and sign
support connections
4) Assembling and erecting the signs
5) Preparing and cleaning the signs
6. Installing Aluminum Signs Mounted on Existing Poles
a. Measurement
1) Measurement for this Item shall be per each sign installed.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Install Alum Sign Ex. Pole
Mount” installed.
c. The price bid shall include:
1) Fabricating the aluminum sign
2) Furnishing and fabricating frames, windbeams, stiffeners, or required joint
backing strips
3) Furnishing bolts, rivets, screws, fasteners, clamps, brackets, and sign
support connections
4) Assembling and erecting the signs
5) Preparing and cleaning the signs
7. Removal of Signs
a. Measurement
1) Measurement for this Item shall be per each sign panel removed, each sign
panel and post removed, and each sign panel and post removed and
reinstalled.
b. Payment
1) The work performed and materials furnished in accordance with this Item
shall be paid for at the unit price bid per each “Remove Sign” for:
a) Various types
b) Various configurations
c. The price bid shall include:
1) Removal of sign panel and post
2) Removal of sign panel
3) Backfill
4) Excavation
5) Returning materials to the City as specified in the plans
6) Cleaning sign panel if sign is to be reinstalled
1.3 REFERENCES
A. Reference Standards
1. Reference standards cited in this Specification refer to the current reference
standard published at the time of the latest revision date logged at the end of this
Specification, unless a date is specifically cited.
2. American Standard Testing Materials (ASTM)
a. ASTM B209-07– “Standard Specification for Aluminum and Aluminum-Alloy
Sheet and Plate”.
b. ASTM D4956 – 09e1 – “Standard Specification for Retroreflective Sheeting for
Traffic Control”.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 4
ALUMINUM SIGNS AND SIGN POSTS
Page 4 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
c. ASTM A1011 / A1011- 10 – “Standard Specification for Steel, Sheet and Strip,
Hot-Rolled, Carbon, Structural, High-Strength Low-Alloy, High-Strength Low-
Alloy with Improved Formability, and Ultra-High Strength”.
d. ASTM B117-09 – “Standard Practice for Operating Salt Spray (Fog)
Apparatus”.
e. AASHTO M 120-08 – “Standard Specification for Zinc”.
3. Texas Manual on Uniform Traffic Control Devices
4. Item 644, Small Roadside Sign Supports and Assemblies, Texas Department of
Transportation, Standard Specifications for Construction and Maintenance of
Highways, Streets, and Bridges.
1.4 ADMINISTRATIVE REQUIREMENTS [NOT USED]
1.5 SUBMITTALS
A. Submittals shall be in accordance with Section 01 33 00.
B. All submittals shall be approved by the City prior to delivery and/or fabrication for
specials.
1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS
A. Shop Drawings
1. Submit 5 sets of sign shop drawings to City Traffic Services Department for
approval prior to fabrication.
1.7 CLOSEOUT SUBMITTALS [NOT USED]
1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
1.9 QUALITY ASSURANCE [NOT USED]
1.10 DELIVERY, STORAGE, AND HANDLING
A. Delivery and Acceptance Requirements
1. Signs and parts shall be properly protected so that no damage or deterioration
occurs during a prolonged delay from the time of shipment until installation.
2. The Contractor shall secure and maintain a location to store the material in
accordance with Section 01 50 00.
B. Storage and Handling
1. Ship, handle, and store completed sign blanks and completed signs so that corners,
edges, and faces are not damaged.
2. Damage to the sign face that is not visible when viewed at a distance of 50 feet,
night and day, will be acceptable.
3. Replace unacceptable signs.
4. Store all finished signs off the ground and in a vertical position until erected.
5. Store finished signs 60 inches x 60 inches or smaller in a weatherproof building.
6. Larger signs may be stored outside.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 5
ALUMINUM SIGNS AND SIGN POSTS
Page 5 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
1.11 FIELD [SITE] CONDITIONS [NOT USED]
1.12 WARRANTY [NOT USED]
PART 2 - PRODUCTS
2.1 PRODUCTS TO BE PURCHASED FROM THE CITY
A. Refer to Drawings and Contract Documents to determine if any Items are to be
purchased from the City and installed by the Contractor.
B. Items eligible for purchase from the City include:
1. Aluminum Signs
2.2 MATERIALS
A. Manufacturers
1. Only the manufacturers as listed in the City’s Standard Products List will be
considered as shown in Section 01 60 00.
a. The manufacturer must comply with this Specification and related Sections.
2. Any product that is not listed on the Standard Products List is considered a
substitution and shall be submitted in accordance with Section 01 25 00.
B. Sign blanks
1. Sign blanks shall be new, unweathered, milled, rolled and finished aluminum alloy
meeting Specifications for 5052H38 as outlined in ASTM B 209 – 02a.
2. Sign blanks shall be free of buckle, crevice, warp, dent, cockles, burrs, corrosion,
dirt, grease, oil, white rust, fingerprints and/or other irregularities.
3. Sign blanks shall be degreased and etched according to industry standards and shall
have an alodined finish applied per MIL-C5541 Class 1A.
4. The thickness of each sign blank shall be uniform throughout.
C. Sign sheeting
1. Acrylic overlay film
a. This film shall be applied to Type I, Type II, Type IV, Type IX, and other
retroreflective sheeting for permanent signing.
b. The film shall be equal to or better than 3M Scotchlite ElectroCut Film Series
1170.
c. Film shall be:
1) Durable
2) Transparent
3) Acrylic
4) Electronic-cuttable
5) Coated with a transparent, pressure sensitive adhesive
6) Have a removable synthetic liner – paper liner is not acceptable
d. Film colors can include yellow, green, blue, brown, red, and orange.
2. Non-reflective vinyl film
a. This film shall be applied to Type IV, Type XI (DG3) retroreflective sheeting
for permanent signing. The film shall be equal to or better than 3M Scotchcal
ElectroCut Film Series 7725.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 6
ALUMINUM SIGNS AND SIGN POSTS
Page 6 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
b. Film shall be:
1) Durable
2) 2 mil opaque cast vinyl
3) Coated with a transparent, pressure-sensitive adhesive
4) Have a removable synthetic liner – paper line is not acceptable
c. Film colors can include yellow, green, blue, brown, red, and orange.
3. High intensity prismatic retroreflective sheeting with adhesive backing shall:
a. Be combined with other components for permanent signing
b. Typically be an unmetallized microprismatic lens retroreflective element
material
c. Have a smooth outer surface that essentially has the property of the
retroreflector over its entire surface
1) The adhesive backing shall be pressure-sensitive, require no heat, solvent or
other preparation for the adhesion to smooth, clean surfaces.
d. Be equal to or better than 3M Series 3930
e. Be of colors including white, yellow, green, red, blue, and brown
4. Super-high efficiency full cube retroreflective sheeting with pressure sensitive
adhesive shall:
a. Be combined with other components for permanent signing
b. Be a super-high efficiency, full cube retroreflective sheeting having the highest
retroreflectivity characteristics at medium and short road distances.
c. Typically be a microprismatic retroreflective element material
d. Have a smooth outer surface that essentially has the property of retroreflector
over its entire surface
1) The adhesive backing shall be pressure-sensitive, require no heat, solvent or
other preparation for adhesion to smooth, clean surfaces.
e. Be equal to or better than 3M Series 4000
f. Be of colors including white, yellow, green, red, blue, brown, fluorescent
yellow, fluorescent yellow green, and fluorescent orange
D. Telescoping Steel Sign Post
1. Posts and anchors shall conform to the Standard Specifications for Hot Rolled
Carbon Sheet Steel, Structural Quality ASTM designation A1011 / A1011- 10.
2. Posts and anchors shall carry minimum certifiable 60,000 psi yield strength.
3. All posts and anchors shall be manufactured from raw steel, formed and welded on
the corner prior to receiving a triple coat protection of inline hot-dipped, galvanized
zinc per AASHTO M-120-08 (0.8 ounces per square foot) followed by a chromate
conversion coating and a cross-linked polyurethane acrylic exterior coating.
4. The interior shall receive a double coat of zinc based organic coating, tested in
accordance with ASTM B-117-09.
E. Hardware
1. Use galvanized steel, stainless steel, or dichromate-sealed aluminum for bolts, nuts,
washers, lock washers, screws, and other sign assembly hardware.
2. Use plastic or nylon washers to avoid tearing the reflective sheeting.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 7
ALUMINUM SIGNS AND SIGN POSTS
Page 7 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
2.3 ACCESSORIES [NOT USED]
2.4 SOURCE QUALITY CONTROL [NOT USED]
PART 3 - EXECUTION
3.1 INSTALLERS [NOT USED]
3.2 EXAMINATION [NOT USED]
3.3 PREPARATION [NOT USED]
3.4 FABRICATION
A. Sign blanks
1. Furnish sign blanks to the sizes and shapes shown on the Drawings and that are free
of buckles, warps, burrs, dents, cockles, or other defects.
2. Do not splice individual extruded aluminum panel.
3. Complete the fabrication of sign blanks, including the cutting and drilling or
punching of holes, before cleaning and degreasing.
4. After cleaning and degreasing, ensure that the substrate does not come into contact
with grease, oils, or other contaminants before the application of the reflective
sheeting.
B. Sign sheeting
1. Use reflective sheeting from the same manufacturer for the entire face of a sign.
2. Apply sheeting to sign blanks in conformance with the recommended procedures of
the sheeting manufacturer.
3. Clean and prepare the outside surface of extruded aluminum flanges in the same
manner as the sign panel face.
4. Minimize the number of splices in the sheeting.
5. Overlap the lap-splices by at least 1/4 inch.
6. Provide a 1-foot minimum dimension for any piece of sheeting.
7. Do not splice sheeting for signs fabricated with transparent screen inks or colored
transparent films.
C. Sign messages
1. Fabricate sign messages to the sizes, types, and colors shown on the Drawings.
2. Use sign message material from the same manufacturer for the entire message of a
sign.
3. Ensure that the screened messages have clean, sharp edges and exhibit uniform
color and reflectivity.
4. Prevent runs, sags, and voids.
D. Telescoping steel sign posts
1. Permissible variation in straightness is 1/16 inch in 3 feet.
2. Tolerances are on the outside size.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 8
ALUMINUM SIGNS AND SIGN POSTS
Page 8 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
Measurements for outside dimensions shall be made at least 2 inches from end of
tube.
Nominal Outside
Dimensions
(inches)
Outside Tolerance
at all Side Corners
(inches)
1 ½ X 1 ½ ±0.006
1 ¾ X 1 ¾ ±0.008
2 X 2 ±0.008
2 ¼ X 2 ¼ ±0.010
2 ½ X 2 ½ ±0.010
3. Permissible variation in wall thickness is plus 0.011 inches, minus 0.008 inches.
4. Measured in the center of the flat side tolerance is ± 0.01 inch applied to the
specific size determined at the corner.
5. Squareness of Sides and Twist
Nominal
Outside
Dimensions
(inches)
Squareness
Tolerance
(inches)
Twist Permissible in 3
inches Lengths
(inches)
1 ½ X 1 ½ ±0.009 0.050
1 ¾ X 1 ¾ ±0.010 0.062
2 X 2 ±0.012 0.062
2 ¼ X 2 ¼ ±0.014 0.062
2 ½ X 2 ½ ±0.015 0.075
6. All top posts must be capable of fracturing at the point of connection with a single
anchor, when impacted, in such a manner that the piece inside of the anchor can be
removed so as to allow the anchor to receive a new top post.
7. The shape of all posts and anchors shall be square and straight with smooth tubing
welded in one corner with a tolerance that permits telescoping of the next larger or
small size, in ¼-inch increments.
8. All anchors shall be 12 gauge with holes that are fully perforated 7/16-inch
diameter on 1-inch centers for at least the top 4 inches of the anchor while being
truly aligned in the center of the section.
Meacham Boulevard at Mercantile Drive
CPN 105417
34 41 30 - 9
ALUMINUM SIGNS AND SIGN POSTS
Page 9 of 9
CITY OF FORT WORTH [Insert Project Name]
STANDARD CONSTRUCTION SPECIFICATION DOCUMENTS [Insert Project Number]
Revised November 12, 2013
9. All top posts shall be 14 gauge with holes that are die embossed knockouts on 1-
inch centers for the entire length of the post and truly aligned in the center of
section.
3.5 REPAIR / RESTORATION [NOT USED]
3.6 RE-INSTALLATION [NOT USED]
3.7 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
3.8 SYSTEM STARTUP [NOT USED]
3.9 ADJUSTING [NOT USED]
3.10 CLEANING
A. Wash completed signs with a biodegradable cleaning solution acceptable to the
manufacturers of the sheeting, colored transparent film, and screen ink to remove
grease, oil, dirt, smears, streaks, finger marks, and other foreign material.
B. Wash again before final inspection after erection.
3.11 CLOSEOUT ACTIVITIES [NOT USED]
3.12 PROTECTION [NOT USED]
3.13 MAINTENANCE [NOT USED]
3.14 ATTACHMENTS [NOT USED]
END OF SECTION
Revision Log
DATE NAME SUMMARY OF CHANGE
11/22/13 S. Arnold Changes to vinyl film, added sign removal bid item
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
34 71 13 - 1
TRAFFIC CONTROL
Page 1 of 6
1 SECTION 34 71 13
2 TRAFFIC CONTROL
3 PART 1 - GENERAL
4 1.1 SUMMARY
5 A. Section Includes:
6 1. Installation of Traffic Control Devices and preparation of Traffic Control Plans
7 B. Deviations from this City of Fort Worth Standard Specification
8 1. None.
9 C. Related Specification Sections include, but are not necessarily limited to:
10 1. Division 0 – Bidding Requirements, Contract Forms and Conditions of the Contract
11 2. Division 1 – General Requirements
12 1.2 PRICE AND PAYMENT PROCEDURES
13 A. Measurement and Payment
14 1. Installation of Traffic Control Devices
15 a. Measurement
16 1) Measurement for Traffic Control Devices shall be per month for the Project
17 duration.
18 a) A month is defined as 30 calendar days.
19 b. Payment
20 1) The work performed and materials furnished in accordance with this Item
21 and measured as provided under “Measurement” shall be paid for at the
22 unit price bid for “Traffic Control”.
23 c. The price bid shall include:
24 1) Traffic Control implementation
25 2) Installation
26 3) Maintenance
27 4) Adjustments
28 5) Replacements
29 6) Removal
30 7) Police assistance during peak hours
31 2. Portable Message Signs
32 a. Measurement
33 1) Measurement for this Item shall be per week for the duration of use.
34 b. Payment
35 1) The work performed and materials furnished in accordance to this Item and
36 measured as provided under “Measurement” shall be paid for at the unit
37 price bid per week for “Portable Message Sign” rental.
38 c. The price bid shall include:
39 1) Delivery of Portable Message Sign to Site
40 2) Message updating
41 3) Sign movement throughout construction
42 4) Return of the Portable Message Sign post-construction
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
1 3. Preparation of Traffic Control Plan Details
2 a. Measurement
34 71 13 - 2
TRAFFIC CONTROL
Page 2 of 6
3 1) Measurement for this Item be per each Traffic Control Detail prepared.
4 b. Payment
5 1) The work performed and materials furnished in accordance with this Item
6 shall be paid for at the unit price bid per each “Traffic Control Detail”
7 prepared.
8 c. The price bid shall include:
9 1) Preparing the Traffic Control Plan Details for closures of 24 hours or
10 longer
11 2) Adherence to City and Texas Manual on Uniform Traffic Control Devices
12 (TMUTCD)
13 3) Obtaining the signature and seal of a licensed Texas Professional Engineer
14 4) Incorporation of City comments
15 1.3 REFERENCES
16 A. Reference Standards
17 1. Reference standards cited in this Specification refer to the current reference
18 standard published at the time of the latest revision date logged at the end of this
19 Specification, unless a date is specifically cited.
20 2. Texas Manual on Uniform Traffic Control Devices (TMUTCD).
21 3. Item 502, Barricades, Signs, and Traffic Handling of the Texas Department of
22 Transportation, Standard Specifications for Construction and Maintenance of
23 Highways, Streets, and Bridges.
24 1.4 ADMINISTRATIVE REQUIREMENTS
25 A. General
26 1. Contractor shall minimize lane closures and impact to vehicular/pedestrian traffic.
27 B. Coordination
28 1. Contact Traffic Services Division (817-392-7738) a minimum of 48 hours prior to
29 implementing Traffic Control within 500 feet of a traffic signal.
30 C. Sequencing
31 1. Any deviations to the Traffic Control Plan included in the Drawings must be first
32 approved by the City and design Engineer before implementation.
33 1.5 SUBMITTALS
34 A. Provide the City with a current list of qualified flaggers before beginning flagging
35 activities. Use only flaggers on the qualified list.
36 B. Obtain a Street Use Permit from the TPW Department’s Transportation Division. The
37 Traffic Control Plan (TCP) for the Project shall be as detailed on the Traffic Control
38 Plan Detail sheets of the Drawing set. A copy of this Traffic Control Plan shall be
39 submitted with the Street Use Permit.
40 C. Traffic Control Plans shall be signed and sealed by a licensed Texas Professional
41 Engineer.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
34 71 13 - 3
TRAFFIC CONTROL
Page 3 of 6
1 D. Contractor shall prepare Traffic Control Plans if required by the Drawings or
2 Specifications. The Contractor will be responsible for having a licensed Texas
3 Professional Engineer sign and seal the Traffic Control Plan sheets.A traffic control
4 “Typical” published by City of Fort Worth, the Texas Manual Unified Traffic Control
5 Devices (TMUTCD) or Texas Department of Transportation (TxDOT) can be used as
6 an alternative to preparing project/site specific traffic control plan if the typical is
7 applicable to the specific project/site.
8 E. Lane closures 24 hours or longer shall require a site-specific traffic control plan.
9 F. Contractor responsible for having a licensed Texas Professional Engineer sign and seal
10 changes to the Traffic Control Plan(s) developed by the Design Engineer.
11 1.6 ACTION SUBMITTALS/INFORMATIONAL SUBMITTALS [NOT USED]
12 1.7 CLOSEOUT SUBMITTALS [NOT USED]
13 1.8 MAINTENANCE MATERIAL SUBMITTALS [NOT USED]
14 1.9 QUALITY ASSURANCE [NOT USED]
15 1.10 DELIVERY, STORAGE, AND HANDLING [NOT USED]
16 1.11 FIELD [SITE] CONDITIONS [NOT USED]
17 1.12 WARRANTY [NOT USED]
18 PART 2 - PRODUCTS
19 2.1 OWNER-FURNISHED [OR] OWNER-SUPPLIED PRODUCTS [NOT USED]
20 2.2 ASSEMBLIES AND MATERIALS
21 A. Description
22 1. Regulatory Requirements
23 a. Provide Traffic Control Devices that conform to details shown on the
24 Drawings, the TMUTCD, and TxDOT’s Compliant Work Zone Traffic Control
25 Device List (CWZTCDL).
26 2. Materials
27 a. Traffic Control Devices must meet all reflectivity requirements included in the
28 TMUTCD and TxDOT Specifications – Item 502 at all times during
29 construction.
30 b. Electronic message boards shall be provided in accordance with the TMUTCD.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
34 71 13 - 4
TRAFFIC CONTROL
Page 4 of 6
1 2.3 ACCESSORIES [NOT USED]
2 2.4 SOURCE QUALITY CONTROL [NOT USED]
3 PART 3 - EXECUTION
4 3.1 EXAMINATION [NOT USED]
5 3.2 PREPARATION
6 A. Protection of In-Place Conditions
7 1. Protect existing traffic signal equipment.
8 3.3 INSTALLATION
9 A. Follow the Traffic Control Plan (TCP) and install Traffic Control Devices as shown on
10 the Drawings and as directed.
11 B. Install Traffic Control Devices straight and plumb.
12 C. Do not make changes to the location of any device or implement any other changes to
13 the Traffic Control Plan without the approval of the Engineer.
14 1. Minor adjustments to meet field constructability and visibility are allowed.
15 D. Maintain Traffic Control Devices by taking corrective action as soon as possible.
16 1. Corrective action includes but is not limited to cleaning, replacing, straightening,
17 covering, or removing Devices.
18 2. Maintain the Devices such that they are properly positioned, spaced, and legible,
19 and that retroreflective characteristics meet requirements during darkness and rain.
20 E. If the Inspector discovers that the Contractor has failed to comply with applicable federal
21 and state laws (by failing to furnish the necessary flagmen, warning devices, barricades,
22 lights, signs, or other precautionary measures for the protection of persons or property), the
23 Inspector may order such additional precautionary measures be taken to protect persons
24 and property.
25 F. Subject to the approval of the Inspector, portions of this Project, which are not affected by
26 or in conflict with the proposed method of handling traffic or utility adjustments, can be
27 constructed during any phase.
28 G. Barricades and signs shall be placed in such a manner as to not interfere with the sight
29 distance of drivers entering the highway from driveways or side streets.
30 H. To facilitate shifting, barricades and signs used in lane closures or traffic staging may
31 be erected and mounted on portable supports.
32 1. The support design is subject to the approval of the Engineer.
33 I. Lane closures shall be in accordance with the approved Traffic Control Plans.
34 J. If at any time the existing traffic signals become inoperable as a result of construction
35 operations, the Contractor shall provide portable stop signs with 2 orange flags, as
36 approved by the Engineer, to be used for Traffic Control.
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
34 71 13 - 5
TRAFFIC CONTROL
Page 5 of 6
1 K. Contractor shall make arrangements for police assistance to direct traffic if traffic signal
2 turn-ons, street light pole installation, or other construction will be done during peak traffic
3 times (AM: 7 am – 9 am, PM: 4 pm - 6 pm).
4 L. Flaggers
5 1. Provide a Contractor representative who has been certified as a flagging instructor
6 through courses offered by the Texas Engineering Extension Service, the American
7 Traffic Safety Services Association, the National Safety Council, or other approved
8 organizations.
9 a. Provide the certificate indicating course completion when requested.
10 b. This representative is responsible for training and assuring that all flaggers are
11 qualified to perform flagging duties.
12 2. A qualified flagger must be independently certified by 1 of the organizations listed
13 above or trained by the Contractor’s certified flagging instructor.
14 3. Flaggers must be courteous and able to effectively communicate with the public.
15 4. When directing traffic, flaggers must use standard attire, flags, signs, and signals
16 and follow the flagging procedures set forth in the TMUTCD.
17 5. Provide and maintain flaggers at such points and for such periods of time as may be
18 required to provide for the safety and convenience of public travel and Contractor’s
19 personnel, and as shown on the Drawings or as directed by the Engineer.
20 a. These flaggers shall be located at each end of the lane closure.
21 M. Removal
22 1. Upon completion of Work, remove from the Site all barricades, signs, cones, lights
23 and other Traffic Control Devices used for work-zone traffic handling as soon as
24 practical in a timely manner, unless otherwise shown on the Drawings.
25 3.4 REPAIR / RESTORATION [NOT USED]
26 3.5 RE-INSTALLATION [NOT USED]
27 3.6 FIELD [OR] SITE QUALITY CONTROL [NOT USED]
28 3.7 SYSTEM STARTUP [NOT USED]
29 3.8 ADJUSTING [NOT USED]
30 3.9 CLEANING [NOT USED]
31 3.10 CLOSEOUT ACTIVITIES [NOT USED]
32 3.11 PROTECTION [NOT USED]
33 3.12 MAINTENANCE [NOT USED]
34 3.13 ATTACHMENTS [NOT USED]
35 END OF SECTION
36
37
Meacham Boulevard at Mercantile Drive
CPN 105417
CITY OF FORT WORT H
ST ANDARD CONSTRUCT ION SPECIFICAT ION DOCUMENTS
Revised March 22, 2021
Birchman Office Space
CPN 105553
34 71 13 - 6
TRAFFIC CONTROL
Page 6 of 6
Revision Log
DATE NAME SUMMARY OF CHANGE
11/22/13 S. Arnold Added police assistance, requirement for when a site specific TCP is required
3/22/2021 M Owen
1.4 A. Added language to emphasize minimizing of lane closures and impact t o
traffic.
1.5 Clarified submittal requirements
3.3 M. Clarified removal requirements
1
Meacham Boulevard at Mercantile Drive
CPN 105417
!!!!!!!! Attention: Mix Designs do not supersede CFW Specifications !!!!!!!!!!
Approval Spec No.Classification Manufacturer Mix ID Mix Description Design Strength @ 28 days Design Rquirements National Spec
Concrete
Class A (Sidewalk, ADA Ramps, Driveways, Curb/Gutter, Median Pavement)
9/9/2022 32 13 20 Mix Design American Concrete Company 30CAF029 3000 psi 3-5" Slump; 3-6% Air
4/3/2025 32 13 20 Mix Design Big Town Concrete 2211 3000 psi 3-5" Slump; 3-6% Air
7/16/2025 322 13 20 Mix Design Big Town Concrete 221113 With 30% Slag 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Burnco Texas 30U101AG 3000 psi 3-5" Slump; 3-6% Air
4/1/2024 32 13 20 Mix Design Burnco Texas 30U500BG 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Carder Concrete FWCC502001 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Carder Concrete FWCC502021 3500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Chisholm Trail Redi Mix C13020AE 3000 psi 3-5" Slump; 4.5-7.5% Air
4/28/2025 32 13 20 Mix Design Chisholm Trail Redi Mix CT6020A 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design City Concrete Company 30HA20II 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Cow Town Redi Mix 253-W 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Cow Town Redi Mix 250 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Cow Town Redi Mix 350 3000 psi 3-5" Slump; 3-6% Air
1/29/2024 32 13 20 Mix Design Estrada Ready Mix R3050AEWR 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Holcim - SOR, Inc.1261 3000 psi 3-5" Slump; 3-6% Air
9/23/2024 32 13 20 Mix Design Holcim - SOR, Inc.5177 3000 psi 3-5" Slump; 3-6% Air
5/8/2025 32 13 20 Mix Design Holcim - SOR, Inc.530WA-T1 3000 psi 3-5" Slump; 3-6% Air
4/7/2023 32 13 20 Mix Design Liquid Stone C301D 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Martin Marietta R2136214 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Martin Marietta R2136014 3000 psi 3-5" Slump; 3-6% Air
4/1/2023 32 13 20 Mix Design Martin Marietta R2136N14 3000 psi 3-5" Slump; 3-6% Air
6/1/2023 32 13 20 Mix Design Martin Marietta R2136R20 3000 psi 3-5" Slump; 3-6% Air
6/1/2023 32 13 20 Mix Design Martin Marietta R2136N20 3000 psi 3-5" Slump; 3-6% Air
11/2/2022 32 13 20 Mix Design Martin Marietta R2141K24 4000 psi 3-5" Slump; 3-6% Air
4/7/2023 32 13 20 Mix Design Martin Marietta R2136K14 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Martin Marietta R2131314 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Martin Marietta R2132214 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Martin Marietta D9490SC 3000 psi 3-5" Slump; 4.5-7.5% Air
5/9/2025 32 13 20 Mix Design Martin Marietta R2136R14 3000 psi 3-5" Slump; 3-6% Air
10/4/2023 32 13 20 Mix Design NBR Ready Mix CLS A-YY 3000 psi 3-5" Slump; 3-6% Air
10/4/2023 32 13 20 Mix Design NBR Ready Mix CLS A-NY 3000 psi 3-5" Slump; 3-6% Air
7/10/2023 32 13 20 Mix Design Osburn 30A50MR 3000 psi 3-5" Slump; 3-6% Air
1/18/2023 32 13 20 Mix Design Rapid Redi Mix RRM5020A 3000 psi 3-5" Slump; 3-6% Air
1/24/2023 32 13 20 Mix Design Rapid Redi Mix RRM5525A 3600 psi 3-5" Slump; 3-6% Air
10/24/2024 32 13 20 Mix Design SRM Concrete 30850 3000 psi 3-5" Slump; 3-6% Air
10/24/2024 32 13 20 Mix Design SRM Concrete 30350 3000 psi 3-5" Slump; 3-6% Air
10/18/2024 32 13 20 Mix Design SRM Concrete 30050 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Tarrant Concrete FW5025A 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Tarrant Concrete CP5020A 3000 psi 3-5" Slump; 3-6% Air
10/10/2022 32 13 20 Mix Design Tarrant Concrete TCFW5020A 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Tarrant Concrete FW5525A2 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design Titan Ready Mix 3020AE 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design True Grit Redi Mix 0250.230 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 20 Mix Design True Grit Redi Mix 0250.2301 3000 psi 3-5" Slump; 3-6% Air
Class CIP (Inlets, Manholes, Junction Boxes, Encasement, Blocking, Collars, (Spread Footing Pedestal Pole Foundations (Reference Detail 34 41 10-D605A)
9/9/2022 32 13 13 Mix Design American Concrete Company 40CNF065 4000 psi 3-5" Slump; 0-3% Air
9/9/2022 32 13 13 Mix Design Burnco Texas 40U500BG 4000 psi 3-5" Slump; 3-6% Air
4/28/2025 32 13 20 Mix Design Chisholm Trail Redi Mix CT6020A 3600 psi 3-5" Slump; 3-6% Air
4/28/2025 32 13 20 Mix Design Chisholm Trail Redi Mix CTFW5520A 3600 psi 3-5" Slump; 3-6% Air
4/28/2025 32 13 20 Mix Design Chisholm Trail Redi Mix CTFW6020A 4000 psi 3-5" Slump; 3-6% Air
8/4/2025 32 13 20 Mix Design Chisholm Trail Redi Mix CTFW5020A With 20% Fly Ash 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 255-2 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 355 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 255 3500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 270 5000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 370 5000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 353 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 257 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 357 3600 psi 3-5" Slump; 3-6% Air
5/7/2025 32 13 13 Mix Design Cow Town Redi Mix 265-42 4200 psi 3-5" Slump; 3-6% Air
2/7/2025 32 13 13 Mix Design Holcim - SOR, Inc.1701 4000 psi 3-5" Slump; 3-6% Air
2/7/2025 32 13 13 Mix Design Holcim - SOR, Inc.1551 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Holcim - SOR, Inc.5409 4000 psi 3-5" Slump; 3-6% Air
8/14/2025 32 13 13 Mix Design Holcim - SOR, Inc.540WA-T1 With 20% Fly Ash and 30% Slag 4000 psi 3-5" Slump; 3-6% Air
4/27/2023 32 13 13 Mix Design Liquid Stone C361DNFA 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2141230 4000 psi 3-5" Slump; 3-6% Air
8/4/2023 32 13 13 Mix Design Martin Marietta R2141R24 4000 psi 3-5" Slump; 3-6% Air
11/20/2023 32 13 13 Mix Design Martin Marietta R2146R33 4000 psi 3-5" Slump; 3-6% Air
11/20/2023 32 13 13 Mix Design Martin Marietta R2146K33 4000 psi 3-5" Slump; 3-6% Air
CITY OF FORT WORTH TRANSPORTATION/PUBLIC WORKS DEPARTMENT
STANDARD PRODUCTS LIST AS OF 8/29/2025
Page 1 of 6
!!!!!!!! Attention: Mix Designs do not supersede CFW Specifications !!!!!!!!!!
Approval Spec No.Classification Manufacturer Mix ID Mix Description Design Strength @ 28 days Design Rquirements National Spec
CITY OF FORT WORTH TRANSPORTATION/PUBLIC WORKS DEPARTMENT
STANDARD PRODUCTS LIST AS OF 8/29/2025
9/9/2022 32 13 13 Mix Design Martin Marietta R2142233 3600 psi 3-5" Slump; 4.5-7.5% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2136224 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2141233 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2146038 4500 psi 3-5" Slump; 3-6% Air
10/24/2024 32 13 13 Mix Design Martin Marietta R2146K34 4000 psi 3-5" Slump; 3-6% Air
5/5/2025 32 13 13 Mix Design Martin Marietta R2146R35 4000 psi 3-5" Slump; 3-6% Air
5/5/2025 33 13 13 Mix Design Martin Marietta R2146K35 4000 psi 3-5" Slump; 3-6% Air
5/5/2025 33 13 13 Mix Design Martin Marietta R2146N33 4000 psi 3-5" Slump; 3-6% Air
9/12/2023 32 13 13 Mix Design NBR Ready Mix CLS P1-YY 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design NBR Ready Mix TX C-YY 3000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design NBR Ready Mix TX C-NY 3000 psi 3-5" Slump; 3-6% Air
1/18/2023 32 13 13 Mix Design Rapid Redi Mix RRM5320A 3000 psi 3-5" Slump; 3-6% Air
1/18/2023 32 13 13 Mix Design Rapid Redi Mix RRM6020ASS 4000 psi 3-5" Slump; 3-6% Air
10/24/2024 32 13 13 Mix Design SRM Concrete 40350 4000 psi 3-5" Slump; 3-6% Air
10/24/2024 32 13 13 Mix Design SRM Concrete 40850 4000 psi 3-5" Slump; 3-6% Air
9/16/2024 32 13 13 Mix Design SRM Concrete 35050 3500 psi 3-5" Slump; 3-6% Air
4/28/2025 32 13 13 Mix Design SRM Concrete 36850 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete FW5320A 3000 psi 3-5" Slump; 3-6% Air
10/10/2022 32 13 13 Mix Design Tarrant Concrete TCFW6025A2 4000 psi 3-5" Slump; 3-6% Air
Class C (Drilled Shaft for Traffic Signal Pole Foundations Reference Detail 31 41 10-D605)
9/9/2022 32 13 13 Mix Design Burnco Texas 36U500BG 3600 psi 5.5-7.5" Slump; 3-6% Air
6/21/2023 32 13 13 Mix Design Cow Town Redi Mix 360-DS 3600 psi 5.5-7.5" Slump; 3-6% Air
10/30/2024 32 13 13 Mix Design Estrada Ready Mix R36575AEWR 3600 psi 5.5-7.5" Slump; 3-6% Air
12/5/2022 32 13 13 Mix Design Holcim - SOR, Inc.1822 3600 psi 5.5-7.5" Slump; 0-3% Air
9/9/2022 32 13 13 Mix Design Holcim - SOR, Inc.1859 4000 psi 5.5-7.5" Slump; 3-6% Air
4/7/2023 32 13 13 Mix Design Liquid Stone C361DHR 3600 psi 5.5-7.5" Slump; 3-6% Air
6/27/2023 32 13 13 Mix Design Martin Marietta U2146N41 3600 psi 5-7" Slump; 3-6% Air
6/27/2023 32 13 13 Mix Design Martin Marietta U2146K45 3600 psi 5-7" Slump; 3-6% Air
5/9/2025 2 13 13 Mix Design Martin Marietta U2146R41 3600 psi 5-7" Slump; 3-6% Air
8/22/2024 32 13 13 Mix Design NBR Ready Mix 135K2524 3600 psi 5.5" Slump; 3-6% Air
8/22/2024 32 13 13 Mix Design NBR Ready Mix 135K0524 3600 psi 5.5" Slump; 3-6% Air
Class C (Headwalls, Wing walls, Culverts)
9/9/2022 32 13 13 Mix Design Carder Concrete FWCC602001 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design City Concrete Company 40LA2011 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 260-2 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 360-1 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 260-1 3600 psi 3-5" Slump; 3-6% Air
8/11/2025 32 13 13 Mix Design Cow Town Redi Mix 275 With 20% Fly Ash 5000 psi 4-6" Slump: 3-6% Air
8/11/2025 32 13 13 Mix Design Cow Town Redi Mix 375 5000 psi 4-6" Slump: 3-6% Air
1/29/2024 32 13 13 Mix Design Estrada Ready Mix R3655AEWR 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design GCH Concrete Services GCH4000 4000 psi 3-5" Slump; 3-6% Air
4/1/2023 32 13 13 Mix Design Martin Marietta 310LBP 3600 psi 3-5" Slump; 4-7% Air
8/30/2023 32 13 13 Mix Design Martin Marietta R2141R30 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2146035 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design SRM Concrete 40050 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design SRM Concrete 35022 3600 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete FW6020A2 4000 psi 3-5" Slump; 3-6% Air
Class P (Machine Placed Paving)
4/3/2025 32 13 13 Mix Design Big Town Concrete 4511 3600 psi 1-3" Slump; 3-6% Air
4/3/2025 32 13 13 Mix Design Big Town Concrete 4411 3600 psi 1-3" Slump; 3-6% Air
6/30/2025 32 13 13 Mix Design Big Town Concrete 5211 With 20% Fly Ash 4000 psi 1-3" Slump; 3-6% Air
6/30/2025 30 13 13 Mix Design Big Town Concrete 52113 With 30% Slag 4000 psi 1-3" Slump; 3-6% Air
6/30/2025 30 13 13 Mix Design Big Town Concrete 5311 4000 psi 1-3' Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Carder Concrete FWCC552091 3600 psi 1-3" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Carder Concrete FWCC602091 4000 psi 1-3" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design City Concrete Company 36LA2011 3600 psi 1-3" Slump; 3-6% Air
9/9/2022 33 13 13 Mix Design Cow Town Redi Mix 257-M 3600 psi 1-3" Slump; 3-6% Air
11/14/2022 32 13 13 Mix Design Cow Town Redi Mix 357-M 3600 psi 1-3" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 260-M 4000 psi 1-3" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 360-M 4000 psi 1-3" Slump; 3-6% Air
2/6/2024 32 13 13 Mix Design Estrada Ready Mix TD3655AEWR 3600 psi 1-3" Slump; 3-6% Air
5/20/2025 32 13 13 Mix Design Gilco Contracting Inc 36MP1643 3600 psi 1-3" Slump; 3-6% Air
6/20/2025 32 13 13 Mix Design Gilco Contracting Inc 36MP1629 3600 psi 1-3" Slump; 3-6% Air
7/29/2025 32 13 13 Mix Design Gilco Contracting Inc 36MP1655 With 20% Fly Ash 3600 psi 1-3" Slump; 3-6% Air
7/29/2025 32 13 13 Mix Design Gilco Contracting Inc 36MP1670 3600 psi 1-3" Slump; 3-6% Air
5/12/2025 32 13 13 Mix Design Holcim - SOR, Inc.1703 4000 psi 1-3" Slump; 3-6% Air
8/4/2023 32 13 13 Mix Design Martin Marietta Q2141R27 4000 psi 1-3" Slump; 3-6% Air
11/2/2022 32 13 13 Mix Design Martin Marietta Q2141K30 4000 psi 1-3" Slump; 3-6% Air
...Concrete (Continues)
Page 2 of 6
!!!!!!!! Attention: Mix Designs do not supersede CFW Specifications !!!!!!!!!!
Approval Spec No.Classification Manufacturer Mix ID Mix Description Design Strength @ 28 days Design Rquirements National Spec
CITY OF FORT WORTH TRANSPORTATION/PUBLIC WORKS DEPARTMENT
STANDARD PRODUCTS LIST AS OF 8/29/2025
5/5/2025 32 13 13 Mix Design Martin Marietta Q2141N27 4000 psi 1-3" Slump; 3-6% Air
10/4/2023 32 13 13 Mix Design NBR Ready Mix TX C SF-YY 3600 psi 1-3" Slump; 3-6% Air
10/4/2023 32 13 13 Mix Design NBR Ready Mix TX C SF-NY 3600 psi 1-3" Slump; 3-6% Air
10/24/2024 32 13 13 Mix Design SRM Concrete 40068 4000 psi 1-3" Slump; 3-6% Air
10/24/2024 32 13 13 Mix Design SRM Concrete 40825 4000 psi 1-3" Slump; 3-6% Air
9/16/2024 32 13 13 Mix Design SRM Concrete 40025 4000 psi 1-3" Slump; 3-6% Air
10/18/2024 32 13 13 Mix Design SRM Concrete 35023 3600 psi 1-3" Slump; 3-6% Air
6/5/2025 32 13 13 Mix Design SRM Concrete 40324 4000 psi 1-3" Slump; 3-6% Air
7/21/2025 32 13 13 Mix Design SINACOLA 24011-4000MP 20%With 20% Fly Ash 4000 psi 1-3" Slump; 3-6% Air
7/21/2025 32 13 13 Mix Design SINACOLA 24011-4000MP Straight Cement 4000 psi 1-3" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete FW5520AMP 3600 psi 1-3" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design True Grit Redi Mix 0255.2301 3600 psi 1-3" Slump; 3.5-6.5% Air
9/9/2022 32 13 13 Mix Design True Grit Redi Mix 0260.2302 4000 psi 1-3" Slump; 3.5-6.5% Air
6/17/2025 32 13 13 Mix Design True Grit Redi Mix 460.230M 4000 psi 1-3" Slump; 3-6% Air
6/23/2025 32 13 13 Mix Design True Grit Redi Mix 360.230M 4000 psi 1-3" Slump; 3-6% Air
Class H (Hand Placed Paving, Valley Gutter)
9/9/2022 32 13 13 Mix Design American Concrete Company 45CAF076 4500 psi 3-5" Slump; 3-6% Air
5/2/2023 32 13 13 Mix Design Big D Concrete CM14520AE 4500 psi 3-5" Slump; 3-6% Air
4/3/2025 32 13 13 Mix Design Big Town Concrete 6211 4500 psi 3-5" Slump; 3-6% Air
4/3/2025 32 13 13 Mix Design Big Town Concrete 6311 4500 psi 3-5" Slump; 3-6% Air
4/5/2025 32 13 13 Mix Design Big Town Concrete 6017 4500 psi 3-5" Slump; 3-6% Air
7/16/2025 32 13 13 Mix Design Big Town Concrete 62113 With 30% Slag 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Burnco Texas 45U500BG 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Carder Concrete FWCC602021 4500 psi 3-5" Slump; 3-6% Air
4/28/2025 32 13 13 Mix Design Chisholm Trail Redi Mix CTFW6520A 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design City Concrete Company 45NA20II 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 265 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 365 4500 psi 3-5" Slump; 3-6% Air
1/29/2024 32 13 13 Mix Design Estrada Ready Mix R4560AEWR/4500 psi 3-5" Slump; 4-6% Air
9/9/2022 32 13 13 Mix Design GCH Concrete Services GCH4500 4500 psi 3-5" Slump; 3-6% Air
5/20/2025 32 13 13 Mix Design Gilco Contracting Inc 45HP1643 4500 psi 3-5" Slump; 3-6% Air
6/20/2025 32 13 13 Mix Design Gilco Contracting Inc 45HP1629 4500 psi 3-5" Slump; 3-6% Air
7/29/2025 32 13 13 Mix Design Gilco Contracting Inc 45HP1670 4500 psi 3-5" Slump; 3-6% Air
10/4/2024 32 13 13 Mix Design Holcim - SOR, Inc.5507 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Holcim - SOR, Inc.1851 4500 psi 3-5" Slump; 3-6% Air
5/8/2025 32 13 13 Mix Design Holcim - SOR, Inc.545WA-T1 4500 psi 3-5" Slump; 3-6% Air
4/5/2025 32 13 13 Mix Design Liquid Stone C451D 4500 psi 3-5" Slump; 3-6% Air
11/2/2022 32 13 13 Mix Design Martin Marietta R2146N35 4500 psi 3-5" Slump; 3-6% Air
8/4/2023 32 13 13 Mix Design Martin Marietta R2146R36 4500 psi 3-5" Slump; 3-6% Air
11/2/2022 32 13 13 Mix Design Martin Marietta R2146N36 4500 psi 3-5" Slump; 3-6% Air
5/22/2023 32 13 13 Mix Design Martin Marietta R2146K37 4500 psi 3-5" Slump; 3-6% Air
12/22/2023 32 13 13 Mix Design Martin Marietta R2146R44 4500 psi 3-5" Slump; 3-6% Air
12/22/2023 32 13 13 Mix Design Martin Marietta R2146K44 4500 psi 3-5" Slump; 3-6% Air
11/15/2022 32 13 13 Mix Design Martin Marietta R2146P36 4500 psi 3-5" Slump; 3-6% Air
11/15/2022 32 13 13 Mix Design Martin Marietta R2146K36 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2147241 4500 psi 3-5" Slump; 4.5-7.5% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2146236 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2146036 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2146242 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Martin Marietta R2146042 4500 psi 3-5" Slump; 3-6% Air
6/3/2025 32 13 13 Mix Design Martin Marietta R2146K43 4500 psi 3-5" Slump; 3-6% Air
10/4/2023 32 13 13 Mix Design NBR Ready Mix CLS P2-YY 4500 psi 3-5" Slump; 3-6% Air
10/4/2023 32 13 13 Mix Design NBR Ready Mix CLS P2-NY 4500 psi 3-5" Slump; 3-6% Air
7/10/2023 32 13 13 Mix Design Osburn 45A60MR 4500 psi 3-5" Slump; 3-6% Air
1/24/2023 32 13 13 Mix Design Rapid Redi Mix RRM6320AHP 4500 psi 3-5" Slump; 3-6% Air
2/7/2025 32 13 13 Mix Design SRM Concrete 45023 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design SRM Concrete 45000 4500 psi 3-5" Slump; 3-6% Air
5/23/2025 32 13 13 Mix Design SRM Concrete 45300 4500 psi 3-5" Slump; 3-6% Air
10/24/2024 32 13 13 Mix Design SRM Concrete 45350 4500 psi 3-5" Slump; 3-6% Air
10/24/2024 32 13 13 Mix Design SRM Concrete 45850 4500 psi 3-5" Slump; 3-6% Air
10/18/2024 32 13 13 Mix Design SRM Concrete 45050 4500 psi 3-5" Slump; 3-6% Air
7/21/2025 32 13 13 Mix Design SINACOLA 24011-4500HP 20%With 20% Fly Ash 4500 psi 3-5" Slump; 3-6% Air
7/21/2025 32 13 13 Mix Design SINACOLA 24011-4500HP Straight Cement 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete FW6020AHP 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete FW60AHP 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete TCFW6020AHP 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Titan Ready Mix TRC4520 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design True Grit Redi Mix 0260.2301 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design True Grit Redi Mix 0265.2301 4500 psi 3-5" Slump; 3.5-6.5% Air
9/9/2022 32 13 13 Mix Design True Grit Redi Mix 270.230 4500 psi 3-5" Slump; 3-6% Air
6/12/2025 32 13 13 Mix Design True Grit Redi Mix 465.230H With 30% Slag 4500 psi 3-5" Slump: 3-6% Air
6/23/2025 32 13 13 Mix Design True Grit Redi Mix 365.230H 4500 psi 3-5" Slump: 3-6% Air
10/9/2024 32 13 13 Mix Design Wildcatter 4520AI 4500 psi 3-5" Slump; 3-6% Air
...Concrete (Continues)
Page 3 of 6
!!!!!!!! Attention: Mix Designs do not supersede CFW Specifications !!!!!!!!!!
Approval Spec No.Classification Manufacturer Mix ID Mix Description Design Strength @ 28 days Design Rquirements National Spec
CITY OF FORT WORTH TRANSPORTATION/PUBLIC WORKS DEPARTMENT
STANDARD PRODUCTS LIST AS OF 8/29/2025
Class HES (High Early Strength Paving)
9/9/2022 32 13 13 Mix Design Big D Concrete 14500AE 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 370-1NC 4500 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 375-NC 5000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 370-NC 4500 psi 3-5" Slump; 3-6% Air
1/18/2023 32 13 13 Mix Design Cow Town Redi Mix 380-NC 4500 psi 3-5" Slump; 3-6% Air
1/29/2024 32 13 13 Mix Design Estrada Ready Mix 4575AESC 4500 psi / 3000 psi @ 3 days 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Holcim - SOR, Inc.2125 5000 psi 3-5" Slump; 3-6% Air
1/24/2023 32 13 13 Mix Design Liquid Stone C451DHR-A 4500 psi 3-5" Slump; 3-6% Air
4/7/2023 32 13 13 Mix Design Martin Marietta R2161K70 6000 psi / 3000 psi @ 24hr.3-5" Slump; 3-6% Air
2/10/2023 32 13 13 Mix Design SRM Concrete 50310 5000 psi 3-5" Slump; 3-6% Air
2/7/2025 32 13 13 Mix Design SRM Concrete 40326 4500 psi / 3000 psi @ 3 days 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete FW6520AMR 4500 psi / 3000 psi @ 3 days 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Tarrant Concrete FW7520AMR 4500 psi / 3000 psi @ 3 days 3-5" Slump; 3-6% Air
Class S (Bridge Slabs, Top Slabs of Direct Traffic Culverts, Approach Slabs)
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 260 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 360 4000 psi 3-5" Slump; 3-6% Air
9/9/2022 32 13 13 Mix Design Cow Town Redi Mix 365-STX 4000 psi 3-5" Slump; 3-6% Air
1/29/2024 32 13 13 Mix Design Estrada Ready Mix R4060AEWR 4000 psi 4-6" Slump; 3-6% Air
5/3/2023 32 13 13 Mix Design Martin Marietta M7842344 4000 psi 3-5" Slump; 4.5-7.5% Air
4/1/2023 32 13 13 Mix Design Martin Marietta R2146P33 4000 psi 3-5" Slump; 3-6% Air
8/18/2025 32 13 13 Mix Design Martin Marietta 610LBT 4000 psi 3-5" Slump; 3-6% Air
4/15/2024 32 13 13 Mix Design NBR Ready Mix TX S-NY 4000 psi 3-5" Slump; 3-6% Air
4/15/2024 32 13 13 Mix Design NBR Ready Mix TX S-YY 4000 psi 3-5" Slump; 3-6% Air
4/5/2025 32 13 13 Mix Design SRM Concrete 40850 4000 psi 3-5" Slump; 3-6% Air
4/5/2025 32 13 13 Mix Design SRM Concrete 40350 4000 psi 3-5" Slump; 3-6% Air
5/5/2023 32 13 13 Mix Design SRM Concrete D100008553CB 4000 psi 3-5" Slump; 3-6% Air
Concrete Base Trench Repair
4/1/2023 03 34 16 Mix Design Burnco Texas 10YH50BF 1000 psi Flowable; 8.5-11.5% Air
9/9/2022 03 34 16 Mix Design Burnco Texas 08Y450BA 800 psi 5-7" Slump; 3-6% Air
Controlled Low Strength Material (Flowable Fill)
2/7/2025 03 34 13 Mix Design Burnco Texas 01Y690BF 100 psi Flowable; 9.5-11.5% Air
5/19/2025 03 34 13 Mix Design Burnco Texas 01Z180AF 100 psi Flowable; 9.5-11.5% Air
9/9/2022 03 34 13 Mix Design Carder Concrete FWCC359101 50-150 psi 3-5" Slump; 8-12% Air
9/9/2022 03 34 13 Mix Design Carder Concrete FWFF237501 50-150 psi Flowable; 8.5-11.5% Air
8/4/2025 03 34 13 Mix Design Chisholm Trail Redi Mix CT150FF 50-150 psi Flowable; 7-9.0% Air
9/9/2022 03 34 13 Mix Design City Concrete Company 11-350-FF 50-150 psi Flowable; 8-12% Air
9/9/2022 03 34 13 Mix Design Cow Town Redi Mix Mix# 9 70 psi 7-9" Slump; 8-11% Air
5/12/2025 03 34 13 Mix Design Holcim - SOR, Inc.3741 100 psi Flowable; 12.0-24.0% Air
8/4/2025 03 34 13 Mix Design Holcim - SOR, Inc.901 100 psi 9-11" Slump; 10-30% Air
03 34 13 Mix Design Holcim - SOR, Inc.904 150 psi 9-11" Slump; 10-30% Air
10/4/2023 03 34 13 Mix Design NBR Ready Mix FTW FLOW FILL 150 psi 7-10" Slump; 8-12% Air
2/7/2025 03 34 13 Mix Design SRM Concrete 910 150 psi Flowable; 8-12% Air
9/9/2022 03 34 13 Mix Design Tarrant Concrete FWFF150CLSM 50-150 psi Flowable; 8-12% Air
Concrete Rip Rap
4/1/2023 31 37 00 Mix Design Martin Marietta R2141030 4000 psi 3-5" Slump; 3-6% Air
4/1/2023 31 37 00 Mix Design Martin Marietta R2146033 4000 psi 3-5" Slump; 3-6% Air
Asphalt Paving
9/9/2022 32 12 16 Mix Design Austin Asphalt FT5B117965 FT5B117965 PG64-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design Austin Asphalt FT1B139965 FT1B139965 PG64-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design Austin Asphalt FT1B117.2 FT1B117.2 PG64-22 Type B Fine Base
5/1/2024 32 12 16 Mix Design Reynolds Asphalt 340-DG-B P 340-DG-B PG64-22 Type B Base Course
9/9/2022 32 12 16 Mix Design Reynolds Asphalt 1112B 1112B PG64-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design Reynolds Asphalt 1612B 1612B PG64-22 Type B Fine Base
4/4/2025 32 12 16 Mix Design Reynolds Asphalt 2315B 2315B PG64-22 Type B Fine Base
12/5/2022 33 12 16 Mix Design Sunmount Paving 3076BV6422 3076BV6422 PG62-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design Sunmount Paving 341-BRAP6422ERG 341-BRAP6422ERG PG64-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design TXBIT 37-211305-20 37-211305-20 PG64-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design TXBIT 44-211305-17 44-211305-17 PG64-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design TXBIT 211305 (1757)211305 (1757) PG64-22 Type B Fine Base
9/9/2022 32 12 16 Mix Design TXBIT 64-224125-18 PG 64-224125-18 PG70-22 Type D Fine Surface
4/1/2024 32 12 16 Mix Design TXBIT 344 MAC-SP-D 70-22XR 344 MAC-SP-D 70-22XR SAC A-R Type D Fine Surface
Detectable Warning Surface
9/9/2022 32 13 20 DWS - Pavers Pine Hall Brick (Winston Salem, NC)Tactile Pavers
9/9/2022 32 13 20 DWS - Pavers Western Brick Co. (Houston, TX)Detectable Warning Pavers
9/9/2022 32 13 20 DWS - Composite Armor Tile
9/9/2022 32 13 20 DWS - Composite ADA Solutions (Wilmington, MA)Heritage Brick CIP Composite Paver
4/7/2023 32 13 20 DWS - Pavers ADA Solutions (Wilmington, MA)Detectable Warning Pavers
...Concrete (Continues)
Page 4 of 6
!!!!!!!! Attention: Mix Designs do not supersede CFW Specifications !!!!!!!!!!
Approval Spec No.Classification Manufacturer Mix ID Mix Description Design Strength @ 28 days Design Rquirements National Spec
CITY OF FORT WORTH TRANSPORTATION/PUBLIC WORKS DEPARTMENT
STANDARD PRODUCTS LIST AS OF 8/29/2025
Silicone Joint Sealant
9/9/2022 32 13 73 Joint Sealant Dow 890SL 890SL - Cold Applied, Single Component, Silicone Joint Sealant ASTM D5893
9/9/2022 32 13 73 Joint Sealant Tremco 900SL 900SL - Cold Applied, Single Component, Silicone Joint Sealant ASTM D5893
9/9/2022 32 13 73 Joint Sealant Pecora 300SL 300SL - Cold Applied, Single Component, Silicone Joint Sealant ASTM D5893
9/9/2022 32 13 73 Joint Sealant Crafco RoadSaver Silicone RoadSaver Silicone - Cold Applied, Single Component, Silicone Joint Sealant ASTM D5893
Utility Trench Embedment Sand
9/9/2022 33 05 10 Embedment Sand Silver Creek Materials Utility Embedment Sand ASTM C33
9/9/2022 33 05 10 Embedment Sand Crouch Materials Utility Embedment Sand ASTM C33
9/9/2022 33 05 10 Embedment Sand F and L Dirt Movers Utility Embedment Sand ASTM C33
9/9/2022 33 05 10 Embedment Sand F and L Dirt Movers Utility Embedment Sand ASTM C33
9/9/2022 33 05 10 Embedment Sand Tin Top Martin Marietta Utility Embedment Sand ASTM C33
Storm Sewer - Manholes & Bases/Frames & Covers/Standard (Round) 33-05-13
9/28/2018 33 05 13 Manhole Frames and Covers AccuCast (Govind Steel Company, LTD)MHRC #220605 MHRC #220605 (Size - **24" Dia.)ASTM A48 AASHTO M306
9/28/2018 33 05 13 Manhole Cover Neenah Foundry NF-1274-T91 NF-1274-T91 (Size - 32" Dia.)ASTM A48 AASHTO M306
9/28/2018 33 05 13 Manhole Frames and CoversNeenah Foundry NF-1743-LM (Hinged)NF-1743-LM (Hinged) (Size - 32" Dia.)ASTM A48 AASHTO M306
9/28/2018 33 05 13 Manhole Frame Neenah Foundry NF-1930-30 NF-1930-30 (Size - 32.25" Dia.)ASTM A48 AASHTO M306
9/28/2018 33 05 13 Manhole Frames and CoversNeenah Foundry R-1743-HV R-1743-HV (Size - 32" Dia.)ASTM A48 AASHTO M306
4/3/2019 33 05 13 Manhole Frames and CoversSIP Industries ++2279ST 2279ST (Size - 24" Dia.)ASTM A48 AASHTO M306
4/3/2019 33 05 13 Manhole Frames and CoversSIP Industries ++2280ST 2280ST (Size - 32" Dia.)ASTM A48 AASHTO M306
10/8/2020 33 05 13 Manhole Frames and CoversEJ ( Formally East Jordan Iron Works)EJ1033 Z2/A EJ1033 Z2/A (Size - 32.25" Dia.)ASTM A536 AASHTO M306
3/8/2024 33 05 13 Curb Inlet Covers SIP Industries ++2296T 2296T (Size - ***24" Dia.)ASTM A48 AASHTO M306
6/18/2024 33 05 13 Curb Inlet Covers SIP Industries ++2279STN 2279STN (Size - 24" Dia.)ASTM A48 AASHTO M306
Storm Sewer - Inlet & Structures 33-05-13
10/8/2020 33 49 20 Curb Inlets Fonterra FRT-10x3-405-PRECAST** (Size - 10' X 3')ASTM C913
10/8/2020 33 49 20 Curb Inlets Fonterra FRT-10x3-406-PRECAST** (Size - 10' X 3')ASTM C913
10/8/2020 33 49 20 Curb Inlets Fonterra FRT-10x4.5-407-PRECAST** (Size - 10' X 4.5')ASTM C913
10/8/2020 33 49 20 Curb Inlets Fonterra FRT-10x4.5-420-PRECAST** (Size - 10' X 4.5')ASTM C913
10/8/2020 33 39 20 Manhole Fonterra FRT-4X4-409-PRECAST-TOP (Size - 4' X 4')ASTM C913
10/8/2020 33 39 20 Manhole Fonterra FRT-4X4-409-PRECAST-BASE (Size - 4' X 4')ASTM C913
10/8/2020 33 39 20 Manhole Fonterra FRT-5X5-410-PRECAST-TOP (Size - 5' X 5')ASTM C913
10/8/2020 33 39 20 Manhole Fonterra FRT-5X5-410-PRECAST-BASE (Size - 5' X 5')ASTM C913
10/8/2020 33 39 20 Manhole Fonterra FRT-6X6-411-PRECAST-TOP (Size - 6' X 6')ASTM C913
10/8/2020 33 39 20 Manhole Fonterra FRT-6X6-411-PRECAST-BASE (Size - 6' X 6')ASTM C913
3/19/2021 33 49 20 Curb Inlets Thompson Pipe Group TPG-10X3-405-PRECAST INLET** (Size - 10' X 3')ASTM 615
3/19/2021 33 49 20 Curb Inlets Thompson Pipe Group TPG-15X3-405-PRECAST INLET** (Size - 15' X 3')ASTM 615
3/19/2021 33 49 20 Curb Inlets Thompson Pipe Group TPG-20X3-405-PRECAST INLET** (Size - 20' X 7')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-4X4-409-PRECAST TOP (Size - 4' X 4')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-4X4-409-PRECAST BASE (Size - 4' X 4')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-4X4-412-PRECAST 4-FT RISER (Size - 4' X 4')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-5X5-410-PRECAST TOP (Size - 5' X 5')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-5X5-410-PRECAST BASE (Size - 5' X 5')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-5X5-412-PRECAST 5-FT RISER (Size - 5' X 5')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-6X6-411-PRECAST TOP (Size - 6' X 6')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-6X6-411-PRECAST BASE (Size - 6' X 6')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-6X6-412-PRECAST 6-FT RISER (Size - 6' X 6')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-7X7-411-PRECAST TOP (Size - 7' X 7')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-7X7-411-PRECAST BASE (Size - 7' X 7')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-7X7-412-PRECAST 4-FT RISER (Size - 7' X 7')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-8X8-411-PRECAST TOP (Size - 8' X 8')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-8X8-411-PRECAST BASE (Size - 8' X 8')ASTM 615
3/19/2021 33 39 20 Manhole Thompson Pipe Group TPG-8X8-412-PRECAST 5-FT RISER (Size - 8' X 8')ASTM 615
3/19/2021 33 49 20 Drop Inlet Thompson Pipe Group TPG-4X4-408-PRECAST INLET (Size - 4' X 4')ASTM 615
3/19/2021 33 49 20 Drop Inlet Thompson Pipe Group TPG-5X5-408-PRECAST INLET (Size - 5' X 5')ASTM 615
3/19/2021 33 49 20 Drop Inlet Thompson Pipe Group TPG-6X6-408-PRECAST INLET (Size - 6' X 6')ASTM 615
8/28/2023 33 49 10 Manhole Oldcastle Precast 4' x 4' Stacked Manhole (Size - 4' X 4')ASTM C478
8/28/2023 33 49 10 Manhole Oldcastle Precast 5' x 8' Storm Junction Box (Size - 5' X 8')ASTM C478
8/28/2023 33 49 10 Manhole Oldcastle Precast 4' x 4' Storm Junction Box (Size - 4' X 4')ASTM C478
8/28/2023 33 49 10 Manhole Oldcastle Precast 5' x 5' Storm Junction Box (Size - 5' X 5')ASTM C478
8/28/2023 33 49 10 Manhole Oldcastle Precast 6' x 6' Storm Junction Box (Size - 6' X 6')ASTM C478
8/28/2023 33 49 10 Manhole Oldcastle Precast 8' x 8' Storm Junction Box Base (Size - 8' X 8')ASTM C478
8/28/2023 33 49 10 Manhole Oldcastle Precast 5' x 8' Storm Junction Box Base (Size - 5' X 8')ASTM C478
8/28/2023 33 49 10 Manhole Rinker Materials Reinforced 48" Diameter Spread Footing Manhole (Size - 4' X 4')ASTM C433
**Note: All new development and new installation manhole lids shall meet the minimum 30-inch opening requirement as specified in City Specification 33 05 13. Any smaller opening sizes will only be allowed for existing manholes that require replacement frames and covers.
Page 5 of 6
!!!!!!!! Attention: Mix Designs do not supersede CFW Specifications !!!!!!!!!!
Approval Spec No.Classification Manufacturer Mix ID Mix Description Design Strength @ 28 days Design Rquirements National Spec
CITY OF FORT WORTH TRANSPORTATION/PUBLIC WORKS DEPARTMENT
STANDARD PRODUCTS LIST AS OF 8/29/2025
8/28/2023 33 39 20 Curb Inlet 10 'x 3' Riser Thompson Pipe Group Inlet Riser (Size - 3 FT)ASTM C913-16
8/28/2023 33 39 20 Curb Inlet 15 'x 3' Riser Thompson Pipe Group Inlet Riser (Size - 3 FT)ASTM C913-16
8/28/2023 33 39 20 Curb Inlet 20' x 3' Riser Thompson Pipe Group Inlet Riser (Size - 3 FT)ASTM C913-16
1/12/2024 33 49 20 Drop Inlet AmeriTex Pipe &Products Drop Inlet (4' X 4')ASTM C913
1/12/2024 33 49 20 Drop Inlet AmeriTex Pipe &Products Drop Inlet (5' X 5')ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products Precast 4'x4' Storm Junction Box ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products Precast 5'x5' Storm Junction Box ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products 5' Precast Transition MH (4' MH on the top of 5' JB)ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products Precast 6'x6' Storm Junction Box ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products 6' Precast Transition MH (4' MH on the top of 6' JB)ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products Precast 8'x8' Storm Junction Box ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products 8' Precast Transition MH (4' MH on the top of 8' JB)ASTM C913
1/19/2024 33 49 20 Manhole AmeriTex Pipe &Products Type C Storm Drain Manhole on Box (4' MH on the top of RCB)ASTM C913
7/16/2024 33 49 20 Curb Inlets AmeriTex Pipe &Products 10x3 Precast** (Size 10' x 3')ASTM C913
7/16/2024 33 49 20 Curb Inlets AmeriTex Pipe &Products 15x3 Precast** (Size 15' x 3')ASTM C913
Storm Sewer - Pipes & Boxes 33-05-13
4/9/2021 33 41 13 Storm Drain Pipes Advanced Drainage Systems, Inc. (ADS)ADS HP Storm Polypropylene (PP) Pipe (Size - 12" - 60")ASTM F2881 & AASHTO M330
8/28/2023 33 41 10 Storm Drain Pipes Rinker Materials Reinforced Concrete Pipe Tongue and Groove Joint Pipe (Size - 21" or larger)ASTM C76, C655
8/28/2023 33 41 10 Culvert Box Rinker Materials Reinforced Concrete Box Culvert (Sze - Various)ASTM C789, C850
10/12/2023 33 41 10 Storm Drain Pipes AmeriTex Pipe &Products Reinforced Concrete Pipe Tongue and Groove Joint Pipe* (Size - 15" or larger)ASTM C76, C506
10/12/2023 34 41 10 Culvert Box AmeriTex Pipe &Products Reinforced Concrete Box Culvert (size - Various))ASTM C1433,C1577
10/18/2023 35 41 10 Storm Drain Pipes The Turner Co.Reinforced Concrete Pipe Tongue and Groove Joint Pipe* (Size - 15" or larger)ASTM C76, C506
10/18/2023 33 41 10 Culvert Box The Turner Co.Reinforced Concrete Box Culvert (size - Various)ASTM C1433,C1577
4/12/2024 33 41 10 Storm Drain Pipes Thompson Pipe Group Reinforced Concrete Pipe Tongue and Groove Joint Pipe* (Size Various)ASTM C76, C506
6/25/2024 33 41 10 Culvert Box Oldcastle Reinforced Concrete Box Culvert ASTM C1433,C1577
6/25/2024 33 41 10 Storm Drain Pipes Oldcastle Reinforced Concrete Pipe Tongue and Groove Joint Pipe* (Size Various)ASTM C76, C506
(4-5-2025) 03 34 13 CLSM specification
….Storm Sewer - Inlet & Structures Continues
(1-29-2025) Removed Argos, Ingram, Redi-Mix, Charley's
(4-3-2025) Bigtown Concrete updated Mix ID's
**Note: Pre-cast inlets are approved for the stage I portion of the structure (basin) only. Stage II portion of the structure are required to be cast in-place. No exceptions to this requirement shall be allowed.
Revision Comments
Page 6 of 6
CFW Product Name Manufacturer Manufacturer Product Name & Description
Makers Sales and Marketing, LLC MRT2470AB‐Type 11, 36" or 60" Rise 2/Bolt 8' Arm,
Galvanized
Makers Sales and Marketing, LLC MRT2470AB‐Type 11, 36" or 60" Rise 2/Bolt 8' Arm,
Black
Valmont Industries, Inc DB01373(page 1 of 6)‐Shoe Base Pole Type 11,
Galvanized
Makers Sales and Marketing, LLC Type 33B, 36" Rise Simplex 8' Arm, Galvanized
Makers Sales and Marketing, LLC Type 33B, 36" Rise Simplex 8' Arm, Black
Valmont Industries, Inc DB01373(page 4 of 6)‐Single Arm Type 33B, Galvanized
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P101‐Mvolt‐R2‐3K‐
MP‐NL‐P7‐AO‐RFD325607
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P101‐Mvolt‐R4‐3K‐
MP‐NL‐P7‐AO‐RFD325606
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P101‐Mvolt‐R2‐3K‐BK‐
MP‐NL‐P7‐AO‐RFD325609
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P101‐Mvolt‐R4‐3K‐BK‐
MP‐NL‐P7‐AO‐RFD325608
McFarland Cascade CREOSOTE 30/35 FOOT TIMBER POLE
Bayou Forest Products 30‐35’ .80 CCA Green Timber Pole
Makers Sales and Marketing, LLC Wood Pole Arm, 36" Rise Simplex 8' Arm, Galvanized
Makers Sales and Marketing, LLC Wood Pole Arm, 36" Rise Simplex 8' Arm, Black
Valmont Industries, Inc DB01373(page 6 of 6)‐Wood Pole Arm, Galvanized
Makers Sales and Marketing, LLC MRT33.585AB‐Type 18, 36" or 60" Rise 2/Bolt 8' Arm,
Galvanized
Makers Sales and Marketing, LLC MRT33.585AB‐Type 18, 36" or 60" Rise 2/Bolt 8' Arm,
Black
Valmont Industries, Inc DB01373(page 2 of 6)‐Shoe Base Pole Type 18,
Galvanized
Makers Sales and Marketing, LLC Type 33A, 60" Rise Simplex 8' Arm, Galvanized
Makers Sales and Marketing, LLC Type 33A, 60" Rise Simplex 8' Arm, Black
Valmont Industries, Inc DB01373(page 3 of 6)‐Single Arm Type 33A, Galvanized
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P303‐Mvolt‐R2‐3K‐
MP‐NL‐P7‐AO‐RFD322792
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P303‐Mvolt‐R4‐3K‐
MP‐NL‐P7‐AO‐RFD322794
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P303‐Mvolt‐R2‐3K‐BK‐
MP‐NL‐P7‐AO‐RFD322793
Acuity Brands Lighting, Inc.American Electric Lighting, ATB0‐P303‐Mvolt‐R4‐3K‐BK‐
MP‐NL‐P7‐AO‐RFD322795
Wood Pole Arm
CFW Lighting Approved Products List
Arterial Luminaire
Residential Luminaire
Residential‐Standard
Arterial‐Standard
Type 11 Pole
Type 33B Arm
Timber Pole
Type 18 Pole
Type 33A Arm
McFarland Cascade CREOSOTE 35/40 FOOT TIMBER POLE
Bayou Forest Products 30‐35’ .80 CCA Green Timber Pole
Makers Sales and Marketing, LLC Wood Pole Arm, 60" Rise Simplex 8' Arm, Galvanized
Makers Sales and Marketing, LLC Wood Pole Arm, 60" Rise Simplex 8' Arm, Black
Valmont Industries, Inc DB01373(page 5 of 6)‐Wood Pole Arm, Galvanized
Washington 10' Pole Acuity Brands Lighting, Inc.Holophane, CLA 10.6(0AL)FT J20P07BK‐MOD, AB‐31‐4
RFD110736
Washington 14' Pole Acuity Brands Lighting, Inc.Holophane, CLA14FT J20DMODC03BK RFD325026, AB‐
16‐4 SPEC RFD325026
Washington Luminaire Acuity Brands Lighting, Inc.Holophane, WFCL3 P40 30K MVOLT FC3 NF BK AO PR7
FRGL RFD338699
Washington Globe
Luminaire Acuity Brands Lighting, Inc.
Holophane, AWDE3 P40 30K MVOLT MS AL3 BK PR7
AO RFD‐315548
Oleander Type A Pole Acuity Brands Lighting, Inc.Holophane, PDA 12S5L20POBBK‐MOD
Oleander Type B Pole Acuity Brands Lighting, Inc.Holophane, PDA20S5L20P08BK‐MOD
Oleander Type B Arm Acuity Brands Lighting, Inc.Holophane, OHC 15IN 2A TN BK
Oleander Luminaire Acuity Brands Lighting, Inc.
Holophane, AUCL2 P40 30K AS BK L3 N P7 AO
RFD338741
Berry 12' Pole Acuity Brands Lighting, Inc.Holophane, RSA 12 50 G12 SC BK AB‐26‐4 RFD326400
Berry 20' Pole Acuity Brands Lighting, Inc.Holophane, PD20S5J20P11BK RFD338816
Berry Arm Acuity Brands Lighting, Inc.Holophane, VLC 27IN 1A TN QSM BK
Berry Luminaire Acuity Brands Lighting, Inc.
Holophane, GPLF3 P40 30K MVOLT ASY QSM BK PR7
AO SH
Banner Arms Acuity Brands Lighting, Inc.Holophane, BA‐24IN‐2A‐C0‐S4J‐BL‐075P‐BK
Cantex Inc.
Rigid Nonmetallic Schedule 80 Conduit, Meets UL 651
specifi cations and NEMA TC2, Rated for 90°C Cable,
Sunlight Resistant, 10’ Lengths and 20' lengths
Heritage Plastics
Rigid Nonmetallic Schedule 80 Electric Conduit, Meets
UL 651 specifications, RUS listed, NEMA TC‐2 and
NEMA TC‐3, Rated for 90°C Cable, Sunlight & Weather
Resistant
Atkore‐Heritage Plastics
PVC Rigid Schedule 80 Conduit, Conforms to UL 651
and NEMA TC 2, Sunlight Resistant, Listed for 90°C
conductors or cable
Prime Conduit, Inc
Schedule 80 PVC Rigid Nonmetallic Conduit, Extra
Heavy Wall EPC‐80, Sunlight resistant, Rated for use
with 90°C conductors, Meets UL651
Splice Kit With Connector NSi Industries, LLC
Gel Stub Splice Kit with Connector, Easy‐Splice, ESSLK
Series
Wood Pole Arm
Timber Pole
Conduit
Decorative‐Pedestrian
System
Southwire Type XHHW‐2 copper conductor, 600V
Encore Wire TYPE XHHW‐2 / RW90, copper conductor, Superslick
Elite, 600V/1000V
Encore Wire THHN / MTW / THWN‐2 Copper conductor, 600V
Service Wire Co Servicepro‐X XHHW‐2, 600/1,000 Volt Copper, CT
Rated
Advanced Digital Cable Inc
XHHW‐2 Low Smoke Halogen Free, Cross‐linked
Polyethylene Insulated 14 AWG‐750 MCM, 600 Volts,
90°C Dry and wet
Aluminum Wire‐Triplex Priority Wire & Cable, Inc Triplex Overhead Aluminum Conductor
Edison General Purpose, Midget Class MEN Fuses, Voltage
Rating: MEN ‐ 250 VAC, Ampere Rating: 0.5 ‐ 30 Amps,
Interrupting Rating: 10,000 RMS Amps @ 125V
Edison Modular Ferrule Fuse Blocks for Midget Class and CC
Fuses
Cooper In‐line fuse holders for Single‐Pole 13/32" x 1 1/2"
Fuses HEB‐AA
EATON
Bussmann Series, HEB breakaway and non‐breakaway
in‐line fuse holders for UL 13/32” x 1‐
1/2”supplemental fuses
EATON Bussmann Series, FNM 13⁄32˝ x 1‐1⁄2˝ 250Vac Ɵme‐
delay supplemental fuses
Connector Thomas & Betts Wire Joints for Copper Conductor, Cat No: 54615,
54620, 54625‐TB, 54635, 54640, 54630
Electrol Systems, Inc TY A (120/240) 100(NS)AL(E)PS(U)
WE Manufacturing & Controls TY A 120/240 100(NS)AL(E)PS(U)
Electrol Systems, Inc TY A (240/480) 100(NS)AL(E)PS(U)
WE Manufacturing & Controls TY A 240/480 100(NS)AL(E)PS(U)
MacLean Highline Polymer Concrete, PHA132412X0002: TIER 22 (X) 22,
500lbs
Oldcastle
Polymer Concrete, H‐SERIES UNIT, H1730‐24 TIER‐22 ‐
TXDOT 2x 1/2" CAPTIVE BOLT ‐ 2x BRASS FLOATING
NUT
Oldcastle
Polymer Concrete, H‐SERIES UNIT, H1324‐24 TIER‐15 ‐
TXDOT 2x 1/2" CAPTIVE BOLT ‐ 2x BRASS FLOATING
NUT
Kearneys NSi Industries, LLC Split Bolt Connectors, Copper Split Bolts 2 Wire, N
Series
Photocell Acuity Brands Lighting, Inc.Dark To Light, DLL Elite, Electronic Locking, Type
Photocontrol, DLL‐127 or DLL‐480
Shorting Caps Acuity Brands Lighting, Inc.Dark To Light, Part # DSHORT SBK U
Residential Luminaire TRASTAR INC.DURA‐STR10A‐3K‐120‐3‐GR‐SCL
Arterial Luminaire TRASTAR INC.DURA‐STR25‐3K‐120‐3‐GR‐SCL
Interim Products
Copper Wire/Conductor
Metered Pedestal 120‐240V
Metered Pedestal 240‐
480V
Ground Box
Fuse & Fuse Holder