ADDENDUM NO. 01 Charlotte Douglas International Airport FAR Part 150 Noise Exposure Map Update January 12, 2014

Transcription

1 ADDENDUM NO. 01 Charlotte Douglas International Airport FAR Part 150 Noise Exposure Map Update January 12, 2014 Please be advised of the following information for purposes of your Qualifications Documents, and acknowledge receipt of same in the cover letter that accompanies your statement of qualifications. This Addendum is hereby made a part of the request for qualifications of the above referenced project. All other requirements of the original advertisement shall remain in effect in their respective order. General Information. The following items are included in this Addendum: Questions and Answers: 1. Q: Does the COVER LETTER, TABS, TABLE OF CONTENTS, COVERS, or FORMS count in the 25-page limit? A: The COVER LETTER, TABS, TABLE OF CONTENTS, COVERS and FORMS do NOT count in the 25-page limit. 2. Q: If we currently do not hold a MBE/DBE cert in North Carolina, what other certifications are acceptable? A: The consultant must to be listed as a DBE in the NCDOT database. MBE certification does not count towards the goal, only DBE. 3. Q: If a North Carolina certification is mandatory, could our firm be recognized while waiting for application approval? A: The firm must be certified as a DBE by the NCDOT when submittals are due. 4. Q: The first paragraph of the Agreement for Professional Services ends with the phrase [INSERT COMPANY NAME AND CORPORATE DESCR.] with offices in Charlotte, North Carolina, ( Company ). Are we correct in assuming that the Company s office location will be changed as appropriate and that a Charlotte business address is not required? The second whereas in the agreement identifies design and construction services. Are we correct in assuming that this phrase will be modified as appropriate to reflect the general services to be provided under this project? A: Specific company information, regardless of company location, and project information will be modified once a firm is selected. In addition, Article #3 of the contract may be modified depending on how the fee detail is structured. Page 1 of 13

2 5. Q: The evaluation criteria state that the RFQ includes attachments for Digital CAD Specifications for Airport Projects and CAD-GIS Data Standard Guidelines. Does Exhibit E to the RFQ, titled CAD Standards, address both of these matters? A: The data collected for the update will be compliant with the Airport s current GIS standards in Attachment #1 of this addendum and the following FAA Advisory Circulars: AC 150/ A, Establishment of Geodetic Control AC 150/ C, Airport Imagery Acquisition AC 150/ B, Aeronautical Surveys and GIS Standards 6. Q: Part 150 requires noise contours and analyses for two time frames: (1) the year of submission and (2) a forecast case that is at least five years from the year of submission. Will the Airfield Capacity Enhancement Plan (ACEP) forecast cover these time frames? If some enhancement to the forecast is required to meet Part 150 requirements, will the ACEP consultant or the Part 150 consultant perform that enhancement? A: The ACEP will produce forecasts for 10 and 20 years into the future. Any enhancements or alterations to the ACEP forecast required to complete the NEM Update will be done by the NEM Update consultant. 7. Q: Is a completed Exhibit F, Section 2 Buy American Certificate required for this submission, since the Noise Exposure Map Update project does not involve a total facility, equipment, or materials? A: No. 8. Q: The final page of the RFQ lists six DBE forms contained in Exhibit G Disadvantaged Business Enterprise Program. Are we correct in understanding that only DBE Form 3 Utilization Commitment, is a required element of the qualifications submission? A: Yes, DBE Form 3: Utilization Commitment, is the only form due with the proposal package. This information is explained in Exhibit G, under DBE Contract Provisions, Section IV: Required Documentation. There is also a table (Pg. 60 of solicitation document) that explains the purpose of each DBE form and when they are due. 9. Q: What is driving the project? A: The Airport has experienced air traffic changes since converging runway operations ceased. 10. Q: How many community outreach meetings does the Airport require? A: The number of community outreach meetings will be determined by the Consultant during scoping. 11. Q: Has the Airport worked with any community outreach firms in the past? A: No. 12. Q: Will the Airport make available data from its noise monitoring software? A: Yes. 13. Q: What type of work code is required on the Subcontractor Utilization/Commitment Form? A: This code is found in the NCDOT vendor database. Page 2 of 13

3 14. Q: Who has won this project in the past and did the work that is GIS related to the project? A: A FAR Part 150 Noise Compatibility Study was completed in 1996 by Landrum and Brown. The GIS portion was completed by HMMH. End of Addendum # 1 Page 3 of 13

