Town of Fishers Digital Record Drawing Submittal Requirements Index

Transcription

1 Town of Fishers Digital Record Drawing Submittal Requirements Index The following three (3) items are included within this digital record drawing submission package: 1. Digital Record Drawing Submittal Outline a. This document is to be followed to outline general digital submittal requirements for the project including payment and delivery items, file types, etc. 2. Digital Record Drawing Submittal Requirements & Review Checklist a. This document is to be used as a checklist to follow to make sure that the specific details of each attribute are included in the submission. 3. Resolution R030110A a. This document is included for reference and is the Town Council Resolution requiring all development to submit digital record drawing submissions to the Town. Version 5.0 1

2 Town of Fishers, IN Digital Record Drawing Submittal Outline Introduction This document is provided to support Resolution No. R030110A A resolution of The Town of Fishers providing for the submission of Record Drawings and the standardization of the digital information submittal format. This document outlines the submittal requirements and process for providing digital Record Drawing data to the Town of Fishers prior to the release of a Section of Subdivision or the issuance of a Certificate of Occupancy. This As-Built data must be delivered to the Town's Department of Engineering at One Municipal Drive, Fishers, IN along with payment by check (payable to Town of Fishers) for the review fee. You must contact the Department of Engineering at for the appropriate review fee. One set of Record Drawing plans (required As-built sheets only) on paper shall be submitted to the Town of Fishers Department of Engineering along with the necessary digital files in order to complete the review. Review comments will be submitted electronically to you via a review checklist. After successful completion of the digital Record Drawing submittal process, one set of Record Drawing plans on Mylar shall be submitted to the Town s Department of Engineering. Questions concerning Resolution No. R030110A, Record Drawing submittals, and any exceptions to this resolution should be directed to the Engineering Technician for the Town of Fishers, Brent Cashman, (317) Digital Record Drawing Requirements Overview All files shall be submitted without using file compression. Files will be submitted in AutoCad.dwg format (Readable by version 2004 or newer). Provide just one.dwg file of the overall site plan drawing - including only the information for that section being submitted as the construction plan or record drawing. It is not necessary to submit copies of the Fishers Standard Detail sheets. Version

3 Do not include title blocks in overall file, or digital professional seals in.dwg file. All text pertaining to utilities shall reflect as-built conditions. An Object Data Table template and instructions on the procedure to populate the Object Data Table are available for download via the internet at the following link: As-built Submittal Information. All relevant structures in the record drawings including but not limited to sewers, ponds, signage and hydrants will be attributed with their corresponding data via the Object Data function within AutoDesk s Map application or with ESRI s ArcGIS products. ESRI shape files are acceptable. See the Object Data Table Tutorial under the As-built Submittal Requirements section of the GIS webpage by clicking on the following link: As-built Submittal Information. Contact the GIS coordinator for other questions regarding the object data table if the tutorial cannot answer your question. Do not use fonts or line-types that are not AutoCAD standard. All utility line-work, blocks, and text shall be standard AutoCAD. Line-work and objects related to said utilities displayed as third party software entities (AEC objects as an example, proxy graphics) will not be accepted. If multiple sections of a project are being submitted, files shall be placed in separate directories on the CD. Care should be taken not to include information that does not pertain to the utilities constructed as part of that section. File names should make sense to a viewer who may not be familiar with the consulting firm s naming conventions and be indicative of the contents of the file. File names should match the project name as submitted during the TAC application process. Submitted drawings shall not contain xref files. All xref s shall be bound using the insert command and exploded. Do not explode all the blocks in the drawing. Care must be taken when binding xref s to avoid duplication of information. All structures, mains, laterals, and annotations relating to all utilities shall be on separate, logically named layers (i.e. san_text, san_line, san_struct, or similar). Each structure, whether Sanitary, Storm, Light Pole, etc. shall be represented by a block whose insertion point is located at the center of the structure s as-built location. Said blocks shall have an identifier attribute tag populated with the structure name or number by using the Object Data Table. The general form of the ID will be a code representing the subdivision or development followed by that structures number. Structures should be numbered consecutively. The subdivisions code will be provided through the TAC process or by request. Utility annotation text (including, but not limited to, structure name or number) shall not be displayed as a block or a block attribute, unless the block attributes are tied to the Object Version

4 Data Table. Annotation must be placed on a unique layer and said text shall be standard text, not mtext. Line-work representing utility mains shall be continuous from structure insertion point to structure insertion point. Line segments between structures must be continuous poly-lines. Line-work representing mains shall share a common endpoint (at the block insertion point) with all other line-work connected to that structure. Do not trim lines at the edge of structure symbols. Do not use a continuous poly-line to represent an entire pipe run. Each line must begin and end at a structure insertion point, connecting only two structures per line. Line-work representing laterals must be a continuous poly-line connected to the appropriate main, not a block. Line-work representing utility mains and laterals must be drawn in the direction of flow. Stationing does not have to be changed. Ponds shall be closed poly-lines representing the normal pool elevation of all detention and retention areas (normal pool elevation for dry detention should be the bottom of the detention area). These polygons must be included in the drawing, as well as the appropriate data in the Object Data Table. All open channel ditches and swales shall be represented by the flow line as a continuous poly-line. The appropriate data shall be included in the Object Data Table. All structure locations and structure numbers indicated in drawing must reflect as-built locations (including connections to existing systems). The proposed structures and mains shall be moved to the correction location. Symbols and line-work representing locations other than those mentioned above shall be deleted. All easements shall be closed poly-lines, representing aggregate areas, not broken by lot lines. As an example, the drainage easement running along the back property line of neighboring lots will be shown as one area. Version

