Microstation Cadd Procedures

of 70 /70
STATE OF NEW HAMPSHIRE DEPARTMENT OF TRANSPORTATION EFFECTIVE: APRIL 12, 2012 2012 CAD/D P ROCEDURES A ND R E Q UIREMENTS

Embed Size (px)

description

Microstation V8i Cadd Procedures

Transcript of Microstation Cadd Procedures

  • STATE OF NEW HAMPSHIRE DEPARTMENT OF TRANSPORTATION

    EFFECTIVE: APRIL 12, 2012

    2012 CAD/D PROCEDURES AND REQUIREMENTS

  • NHDOT CAD/D Procedures and Requirements

    April 2012 i Table of Contents

    PART I GENERAL INTRODUCTION........................................................................... 1

    Disclaimer.....................................................................................................................................................................1

    About the Cover...........................................................................................................................................................1

    Revision Summary.......................................................................................................................................................2 April2012 ..................................................................................................................................................................2 July2009 ....................................................................................................................................................................2 April2007 ..................................................................................................................................................................3 April2006 ..................................................................................................................................................................3 April2005 ..................................................................................................................................................................4 April2004 ..................................................................................................................................................................4 April2002 ..................................................................................................................................................................5

    Introduction .................................................................................................................................................................6

    Current NHDOT Software Versions..........................................................................................................................7 MajorSoftwareandCurrentProductionVersions ....................................................................................................7 FutureUpgrades ........................................................................................................................................................7

    PART II GENERAL CAD/D INFORMATION ............................................................... 9

    Documentation.............................................................................................................................................................9

    Survey Datum ..............................................................................................................................................................9

    Project Journal Files ...................................................................................................................................................9 ProjectJournalGuidelines .........................................................................................................................................9 SampleCAD/DProjectJournal ................................................................................................................................10

    Directory Structure ...................................................................................................................................................14

    PART III MICROSTATION......................................................................................... 15

    MicroStation Workspace ..........................................................................................................................................15

    File Naming ................................................................................................................................................................15

    Level Assignments and Symbology ..........................................................................................................................15

    Reference File Attachments ......................................................................................................................................16

    Seed Files ....................................................................................................................................................................16 Imperial2DSeedFile(NHSEEDF2.DGN) ..................................................................................................................17 Imperial3DSeedFile(NHSEEDFT.DGN) ..................................................................................................................17

    Fonts ...........................................................................................................................................................................18

    Text Height and Spacing...........................................................................................................................................19

  • NHDOT CAD/D Procedures and Requirements

    Table of Contents ii April 2012

    Text Styles ..................................................................................................................................................................19

    Line Styles ..................................................................................................................................................................20 NHDOTCustomLineStyleResourceFiles................................................................................................................20 TrueSizeLinestyles..................................................................................................................................................20 ScaledLinestyles ......................................................................................................................................................21 CustomLinestyleScalingCharts ..............................................................................................................................21 LinestylesCreatedat1:1 .........................................................................................................................................22

    Color Table.................................................................................................................................................................22

    Cross Hatching...........................................................................................................................................................22

    Cell Files .....................................................................................................................................................................24

    Dimensioning..............................................................................................................................................................25

    Plotting .......................................................................................................................................................................25

    Batch Print/Print Organizer.....................................................................................................................................25

    Pen Tables ..................................................................................................................................................................26

    PART IV MX............................................................................................................... 27

    File Naming ................................................................................................................................................................27

    Model Naming............................................................................................................................................................27

    String Labeling ..........................................................................................................................................................27

    Style Sets.....................................................................................................................................................................28

    Feature Sets................................................................................................................................................................28

    Drawing Macros ........................................................................................................................................................29

    Cross-Section Settings Files ......................................................................................................................................29

    Macro Symbols & Lines............................................................................................................................................29

    Add-Ins .......................................................................................................................................................................29

    PART V PROCEDURES............................................................................................ 31

    Introduction ...............................................................................................................................................................31

    Exchanging Right-of-Way Data ...............................................................................................................................31

    Legacy Alignments ....................................................................................................................................................32

    Roll Plans....................................................................................................................................................................32

  • NHDOT CAD/D Procedures and Requirements

    April 2012 iii Table of Contents

    Cut Sheets...................................................................................................................................................................32

    Cross-Section Drawings ............................................................................................................................................33

    Bridge Detail Sheets...................................................................................................................................................33

    PART VI OTHER PROJECT DATA........................................................................... 35

    Drawing Quality Assurance / Quality Control........................................................................................................35

    PART VII - ENGINEERING CONSULTANT DELIVERABLE REQUIREMENTS ......... 37

    Overview.....................................................................................................................................................................37

    File Format And Delivery .........................................................................................................................................37 RequirementsForSubmittingElectronicDataToNHDOT ......................................................................................37 DataSubmission ......................................................................................................................................................38 IntermediateSubmissions .......................................................................................................................................38 DeviationFromFormat............................................................................................................................................39 MicroStationOnlyDeliverable.................................................................................................................................39 MicroStationPlotFiles(FinalDesignConsultantsOnly)..........................................................................................39 FileConversion ........................................................................................................................................................39

    NHDOT Design Process ............................................................................................................................................40 PlanPreparation ......................................................................................................................................................40 PreliminaryDesign...................................................................................................................................................41 FinalDesign..............................................................................................................................................................42 ProjectsDesignedusingInRoads .............................................................................................................................42 SpecializedDevelopmentbyDesignConsultants ....................................................................................................43

    NHDOT Resources Available for Consultants........................................................................................................44

    PART VIII - APPENDIX................................................................................................. 45

    Appendix A - MicroStation Drawing Names...........................................................................................................45 BridgeDesignDetailDrawings.................................................................................................................................45 HighwayDesignContractPlandrawings .................................................................................................................46 OtherHighwayDesignContractPlandrawings .......................................................................................................46 HighwayDesignPlanDrawings................................................................................................................................46

    Appendix B - Level Mapping Convention ...............................................................................................................49

    Appendix C - NHDOT Custom Linestyles & Font .................................................................................................51

    Appendix D MX Model Naming Convention .......................................................................................................55 PlanPreparationModels .........................................................................................................................................55 PreliminaryDesignModels ......................................................................................................................................55 FinalDesignModels.................................................................................................................................................56 OTHERMODELS .......................................................................................................................................................56

    Appendix D MX Data Transfer Formats..............................................................................................................57 LandXML ..................................................................................................................................................................57

  • NHDOT CAD/D Procedures and Requirements

    Table of Contents iv April 2012

    HALGN .....................................................................................................................................................................57 SampleHALGNInputData.......................................................................................................................................57 DescriptionofHALGNFormat .................................................................................................................................58 VERAT ......................................................................................................................................................................59 SampleVERATInputData........................................................................................................................................59 DescriptionofVERATFormat ..................................................................................................................................59

    Appendix E Construction Reports .......................................................................................................................61 SampleAlignmentReport(COGOStyle)..................................................................................................................61 SampleAlignmentReport(Coordinates) .................................................................................................................62

    Appendix F Cross Section Set Labels ...................................................................................................................63 CrossSectionDetailFeatureStrings........................................................................................................................63

  • April 2012 1 Part I General Introduction

    PART I GENERAL INTRODUCTION

    DISCLAIMER

    Theproceduresdescribed inthisdocumentareforreferenceonly. This information isprovidedonan"as is"basis. Thematerialcontained isprovidedwithoutwarrantyor liabilityofanykind to theNewHampshireDepartmentofTransportation(NHDOT).Updatingthismanual is intendedtobeacontinuousprocess. Astechnologyevolves,policieschange,andprocessimprovementsarediscovered,thisdocumentwillbeupdatedtoreflectthosechanges.Aswith any documentation, improvements can and should bemade. Any additions, suggestions orcomments for improvement are encouraged. This documentation is notmeant to be a completeinstructionaldocument.Theintentistoprovideguidelinesthat,iffollowed,willresultinbetterqualityandconsistencyforelectronicplansanddocuments.This manual, in its entirety, may be freely copied and distributed for the purpose of providing aconsistentguidetothecomputeraideddesign&drafting(CAD/D)requirementsoftheNewHampshireDepartmentofTransportation. Copiesof thismanualalongwithCAD/D resource files (style libraries,namingconventions,etc.)canbedownloadedathttp://nh.gov/dot/cadd/cadd.html.Anyrecommendationsforimprovementstothisdocumentationarewelcome.AnyerrorsfoundshouldbebroughttotheattentionoftheCAD/DStaffsocorrectionscanbemade.Foradditionalinformationordetailedexplanationsofthestandardsdescribedwithinthisdocument,contact: CAD/DSupportandDevelopment

    NewHampshireDepartmentofTransportation POBox483 Concord,NH033020483 Email:[email protected]

    Tel:6032712171

    ABOUT THE COVER

    Thisyearscovershowsthedoubledeckerbridge inSuncookcompleted in2007. Ontop isaphotoofthe completed structure takenby JerryZolleronNovember30,2007. Below it isa renderingof theproposaldevelopedduringthedesignphasebyLysaBennetCrouchoftheCAD/DSection.

  • NHDOT CAD/D Procedures and Requirements

    Part I General Introduction 2 April 2012

    REVISION SUMMARY

    APRIL2012

    PartIGeneralIntroduction

    Newsoftwareversions.PartIIGeneralCAD/DInformation

    TheprojectdirectorystructurewasmodifiedtoseparateMXdatafromcontractplandrawingdata.PartIIIMicroStation

    Updatestocellfilelisting. Seedfileinformationnowincludesgeographiccoordinatesystembeingused. InformationabouttheNHDOTpentablehasbeenupdated.

    PartVProcedures

    Theprocessforcreatingcutsheetshasbeenmodifiedalongwiththesheetnamingconvention.PartVIOtherProjectData

    NotesonQA_InputandotherGDMprogramshavebeenreplacedbydescriptionsoftaskmenus.Appendix

    ChangestoMicroStationdrawingnamesinAppendixA. LinestylechartshavebeenupdatedinAppendixC. AppendixD(MXmodelnames)hasbeenupdatedtoreflectcurrentpractices. MXStringlabellistshavebeenupdated.

    JULY2009

    PartIIIMicroStation

    Newcellfilesadded.Theseareidentifiedwithinthetext.PartVProcedures

    Newsectiontoremovedescriptionsofspecificproceduresfromsectionsdescribingsoftwareprograms. InformationaboutLegacyAlignmentshasbeenadded. Anadditionaloptionhasbeenaddedtotheprocessforcreatingcutsheets.

    Appendix

    MXStringlabellistshavebeenremovedseetheCAD/Dwebsiteforcurrentinformation.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 3 Part I General Introduction

    APRIL2007

    PartIIGeneralCAD/DInformation

    NewsectionPartIIIMicroStation

    TheBrDdirectoryforBridgeDesignfileshasbeenrenamedtoBRC. Detailsofchangestothenh_engineeringfont. AdditionofBridgeDesigncrosshatchingdetails.

    PartIVMX

    TheERW8stylesethasbeenrenamedtoERL. DocumentationofMXaddinshasbeenadded.

    PartVIEngineeringConsultantRequirements

    TheRightofWayprocesshasbeenrevised.Appendix

    AppendixAhasbeenexpandedtoincludeadditionaldrawinginformation. AppendixCshowsupdatestothenh_engineeringfont. AppendixJhasbeenupdatedtoreflectchangestotheMXaddinforaddingcrosssectiondetailsymbols.

    APRIL2006

    General

    TheCAD/Dwebsiteaddresshasbeenchangedto:http://nh.gov/dot/cadd/ [email protected]

    PartIIIMicroStation

    UseofNHDOTdefinedMicroStationlinestylesisrequired. Thetextstyleandlinestylesectionshavebeenexpandedandclarified. Thelistsofdrawingnameshavebeenexpandedandclarified.

    PartIVMX

    AerialsurveydatahasbeenmergedintotheEXDstyleset.PartVIEngineeringConsultantRequirements

    LandXMLisnowthepreferredmethodofexchangingdesigndatabetweenMXandotherdesignsoftware. Aprocessforexchangingrightofwaydatahasbeenadded. FilesubmissionrequirementsforprojectsdesignedwithInRoadshavebeenupdated.

    Appendix

    AppendixAhasbeenexpandedtoincludeadditionaldrawinginformation.

  • NHDOT CAD/D Procedures and Requirements

    Part I General Introduction 4 April 2012

    AppendixHhasbeenmodifiedtoencouragetheuseofLandXMLwhentransferringdesigndatabetweenMXandotherdesignsoftware.

    APRIL2005

    General

    Nosignificantchanges.PartIIIMicroStation

    AddedNHDOTwebsitelocationofengineeringdetaildrawings. Updatetodirectorystructureforprojectscontainingmultiplebridges. AddedtextstyleinformationforBridgeDesignprojects.

    PartIVMX

    Styleset&featuresetlistingreformattedtoincludeadditionalinformation.Appendix

    ChangestoMicroStationdrawingnamesinAppendixA. LinestylechartshavebeenupdatedinAppendixC. Specialcharactersincludedinthenh_engineeringfont(font180)arelisted. AppendixD(MXmodelnames)hasbeenupdatedtoreflectcurrentpractices. MXStringlabellistshavebeenupdated. AnewsectionAppendixJhasbeenaddedtodocumentMXCrossSectionSets.

    APRIL2004

    General

    Nosignificantchanges.PartIIIMicroStation

    ReferencestoMicroStation/JfeatureshavebeenmodifiedtoreflecttheupgradetoMicroStationv8. ReferencestoSettingsManagerhavebeenremoved. Correctederrorsincustomlinestylescalingcharts. Newcellfilesadded.Theseareidentifiedwithinthetext.

    PartIVMX

    StylesetshavebeenupdatedforMX2.6/MicroStationv8.Appendix

    ReferencestoMXversion2.5havebeenmodifiedtoreflecttheupgradetoMX2.6 ModificationshavebeenmadetotheMicroStationdrawingnamelist.Specificchangesareidentifiedin

    thedrawinglist. SomeMXstringlabelshavebeenaddedormodified.Theseareidentifiedwithinthestringlabeltables.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 5 Part I General Introduction

    APRIL2002

    GeneralConsultantdeliverablespecificationsrelocatedfromvariouspartsofthedocumentandcombinedasPART VII - ENGINEERING CONSULTANT DELIVERABLE REQUIREMENTSPartIIIMicroStation

    Theprocessforcreatingcutsheetshasbeenmodifiedalongwiththesheetnamingconvention. Theprojectdirectorystructurewasmodifiedtoincludesubdirectoriesforfrontsheetsandprofiles.The

    bridgedirectorynowincludesadditionalsubdirectories. Changestocellfilelistingtitles.celwasrenamedtostamps.cel,borders.cel,br_borders.cel,stnoffset.cel,

    andturnrad.celhavebeenadded. InformationabouttheNHDOTpentablehasbeenincluded. BatchPlotinformationhasbeenadded.

    PartIVMX

    Additionalstylesetshavebeenlisted.PartVOtherProjectData

    Informationaboutthequalityassurance/qualitycontrolsoftwarehasbeenincluded.PartVIEngineeringConsultantRequirements

    Newsection. NHDOTwillonlyacceptplandrawingsthatweredevelopedinMicroStationforprojectsthatwere

    initiatedafterApril18,2002. MicroStationplotfilereturnablechangedfromHPGLtoPDFformat.

    Appendix

    ModificationshavebeenmadetotheMicroStationdrawingnamelist.Specificchangesareidentifiedinthedrawinglist.

    InformationaboutMicroStationlevelcolors,styles,andcellnameshavebeenremovedtoavoidpotentialconflictswithdocumentationontheCAD/Dwebsite.

    SomeMXstringlabelshavebeenaddedormodified.Theseareidentifiedwiththestringlabeltables.

  • NHDOT CAD/D Procedures and Requirements

    Part I General Introduction 6 April 2012

    INTRODUCTION

    ThisdocumentcontainstheNewHampshireDepartmentofTransportations(NHDOT)specificationsforelectronic (computer) data as it relates to engineering design projects. It explains the minimumrequirementsthatmustbemetforallComputerAidedDesign&Drafting(CAD/D)dataproducedbyandfortheNewHampshireDepartmentofTransportation.ThisistoensurethatCAD/Dfilescanbeusedbythe entire project team throughout all phases of project development. While the requirementscontained herein provide a basis for uniform CAD/D practice forNHDOT projects, precise rules thatwouldapplytoallpossiblesituationsthatmayarisearenotpossibletodescribe. Situationsmayexistwherethesestandardswillnotapply. Ifvariancesfromthe"CAD/DPROCEDURESANDREQUIREMENTS"arenecessary for a project, they must be approved in writing by the NHDOT Project Manager anddocumentedintheProjectJournalFileasdefinedherein.ThecreationofMicroStationdrawingsand/orlevelsforfeaturesthatarenotdescribed inthisdocumentshallbedocumented intheProjectJournalFile. ThecreationofMXmodels thatarenotdescribed in thisdocumentshallbedocumented in theProjectJournalFile.As a minimum, NHDOT Design staff and engineering consultants are expected to adhere to thestandardsthatwereinforceatthetimethecontractwasinitiated.Althoughnotrequired,followingthelateststandardisrecommendedwheneverfeasible.Inaddition to the traditionalhardcopydelivery items,NHDOT requiressupplementaryelectronicdatadelivery items. Thisdata shallbe submitted in the formats specifiedby thisdocument. In general,designdataandDigitalTerrainModel(DTM)dataistobeprovidedintheMXmodelfile,LandXML,or3D DXF file formats, and graphical data is to be provided in MicroStation's .DGN drawing format.Organizationswishing toperformprofessionalengineeringservices forNHDOTarerequired todeliverelectronicdataasspecifiedby thisdocument. Thisspecificationalsorequiresorganizations toacceptandutilizepertinentelectronicinputdataasprovidedbyNHDOT.TheseelectronicdeliveryitemsDONOTreplaceanyhardcopydeliveryitems.Thisdocumentispublishedasanupdatetothe"CAD/DPROCEDURESANDREQUIREMENTS"documentdatedJuly2009andsupersedesallCAD/Dstandardspreviouslypublished.

    Trademarks

    MicrosoftandWindowsareregisteredtrademarksofMicrosoftCorporation.MicroStation,MDL,InRoads,GEOPAK,MX,andMXROADareregisteredtrademarksofBentleySystems,Inc.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 7 Part I General Introduction

    CURRENT NHDOT SOFTWARE VERSIONS

    NHDOTdesirestostaycurrentwithstateofthearttrendsinthemarket,however,budgetconstraints,statewide implementation, impact on users, and providing support for the new features must beconsideredpriortoanychange.AsNHDOTmakesachangethatresultsinmodifyingelectronicprocedures,the"CAD/DPROCEDURESANDREQUIREMENTS"willbeupdatedwherenecessarytoreflectthechange.Alistofthemodificationswillbefoundintherevisionsummary.Asarule,untildocumentationismodified,deviationfromthecurrentdatedrequirementsmustbeapprovedbytheProjectManager.

    MAJORSOFTWAREANDCURRENTPRODUCTIONVERSIONS

    1. MicroStationV8i(SELECTseries2)(version08.11.07.443)2. MXV8i(SELECTseries2)(version08.11.07.536)3. MicrosoftOffice2000productswithExcel2002

    FUTUREUPGRADES

    BentleyreleasedMicroStationSELECTseries3asthisdocumentwasbeingpreparedandaSELECTSeries3 version of MX is forthcoming. The Department will be testing those updates when time andavailabilitypermit.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 9 Part II General CAD/D Information

    PART II GENERAL CAD/D INFORMATION

    DOCUMENTATION

    Documentation of NHDOT CAD/D practices and procedures can be found on the Internet athttp://nh.gov/dot/cadd/. Summariesofselectedprocedureswillbe found inPARTVPROCEDURESbeginningonpage31.

    SURVEY DATUM

    ForNHDOTprojects,theverticaldatumisbasedonNGVD29andthecoordinatesystemisNAD83/86.

    PROJECT JOURNAL FILES

    PROJECTJOURNALGUIDELINES

    AProject Journalwillbeproduced foreachproject. On consultantdesignedprojects, a copyof thejournalfilewillbedeliveredwitheachelectronicprojectplansubmission.Thepurposeforthisjournalisto aid downstream customers of the CAD/D data so theymay utilize existing CAD/Dwork in theirprocesses. The format of the journal will be an electronic file, either in text format or a formatsupportedbyMicrosoftWord2000.Asaminimum,thejournalwillcontainthefollowinginformation:

    Alisting(Index)oftheprojectfiles,includingbriefdescriptionsofeachfileandwherethefileislocated.

    Documentationabout theCAD/Dsoftwareused,specialCAD/Ddecisionsmade,exceptions tostandardsthatweremade,problemsencounteredandworkaround,orother important issuesthataroseduringthecourseoftheCAD/Dwork.Forexample,ifacustomlinestyleneededtobe created, the justification, resource file, and fileswhere that line stylewasusedwouldbedocumented in the Journal. Other documentationwould include the design software used(includingversionnumber),particularsoftwaresettings,andotherinformationthatwouldhelpadownstreamuserofthedataunderstandhowitwascreated.

    ImportantdatathatshouldalsobecontainedintheJournalinclude:

    AllinformationnecessaryfortheregenerationoruseofthosefilesbysubsequentcustomersoftheCAD/Ddata

    Documentthedesigndata,controllingalignmentandprofilenamesandgeometryinput/outputfiles,relevantsurveyinformation,crosssectionsandthemethodologyusedtoobtainthefinalgeometriccontrolsintheCAD/Dproduct.

    NHDOThasnotestablishedaspecificformatfortheJournalfile.Thesamplefileshownonthefollowingpagesshouldbeusedaguidelineforthetypeofinformationtobeincludedandformatthatisexpected.

  • NHDOT CAD/D Procedures and Requirements

    Part II General CAD/D Information 10 April 2012

    TheprojectjournalmustbekeptuptodateastheCAD/Ddesignworkprogressesandbedeliveredwiththeprojectonthepreferredmediaforarchivalpurposes.

    SAMPLECAD/DPROJECTJOURNAL

    CAD/DPROJECTJOURNAL(12345_project_index.doc)

    4/13/00

    PROJECTJOURNALThisfilecontainsinformationabouttheproject12345andthecorrespondingelectronicfilescontainedintheprojectdirectory.Thisfileshouldbekeptuptodateandarchivedwith the project's electronic files. When filling in the required information, pleasedeletetheinstructionsandexamplesinordertomaintainaconciserecord.

    PROJECTDESCRIPTIONStateProjectNumber:12345FederalAidNumber:N/ACounty:MerrimackProjectManager:ProjectManagerProjectDesigner:ProjectDesignerProjectDirectory:N:\CADD\pbt\town\12345\cadd\prj

    SCOPEOFWORKThescopeofworkforproject12345goeshere.Includeasmuchdetailasnecessarytodefinetheworkdonefortheproject.

    PROJECTFILES

    Listanyfilesthatdonotfitintothestandardnamingconvention.Includeabriefdescriptionofthedatacontainedineachone.

    MICROSTATIONFILEINFORMATION

    SeedFileUsedforthisProject: nhseedft.dgn,nhseedf2.dgn,nhseedm.dgn,nhseedm2.dgn(selectone,deletetherest)

  • NHDOT CAD/D Procedures and Requirements

    April 2012 11 Part II General CAD/D Information

    NonStandardDrawings

    Listanydrawingsthatarenotonthestandardnamingconventionlistwithabriefdescriptionofeachone'scontents.

    PlotInformation

    Listinformationaboutbatchprintspecifications,pentables,orotherfeaturesusedtogeneratetheprintfiles.

    MXFILEINFORMATION(orinformationforotherdesignprogramsused)

    MXTopoinputfile:topo.inp

    PreliminaryDesignEngineer:YourName

    FinalDesignTeamLeader:TeamLeader

    MXDesignInputFileNames Description

    pdesignmc0m.inp ThefilethatcreatesthealignmentMC0Manddesignstringsuptoandincludingtheinterfacestage.

    psectmc0m.inp CreatestheoldgroundandproposedcrosssectionsforalignmentMC0M

    MXDesignOutputFileNames Description

    Topo.prn OutputfromTopo.inpReportsassignedstringlabelsanderrors.ContainsX,Y,Zcoordinatesofthesurveypoints.

    Triangles.prn OutputfromTriangles.inpReportscrossingstrings,minimumandmaximumelevationsandplanarea.

    Sprofiles.prn OutputfromSprofiles.inpReportsx,y,zcoordinatesofeachsurveyalignment.

  • NHDOT CAD/D Procedures and Requirements

    Part II General CAD/D Information 12 April 2012

    Ssections.prn OutputfromSsections.inpReportsstringassignmentsaswellaspointandoffsetinformationforeachsurveyalignment.

    TEXTFILES

    Includeinformationaboutoutputfiles,geniofiles,orotherASCIIfilesprovidedwiththeprojectdrawings.

    NONSTANDARDMODELNAMES

    Includeinformationaboutanymodelsthatdonotconformtostandardnamingconventions.Thesecouldbemodelsdevelopedasstudyalternativesorotherspecialuses.

    SPECIALINFORMATION/COMMENTS

    Includeanyinformationaboutspecialconsiderationsorproblemsdiscoveredduringthedesignprocess.MAINLINE"MainStreet(NH25)"Survey(PlanPrep)MasterAlignmentModel: SALIGN MasterAlignmentName: .MC1STriangleModel:.................TrianglesTriangleString:..................TX00CrossSectionModel: ........ SSECTMC1SPreliminaryDesignMasterAlignmentName: .MC1MMasterAlignmentModel: PALIGNDesignModel:...................PDESIGNMC1MProposedTriangleModel: ProposedTriangleString: . CrossSectionModel: ........PDESIGNMC1MSECTIONSFinalDesignMasterAlignmentName: . MasterAlignmentModel: DesignModel:................... ProposedTriangleModel: ProposedTriangleString: . CrossSectionModel: ........

  • NHDOT CAD/D Procedures and Requirements

    April 2012 13 Part II General CAD/D Information

    SIDEROADPleasantStreetSurvey(PlanPrep)MasterAlignmentModel: SALIGNMasterAlignmentName: .MC2STriangleString:..................TX00CrossSectionModel: ........ SSECTMC2SPreliminaryDesignMasterAlignmentName: .MC2AMasterAlignmentModel: PALIGNDesignModel:...................PDESIGNMC2AProposedTriangleModel: ProposedTriangleString: . CrossSectionModel: ........PDESIGNMC2ASECTIONSFinalDesignMasterAlignmentName: . MasterAlignmentModel: DesignModel:................... ProposedTriangleModel: ProposedTriangleString: . CrossSectionModel: ........

    CrossSectionSettingsFile(CSU) Description

    mc1m.csu CrosssectionsforMainSt.includingdrivesandskewedsections.

    mc1m_all.csu CrosssectionsforMainSt.cutateverypointonthealignmentfordrainagestudy.

    mc2a.csu CrosssectionsforPleasantSt.includingdrivesandskewedsections.

  • NHDOT CAD/D Procedures and Requirements

    Part II General CAD/D Information 14 April 2012

    DIRECTORY STRUCTURE

    The standard directory structure being used for CAD/D projects within NHDOT is shown below:Directoryand filenameswillonlycontainalphanumericcharactersandunderscores ("_"). Nospaceswillbeincludedinnames.

    CAD/DfilesarestoredindirectoriesundertheCaddfolder.FilesthatareusedwithMicroStationorbymultiplebureausarestoredinthePrjfolder.FilesthatareusedwithMXv8iarestoredintheMXfolder.Thefollowingfolderswillcontainfilesthatareonlypertinenttothatparticularbureau:

    BRCBridgeDesignEnvEnvironmentHwyHighwayDesignRowRightofWayTrfTraffic

    TheBRCfoldercontainsthefollowingsubdirectories:AbutA DetailplansdepictingAbutmentAfooting,masonry,and

    reinforcing.AbutB DetailplansdepictingAbutmentBfooting,masonry,and

    reinforcing.BrSite GeneralPlan,SitePlan,notes,andboringlogs.DetailsMiscellaneousdetails,forexampleBridgeandApproachRail.Pier DetailplansdepictingPierfooting,masonry,andreinforcing.PrelimPreliminaryPlans.Afterpreliminaryplansareaccepted,pdffiles

    oftheGenplan&Siteplandrawingsarecreated.Otherdrawingsarecopiedintothisdirectoryandrenamed.

    Super Superstructuredetails.

    TheCutSheetfolderunderPrjiswhereHighwayDesign'sfinalcontractplanDGNfileswillbestored.FrontsheetsarestoredintheFrontSheetfolderunderPrj.BridgeDesigncontractplanfilesarestoredinthevariousBridgedirectories.

    Theimperial_macros,imperial_stylesandtheMxDatafoldersunderMXarecreatedbyMX.Theimperial_macrosandimperial_stylesstoreprojectspecificmacrosandstylesets.MXDataisusedtostoremiscellaneousMXfiles.

    Iftherearemultiplebridgesonaproject,theBRCdirectorystructureistypicallymodifiedsothatdrawings foreachbridgearekeptseparate.The subdirectories under BRC can be named for the feature beingcrossedor incaseswherethesame feature iscrossedmultipletimes,thebridgenumberasshownhere.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 15 Part IV - MX

    PART III MICROSTATION

    MICROSTATION WORKSPACE

    Throughacollaborativeeffort, theNHDOThasmadeavailableaspreadsheet (nhdotdownloads.xls) toclarifyhowtobestandmosteasilyutilizethe filesprovided fordownloadontheDOTswebsite. Thespreadsheet and associated readme files found in nhdotmsv8iworkspace.zip should provide theinformationnecessarytoduplicatetheintentoftheMicroStationworkspaceusedatNHDOT.Thiswillaidtheconsultant inproducingplansthatmeettheexpectations laidout intheDepartment's"CAD/DPROCEDURESANDREQUIREMENTS"documentwithminimalinterferencetoasitesestablishedworkspace.

    FILE NAMING

    AnattemptshallbemadetohaveMicroStationfilesnamedusingonlyaneightcharacterfilenamewitha.DGNextension.However,itisunderstoodthatthiswillnotalwaysbepossibleorpreferable.Drawingnameswillonlycontainalphanumericcharacters,"",and"_". No spacesorother specialcharactersshallbeused.SeeAppendixAMicroStationDrawingNamesbeginningonpage45formoredetails.

    LEVEL ASSIGNMENTS AND SYMBOLOGY

    ThefilesmentionedinthissectionareavailableontheCAD/DwebsiteorcanberequestedthroughtheProjectManager.ThewebsiteaddressislistedintheDOCUMENTATIONsectiononpage9.Level libraryfilescontain levelnamesandcolor/weight/style informationforMicroStation .DGNs. ForHighwayDesigntherearelevellibraryfilesavailableformostdetaildrawings.Thesefileshavethesame3characternameasthedrawingwitha.csvextension.Forexample,thelevelnamingfilefordrawing12345exd.dgnwillbeexd.csv.Therearetwo*.CSVfilestobeutilizedwhencreating.DGNsfortheBureauofBridgeDesign.Thefirstfileiscalledbrc.csv,andstandsforBRidgeCutsheet.Itcontainsthenamesrequiredtoaccuratelyplacegraphicalelementsonacutsheet (also referred toasadetailsheet). Thesecond file,calledbrd.csv,containsthenamesrequiredtoplacegraphicalelementsina.DGNatprojectcoordinates.Manyofthenamesinbrd.csvarerequiredinordertoconvertelementstoMXfromMicroStation.Levelstandardsforfrontsheetsisfsh.csv,andforallothercutsheetsisthebxx.csv.FiltersfordisplayingbordersareincludedinBorderFilters.dgnlib.Standard plan drawings aremaintained by the CAD/D Section and were revised and approved on7/29/2010.TheyareavailableontheNHDOTwebsite(www.nh.gov/dotDoingBusinesswithDOTEngineers/ConsultantsStandardPlansforRoadConstruction). SymbolsheetscanalsobefoundontheNHDOTwebsite (www.nh.gov/dotDoingBusinesswithDOTEngineers/ConsultantsDetailSheetsHighwayDesign)

  • NHDOT CAD/D Procedures and Requirements

    Part IV - MX 16 April 2012

    Lineweights,stylesandtextheightsshallconformtotheNHDOTlevelmappinglocatedontheNHDOTCAD/Dwebsite. UseofNHDOTdefinedMicroStation linestyles isrequired. Theconsultant,with theapprovaloftheProjectManager,maycreatesymbolsthatarenotcoveredintheNHDOTDesignManualor contained in NHDOT cell libraries that are needed to complete project plans. Resource filescontaininganylinestylesand/orsymbolscreatedbytheconsultantforuseontheprojectdrawingswillbeprovidedtoNHDOT.MicroStationsymbols,includingstandardborders,arecontainedinNHDOTsstandardcelllibrariesandare available inMicroStation .CEL file format. A standard color table, line style resource fileswithNHDOT line styles and font library with NHDOT fonts for use with MicroStation are available fordownload.

    REFERENCE FILE ATTACHMENTS

    A reference file isaMicroStationdrawingorotherCAD/D fileattachedasabackground toanactivedesignfile,thusallowingseveraldesigngroupstosharethesameinformationwithouttheneedtocopythefile(s).MicroStationandMXv8icanattachareferencefilebyoneofthreedifferentways:

    1. Name only the path to the referenced file is resolved by theMicroStation configurationvariableMS_RFDIR.

    2. Relativepaththereferencefilenameanditslocationrelativetothemasterfile.3. URLaddressthefileisattachedintheformofaURLaddressusingrelativepaths.

    InorderforaprojecttobedeliveredtoNHDOTinanelectronicformatthatwillallowfutureuseofthefiles forprintingpurposeswithoutmodification to the files, the reference filesmustbeattached inawaythatwillallowMicroStationorMXv8itoresolvethereferencefileattachmentpathsregardlessofthe drive or parent directory of the project. Option 1 above is the preferredmethod for NHDOTprojects, since it allows the files to bemoved from drive to drivewithout losing the reference fileattachments.However,thisoptionrequirestheMicroStationconfigurationvariable,MS_RFDIR,besetforallNHDOTprojects.

    SEED FILES

    MicroStationusesseedfilestocreatealldesignfiles.Theseseedfilesaretemplatesinwhichstandardparameters are set according to what is needed to begin drafting for a specific type of work inaccordancewithNHDOTstandards. Seed filesallow theuser tobeginwork inastandard formatandmaintain uniformity. The seed file defines the working units for the file, global origin, coordinatesystem, view attributes, default color table, text settings, coordinate readout and several otherimportantparameters.NHDOTsuppliesseedfilesforboth2Dand3Ddrawings.

    Bydefault,NHDOTdesignteamsareworkingwith2DMicroStationdrawings.Ifaconsultantpreferstouse3DMicroStationdrawings,thisshouldbementionedpriortoobtainingsurveyordesigndatafromtheDepartment.

    Twoof themost importantsettings in theseed fileare theworkingunitsandglobalorigin. Workingunitsareexpressedasmasterunitsandfractionalsubunits.Thenumberofpositionalunitspersubunitiscalledtheworkingresolution.Theworkingresolutiondeterminestheprecisiontowhichelementsaredrawn.TheformatfortheworkingunitsinMicroStationisdefinedasMU:SU(masterunits,subunits).

  • NHDOT CAD/D Procedures and Requirements

    April 2012 17 Part IV - MX

    IMPERIAL2DSEEDFILE(NHSEEDF2.DGN)

    WorkingUnits:MasterUnits=ftSubUnits=inchesGlobalOrigin: X=500 Y=500Resolution 254/inch

    IMPERIAL3DSEEDFILE(NHSEEDFT.DGN)

    WorkingUnits:MasterUnits=ftSubUnits=inchesGlobalOrigin: X=500 Y=500 Z=10,000Resolution 254/inch

    The global origin has been set at 500, 500, 10000using the NAD83 New Hampshire State Planecoordinatesystem.Usingthesecoordinates,theseedfiles can be used for both drawings based at StatePlane Coordinates and drawings, such as crosssections,profiles, typicalsandspecialdetails,usingalocalcoordinatebase. The10,000unitoffsetallowsMX data with null elevations to be transferredproperly.

    To reset the globalorigin foradrawing file,enter the keyinGO=500,500,10000anduse the rightmousebuttontoissuea"reset"command.

  • NHDOT CAD/D Procedures and Requirements

    Part IV - MX 18 April 2012

    FONTS

    MicroStation font resource files are binary files created from font cells, TrueType, Postscript, orAutoCADSHXfonts.MicroStationwillreadmultiplefontresourcefilesaccordingtothepathssetbytheMS_SYMBRSCconfigurationvariableintheselectedworkspace.However,withinMicroStationtheyarecompiledintoalistofallthefontsfromalltheresourcefilesthatwerefound.Ifonefilecontainsafontwiththesamenumberassignedasanotherfontresourcefile,theuserwillseethelastonelocated.TheNHDOTfontresourcefilesarecallednhcustomfont.rsc&nhttfont.rsc.AnyfontswithintheNHDOTresource files thatareno longer inusewillbemaintained forbackwardcompatibilitypurposes. Thefonts containedwithin theNHDOT resource filesaredescribedbelow. Fontnumbersbelow170arereservedforstandardMicroStationfonts.NHCUSTOMFONT.RSC

    FontDescription

    180 nh_engineering(Engineeringw/bridgeanddraftingsymbols)NonalphanumericcharacterscontainedwithinthisfontarepicturedinAPPENDIX C - NHDOT CUSTOM LINESTYLES & FONTonpage51.

    Thefollowinginformationisonlyincludedforhistoricalreference.ProjectdrawingsshouldusetheWindowstruetypefontsinsteadoftheMicroStationfontslistedbelow.NHTTFONT.RSC

    FontDescription

    170 TrueTypefontArial

    171 TrueTypefontArialBold

    173 TrueTypefontCourier

    174 TrueTypefontCourierBold

    176 TrueTypefontTimesNewRoman

    177 TrueTypefontTimesNewRomanBold

    182 TrueTypefontComicSans

    183 TrueTypefontComicSansBold

  • NHDOT CAD/D Procedures and Requirements

    April 2012 19 Part IV - MX

    TEXT HEIGHT AND SPACING

    Standard text heights and fonts have been defined to ensure uniformity and legibility on all CAD/Ddrawings. Thecorrect textheight is shownon the levelmapping tableand isdependenton theplotscale. Note that the text height listed represents both the text height andwidth. Since, themostimportant issue with text is that it should be legible, font and text heightmay vary if absolutelynecessary.Textlinespacingvariesbetweenhalfofthetextheightandthetextheightdependingontheuse.

    TEXT STYLES

    Forbridgedrawings,textstylesareavailableatvariousengineeringandarchitecturalscales.ThestylesarelocatedwithinnhdotTextandDimStyleLibraryFT.dgnlib(Imperial).

    ThesedgnlibsshouldbedefinedbytheMS_DGNLIBLISTvariable.Thestylenamesincludetheintendedpurposeofthetextandthescaleofthedrawingstheywillbeusedon.nh_eng UsedfornoteanddetailtextTitlenh_eng UsedfordetailtitletextNoteTitlenh_eng UsedforasmallerorsubtitletextDimensionandtextstylelibrariesusedbyBridgeDesignareavailableontheNHDOTCAD/Dwebsite.

  • NHDOT CAD/D Procedures and Requirements

    Part IV - MX 20 April 2012

    LINE STYLES

    LinestyleispartofthesymbologyofgraphicalelementsinMicroStation.AnelementcanbesettothestandardMicroStationlinestyles(numbered07)ortoacustomlinestyledefinedinacustomlinestyleresourcefile. Custom linestylesareuserdefinableresourcefilesforthedisplayofdifferentpatterns,forexample,a tree line, fence line,guardrail,etc. Whenanelement isdrawn inMicroStationwithacustomlinestyle,thedefinitionofthelinestyleisnotcontainedwithinthedesignfile.TheresourcefilefromwhichitwasselectedmustbepackagedwiththedesignfileanditmustbefoundbyMicroStation'sconfiguration in order to properly display the line. Therefore, users are strongly discouraged fromcreatingtheirowncustom linestyles. UsetheNHDOTsuppliedcustom linestyleresourceswheneverpractical. GraphicaldepictionsofNHDOTMicroStation linestylesare shown inAPPENDIX C - NHDOT CUSTOM LINESTYLES & FONTonpage51.

    NHDOTCUSTOMLINESTYLERESOURCEFILES

    Asmentioned above, custom line styles are user definable inMicroStation. NHDOT linestyles arecreated at twodifferent scales (1:1 and1=50)dependingon the intendeduse. These settings areincluded in the task menus. The task menus are described in more detail in DRAWING QUALITY ASSURANCE / QUALITY CONTROLonpage35.Cautionmustbeexercisedasthedefinitionforthelinestyleismaintainedinaresourcefileandadesignfileonlycontains links tocustom linestyle resource files. Ifanew (nonstandard)custom linestyle isdevelopedbyauser,thoseresourcefilesmustbedeliveredwiththeproject.UsersshallnotmodifytheNHDOTdeliveredstandardcustomlinestylefiles.

    TRUESIZELINESTYLES

    Linestylesthataredefinedtobeaspecificsize(suchaspipeandrailroadstyles)shouldalwaysbedrawnatascaleof1.Stylesinthisgroupinclude:BmGrDblBmGrLtBmGrRtCblGrLtCblGrRtCblGrMedCurbLt

    CurbRtDrainPipeJerseyBarrierPCurbLtPCurbRtPavemarkPipeE#

    PipeP#RailroadSheetPileTrafBarlsUnderDrainXPipE#XPipP#

    StandardNHDOTCustomlinestylefiles lineft.rsc pipeft.rsc

  • NHDOT CAD/D Procedures and Requirements

    April 2012 21 Part IV - MX

    SCALEDLINESTYLES

    Linestylesforplandrawingshavebeencreatedforuseona1=50'scaleImperialdrawing.Thisincludesmost of the linestyles available. When these linestyles are used on 1"=20' Imperial drawings, theyshouldbescaledby0.4.Chartsshowingscalevaluesforotherdrawingscalesareshownbelow.

    CUSTOMLINESTYLESCALINGCHARTS

    Imperial

    Scaleforplotting

    Ratio Customlinestylescalesetting

    1=1 1:1 0.0016 6=1' 1:2 0.003 3=1' 1:4 0.006 2=1' 1:6 0.01

    11/2=1' 1:8 0.013 1=1' 1:12 0.02 3/4=1' 1:16 0.026 1/2=1' 1:24 0.04 3/8=1' 1:32 0.053 1/4=1' 1:48 0.08 1"=5' 1:60 0.1

    3/16=1' 1:64 0.1066 1/8=1' 1:96 0.16 1=10' 1:120 0.2 3/32=1' 1:128 0.2135 1/16=1' 1:192 0.32 1=20' 1:240 0.4 1=30' 1:360 0.6 1=50' 1:600 1 1=100' 1:1200 2

  • NHDOT CAD/D Procedures and Requirements

    Part IV - MX 22 April 2012

    LINESTYLESCREATEDAT1:1

    Thelineft.rscfilealsocontainscustomlinestylescreatedatascaleof1:1.Inorderfortheselinestobeproperlyproportioned,theusermustenterthescaleassociatedwiththeplotsizeofthedrawingintheLineStylesdialogboxforcustom linestylesbeforeplacingthe line. The linestylesforwhichthisruleappliesinclude:ArBegOpnArBegSldArEndOpnArEndSldArrowBr

    BreakBrBreakDimBrDimBrGroundBrITSProp

    LeaderBrLedgeBrRocklineBr

    Therearemultiplewaystoalterthescaleoflinestylesonadrawing.Tosetthescale,selectElementLineStyleCustom.Selectthelinestyle,checkthe"Scalefactor"boxandenterthedesiredscale.Clickonthegraphicrepresentationofthe linestyleto implementthechange. Analternativeway isto issuethekeyindwgceltscale#wherethe#isreplacedwiththedesiredscale.Futurelineswillbedrawnatthenewscale.Toalterthescaleoflinestylesthathavealreadybeendrawn,selectalltheelementstobechanged.IssuetheChangeLinestyleScale#keyinreplacingthe#withthedesiredscale.

    COLOR TABLE

    Astandardcolor table isnecessary toprovidevisualconsistency thusallowingusers toeasily identifyelements in shared filesand forconsistency incolorplotting. NHDOThas itsowndefaultcolor tablecallednhcolor.tbl.Thetabledefines256colorsfromwhichanactivecolorcanbeselectedandappliedtoanelement.NHDOTsblackandwhiteplottersareconfiguredtoprintallcolorsexcept1014inblack.Colors1014willplotintheshadesofgraydisplayedinMicroStation.

    CROSS HATCHING

    CrosshatchingusedbyBridgeDesignisshownonthenextpage.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 23 Part IV - MX

  • NHDOT CAD/D Procedures and Requirements

    Part IV - MX 24 April 2012

    CELL FILES

    ThefollowinggraphiccellfileshavebeencreatedforuseonNHDOTprojects.Itemsshowninitalicshavebeenaddedsincethepreviousedition.

    alignment.cel symbolsforalignmenttransfersandmstasks

    borders.cel cutsheetborders(includingfrontsheets,ROWsummary,propertylayoutandxsectionbordersandtheirtextcells)

    br_Borders.cel miscellaneousbridgeborders

    br_bore.cel boringsheetsymbols

    br_Misc.cel riprap,slopelines,waterstops,sheetpiles,sectionAA,Northarrow,shearconnector,&RRsection

    br_pile.cel HPsectionsandPileKey

    br_precast.cel NewEnglandBulbTees(precastconcretebeams)

    br_Rail.cel 2bar,3baraluminumandT2,3,4steelbridgeandapproachrails

    br_Railmisc.cel existing/superseded,temporary,andTexas101bridgeandapproachrails

    br_weld.cel weldsymbols

    drainage.cel proposeddrainagedetailcells

    environ.cel environmentaldetailcells

    existin.cel existingtopographycells

    geotech.cel geotechnicalcellsgrdrail.cel proposedguardraildetailcells

    legends.cel hearingplanlegends

    logos.cel NHDOTandotherlogos

    notes.cel projectbegin/endnotes

    pavemark.cel proposedpavementmarkingdetailcells

    profile.cel cellsforprofiledrawings

    row.cel proposedrightofwaydetailcells

    signals.cel proposedsignalizationdetailcells

    signs.cel proposedsigndetailcells

    stamps.cel miscellaneousroll/plansheetcells

    StnOffset.cel StationOffsetmacrocells

    turnrad.cel Imperialturningradiitemplates

    utility.cel proposedutilitydetailcells

    xsect.cel crosssectiondetailcells

    ThefollowingpatterncellfilehasbeencreatedforuseonNHDOTprojects.

    nhpatern.cel hearingplanremovalpatterns

    CellsfromBentley'sarchpa.celmayalsobeused.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 25 Part IV - MX

    DIMENSIONING

    DimensionsshouldappearasshownintheHighwayDesignManualwiththefollowingexception:ThedimensionsforBridgedetaildrawingsshallbeplacedtohavetheappearanceofthosethatfollow:

    TheuseofDimensionStyles isstronglyencouragedfor the placement of all dimensions on structuraldesigndrawings,since,ataminimum, itwillselectthe proper text height. It is understood that inordertoachievethedimensionappearancesshownabove, theDimension Styledefaultswill, at times,needtobeoverridden.

    Dimensionstylenamesreflectthescale.

    Dimension and text style libraries are availableontheNHDOTCAD/Dwebsite.

    PLOTTING

    Theplotterconfiguration file (fileextension .PLTCFG)isusedtosetdefaultplottersettings.Blackandwhiteplotconfigurationfileshavebeenmodifiedtoforceallpen colors to black except pens 1014 which aredefinedasvariousshadesofgrayintheNHDOTcolortable. Line weights for full size plotters are asindicatedinthegraphic. Plotterdriverfilesshouldbeeditedforplotterspecificadjustmentsonly.Changesintendedtoaffectallplotsshouldbemadeinthepentables.

    BATCH PRINT/PRINT ORGANIZER

    Toplotcutsheets,arectangularelementdrawnon levelBorderand incolor84,style0,weight0hasbeen placed at the outer edge ofNHDOT border cells. Batch Print looks for these elementswhenplottingcutsheets.WhendevelopingCAD/Ddrawings,elementsofthiscolor,styleandweightshouldbe avoided unless an element defining a batch print limit is being created. A print styleBorderLevelandColorwascreatedforPrintOrganizertousethissameelement.

  • NHDOT CAD/D Procedures and Requirements

    Part IV - MX 26 April 2012

    PEN TABLES Apentableisusedtoalterthewayadrawingissenttotheplotter.Itcanbeusedtocontrolthelevelsthatareplotted,controltheorderinwhichtheyareplotted,maketextsubstitutions,orrunmacrosatplottime.NHDOTusesapentablecallednhdotpen.tbltomakeanumberoftextsubstitutionsinplanbordersandfrontsheets.Thevariablesthataresubstitutedaretypicallydefinedintheprojectcontrolfile(pcf).Currentlydefinedsubstitutionsinclude:

    Drawingtext Textsubstitution Description $PROJCLASS$ $(PROJCLASS) Projectclass $STNO$ $(STNO) Stateprojectnumber $SCALE$ $(NH_SCALE) Projectscale $FEDNO$ $(FEDNO) Federalprojectnumber $NHPROJ$ $(NHPROJ) "N.H.PROJECTNO.12345" $ROUTENO$ $(ROUTENO) Routenumberorroadname $CSHTOT$ $(CSHTOT) Totalnumberofconstructionplansheets $LSHTOT$ $(LSHTOT) $MRSHTOT$ $(MRSHTOT) TotalnumberofMaterials&Researchplansheets $RSHTOT$ $(RSHTOT) Totalnumberofrightofwayplansheets $SSHTOT$ $(SSHTOT) Totalnumberofshorelandplansheets $WSHTOT$ $(WSHTOT) Totalnumberofwetlandplansheets $BT$ $(BT) Totalnumberofbridgesheets $PBT$ $(PBT) Totalnumberofpreliminarybridgesheets $BRNO$ $(BRNO) Bridgeinventorynumber $BRDESCR$ $(BRDESCR) Bridgedescription(roadoverfeaturecrossed) $BRFILNO$ $(BRFILNO) Bridgefilenumber $BRDIR$ $(lastdirpiece(_DGNFILE)) Bridgedirectory $TIME$ _TIME_ Currenttime $FILE$ _FILE_ DGNfilename $USER$ $(_USTN_USERNAME) Username $DATE$ _DATE_ Currentdate $FILENAME$ $(basename(_DGNFILE)) DGNfilenamewithoutdirectorypath $ROWTOWN$ $(ROWTOWN) "TOWNOF" $COUNTY$ $(COUNTY) Countyname $TOWN$ $(TOWN) ProjectName(Town) $MODELNAME$ _MODELNAME_ Modelname $REVNUM$ $(REVNUM) RightofWayplanrevisionnumber $REVDATE$ $(REVDATE) RightofWayplanrevisiondate $PROJNAMENUM$ $(PROJNAMENUM) identifierforProjectExplorertofindV:/project

  • NHDOT CAD/D Procedures and Requirements

    April 2012 27 Part IV - MX

    PART IV MX

    FILE NAMING

    MXfilesshouldbenamed insuchawaythatsomeoneunfamiliarwiththeprojectcanfigureoutwhatthe file is for. MXprojectsare typicallygivennamesbeginningwith the townname followedby thestateprojectnumber.Forexample:Concord12345.mmd.Otherfiletypesarelistedinthetablebelow.

    Type Extension Description

    Input .INP UsedtostorelinemodecommandstocreateormodifyMXstrings

    Output .PRN Usedtostoretheresultsofaninputfileorinteractivecommands

    Draw .DRW AninputfilethatisusedtocreateadisplayusingadrawingmacroormajoroptionDRAWand/orENHANCEcommands

    Journal .JOU AjournalfilestorescommandsissuedduringanMXsessionsotheycanbererunatalatertime

    MODEL NAMING

    SuggestedMXmodelnamesarelistedinAPPENDIX D MX MODEL NAMING CONVENTION,onpage55.Anyvariationsfromthisconventionshallbenotedintheprojectjournalfile.

    STRING LABELING

    MXdataiscontainedinstringsandthestringsarecontainedinmodels.Eachstringhasauniquefourcharacter label. Typically the first two charactersof the string labelareused to identify the typeofstring. NHDOT's string labelingconventioncanbe found in theMX sectionof theCAD/Dwebsiteat theaddresslistedintheDOCUMENTATIONsectiononpage9.

  • NHDOT CAD/D Procedures and Requirements

    Part IV - MX 28 April 2012

    STYLE SETS

    A style set is a collectionof styleswhich isused todraw a completemodelor a selectedpartof it.BeginningwithMXv8i,stylesetreferencestoMXmacrosymbolsandmacro lineshavebeenreplacedwithMicroStation cell and linestyle references. NHDOT style and features sets are stored on thenetwork inMX'sPublicfoldersotheyareaccessibletoallusers. Thiseliminatestheneedtoupgradeeachworkstationwhenchangesaremade.

    FEATURE SETS

    Feature setsareameansofgrouping stringsand identifying themwithadescription. TheyareusedthroughoutMXtomakeiteasiertoselectstringsforsubsequentoperations.Thestringsbelongingtoafeaturesetarespecifiedusingapartialstringname,andaredrawnwithastyleset(usuallyhavingthesamename as the feature set). Fordesigndetail,NHDOTuses amodified versionofmxroad.fns toconformtoMXdesignwizards.WhentransferringdetailbetweenMXandMicroStation,beawarethatMicroStationelementsaredrawnbasedonthemodel'sdefaultstyleset.ThisshouldbethesamestylesetthatwasusedtodrawtheMXDPW/DPF.

    NHDOTDevelopedStylesetsforMXdrawingsStyleSets FeatureSets Description

    brd8.pss brd8.fns UsedtotransferproposedbridgestructurestringsbetweenMXandMicroStation.

    catchment.pss catchment.fns Usedtotransferdrainagecatchmentmodels.

    ctr8.pss ctr8.fns Usedtodrawandtransfercontours.

    env8.pss env8.fns Usedtodrawandtransferenvironmentalfeatures.

    erl.pss erl.fns UsedtodrawandtransferexistingRightofWaydetail.

    exd.pss exd.fns

    UsedtodrawexistingandaerialsurveydetailinMX2.6thatwillbecomeMicroStationv8idetaildrawings.Thisstylesetisusedtocreatetheproject'sEXDandAIRdgnfiles.

    mxroad.pss mxroad.fns

    UsedforMXdesignoptions.

    Usedtodrawalignments.AlignmentstobetransferredtoMicroStationaredrawnwiththeNHAlignaddin.SeetheCAD/Dwebsiteformoredetails.

    ply8.pss ply8.fns Usedtodrawandtransferproposedroadwaydetail.

    prw8.pss prw8.fns UsedtotransferproposedRightofWaystringsbetweenMXandMicroStation.

    pvm8.pss pvm8.fns Usedtodrawproposedpavementdesign.

    trav.pss trav.fns Usedtodrawsurveytraverses.

    xsu.pss xsu.fns Tobesetasthemodeldefaultforcrosssectionmodels.CrosssectionstobetransferredtoMicroStationaredrawnwiththeXSMSmacro.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 29 Part IV - MX

    DRAWING MACROS

    Inadditiontothestyleandfeaturesetsmentionedabove,MXuserscanalsodrawdetailandsectionswithdrawingmacros.AnumberofthesemacroshavebeendevelopedandareavailablefordownloadfromtheNHDOTwebsite.

    CROSS-SECTION SETTINGS FILES

    Cross sectionsandprofiles canbegenerated inanumberofdifferentways. Using the crosssectionwizard withinMX allows the user to save parameters defining the crosssection set. These savedsettingsfileshavea.CSUextensionandarestoredintheprojectdirectory.Thesettingsfilewilldefinethetypeofsectionscut(basedonthecrosssectionfeaturesetused),modelsselected,andinformationaboutanyspecialstationsorskewedsections.Bydefault,thecrosssectionwizardusestheinformationinthecrosssectionmodel'sdefaultstylesettodeterminethedifferenttypesofcrosssections. StringlabelsforcrosssectionsarelistedinAPPENDIX F CROSS SECTION SET LABELSonpage63. ForNHDOTprojects,thedefaultcrosssectionstylesetandfeaturesetarelistedinthetableonthepreviouspage.

    MACRO SYMBOLS & LINES

    SymbolsforusewithversionsofMXsoftwarebeforev8i,includingstandardlinepatterningsymbols,areavailableintheMX.MMSand.MMLfileformats.TheseMXsymbolsandlinesarebeingphasedoutinfavor ofMicroStation cells and lines in theMX v8i style sets. This data is available on theNHDOTwebsiteorcanberequestedthroughtheProjectManager.

    ADD-INS

    MX AddIns are applications such as Visual Basic programs that can interactwithMX. NHDOT hasdevelopedanumberoftheseprogramstosimplifysomeoperations. TheseprogramsareavailableontheCAD/Dwebsite.

    CONREPO Usedtogenerateanoutputfileofstringpointsfromaspecifiedmodel.Thisreportiscommonlyusedtoprovide3dimensionalstringinformationtononMXconsultants.

    DataImport ForimportingGPSdataorotherdelimited/formattedtextfilesintoMX.

    NHAlign-v8i UsedtocreateanalignmentdrawingthatcanbetransferredtoMicroStation.Improvedtohandlespiralcurves.

    NHAliReport UsedtocreateaformattedreportofanMXalignment.ThisreportcanalsobeusedtoplotcurvedataonaMicroStationalignment.

    NHDraper Usedtoaddelevationstooneormorestringsinamodel

    NHProfile UsedtodrawexistingandproposedprofilesthatcanbetransferredtoMicroStation.

    PointScan Usedtocreateareportofprojectfeaturesreferencedbystationandoffset.

    RenameM UsedtorenameMasterAlignmentstringsIteliminatestheneedtoaddressit'sSubreference,theGeometrystring,andit'sSubreference.

    XSDetail Usedtocreatesectionsetsrepresentingdetailsymbolsplottedoncrosssections.Forbestresults,crosssectionscreatedwiththisprogramshouldbedrawnwiththeXSMSdrawingmacro.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 31 Part V Procedures

    PART V PROCEDURES

    INTRODUCTION

    ThissectionofferssummariesofsomeNHDOTCAD/Dprocedures. It isnot intendedtoprovidean indepthdiscussionofanyparticulartopic.Formoredetails,refertotheCAD/Dwebsite.

    EXCHANGING RIGHT-OF-WAY DATA

    Rightofway data is routinely updated during the project's lifetime. This information is typicallymaintainedbytheNHDOTBureauofRightOfWayforbothinhouseandConsultantdesignedprojects.Knowing thatDOT staff andConsultantsbothneed toworkon the existing rightofwaydrawings, aprocesshasbeendevelopedtoensurethatthisdataiskeptcurrentandaccurate.Theexistingrightofwayinformationwillbedividedbetweentwodrawings.Onecontainsthelinework(ERL) and the other will have the text information (ERT). It is intended that the Department willmaintainthemasterERLdrawing(abstracting)andsendtheconsultantacopywhenupdateshavebeenmade.TheBureauofRightOfWaywillcontinue toutilizeDesignHistoryand that recordwillbemaintainedthroughoutthe lifeoftheproject. This is in linewithhowbusinesswasconductedwhentheprocessincludedtheROWAbstractingmylar.TheBureauofRightOfWaywillcontinuebusinessasusualwiththe ability tomake changes at any time during the design processwith the understanding that theNHDOTConsultantReviewerwillbenotifiedwhenchangeshavebeenmade.Theprocessshallbe:

    ERTandERLdrawingsarecreatedbytheBureauofRightOfWayandDesignHistory isturnedon. Undernormalcircumstances,only theNHDOTBureauofRightOfWayshouldbemakingchangestotheERLdrawing.

    TheConsultantreceivesacopyoftheERTdrawing.Attheirdiscretion,theConsultantisfreetoadjusttextpositionormakeothercosmeticchangestoimproveappearanceofthedrawings.

    Updates to parcel ownershipsmade by the NHDOT abstractors are revised on the ERTdrawingandacopyoftheupdatedERTdrawing issenttotheConsultant.TheConsultantwillberesponsibleforupdatingtheircopyoftheERTdrawing.DesignHistorycanbeusedtohighlightchangesandtextrevisionsmadetotheERTdrawingbyNHDOTstaff.

    TheConsultantalsoreceivesacopyoftheERLdrawingwhichisreferencedintootherdrawings(Notcopiedormerged).

    Updates to property lines, ROW lines, easement lines etc. aremade to the ERL.dgn byNHDOT Bureau of RightOfWay staff and a copy is sent to the Consultant. The revisedERL.dgnsupercedesallpreviousversions.

    Updates to theERL.dgncanbereviewedusing theDesignHistory to identifychangesandimpactstothepropertylineandROWlinelocations

  • NHDOT CAD/D Procedures and Requirements

    Part V Procedures 32 April 2012

    RightofwaydataissubmittedinbothpaperandDGNformattoNHDOTBureauofRightofWayforreviewandapprovalpriortotheproductionofrecordablemylars.

    LEGACY ALIGNMENTS

    Priortothe implementationofaCAD/Dsystem inthe1980s, itwascustomarytoshowalignmentsofformerprojectsonplandrawingsasareferencebetween theoldandnewprojects. Computeraideddesign, electronic survey equipment and advancement in GPS technology eliminated the need toreferenceformeralignmentswhencreatingnewones. Asaresult,formerprojectdatawasno longershownontheplandrawings.TheBureauofRightofWayhasexpressedaneed to reference thishistorical information to facilitatethe locatingofrightofwayboundariesthatwere laidoutduringtheseformerprojects. Toassistthisprocess, future projects are to include information about these legacy alignments. Wheneverpossible,thisinformationshouldalsobeaddedtocurrentprojects.Theprocessincludes:

    Researching former projects to identify those within the limits of the current project. Onconsultantprojects,theBureauofRightofWaywilldotheresearch.

    Obtainingalignmentinformationfromtheasbuiltplans. Draftingthatinformationontothealignmentdrawingofthecurrentproject.

    ROLL PLANS

    Projectrollplanfilenamesarecomposedofthreeparts;theNHDOTstateprojectnumber(firstfivecharacters),drawingtype(lastthreecharacters),andthe.DGNfileextension.AfurtherexplanationofstandardnamingconventionsanddrawingtypedesignatorsusedbyNHDOTiscontainedinAPPENDIX A - MICROSTATION DRAWING NAMESbeginningonpage45.

    CUT SHEETS

    TheHighwayDesigngroupatNHDOTpresentlyusesamethodforpreparingcutsheetswhereasingledrawing is created foranentire setofdrawings (generalplans,drainageplans,etc.)witheach sheetstoredinadifferentmodelwithinthedrawingfile.The drawing file names will be the project number followed by the type of drawing such as12345genplans.dgn for thegeneralplansofproject#12345. Within this file therewillbemodels foreach individual sheetusing thenaming conventionoutlined in the following table. Forexample, themodelforthefirstgeneralplansheetwillbecalledGEN01.Formore details of the processes for developing cut sheets, see the documentation on the CAD/Dwebsite.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 33 Part V Procedures

    Realizing that there are a number of differentways to accomplish this same task, variations to themethoddescribedabovemaybeacceptablewithpriorapprovalofNHDOT.ConsultantswishingtouseanalternativemethodshouldcontacttheCAD/DDevelopmentStaff.Anydeviationsfromtheseformatsshall be noted in the Project Journal File. A listing of drawing type designators used byNHDOT iscontainedinAPPENDIX A - MICROSTATION DRAWING NAMESbeginningonpage45.

    CROSS-SECTION DRAWINGS

    NHDOThasdecidedtostoreMicroStationcrosssectionsinoneormorefileseachcontaininganumberofcrosssections.ThismethodiscompatiblewithMXandallowsforasmallernumberofDGNfilestobecreatedfortheproject.Thesectionsareplottedusingabatchprintoptionthatprintsallinstancesofanelementcontainedwithinthebordercell.Realizing that there are a number of differentways to accomplish this same task, variations to themethod described above may be acceptable with prior approval. Consultants wishing to use analternativemethodshouldcontacttheCAD/Ddevelopmentstaff.

    BRIDGE DETAIL SHEETS

    A single detail sheet frequently requires the placement of several details of various scales. Toaccomplishthis,alldetailsshallbedrawnatascaleof1:1whileusingtheNHDOTstandardworkingunitsdefinedwithintheNHDOTseedfiles. Thedetailsheetshallbecomposedbyapplyingscalefactorstothe selfreferencedattachmentsof thedetaildrawing. Theborderof thedetail sheet shallbea cellplacedonthedrawingatascaleof1.Detaildrawingsshallnotbecreatedbyeitherincreasingthescaleoftheborderorbytemporarilyadjustingtheworkingunitsofthefile,inanyway.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 35 Part VI Other Project Data

    PART VI OTHER PROJECT DATA

    DRAWING QUALITY ASSURANCE / QUALITY CONTROL

    Toaid theconsultantand inhousestaff indevelopingasetofcontractplans that conform to the requirements contained inthisdocument,NHDOThasdevelopedaseriesoftaskmenusforworking on MicroStation drawings. Using the task menusprovidedwillensurethatelementsonthedrawingsarecreatedaccording to the establishedMicroStation standards. At thistime, use of the taskmenus is optional although their use isstronglyencouraged.The taskmenu system is composed of a collection of dgnlibfiles.Thedgnlibfilescontaintheelementtemplates,tools,andtasks for the particular drawing name. Separate taskmenushavebeencreated foreachof thestandarddrawingnamesatboth50scaleand20scale. Metric fileswillbe createdwhennecessary. The taskmenu for 20scale alignment drawings isshownhere. Themenu includessectionsforthevarioustypesof alignments, each containing commands to set thelevel/color/stylefordraftingtheparticularfeature.For NHDOT operators, a macro checks the dgn name andproject scale when a drawing is opened to determine theappropriate task list to load. If thedgnname isnonstandardtheNH50bxxTasksare loadedassumingthedgn isacutsheettypeofdrawing.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 37 Part VII Deliverable Requirements

    PART VII - ENGINEERING CONSULTANT DELIVERABLE REQUIREMENTS

    OVERVIEW

    The purpose of this section is to establish the minimum acceptable criteria for electronic CAD/Ddeliverables. Obtainingdrawingsandgroundmodels inacommon formatwill reduce theamountoftimespentbecomingfamiliarwiththedesignsiftheyaretransferredfromonedesignertoanotherandallowsfortheirreuseinthefuture.

    FILE FORMAT AND DELIVERY

    REQUIREMENTSFORSUBMITTINGELECTRONICDATATONHDOT

    AllelectronicdatafurnishedtotheNHDOTshallusetheappropriatenamingschemeandformatforthetypeofdatatobetransmitted. It isvery importanttoclearlycommunicatewhat isbeingtransmittedandtodescribetheformatofthetransmittedfiles.Aletteristobeattachedtoallsubmissionsstatingbriefly:1. Filecontent2. FileFormat(zipped,MicroStation,MX,etc.andtheutilityused)3. MXand/orMicroStationversion4. NumberofCDs,DVDs,etc.5. Files must be in the proper format before transmitting to NHDOT. No translating of

    informationbyNHDOTpersonnelshallberequired.6. Iffilesarezippedorbackedup,abriefexplanationoftherecommendedproceduretoextract

    thefilesshouldbeincluded.7. VersionsofsoftwaremustbecurrenttoorfullycompatiblewiththatoftheNHDOT.8. EachdisksubmittedshallbelabeledanddatedwithaminimumoftheStateProject#anddate.

    IfaseriesofCDs/DVDsaretransmitted,thedisklabelshallalsoincludethedisknumberandthetotalCDs/DVDsofthatset,(ex:1of10).OthersubsequentCDs/DVDsshallbelabeledsoastouniquelyidentifyeachgrouporsetandshallincludethesequencenumberfollowedbythetotalnumberinthegroup(ex:2of10,3of10,etc.)

    9. NHDOT reserves the right to reject any file transmitted that does not conform to theserequirements.

  • NHDOT CAD/D Procedures and Requirements

    Part VII Deliverable Requirements 38 April 2012

    DATASUBMISSION

    In addition to hard copy drawings specified by the contract, the consultant shall submit electronicdrawingfilesinMicroStation.DGNfileformat.Electronicfilesshallbedeliveredononeofthefollowinginorderofpreference:

    1) DVD2) CDROM3) PlacedonDOTFTPsite14) Flashdrive

    The final submission shall include all files necessary to reproduce the cut sheet drawings aswell ascopies of the original rollplan drawings used to generate the cut sheets. Documentation ofproceduresandprojecthistoryshallbemaintainedinaProjectJournalFile.AnindepthdescriptionoftheProjectJournalFileisinPARTIIGENERALCAD/DINFORMATIONbeginningonpage9.TheProjectJournalFilewillbeprovidedwiththesubmission. Anydrawingsnot included intheNHDOTstandarddrawinglistwillbeidentifiedandwillincludeadescriptionoflevelsusedoneachdrawing.DetaileddescriptionsofthedatatobeprovidedbyNHDOTtotheconsultantandexpecteddeliverablesatvariousstagesoftheproject'sdevelopmentareincludedinthenextsection,NHDOT DESIGN PROCESSonpage40.IfMicroStationtablesforlinestyles,multilines,leveltables,symbologytables,database,specialfonts,oranyspecialuserdefinedfeatureisused,thatinformationmustbeprovidedandshallbecomepropertyof NHDOT. Similarly, anyMXmacro, symbol, linestyle, style set, or feature set developed by theconsultantthatisnecessarytoproperlydisplaytheprojectdatashallbecomepropertyofNHDOT.AnyMX input filedeveloped togenerate,enhance,oralter theproject'sdesign that the consultant feelswouldbebeneficialtofuturedesignersoftheprojectshouldalsobeprovided.Anameanddescriptionof each filemust also be provided. NHDOTwill not distribute these items to any other individual,consultantorStateTransportationDepartmentwithoutpriorpermissionofthedeveloper.

    INTERMEDIATESUBMISSIONS

    The consultant shallbeprepared to submit sample cut sheet,profile, typicalordetail, and/or crosssection sheets for reviewof conformity to theNHDOTCAD/D specifications at various stagesof theproject's development. As a minimum, the final design consultant should be prepared to submitelectronicprojectdrawingsatthePreliminaryPlans,Specifications&Estimate(PPS&E)andPS&Estagesoftheproject.Dependingontheproject,NHDOTmayrequestelectronicsubmissionsatamoreorlessfrequentinterval.Sincenumerousgroupsworktogetherduringtheproject'sdesign,itisimportantthateveryoneusesthesamedata.Therefore,whenchangesaremadethatwouldaffectthedesign,updateddrawingsshallbeprovidedtotheNHDOTConsultantReviewer.These,inturn,willbedistributedtoallaffectedparties.

    1TheNHDOTftpsiteislocatedatftp://nhftp.admin.state.nh.us/.ContactyourConsultantReviewerforusernameandpasswordinformation.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 39 Part VII Deliverable Requirements

    DEVIATIONFROMFORMAT

    Any file tobe submitted thatdeviates from the abovementioned formatmusthavepriorNHDOTapproval. The approval must be in writing with the name of the individual from NHDOT whopermittedthevaryingformat.

    MICROSTATIONONLYDELIVERABLE

    Forprojects thatwere initiatedafterApril18,2002,NHDOTwillonlyacceptplandrawings thatweredevelopedinMicroStation'sDGNformat.TranslationsfromAutoCADoranyotherCAD/Dsoftwarewillno longerbeallowedonthoseprojects. Projects initiatedbeforethatdatewillcontinuetofollowtherequirements in place at the time the projectwas initiated. Engineering consultantsmay, at theirdiscretion,choosetofollowasubsequentreleaseoftheserequirements.

    MICROSTATIONPLOTFILES(FINALDESIGNCONSULTANTSONLY)

    In addition toMicroStation format drawings, plot files of project cut sheets in PDF format will berequired at the completionof theproject. Plot files shouldbenamedwith the convention forplansheets outlined Appendix A - MicroStation Drawing Names beginning on page 45 using a .PDF fileextension. The purpose of this requirement is to provide a viewable and reproducible copy of thedrawingasitexistedattheendoftheconsultantcontract.

    FILECONVERSION

    ThisinformationonlyappliestoprojectsinitiatedpriortoApril18,2002.Translation tables, conversion tables, or special software programs have not been created orstandardizedforexchanging informationbetweencommonfileformatssuchasDXF,DWG, ICES, IGES,orsoftwaresuchasAutoCAD,ARCVIEW,ARCINFO,GDS,etc.MicroStationprovidesmethods forexchanging select file typesbutdata isoftenmodifiedduring theprocess. TheConsultant is solely responsible forany translationandverification required to convertnonMicroStationgraphics files to the currentNHDOTMicroStationdesign file format. All translateddesignfilesshallconformtothestandardsadoptedbyNHDOTforelectronicplansandthespecificationsrequiredinthisdocument.ThosefilesshallbeconvertedtoMicroStationandthoroughlyreviewedpriortotransmittingtoNHDOT.

  • NHDOT CAD/D Procedures and Requirements

    Part VII Deliverable Requirements 40 April 2012

    NHDOT DESIGN PROCESS

    This section is intended todescribe thedata that is tobeprovidedwhenaprojectmoves fromonedesignphase to thenext. Thereare twomajor transitionpointswhereHighwayDesignCAD/Ddataneedstobetransferred:theturnoverfromthePlanPreparationSectiontoPreliminaryDesignandtheonefromPreliminaryDesigntoFinalDesign.TheBridgeDesignsectionisresponsiblefordevelopingthepreliminaryand/orfinalplansand,asaresult,BridgeDesignfallswithinboththePreliminaryandFinalDesignsectionsdefinedbelow.

    PLANPREPARATION

    ThePlanPreparation section is responsible for takingproject surveyandpreparing thedigital terrainmodel(DTM)andbasedrawingsthatwillbeusedduringthedesignprocess. TheyshouldalsobetheonestoinitiatetheProjectJournalFiledescribedinPARTIIGENERALCAD/DINFORMATIONbeginningonpage9.Bydefault,NHDOTdesign teamsareworkingwith2Ddrawings. Ifaconsultantprefers touse3Ddrawings,thismustbementionedpriortoobtainingsurveyordesigndatafromtheDepartment.

    ElectronicdatatobeprovidedbyPlanPreparationto:

    NHDOTPreliminaryDesignSectionandconsultantsusingMXsoftware:

    1. CopyoftheMXmodelfile2. Copy of the topo input file (TOPO.INP) containing survey data and Plan Preparation

    modifications/enhancements.3. CopyofannotatedMicroStation.DGNfilesdevelopedfortheproject.4. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.

    ConsultantswithoutMXsoftware:

    1. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromtheMXmodelfile2. CopyofannotatedMicroStation.DGNfilesdevelopedfortheproject.3. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 41 Part VII Deliverable Requirements

    PRELIMINARYDESIGN

    The Preliminary Design section is responsible for taking the data provided by the Plan Preparationsection and designing the project up to the Public Hearing stage. This includes gathering all datanecessary to prepare designs to be presented at the Public OfficialsMeeting, Public InformationalMeetings,andPublicHearing.ElectronicdeliverablesexpectedatthecompletionofthePreliminaryDesignprocess:

    NHDOTPreliminaryDesignStaffandConsultantsusingMXsoftware:

    1. CopyoftheMXmodelfile2. Copyofanyinputfilesavailabletorecreatethesubmitteddesign3. CopyofMicroStation.DGNfilesdevelopedfortheproject4. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.5. CopiesofanyMicroStationcellfilesandlinestyleresourcefilesusedontheprojectthatare

    notincludedintheNHDOTstandards.

    ConsultantswithoutMXsoftware:

    1. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromthedesignsoftware2. Copy of project horizontal and vertical alignments and associated design features in

    LandXML formats. Descriptionsof file transfer formatscanbe found inAPPENDIX D MX DATA TRANSFER FORMATSbeginningonpage57

    3. CopyofMicroStation.DGNfilesdevelopedfortheproject4. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.5. CopiesofanyMicroStationcellfilesandlinestyleresourcefilesusedontheprojectthatare

    notincludedintheNHDOTstandards.

    ElectronicdatatobeprovidedbyNHDOTPreliminaryDesignsectionto:

    NHDOTFinalDesignSectionandconsultantsusingMXsoftware:

    1. CopyoftheMXmodelfile2. Copy of the topo input file (TOPO.INP) containing survey data and Plan Preparation

    modifications/enhancements3. CopyofMicroStation.DGNfilesdevelopedfortheproject4. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.5. CopyoftheProjectPublicHearingPlaninPDFformat

    ConsultantswithoutMXsoftware:

    1. Copy of project horizontal and vertical alignments and associated design features inLandXML formats. Descriptionsof file transfer formatscanbe found inAPPENDIX D MX DATA TRANSFER FORMATSbeginningonpage57

    2. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromtheMXmodelfile

  • NHDOT CAD/D Procedures and Requirements

    Part VII Deliverable Requirements 42 April 2012

    3. CopyofMicroStation.DGNfilesdevelopedfortheproject4. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.5. CopyoftheProjectPublicHearingPlaninPDFformat

    FINALDESIGN

    TheFinalDesignsectionisresponsiblefortakingthedataprovidedbythePreliminaryDesignSectionorPreliminaryDesignConsultantanddesigningtheprojectuptotheContractPlansstage. This includesrefining the project design as approved at the Public Hearing, preparing a project estimate, biddocuments,andobtainingnecessaryconstructionpermits.Electronicdeliverablesexpectedattheproject'scompletion:

    AllConsultantsandNHDOTFinalDesignStaff

    1. CopyofMicroStation.DGNfilesdevelopedfortheproject2. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.3. COGO and coordinate reports of each alignment similar in format to the ones shown in

    APPENDIX E CONSTRUCTION REPORTSonpage614. Stationandoffsetlistingofproposedbounds5. PlotfilesinPDFformatofeachcontractplansheet

    ConsultantsusingMXsoftware:

    1. CopyoftheMXmodelfile2. Copyofanyinputfilesavailabletorecreatethesubmitteddesign3. CopiesofanyMicroStationcellfilesandlinestyleresourcefilesusedontheprojectthatare

    notincludedintheNHDOTstandards.

    ConsultantswithoutMXsoftware:

    1. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromthedesignsoftware2. Copy of project horizontal and vertical alignments and associated design features in

    LandXML formats. Descriptionsof file transfer formatscanbe found inAPPENDIX D MX DATA TRANSFER FORMATSbeginningonpage57

    3. IftheprojectwasdesignedwithInRoads/SelectCAD,includefilesmentionedbelow4. CopiesofanyMicroStationcellfilesandlinestyleresourcefilesusedontheprojectthatare

    notincludedintheNHDOTstandards.

    PROJECTSDESIGNEDUSINGINROADS

    Ifaproject isdesignedwith InRoads the following files shouldbedelivered aspartof theelectronicdeliverable:

    Surfacedata: (*.dtm):These fileswillcontainexistingandproposedsurface information. Thisinformationwill includebut isnot limited to thesurface triangulation. Other informationthat will potentially be found in the dtm include planemetric features like: breaklines

  • NHDOT CAD/D Procedures and Requirements

    April 2012 43 Part VII Deliverable Requirements

    representing existing and proposed objects, feature lines for entities like R.O.W. oreasements,aswellasrandompoint informationthatcandepictfeatures likecatchbasins,mailboxes,orothersinglepointfeatures.

    Alignmentdata (alg):Thiswillcontainallcoordinategeometryandalignment information fortheprojectalignments.

    Roadway designer files (*.ird): The roadway designer filewill include the templates (Typicalsections) in addition to the roadwaymodel definition, this is the recipe to build yourdesign.Itemsinthisfileinclude:superelevation,linkstothealignmentsusedinthedesign,aswellasthelimitsofdesign.

    Surveydata (*.fwdorother formats): If the survey for theprojectwas completedbypeopleoutside the department all data used to create the existing conditions plans should beprovided. Ifthesurveywasdone in InRoadsSurveythe.fwdfilesthatwere imported intoInRoadsSurveyshouldbeprovided. If thesurveywasdonewithadifferentsoftware thedatabroughtintoInRoadsshouldbeprovidedinitsoriginalformat.

    StyleSheets (*.xsl): InRoadsreportstylesheetsused forreports included inthedesignshouldalsobedeliveredwiththeproject.

    InRoads Preferences (*.xin): This filewill contain the settings used to control the display ofinformation aswell as thedefault valuesdisplayed in InRoadsdialogs for generating thedesigngraphics.

    Storm&Sanitary files (*.sdb):Thedesign informationentered into InRoadsStorm&Sanitaryshould also be included for the Departments use. Thiswill include location, sizes andstructuretypesforthedrainagedesign.

    QuantityManagerfiles(*.mdb):ThisfileisthedatabasecontainingtheautomaticallygeneratedquantitiesfromInRoadsfortheproject.

    SPECIALIZEDDEVELOPMENTBYDESIGNCONSULTANTS

    Any specialized programs, macros, utilities, symbology, etc., developed by the consultant that arenecessary to properly display drawings submitted to NHDOT shall be included with other projectdeliverables.

    Submission of copies of other specialized programs,macros, utilities, symbology, etc. developed toimproveMicroStation andMX drafting and design processes is encouraged. It is understood thatNHDOT accepts these itemswithout any guarantee of usefulness or expectations of support by thedeveloper. In addition,NHDOTwillnotdistribute these items to anyother individual, consultantorStateTransportationDepartmentwithoutpriorpermissionofthedeveloper.

  • NHDOT CAD/D Procedures and Requirements

    Part VII Deliverable Requirements 44 April 2012

    NHDOT RESOURCES AVAILABLE FOR CONSULTANTS

    To assist in the production of the required CAD/D files,NHDOT has providedMX andMicroStationsupport files available from the Department's web site. The website address is listed in theDOCUMENTATION section on page 9. Many of the files that are available are described in the LEVEL ASSIGNMENTS AND SYMBOLOGYsectiononpage15.

  • NHDOT CAD/D Procedures and Requirements

    April 2012 45 Part VIII Appendix

    PART VIII - APPENDIX

    APPENDIX A - MICROSTATION DRAWING NAMES MicroStationdrawingnameswillbeginwiththeNHDOTstateprojectnumberfollowedbythedrawingtype.Thetablesbelowshowthetextthatwillfollowtheprojectnumberalongwithadescriptionofthedrawing.

    Forexample:12345ALI.DGNwouldcontainalignmentdataforproject12345.

    BRIDGEDESIGNDETAILDRAWINGS

    Forprojects that containmultiplebridges the sixdigitbridge inventorynumber shallbeused after thenamesbelow. Forexample:12345AAbut123_456.DGNwillcontaintheabutmentAmasonry forthe12345project forbridgenumber123/456.

    AbutA

    AAbut AbutmentAMasonryARebar AbutmentAReinforcementAWings AbutmentAWingsAReWings AbutmentAWingsReinforcementAFoot FootingAMasonryAReFoot FootingAReinforcement

    AbutB

    BAbut AbutmentBMasonryBRebar AbutmentBReinforcementBWings AbutmentBWingsBReWings AbutmentBWingsReinforcmentBFoot FootingBMasonryBReFoot FootingBReinforcement

    Pier

    Pier1 Pier1MasonryRePier1 Pier1ReinforcementPier2 Pier2MasonryRePier2 Pier2Reinforcement

    Box

    BXDeck BoxDeckBXReDeck BoxDeckReinforcementBXFoot BoxFootingBXReFoot BoxFootingReinforcementBXWings BoxWingsMasonryBXReWings BoxWingsReinforcementBXWalls BoxWallsBXReWalls BoxWallsReinforcementBXDetls BoxDetails

    Frame

    FRDetls FrameDetailsFRFoot FrameFootingFRReFoot FrameFootingReinforcementFRALeg FrameLegAFRReALeg FrameLegAReinforcementFRBLeg FrameLegBFRReBLeg FrameLegBReinforcementFRDeck FrameDeckFRReDeck FrameDeckReinforcementFRWings FrameWingsFRReWings FrameWingsReinforcement

    PrelimPlans

    PreGen PreliminaryGenplanPreSite PreliminarySitePlan

    BrSite

    Genplan GenplanSiteplan SiteplanBorings BoringLogsBorReq BoringRequestDevlView DevelopedViewsBrNotes BridgeNotesBrDetour BridgeDetour

    Super

    DeckDetls DeckDetailsDeckBars DeckReinforcingDeckSect DeckSectionGirder GirderLayoutandDetailsFramePlan FramingPlanSSDetls SuperStructureDetailsShoes BridgeShoesJoints FixedJointsandExpansionJoints

  • NHDOT CAD/D Procedures and Requirements

    Part VIII Appendix 46 April 2012

    HIGHWAYDESIGNCONTRACTPLANDRAWINGS

    Drawing(DGN)Name Content PrefixforModelNames* 12345crbplans Curbing CRB 12345drnplans Drainage DRN 12345detplans Detour DET 12345eroplans Erosion ERO 12345genplans General GEN 12345geoplans Geotechnical GEO 12345lndplans Landscaping LND 12345pvtplans PavementMarking PVT 12345plplans Propert