4 Attachment #1 Subject/Title CAD-GIS Data Standard Guidelines Date Effective Revision Date Effective Version 5.1 March 1, 2011 PURPOSE CAD-GIS Guidelines leverage investments in survey accurate data produced in Computer-Aided Design (CAD) software applications to update and maintain data in the City of Charlotte s (City) Geographic Information System (GIS). These guidelines: 1) Provide a flexible and consistent guide for compiling CAD drawing features found in land development plans and other internal and external sources so that they can be used as source data to update and maintain the City s GIS data, 2) Blend with existing City business processes for land development, planimetric/topographic mapping, and capital improvement projects, and 3) Make it possible to merge digital mapping of CAD data with GIS by developing conversion methodologies or translator software processes between spatial and attribute features in both systems. SCOPE These guidelines are established for CAD data created or received by the City of Charlotte that can be used to support City GIS data. CAD-GIS Guidelines are intended for use by: 1) Architects, surveyors, and engineering firms that submit land development plans to the City for review; 2) Internal sources and contractors working on City capital improvement projects; 3) Topographic mapping contractors; and Page 4 of 13

5 4) Others who originate CAD data for the City. The guidelines assume survey accurate or source data is prepared using some type of CAD software and can be represented in GIS format. The following CAD file documents types, supporting business processes, and associated KBU and KBU Divisions responsible for receiving these CAD files are identified in table 1. Page 5 of 13

6 Electronic Document Dependant Business Process Responsible KBU Rezoning Plans Land Development Cycle, zoning and rezoning, Code Enforcement Planning Existing Condition Surveys Capital Improvement Projects (CIP) E&PM Development Plans Land Development Cycle, CIP, base mapping, Work Order and Asset Management (WAM) Planning, CMU, E&PM Site/Construction Plans Land Development, CIP, base mapping, WAM, permitting Planning and E&PM Final Plat Maps As-Built Surveys Land Development, cadastral/right-of-way dedication, Powell Bill source data base mapping, CIP, WAM, and, Risk Management Land Development, Water Quality regulations, Post Construction Control Ordinance Process (PCCO), approved Storm Water BMP (bioretention) as-builts, CIP, base mapping, WAM Planning and E&PM CMU and E&PM Topographic Mapping Annual Topographic Mapping Contract, drawing files that should support base mapping data, CIP, WAM E&PM Table 1 Electronic CAD Files Identified for CAD-GIS Guidelines BACKGROUND The City of Charlotte has been using geographic information system (GIS) technology since 1988 to store, manage, and maintain spatially enabled data to facilitate delivery of citizen services. Data created in computer aided design (CAD) software is currently submitted as hard copy printed format, electronically as PDF, or as drawing (.dwg) files and should be used to maintain GIS data. A consistent receipt of CAD data in a standardized.dwg will improve spatial data maintenance. Implementation of CAD-GIS Guidelines, where no contract or ordinance exists, has been unsuccessful. This is a gap in the GIS data workflow. CAD-GIS Guidelines are therefore needed to ensure the quality and content of CAD data will be useful for maintaining the GIS database, will enhance data positional accuracy harvested from.dwg files. DEFINITIONS Term CAD Definition Computer Aided Design - is the use of computer technology for the process of design and design-documentation. CAD software applications are used to prepare survey and engineering drawings. The City s preferred CAD software is AutoCAD from Autodesk. CLDSM Charlotte Land Development Standards Manual - Specifications and special provisions intended to be used in conjunction with Charlotte Land Development Standard Drawings, NCDOT Roadway Standard Drawings, and NCDOT Standard Specifications for Roads and Structures for all development within the City of Charlotte and the City of Charlotte ETJ unless otherwise directed by the City Engineer. Page 6 of 13