5 Town of Fishers, IN Department of Engineering Digital Record Drawing Submittal Requirements & Review Checklist Project Name: Submitting Company: Contact name: Date: No. Completed Incomplete Not Item Applicable 1.0 General 1.1 Files must be saved and submitted on a CD-ROM in a jewel case without using file compression. 1.2 The CD label shall include the following: Engineering Company Name with prepared by statement (1.2.1) Project Name (1.2.2) Date that data is burnt onto CD (1.2.3) Designate CD as As-built, Construction Plan or Other (1.2.4) 1.3 Files must be submitted in DWG format. 1.4 Each file should be for one section of development. Multiple sections will not be accepted in one file and care must be taken to clearly mark existing infrastructure facilities. 1.5 If multiple sections of a project are

6 being submitted, files shall be placed in separate directories on the CD. 1.6 File names should make sense to a viewer who may not be familiar with the consulting firms naming conventions and be indicative of the contents of the file. 1.7 All pertinent drawing elements will reside in the primary drawing file. There shall be no external reference files (xrefs) attached to the drawing. 1.8 Separate layers for structures, pipes, annotation etc. with a logical description for each layer per the As-built Attribute Definitions for Object Data Table document. Note that each layer should contain only a point, line, or polygon. 1.9 Projection shall be referenced to NAD83, Indiana State Plane Coordinate System, East Zone, using U.S. Survey Feet and per the Hamilton County datum. Elevations shall be in the NAVD 88 vertical datum. The coordinate location of the items listed below shall be obtained by a field survey and with vertical data that meets survey grade accuracy Tie into section corners in the Indiana State Plane Coordinate System to insure proper orientation. Section corner tie sheets can be obtained from the Hamilton County Surveyor s web page All easements shall be represented and drawn as closed polylines or polygons representing aggregate areas Must have graphical representation of all off-site platted easements, right-of-ways, lot lines, etc. encompassing infrastructure improvements. See Section 3.0.

7 2.0 As-built - Infrastructure 2.1 Object Data Table template will be provided and will be populated with asbuilt data. 2.2 All Stormwater Structure BMP s must be listed in the Object Data Table. 2.3 The digital construction file must be revised to show the exact as-built location of the following items with information provided per the As-built Attribute Definitions for the Object Data Table as provided: Sanitary Pipe (2.3.1) Sanitary Structures (2.3.2) Sanitary Laterals (2.3.3) Storm Pipe (2.3.4) Storm Structures (2.3.5) Valve (2.3.6) Hydrants (2.3.7) Ditches and Swales (2.3.8) Show flow lines and flow direction. Show Tributaries within 100 feet up and downstream of ditch. Impervious Surface (2.3.9) Pervious Surface(2.3.10) Ponds (wet and dry) (2.3.11) Signage (2.3.12) Lamp Posts (2.3.13) Traffic Signal (2.3.14) Lift Stations (2.3.15) Easements (2.3.16) Right-of-Way (2.3.17) Fiber (2.3.18)

8 Handholes (2.3.19) Path (2.3.20) Underground Detention Facilities (2.3.21) BMP (2.3.22) (see BMP list at end of Attribute Definitions document) Subsurface Underdrain (2.3.23) 2.4 The as-built location of the sewer wyes shall be located on the plans as measurement along the pipe centerline from the nearest downstream manhole. 2.5 Sub-surface drain lateral locations should be located with a proper distance from the nearest structure or property line and should not be overlapped with other pipes, lines, or structures. 2.6 All storm water and sanitary structures will have top of castings and invert elevations. Design Values for all infrastructure shall be the as-built values and any construction values will be crossed out with the construction data still legible. 2.7 Structures will be points and have an appropriate Structure Id. 2.8 All Infrastructure pipes will have a length, pipe size (in inches) and material listed shown on the plans 2.9 Infrastructure line work must be continuous polylines with a beginning and ending at a structure insertion point, connecting only two structures per line. Lines must be drawn with the direction of flow Submit a PDF of the signed and stamped paper as-built documents. It must be legible and contain all as-built data including the profile sheets. The PDF will be reproducible to scale, rotated properly, and be stored in a

9 separate folder on the CD Impervious surface area in square feet must be submitted for each parcel of the project. Impervious surface areas are defined as those areas that do not allow infiltration and create runoff and include concrete, asphalt, wood, rooftops, compacted gravel driveways or parking areas, etc. A separate digitized impervious surface area polygon should be created for each privately owned parcel including but not limited to residential common areas, eyebrow island parcels, or amenity centers; privately owned street parcels, commercial parcels, etc. that contain impervious surface areas. Individually owned residential home parcels are the only parcels that do not need to be digitized as these parcels are all charged a flat rate. Sidewalks or paths 8 feet or less with 5 feet of green space on each side will not need to be digitized. All digitized impervious surface area polygons for a single project shall be combined into one layer (named imp_surf ), but the impervious surface area polygons should be separate for each parcel. Each parcel polygon should also include an attribute table that includes the total impervious area in square feet for that parcel, parcel number, and lot or block number, project name, date of installation, and source.

10 3.0 Secondary Plats 3.1 A PDF file of the recorded Plat with the recording stamp.