7 GET GIS GIS Enterprise Team The GET is a team of City KBU representatives selected to oversee Geographic Information System strategies, standards, budgets, and priorities to meet the City s business needs and advance comprehensive citizen service. Geographic Information System A GIS integrates hardware, software, and data for capturing, managing, analyzing, and displaying all forms of geographically referenced information. The GIS developed by the City of Charlotte is used by staff to provide information on the geographic location and characteristics of natural or constructed features and boundaries on the earth. The City s preferred GIS software is ArcGIS from ESRI. NCBELS GUIDELINES North Carolina Board of Examiners for Engineers and Land Surveyors the board is responsible for the administration and regulation of the professions of engineering and land surveying in North Carolina. The City of Charlotte advocates CAD-GIS Guidelines to support the maintenance of its GIS data. Guidelines are intended to be consistent with existing City standards. If conflicts are found staff are encouraged to submit their concerns to the City GIS Enterprise Team (GET). Where any potential redundancy or conflict exists between these guidelines and existing City or business standards stated within a contract or otherwise specified by the business, please adhere to the existing specified standards. Otherwise, it is encouraged but not required that digital CAD files submitted to the City adhere to the following format. File Submission CAD files may be submitted to individual City KBU consistent with current processes or per current contract requirements. File Formatting Component File Format AutoCAD Version Master File or Base Drawing Definition 1) The digital file format should be AutoCAD drawing files (.dwg) format, unless otherwise specified by the recipient KBU. 2) Microstation users should combine reference files to one AutoCAD.dwg. 3) ASCII or Text Files with additional information (i.e. attribute information) about the drawings or drawing features should be comma delimited and may be submitted as separate files in PNEZD format (Point number, Northing, Easting, Zenith, and Description). 1) Drawing files are preferred in AutoCAD Version Release 2007 or greater. 2) Drawing files produced in AutoCAD Version Release 2010 are presently not compatible with the City GIS and should be resaved to AutoCAD ) Drawing files should be provided in model space as the base drawing or master file. 2) The drawing files should include all layers and graphic elements included in the submitted paper document (for instance- geography, text, legend, scale, labels). Plan Sealing, Signing and Dating File and Drawing Sheet Naming Drawing Coordinates 1) CAD files submitted electronically to the City must be in accordance with North Carolina Board of Engineers and Land Surveyor (NCBELS) requirements (21 NCAC ). CAD drawings are requested for submittal using the naming conventions consistent with those found in: 1) the Charlotte Land Development Standards Manual 2) with other naming conventions requested by the recipient KBU; or 3) with those specified by contract. It is essential that the geodetic control used be referenced and clearly described in the plan drawing. 1) Submit files in the North Carolina State Plan Coordinate System, Zone 3200, in survey feet using North American Datum 1983 (NAD83). 2) City of Charlotte Subdivision Ordinance require plans to be tied to the NC Grid. 3) Land survey information, like basis of bearings, and/or any assumptions should also be submitted and annotated on the design file consistent with hard copy map submittal requirements listed in the North Carolina General Statutes, section Page 7 of 13

8 Drawing File Content Content Submission Preparation Map Precision Description Steps recommended prior to submission: 1) Turn all layers to visible 2) Zoom to the drawing extents to confirm no drawings features exist beyond the plan view extents 3) Purge any unwanted CAD layers 4) Copy to a new drawing using Copy with Base Point (0,0,0) 5) Paste contents into a new drawing using clean or blank drawing template (ACAD.DWT) 6) Create a file and save in AutoCAD 2007 file format 1) The digital version of a map should be of high precision in accordance with requirements of the North Carolina Board of Examiners for Engineers and Surveyors (NCBELS). Layer Names Text Color Symbology Feature Types Blocks External References (XREF s) 1) Existing and proposed features should be distinguished by using separately named layers (i.e. EX_P_PARCELBOUNDARIES (is this supposed to have the _P_?) for existing parcel lines, P_PARCELBOUNDARIES for new). 2) The choice of layer name used for each drawing feature should remain at the discretion of the customer for the present time. 3) Drawing features should include separate layers names for features specified in the table included as Appendix A Digital Submittal Layer Guidelines. 4) Layer naming requirements should remain at the discretion of the customer for the present time unless using a City supplied drawing template. Those seeking further guidance on layer naming should consult the City AutoCAD Design Manuals of Engineering and Property Management (E&PM), Charlotte- Mecklenburg Utilities (CMU), or the National CAD Standard for suggestions. 1) Any features or text that is not organized into specified layers may be placed into the miscellaneous feature layer and miscellaneous annotation layer. 2) Text labels should be used in standard fonts that can be read without third-party software. 3) No annotation text should be included in any feature layer and no features should be included in any text layer. 4) Text and miscellaneous linework (leader lines) should be placed on unique layers (text layers) separate from the features they annotate. 5) Text labels and text leaders should be placed in the drawings in such a manner so as not to break continuity of line or polyline of features to which associated (see points, lines, and polygons). 1) Drawing layer line color preferences should remain at the discretion of the customer for the present time. 1) All data should be completed using standard symbol sets/graphics that require no third-party software unless otherwise allowed by the recipient City KBU. 1) Feature types include points, lines and polygons. 2) Similar features types cannot be placed on multiple layers and different feature types should not be combined onto the same layer. 3) Features other than those thematically defined by the individual layer name/description should not be included in that layer. 1) When using CAD drawing blocks, do not store text, polylines, or points as part of the block. 1) References to external CAD layers should be removed and the referenced information included directly in the plan drawing submittal for layers identified in Appendix A that contain new (non-existing) features important for updating GIS data. Page 8 of 13

9 Feature Topology 1) Digital linework should be topologically clean meaning geometrically continuous and boundaries should be closed with no undershoots or dangles where boundaries intersect. 2) The digital linework should not include gaps or overlaps between features. 3) Traverse features should be snapped closed at intersections. 4) All unique features should be closed (i.e. no undershoots or dangle) if they represent areas and continuous (i.e. no gaps or overlaps) if they represent lines. 5) Polygons should be digitized clockwise. 6) Polylines and Lines should be of a continuous line-type, such that each individual line (i.e. pipe) feature is only broken at the ends where a node (i.e. structure) is located. 7) Polyline type features such as parcel boundaries, subdivision boundaries, building footprints, etc. should be snapped closed, even if this means lines may need to be duplicated on more than one layer. 8) Where a polygon reference feature extends beyond the edge of the plan, the property boundary (repeated on the polygon feature s layer) may be used to close the polygon. Alternatively, include partial polygons (parcel boundaries) shown for reference on an unnamed separate layer so that they are not selected during conversion to GIS. 9) All edges on polygon features should be snapped together at the vertices. 10) All point features should be entered using standard point/node symbols so that 3rd party software is not required. Guidelines by Feature Theme Theme Transportation Storm Water Features Cadastral Features Definition 1) Street centerlines lines should be snapped together at intersections. 2) When submitting plans that include surveyed ground surfaces, the following options are available: a. Separate ASCII text file containing all elevations points delivered in a single comma-delimited ASCII text file with each line of the file containing values for a single point as follows Easting, Northing, Elevation. b. Elevations can also be annotated on a separate annotation defined layer. 1) Storm water line and point features should be digitized with proper directionality: lines should be drawn from the uphill node to the downhill node or flipped after the lines have been digitized. 2) Each individual feature class should be differentiated and each appurtenance type should be differentiated (i.e. different pipe sizes) on separate layers. 3) When submitting plans that include surveyed ground surfaces, the following options are available: a. Separate ASCII text file containing all elevations points delivered in a single comma-delimited ASCII text file with each line of the file containing values for a single point as follows Easting, Northing, Elevation. b. Elevations can also be annotated on a separate annotation defined layer. 4) Curves may be digitized with enough vertices to capture the curve geometry, but they should be single, continuous lines. Curves or arcs may also be used to designate curved pipe. 5) All storm water lines should be continuous, with pipe endpoints snapped to each other at endpoints (nodes). 1) Subdivision / project parcels, and easements (public, private, greenway, utility) should be delivered as closed polygon features within their own layers (i.e. not closed with the subdivision/project boundary). Page 9 of 13

10 Utility Features Sewer Features: 1) Sewer Lines and Sewer Taps should be digitized with proper directionality: lines should be drawn from the uphill node to the downhill node or flipped after the lines have been digitized. 2) All tangents between sewer manholes should be drawn with a single line. Lines should not continue for more than one tangent. 3) All tangents should be snapped at endpoints intersecting at the exact center of the manhole. No gaps should exist between tangents. 4) Manholes should be symbolized consistently with an insert centered and snapped on the tangent endpoints. 5) Sewer tap locations should be snapped to the sewer tangent and accurately placed. 6) The sewer tangents between the manholes should NOT be broken by the tap locations. 7) Sewer manholes, cleanouts, appurtenances or any other item requiring elevations should be annotated on a separate annotation defined layer. Water Features: 1) Water lines should be digitized with all straight-line pipes consisting of only two end points. Straight-line pipes will begin and end at the following features (nodes): hydrants, valves, meters, pumps, tees, crosses, and valves. Polylines should be used wherever a water line contains elbows or bends (i.e., when the line does make a straight run from node to node). The water lines should be mapped according to the curvature of the road right-of-ways and not be broken with the exception of a node. Bends are not considered nodes and are to be mapped using vertices. Please try to limit the number of vertices drawn. 2) Curves may be digitized with enough vertices to capture the curve geometry, but they should be single, continuous lines. Curves or arcs may also be used to designate curved pipe. 3) Hydrants should be shown in their true, surveyed location, and should be connected to the water main via a valved fire hydrant line. 4) All water lines should be continuous, with pipe endpoints snapped to each other at endpoints (nodes). 5) Stud fittings should be drawn to differentiate end-of-lines from lines that extend beyond the extent of the drawing. Stud fittings should be drawn for lines that are to be permanently capped when the project is complete, not for lines that are temporarily capped pending inspection. IMPLEMENTATION CONSIDERATIONS The CAD-GIS Guidelines will serve as a resource to all new investments after its adoption. The Project Alignment Resource Team (PART) will be responsible for initiating procedures with the GET for new investments that flow through the Technology Project Evaluation Team (TPET) process to encourage compliance. COMPLIANCE The CAD-GIS Guidelines will be reviewed and updated annually. The GET shall convene a workgroup annually for review of changes to monitor state, to advance or retract guidelines, for ensuring continued applicability and compliance with existing or planned City business standards including: 1) STD-DATA-001 Geospatial Data Properties Standard 2) CLDSM Charlotte Land Development Standards Manual 3) CMU Design Manual 4) Charlotte-Mecklenburg Storm Water Design Manual 5) Charlotte-Mecklenburg BMP Design Manual 6) Other KBU CAD standards Page 10 of 13

11 Reviewer Approved Review Notes Next Review GIS Enterprise Team Approval via 3/1/2013 Page 11 of 13

12 Appendix A Digital Submittal Layer Guidelines Digital Submittal Layer Guidelines Framework Separate features by CAD layer for conversion to GIS CAD Feature Type KBU Geodetic Elevation Point E&PM Elevation 2 ft. Contours Polyline E&PM Elevation 10 ft. Contours Polyline E&PM Benchmarks/Control Points Point E&PM Transportation Street Centerline (Paved) Polyline E&PM Street Centerline (Unpaved) Polyline E&PM Road Width Annotation Text E&PM Pavement Markings Point E&PM Signs Point E&PM Edge of Pavement Polyline E&PM Railway Polyline CATS Back of Curb Polyline E&PM Medians Polygon E&PM Sidewalk Centerline Polyline CDOT Land Use Proposed Land Use Polygon Planning Rezoning Polygon Planning Street Trees Points E&PM Building Footprints Polygon E&PM Building Rooftops Polygon E&PM Parking Lots (paved) Polygon E&PM Parking Lots (gravel) Polygon E&PM Driveway Polygon E&PM Medians Polygon E&PM Tree Canopy Polygon E&PM Street Trees Point E&PM Cadastral Street Right-of-Way Polyline E&PM Jurisdiction Boundary Polyline E&PM Regulatory Access Easements Polygon E&PM Conservation Easements Polygon E&PM Sidewalk Easements Polygon CDOT Storm Drainage Easements Polygon E&PM Utility Easements Polygon CMU Sanitary Sewer Easements Polygon CMU Waterline Easements Polygon CMU Overhead Utility Easements Polygon E&PM Tree Save Area Polygon E&PM Water Quality/Stream Buffer Polygon E&PM Page 12 of 13

13 Hydrography Stream Centerline Polyline E&PM Stream Cross Sections Polyline E&PM Shoreline/Stream Bank Polyline E&PM Wetlands Polyline E&PM Dam Point E&PM Utility BMP (Name, Location, Size, Elevation (NAVD 88)) E&PM Lakes, Marshes, Ponds Polyline E&PM Storm Inlets (Specify Catch Basin, Double Catch Basin, Curb Inlet, Elongated Throat, Drop/Yard Inlet, or Slab-Top Inlet/Weir with # of open sides) Point E&PM Storm Junctions (Specify Junction Box or Manhole) Point E&PM Storm Endsections (Specify Headwall, Exposed Pipe End, or Flared End) Point E&PM Storm Pipes Polyline E&PM Storm Culvert Polyline E&PM Surface Drainage (Specify Channel, Drainage Ditch, Paved Flume) Polyline E&PM Conduit (is this storm water?) Polyline E&PM Trench Drain (is this storm water?) Point E&PM Sewer Manhole Point CMU Sewer Force Main Polyline CMU Sewer Gravity Main Polyline CMU Sewer Private Main Polyline CMU Abandoned Sewer Main Polyline CMU Sewer Manhole Point CMU Sewer Pump Station Point CMU Sewer Air Release Valve Point CMU Water Pressurized Main Polyline CMU Water Private Main Polyline CMU Abandoned Water Main Polyline CMU Utility Locations Polyline CMU Fittings Point CMU Water Valve: Gate, Butterfly, Air, Blow Off, Pressure Reducer Point CMU Fire Hydrants Point CMU Page 13 of 13