SOW_Attachment_5_-_Combined_Surveying_CAD_GIS.PDF
PDF 2 MB Posted
- Attached to
- NOSC Communication Upgrade Federal contract opportunity
- Solicitation number
- FA3047-14-R-0046
About this file
SOW Attachment 5- Combined Surveying
View the file
Other files for this federal contract opportunity
Show all 25
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SECTION 01 35 13.10 00
SPECIAL PROJECT PROCEDURES – SURVEYING
JOINT BASE SAN ANTONIO, TX
01 35 13.10 00 - 1 27 FEB 2014, rev5
PART 1: GENERAL: This Section covers the project requirements unique to Joint Base San
Antonio, Texas. These unique requirements relate to Surveying.
1.1 REFERENCES: The publications listed below form a part of this specification to the extent referenced. The publications are referred to in the text by basic designation only.
1.1.1 U.S. ARMY REGULATIONS (AR) (NOT USED)
1.1.2 UNITED STATES ARMY CORPS OF ENGINEERS ENGINEERING MANUALS
(EM)
a. EM 1110-1-1002 Survey Markers and Monumentation, http://140.194.76.129/publications/eng-manuals
b. EM1110-1-1005 Engineering and Design: Control and Topographic Mapping, (http://140.194.76.129/publications/eng-manuals)
1.1.3 JOINT BASE SAN ANTONIO (JBSA) PUBLICATIONS
a. JBSA Installation Design Guide, July 2006, (http://www.samhouston.army.mil/dpw/) obtain pending updates by email to usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.
b. San Antonio Unified Development Code http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=Te xas
c. Tri-Service A/E/C CAD Standards, https://cadbim.usace.army.mil/CAD Manhole
Entry Request Form, obtained from Network Enterprise Center, Transmission
Branch, ph: 808-8888, poc: Mr Joseph P. Saladin.
1.1.4 ATTACHMENTS AND APPENDICIES
a. Appendix A – Meta Data Sample
b. Appendix B – Monument Construction
c. Attachment A – Control Monument Form
d. Attachment B – Existing Monuments
e. Attachemnt C – Table 1 – Existing Monument values for localized scale factor
1.2 SUBMITTALS: The following shall be submitted in accordance with applicable
SUBMITTAL PROCEDURES:
a. Survey Work Plan
b. GIS FILES in ESRI file format. email usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil for current version meeting requirements of Section 01 35 13.30 00 http://140.194.76.129/publications/eng-manuals http://140.194.76.129/publications/eng-manuals file:///C:/Users/don.n.morgan/AppData/Roaming/Microsoft/Word/(http:/www.samhouston.army.mil/dpw/) mailto:usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil mailto:usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=Texas http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=Texas https://cadbim.usace.army.mil/CAD mailto:usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil
01 35 13.10 00 - 2 27 FEB 2014, rev5
c. All FINAL and all INTERIM review plans shall include CAD files, in AutoCAD drawing format, per Section 01 35 13.20 00.
d. Metadata as required by Executive Order 12096, containing as a minimum the metadata elements defined in the Content Standard for Digital Geospatial Metadata
(CSDGM). A sample of the type and desired format is shown in Appendix A –
Metadata Sample.
e. Verification in writing of survey completion (submitted prior to preconstruction meeting).
PART 2 PRODUCTS: (Not Applicable)
PART 3: EXECUTION:
3.1 TOPOGRAPHIC, PLANIMETRIC, AND UTILITY SURVEYS
3.1.1 The contractor shall accomplish the survey in accordance with the following United
States Army Corps of Engineers Engineering Manuals (EM). These EMs may be accessed at http://140.194.76.129/publications/eng-manuals. In case of conflict between the specifications, the scope of work, and the referenced EMs, the scope of work shall have precedence.
a. EM 1110-1-1002 Survey Markers and Monumentation
b. EM 1110-1-1005 Engineering and Design: Control and Topographic Mapping
3.1.2 The contractor shall coordinate and conduct a kick-off meeting prior to the initiation of the field survey. The purpose of the meeting is to ensure a mutual understanding among the contractor and the Government Agents of the survey requirements, deliverables, and submittals. At a minimum, the participants from the contractor shall include the Survey
Manager and Survey Chief one of which a Registered Professional Land Surveyor
(RPLS).
3.1.3 Using control points provided by the government and as set as needed by the contractor, the contractor shall layout horizontal and vertical control in the survey area.
JBSA uses a localized scale factor for all survey work at all JBSA installation locations.
Email usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil for the current scale factor, coordinate of record, and procedures.
3.1.3.1 The Contractor shall establish additional temporary semi-permanent control points (rebar w/cap) set in inter visible pairs, as needed with a minimum of one pair in locations that will remain usable for construction layout. The contractor shall record data in field books, including setups, backsights, measure ups, shot numbers, and shot descriptions.
http://140.194.76.129/publications/eng-manuals
01 35 13.10 00 - 3 27 FEB 2014, rev5
3.1.3.2 If required, the Contractor shall establish additional permanent control in accordance with Appendix B – Monument Construction, essentially a ‘type
G” monument as described in EM1110-1-1002 – for 3 rd order work.
3.1.3.3 All control points set, temporary, semi-permanent, or permanent shall have a completed Monument Control Sheet and will be required upon final submission.
(form attached )
3.1.4 The contractor shall acquire field topographic points to be used for 1-inch equals 30-feet scale mapping with a 1-foot contour interval. Density of field elevations shall show all breaks in grade, changes in terrain, and physical features. The contractor shall provide a topographic survey in the form of a three-dimensional AutoCAD 2010/2011
.dwg file named ******-V-SP.dwg. The file shall contain breaklines and a triangulated irregular network (TIN) composed of topologically correct nodes, edges, and triangles at their correct elevations and any other data required to create an accurate digital terrain model. Spot elevations in the file shall be placed as a block with attributes, with the insertion point being the location of the shot, the block shall be provided by the government. The contractor shall record data in field books including setups, backsights, measure ups, shot numbers, shot descriptions or other data as necessary to fully record the data, conditions, adjustments, methods, etc of the survey.
3.1.5 The contractor shall survey all improvements and generate planimetric data, including but not limited to: surface type for roads (paved and unpaved), parking lots (paved and unpaved), curbs, sidewalks, trails (paved or unpaved), bridges (including deck and low chord elevations), buildings and other structures, fences, handrails, retaining walls, headwalls, catch basins, utilities, manholes, utility poles, signs and all other man made physical features. For buildings or structures, provide the type of structure, number of stories or floors, and building number. The contractor shall acquire planimetric information to be used for 1-inch equals 30-feet scale mapping. Planimetric features shall be placed at zero elevation.
3.1.6 The contractor shall survey all utilities as described in the following sections. All field tied utilities shall be placed into the ******-V-SP.dwg AutoCAD file, on the appropriate layer for that entity. All horizontal and vertical control established for ties shall be shown as a symbol with annotation. All symbols utilized shall conform to
A/E/C CADD Standard Release 5.0 and shall be identified on the drawings. All line styles, layer names, symbols, and template files shall be obtained from the government by email request to usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.
3.1.6.1 Water - Locate all valves, standpipes, regulators, etc. Locate all fire hydrants.
Provide size of pipe and distance above ground. Provide elevations at the top of valve cover and the elevation of the valve, and top of all other feature elements.
3.1.6.2 Sanitary Sewer - Locate all manholes and provide top of rim elevation along with an invert elevation of all pipes connected to the manhole; identify type, size, and direction of each pipe extending from the manhole. Locate all clean-outs. For sanitary sewer lines that extend outside the primary survey area, locate
01 35 13.10 00 - 4 27 FEB 2014, rev5 the next manholes along the line, upstream and downstream, and provide the top of rim elevation and invert of pipes extending from the manhole.
3.1.6.3 Storm Drainage - Locate manholes and all other storm drainage structures such as culverts, headwalls, catch basins, and clean-outs. Provide top of manhole, catch basin elevation, or other structure, along with an invert elevation of all pipes connected to a manhole or catch basin and bottom elevation; identify type, size, and direction of each pipe extending from the manhole. Provide type, size, and invert elevation for all culverts. For storm drain lines that extend outside the primary survey area, locate the next storm drain structure along the line, upstream and downstream, and provide the top of structure elevation and invert of pipes extending from the structure.
3.1.6.4 Electrical and Communications Equipment - Specific data to be collected includes; pole height, type of pole, class of wood poles (if applicable), number of cross arms, direction, type (electrical or communication) and number of wires; low wire elevation at each pole; number and type of lights on poles, and quantity and rating for pole mounted transformers. In addition, collect data on manholes, manhole sizes, pullboxes, handholes, and top and bottom elevations.
Collect the number and location of ducts entering manholes, pullboxes, and handholes, and provide their invert elevations. Indicate location of the ducts exiting the structure within the survey limits. Provide number of cables in each duct and indicate size and type of cable. The contractor must request access prior to opening and communications manholes at least 1 week in advance by processing a Manhole Entry Request Form, obtained from Network Enterprise
Center, Transmission Branch, ph: 808-8888, poc: Mr Joseph P. Saladin
3.1.6.5 Gas - Locate all valves, meters, and gas line markers. Provide elevations at the top of valve cover and the elevation of the valve, and top of all other features elements.
3.1.6.6 The contractor shall take digital photographs of all electrical and communications equipment including poles, manholes, and transformers.
Photographs of the manholes shall show the interior of the manhole, showing the ducts and lines that extend from the manhole. The contractor shall take photographs of any downstream and upstream culvert including headwalls. The contractor shall take photographs looking downstream and upstream from the culvert headwalls. Photographs shall be keyed to collected data and key information placed in the drawing, to show general location and direction of shot.
3.1.6.7 Utilities that cannot be field tied shall be illustrated in electronic file format utilizing the following descending order of accuracy: As-Built, GIS, or Base
Map and shall reside in separate model files, or, alternatively, a layer suffix may be used, xxxx-A (As-Built), xxxx-G (GIS), xxxx-M (other map) and reside in a single model file.
01 35 13.10 00 - 5 27 FEB 2014, rev5
3.1.7 JBSA uses a localized scale factor for all survey work. Contact usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil a copy of the Geodetic Control Network
Adjustment Factor Report if you want a copy. In general, all survey work shall meet the following Technical Requirements:
a. Horizontal Control: Texas State Plane (Grid), South Central Zone (4204), NAD
83; shall comply with Corps of Engineers 3rd Order, Class I standards.
b. Vertical Control: NAVD 88; will comply with Corps of Engineers 3rd Order
c. Measurements: All measurements will be collected using an electronic data collector; all elevations will be measured at hundredths-of-feet (0.00)
d. The Combined Scale Factor, for all non boundary survey work on the base, that shall be used is 0.99983000 (nearest 100,000 th ) with the inverse being 1.00017, with Mon 6 being the coordinate of record (N13714201.155, E 2146430.189, Elev 726.32)
1) To convert from Grid to Surface Multiply Grid coordinate by 1.00017.
2) To convert from Surface to Grid, Multiply Surface coordinate by .99983000
e. Unit of Measure: U.S. Survey Feet
f. Map scale: 1-inch equals 30-feet
g. Contour interval: 1-foot
h. Metadata: Federal Geodetic Data Committee (FGDC) standards. The following link contains information and tools for metadata: http://www.fgdc.gov/metadata
i. CADD Standard: AutoCAD (current release); A/E/C Release 5.0 standards compliant, as modified by sect ion 3.3 of this specification.
j. CADD files shall be produced in Texas State Plane (Surface) and/or Texas State
Plane (GRID)
3.1.8 The government will furnish the following material:
a. Location map of area to be surveyed
b. Network Control Points and procedures
c. Block library
d. Template Files
e. Utility maps – not in coordinate system and may be paper, scanned, or CAD files.
f. Control Monument form mailto:usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil http://www.fgdc.gov/metadata
01 35 13.10 00 - 6 27 FEB 2014, rev5
3.2 DELIVERABLE FORMAT AND MEDIA
3.2.1 The draft and final survey data shall be submitted either on a DVD or CD and a transmittal letter shall accompany each submittal.
3.2.2 Complete Survey Submittal Package
3.2.2.1 AutoCAD files will include metadata, control points, topographic, planimetric, and data. The files shall follow the Layer name, and Linetype, of the template files. Lineweights and colors may be adjusted as desired to produce the desired print. Attribute information (text) for each utility shall be placed in the graphics file. All work shall conform to Section 01 35 13.20 00.
3.2.2.2 Completed Control Monument Form for all control points SET.
3.2.2.3 Raw Data and Computations – The contractor shall furnish the government computer output of unadjusted bearings, azimuths, distances, and coordinates of all traverse points. The error of closure, both azimuth and positions, shall be shown. The final data will be adjusted by the compass method and display the adjusted bearings, distances, and coordinates of all points surveyed. The contractor shall provide a final list of coordinates for all points. All level lines shall be reduced and adjusted in accordance with accepted procedures and practices. All computations shall be arranged in a sequential and understandable order with notes when appropriate so a review can be made with minimum reconstruction.
3.2.2.4 Field Books - Field books shall be neat, legible, and sequential. Each field book shall have an index; the index shall also display the serial number and type of instruments used. The field books will also display the names of crew members and date at the beginning of each day. All print and sketches shall be dark enough to produce legible photocopies. There is to be a maximum of one (1) horizontal setup per page. Field books shall also be scanned into a .pdf file.
3.2.2.5 Digital Photos – Digital photographs shall be clearly marked and identified by point shot. The numbers of the photographs must match the shot number in the
AutoCAD file and the shot number in the field book.
3.2.2.6 Signed Statement of Services – A statement will be signed and dated by the
Survey Chief, Quality Control Manager, Survey Manager, and Company
Principal attesting that the survey was completed in accordance with requirements.
3.2.2.7 Transmittal Letter - A transmittal letter will accompany each submittal.
3.2.2.8 All items listed in Complete Submittal Package plus a letter describing how comments were addressed and/or corrected.
01 35 13.10 00 - 7 27 FEB 2014, rev5
END OF SECTION
Joint Base San Antonio Vehicle Parking and Roads FGDC, Biological Metadata
Hide Definitions
Description | Spatial | Data Quality | Data Source | Metadata
Description Citation
Information used to reference the data.
Title: Joint Base San Antonio-Fort Sam Houston (JBSA-FSH) Vehicle Parking and Roads Originators: Your Company Name Here Publication place: San Antonio, Texas Publication date: 20081108 Data type: CAD data
Description
A characterization of the data, including its intended use and limitations.
Abstract: This data set represents the results of a topographic,planimetric, and utility survey of two seperate site that total approximately 71 acres at JBSA-FSH in San Antonio, Texas. The most northern area is a strip about 260 feet wide that overlaps and follows Dickman Rd. from about 215 feet north of Austin Rd. to about 150 feet west of N. New Braunfels Ave. The second area, to the southeast is overlapping Scott Rd., at varing widths from Taylor Rd to Hood St. The objective is to generate a one-foot contour map to support a 1" = 30' mapping scale showing all grade breaks, planimetric and visible utility information and to establish secondary control points around the project.
Purpose: The purpose of this data set is to provide for engineering design.
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Person: Data Owner or Representative Organization: US Army Corps of Engineers Fax: (817) 886-6498 Telecommunications Device or Teletypewriter (TDD/TTY) phone: (817) 886-1862 Address type: mailing and physical
Address: P.O. Box 17300 Address: 819 Taylor St. Room 3B05 City: Fort Worth State or Province: TX Postal code: 76102-0300 County: USA
Data Type
How the data are represented, formatted and maintained by the data producing organization.
Data type: CAD data
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Beginning date: 20080818 Ending date: 20081112 Currentness reference: observed
12/22/2011 don.n.morgan Text Box
APPENDIX - A
Status
The state of and maintenance information for the data.
Data status: Complete Update frequency: None planned
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: imageryBaseMapsEarthCover,010 Keyword thesaurus: ISO 19155 Topic Category
Theme:
Keywords: topographic, planimetric, and visible utility survey Keyword thesaurus: None
Place:
Keywords: JBSA-FSH Keyword thesaurus: None
Place:
Keywords: Bexar County Keyword thesaurus: None
Place:
Keywords: Texas Keyword thesaurus: None
Data Access Constraints
Restrictions and legal prerequisites for accessing or using the data after access is granted.
Access constraints: None Use constraints: None
Spatial Reference Information Horizontal Coordinate System
Reference system from which linear or angular quantities are measured and assigned to the position that a point occupies.
Coordinate System Details
Grid coordinate system
Grid coordinate system name: State Plane Coordinate System 1983 State Plane Coordinate System:
SPCS xone identifier: 4204 Lambert Conformal Conic:
Standard parallel: 30.28333 Standard parallel: 28.38333 Longitude of central meridian: 99.00000 Latitude of projection origin: 27.83333 False easting: 19684999.000 False northing: 13123333.333
Planar Coordinate Information
12/22/2011 don.n.morgan
Planar coordinate encoding method: distance and bearing Distance and bearing representation:
Distance resolution: 0.01 Bearing resolution: 0.01 Bearing units: Degrees, minutes, and decimal seconds Bearing reference direction: North Bearing reference meridian: Geodetic
Planar distance units: survey feet
Geodetic model
Horizontal datum name: North American Datum of 1983 Ellipsoid name: Geodetic Reference System 80 Semi-major axis: 6500000 Denominator of flattening ratio: 298.25722210088
Vertical Coordinate System
Reference system from which vertical distances (altitudes or depths) are measured.
Altitude system definition:
Altitude datum name: North American Vertical Datum of 1988 Altitude resolution: 0.01 Altitude distance units: feet Altitude encoding method: Explicit elevation coordinate included with horizontal coordinates
Spatial Domain
The geographic areal domain of the data that describes the western, eastern, northern, and southern geographic limits of data coverage.
Bounding Coordinates
Description of geographic extent: JBSA-FSH, San Antonio, Texas
In Unprojected coordinates (geographic)
Data Quality and Accuracy Information General
Information about the fidelity of relationships, data quality and accuracy tests, omissions, selection criteria, generalization, and definitions used to derive the data.
Logical consistency report: Processed digital conventional data collection using AutoCAD Civil 3D Land Desktop 2008 with multiple checks to established control. Conventional digital leveling data processed using StarLev version 1.27, a least squares adjustment program. The GPS/RTK data was processed using Trimble Geomatics Office version 1.63 after making redundant observations at different satellite constelations.
Attribute Accuracy
Boundary Coordinate West -98.46144 (latitude)
East -98.44701 (latitude)
North 29.46322 (longitude)
South 29.44397 (longitude)
12/22/2011 don.n.morgan
Accuracy of the identification of data entities, features and assignment of attribute values.
Attribute accuracy report: Conventional field survey data entries and line connectivity verified against field notes and sketches. GPS/RTK data verified using checks to existing JBSA-FSH GPS Control Network and making redundant observations on new established project control points. Vertical positions verified using digital leveling from multiple control network monuments.
Positional Accuracy
Accuracy of the positional aspects of the data.
Horizontal accuracy report: Project control complies with Corps of Engineers standards for Third Order Class I as outlined in EM 1110-1-1005, Table 6-1.
Data Source and Process Information Methodology
Information about individual steps of field and/or biological laboratory work.
Methodology information
Method 1
Methodology Type: Lab Methodology Description: GPS/RTK calibration created using existing JBSA-FSH GPS Control Network.
Method 2
Methodology Type: Field Methodology Description: Using GPS/RTK calibration, ties were made to existing control monuments and verified for accuracy, ties were then made to new secondary control points needed for conventional topographic work.
Method 3
Methodology Type: Lab Methodology Description: GPS/RTK observations were processed and derivations checked with tolerances set at 0.05 of a foot horizontally and 0.08 of a foot vertically.
Method 4
Methodology Type: Field Methodology Description: Conventional digital leveling from existing JBSA-FSH control monuments previously established for JBSA-FSH base utility survey to new secondary control points set for the conventional data collection.
Method 5
Methodology Type: Lab Methodology Description: Digital levels processed, leveled elevations versus GPS/RTK elevations on average varied no more than 0.06 of a foot.
Method 6
Methodology Type: Field Methodology Description: Conventional topographical survey data collected tying planimetric and visible utility information.
Method 7
Methodology Type: Lab Methodology Description: Conventional survey data processed and checked against field notes, sketches, and existing control.
12/22/2011 don.n.morgan
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description: No process steps have been described for this data set Process date: Unknown
Metadata Reference Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20081119
Metadata Point of Contact
Contact information for the individual or organization responsible for the metadata information.
Organization: Your Company DATA here Fax: xxx-xxx-xxxx Telecommunications Device or Teletypewriter (TDD/TTY) phone: xxx-xxx-xxxx Address type: physical
Address: XXXXX Some Street City: Some City State or Province: Your State Postal code: Your Zip County: USA
Metadata Standards
Description of the metadata standard used to document the data and reference to any additional extended profiles to the standard used by the metadata producer.
Standard name: FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata Standard version: FGDC-STD-001.1-1999
FGDC Plus Metadata Stylesheet
Stylesheet: FGDC Plus Stylesheet File name: FGDC Plus.xsl Version: 2.0 Description: This metadata is displayed using the FGDC Plus Stylesheet, which is an XSL template that can be used with ArcGIS software to display metadata. It displays metadata elements defined in the Content Standard for Digital Geospatial Metadata (CSDGM) - aka FGDC Standard, the ESRI Profile of CSDGM, the Biological Data Profile of CSDGM, and the Shoreline Data Profile of CSDGM. CSDGM is the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies are ordered to use this standard to document geospatial data created as of January, 1995. The standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the federal level with State and local governments adopting the metadata standard as well. The Biological Data Profile broadens the application of the CSDGM so that it is more easily applied to biological data that are not explicitly geographic (laboratory results, field notes, specimen collections, research reports) but can be associated with a geographic location. Includes taxonomical vocabulary. The Shoreline Data Profile addresses variability in
12/22/2011 don.n.morgan the definition and mapping of shorelines by providing a standardized set of terms and data elements required to support metadata for shoreline and coastal data sets. The FGDC Plus Stylesheet includes the Dublin Core Metadata Element Set. It supports W3C DOM compatible browsers such as IE7, IE6, Netscape 7, and Mozilla Firefox. It is in the public domain and may be freely used, modified, and redistributed. It is provided "AS-IS" without warranty or technical support.
Instructions: On the top of the page, click on the title of the dataset to toggle opening and closing of all metadata content sections or click section links listed horizontally below the title to open individual sections. Click on a section name (e.g. Description) to open and close section content. Within a section, click on a item name (Status, Key Words, etc.) to open and close individual content items. By default, the Citation information within the Description section is always open for display.
Download: FGDC Plus Stylesheet is available from the ArcScripts downloads at www.esri.com.
Federal Geographic Data Committee
12/22/2011 don.n.morgan
JOINT BASE SAN ANTONIO
CONTROL MONUMENT CONSTRUCTION
NOTE: The instructions are based on Berntsen brand Sectional Rod monuments with sleeve, access cover, and Aluminum Cap for illustrative needs only. Any other comparable system may be used upon submission and approval. The product can be seen at http://www.berntsen.com/.
Equipment needed: Items needed, but not limited to, are Inclinometer, measuring tape, lathe, marker, flagging, clip board with monument sheet, pencil with template, shooter shovel, post hole diggers, digging bar, access cover, hammer and stamping set, Berntsen rods with plenty of points, 16 lb. sledge hammer or gasoline drive impact hammer, safety glasses, two pairs of vice grip pliers, “Lock Tight Liquid” or lock washers, generator, grinder with cutting wheels and grinding wheels, drill with datum point shaping tool, punch, 12” form tube cut to approx. 24” high, 24” length of 6” Sched 40 PVC, wheel barrow and spade shovel, a small amount of pea gravel, “Ready Mix Concrete”, sand, and a trowel for finishing concrete.
1.) Location: Select a location for this monument by looking for a clear area, preferably close to the ROW, with no obstructions, no overhanging trees or billboards towering over the proposal point, no underground utilities in the area, no nearby microwave towers, and not too close to traffic. The location of the point must be suitable for occupation by a base or a rover. If this monument is to be paired with an azimuth mark, the pair must have line of sight at a distance according to job scope. Any obstruction must comply with the project manager’s scope of inclination.
2.) Starting to set the rod: Dig grade to depth of approximately 2’-3” with bell at bottom, see drawing SK-01. Assemble your first rod per manufacturer direction, w/point on one end and the insert on the other before driving. Be sure to tighten all the pairs after you squeeze Lock Tight on all the threads of the bolts or lock washers with the two vice grip pliers, depending on what the project manager wants. (Do not put Lock Tight on the threads of the insert.). Drive rod to approximately 4 tenths of a foot above the ground, remove the insert and screw another rod to the rod in the ground and tighten once again. You must retighten the insert at the top of the rod several times to ensure the rods are not loosening as you are striking. The person holding the setting tool will be able to feel when to stop striking and remove the setting tool and tighten the rod. When you tighten the rod it is a good idea to tighten as much as possible to ensure the joints in the ground are tight also. Keep repeating until you reach Refusal (Definition of Refusal: Refusal is reached when the rod has not moved a tenth of a foot with your last ten strikes, or 1 foot after 1 min of continuous operation with the impact hammer.)..Cut rod to approx 3-4 inches below grade, grind smooth top.
3.) Preparing for concrete: Install 12” form tube at top of bell, bottom of hole, with no more that 1” above grade. The access cover must be stamped with the point name before it is set in PVC. Set stamped cover in PVC, glue in place, let dry thoroughly. Drive 2 #4 deformed Rebar anchors in bottom of hole, ensure 4” into in-situ earth. Fill bottom of hole with approximately 3” sand. Ensure approximately 2” of Rebar extends above sand bed. Drill holes for 60D nails in PVC below access cover collar and install 60D nails. Place PVC over rod into sand. The sides of the hole must be belled outward and down from the bottom of the form tube to the estimated depth and shape as shown in SK01.
4.) Place concrete: Place Ready Mix into a wheelbarrow, using the spade shovel stir water in thoroughly to make a paste.
Backfill around PVC with mixed concrete, fill PVC with Sand and Top with 3” pea gravel to approximately 3” below top of Rod. Trowel concrete smooth. The access cover must be above ground but not more than one inch but must be below ground. The concrete must be smoothed with a trowel.
5.) Finish up: Stamp Rod Cap with required information and install on end of rod. Cap should be approximately centered between access cover and top of gravel. When monument is complete be sure not to leave site without removing all debris and trash. The site should be left as it was found with the exception of the new monument.
SKETCH: See attached
M
A X
FORM TUBE OR
NATURAL FORM
SECTIONAL ROD
CONCRETE,
BELL AT BOTTOM
ACCESS
COVER & CAP
12"
GRADE
D E
P T
H
T
O
P
O I N
T
O F
R
E F
U S
A L
3' MIN DISTANCE TO
VERTICAL OBSTRUCTION
PEA GRAVEL
" x 8" REBAR, DEFORMED
SAND
IN-SITU EARTH
60 "D" NAILS
6" SCHD 40
PVC
P
R
O
J
E
CT
N
A
M
E
A
N
D
I
F
O R
M
A
T
I
O
N
S
U
R
V
Y
MO
U
M
E
N
T
T
D I S
T
U
R
B
C
S
S
U
R
V
E
Y
S
T
B
S
T
A
T
I O
I
DATE:
F S
N
Sheet of
F I L
E
N
A M
E
D W
N
B
Y
D E
S I G
N E
D
B
Y
R E
L E
A S
B
C K
D
B
Y
P R
O J E
U M
B E
R
C O
N T
R A
U M
B E
R
D R
A W
I N
G
C
O D
E
D A
T
WORK ORDER REF:
Scale: N.T.S.
TYPE 'G' MONUMENT
A
Scale: N.T.S
ACCESS COVER
B
Scale: N.T.S
ROD CAP
C
SK-01
G E
N E
R A
L
C
O N
S T
R U
C T
I O
N
C
O N
C E
P T
T Y
P
G
M
O N
U M
E N
T
JBSF12XXXXX
S U
R V
N
T R
O L
J O
I N
T
B
A S
E
S
A
A
T
O N
I O
M o r g a n
D
M o r g a n
D
R e l e a s e w i t h
S p e c s
J a n r e v
J a n
F�
Monument
| �heet | |
| ���� | � |
��������� JBSF TYMX JBSC CYRB Station Name:
MPLS DAXG VGJT JBSG KELL
MBPB MPYJ
JBSA ������� �����
���� � XXXXXX ������ #$�
| �� | ��&� | |
| �' | ���&� � |
| ���&� | ,��)�� | ����-���� |
| � | � |
| ����� | ,��� |
| ����� |
,��0 ����� ��� �+* 1+' �22 ���3� ����2���� ����)����
| ��������� | �������� |
| ,��0��� | � |
| �� � | ��� |
| � | ������� |
| ��������� | � |
| �&����� | ������� |
�2���� ����)��
#� 4���) *�����2����
Monument Control Sheet ���� 5
��������� JBSF TYMX JBSC CYRB Station Name:
MPLS DAXG VGJT JBSG KELL
MBPB MPYJ
�JBSA ������� ����
������� �0���)
| �)��� | � | 6 | ������� | *���� | ||
| �)��� | 5 | 6 | ������� | ���� | ������� |
SECTION 01 35 13.20 00
SPECIAL PROJECT PROCEDURES –CAD
01 35 13.20 00 - 1 1 DEC 2013, rev6
PART 1: GENERAL: This Section covers the project requirements related to Computer Aided
Drafting (CAD) files unique to Joint Base San Antonio, Texas.
1.1 REFERENCES: The publications listed below form a part of this specification to the extent referenced. The publications are referred to in the text by basic designation only.
1.1.1 U.S. ARMY REGULATIONS (AR) (NOT USED)
1.1.2 UNITED STATES ARMY CORPS OF ENGINEERS
a. Engineer Research and Development Center (ERDC) / Information Technology
Laboratory (ITL)
ERDC/ITL TR-12-X: A/E/C CAD Standards Release 5.0, https://cadbim.usace.army.mil/CAD; Whole Building Design Guide, http://www.wbdg.org/ccb/AECCAD/aecstandardR5.pdf.
ERDC/ITL TR-12-1: CAD Drafting Standard, https://cadbim.usace.army.mil/CAD; Whole Buildin g Design Guide, http://www.wbdg.org/ccb/AECCAD/aeccadstd.pdf.
1.1.3 JOINT BASE SAN ANTONIO (JBSA) PUBLICATIONS
a. JBSA Installation Design Guide, July 2006, (http://www.samhouston.army.mil/dpw/) obtain pending updates by email usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.
1.1.4 CITY OF SAN ANTONIO PUBLICATIONS
a. San Antonio Unified Development Code http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=
Texas.
1.2 PURPOSE
1.2.1 The purpose of the A/E/C CAD standard is to set a basic CAD standard to ensure consistent electronic deliverables within the DOD. These consistent deliverables are part of a comprehensive installation life-cycle management strategy. The
A/E/C CAD standard sets a CAD standard specifically for the A/E/C disciplines of facilities development and civil works projects. The A/E/C CAD standard is utilized as tailored by this section.
1.3 SUBMITTALS
1.3.1 DELIVERABLE FORMAT AND MEDIA: FINAL and all INTERIM CAD submittals::
1.3.1.1 All CAD files shall be provided in the Joint Base San Antonio target CAD system, AutoCAD 2010/2011 drawing format (.dwg). The Contractor shall ensure that all delivered CAD digital files and data (e.g., base files, reference files, https://cadbim.usace.army.mil/CAD http://www.wbdg.org/ccb/AECCAD/aecstandardR5.pdf https://cadbim.usace.army.mil/CAD http://www.wbdg.org/ccb/AECCAD/aeccadstd.pdf file:///C:/Users/don.n.morgan/AppData/Roaming/Microsoft/Word/(http:/www.samhouston.army.mil/dpw/) mailto:usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=Texas http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=Texas
01 35 13.20 00 - 2 1 DEC 2013, rev6 block libraries) are compatible with the Government’s target CAD systems and operating systems, and adhere to the standards and requirements specified herein.
NOTE: The term “compatible” means that data are in native digital format (i.e.
.dwg , .pdf, .docx, .xlsx, etc.) and can b e ac ces sed dir ectly by the ta rget CAD system without translation, proxy errors, preprocessing, or post processing of the digi tal data f iles. It is the responsib ili ty o f the Con tra ctor to en sure this level of compatibility.
1.3.1.2 All CAD files shall contain the original vector line work (a scanned file placed in the cad file as an image is not sufficient). Any work done in a non-target CAD system must be translated by the Contractor to the target CAD
System, and must be done in such a way that drawing functionality is maintained. For example the separation of the arrowhead from a leader line or dimension line is considered loss of functionality. All translation tables, mapping schemes, and original files (i.e. *.dwg files), and mapping tables, must be provided.
1.3.1.3 All project drawing sheets shall be submitted to the government with a matching CAD sheet file from which respective sheet was created from and a corresponding .pdf format file w i t h m a t c h i n g file naming convention (i.e. if files A-101.dwg and C-101.dwg are submitted, files A-
101.pdf and C-101.pdf will need to be present within the submission).
1.3.1.4 All files shall be submitted on a DVD or CD, using the current government folder structure; Sheet files shall go in a sub-directory named “Sheets”, Model files (those referenced into the sheets) shall go in a sub-directory named
“Support”, and PDF files shall be placed in a sub-directory named “PDF.”
1.3.1.5 Include metadata, control points, topographic, planimetric, and any additional supporting data.
1.3.1.6 Include other native formats if used – (i.e. MS Word, Excel, Access, Microstation, etc.).
Email usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil for current versions required.
PART 2: PRODUCTS: (Not Applicable)
PART 3: EXECUTION:
3.1 CAD FILES:
NOTE: Page numbers refer to the A/E/C CAD Standard Release 5.0 unless stated otherwise.
3.1.1 The Contractor shall provide complete sheet files along with all model files referenced into these sheet files. For example, if a final design consists of 40 hardcopy sheets, then
01 35 13.20 00 - 3 1 DEC 2013, rev6 a minimum of 40 CAD sheet files and all external reference files (model CAD files, image files, etc.) used for the 40 sheets shall be provided. There shall be no deviation from A/E/C CAD Standards Release 5.0, CAD drafting Standard, and this specification unless prior approval by 502 CES/CENMT has been officially obtained.
3.1.2 The Contractor shall provide all associated files used in the production of drawings
(i.e. plot styles, line types, external references, ect.) and be fully functional to reproduce submitted drawings. The preferred method of transmitting CAD files is to use the AutoCAD “eTransmit” command onto a disk that is clearly marked with
Project Name, Project Number, Type of Submission and date, as a minimum.
3.1.3 General instruction for drafting & plotting:
3.1.3.1 Drafting shall be done in accordance with A/E/C CAD Standard Release 5.0 and
CAD Drafting Standard. Plotting shall be done at a scale of 1:1 and utilizing the aecstdbandw named style table (aecstdbandw.stb). The Contractor shall not alter the assignments of the aecstdbandw.stb file; Joint Base San Antonio will supply generic templates and the border sheet for use upon request by email to usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.
3.1.3.2 Use of the available upon request templates and Sheet Set Manager (SSM) is preferred.
3.1.3.3 All drawings shall be in Imperial Units (inches and feet).
a. “Decimal and feet” units are only used for site plans.
b. All other drawings shall utilize “architectural and inches” units.
3.1.3.4 LOGOS: If the drawing is to be sealed, replace the 502 CES Logo in the top position of the title bar with the Seal. The Contractor may then place a Logo under the JBSA Logo located approximately half way up the title bar. If the drawing is not sealed, the Contractor may replace the 502 CES logo with the prime Contractor logo and place any subs below the JBSA Logo. In any case
DO NOT ERASE the JBSA Logo.
3.1.4 Drawing File Organization:
3.1.4.1 Chapter 2, page 6, Origin – 0,0,0 shall be used as the common origin point for all drawings – model, sheet, symbol, etc. unless otherwise approved. In the rare instance a different origin point is approved for a model file, a minimum of 3 registration points shall be incorporated into the file with reference to true state plane coordinate system (See Section 01 35 13.30 00 Special Project Procedures
– GIS for coordinate system).
3.1.4.2 Chapter 2, page 7-8, File Types & Drawing Sheet Assembly:
01 35 13.20 00 - 4 1 DEC 2013, rev6
a. All drawing graphics (lines, arcs, polygons, etc.) shall be in the model space
(Model tab) of the model file.
b. All model files must be drawn at full scale (1:1).
c. All sheet files shall be a “ready-to-plot” CAD file.
d. The title block shall be externally referenced in the Layout tab (Paper Space) of each sheet file. All other drawings shall be externally referenced in the
Model Tab of the sheet file.
3.1.4.3 Chapter 2, page 9-23, Electronic Drawing File Naming Conventions (Four mandatory fields):
a. Both model and sheet file naming convention shall begin using the same 10 to 12 character project code assigned by 502 CES. Project codes can be obtained by request to usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil.
b. A two character discipline designator shall follow the project code for both model and sheet files (The sheet file requires a level 2 designator).
c. The last two mandatory fields for model file names shall consist of a two character ‘model file type’ and a four character ‘user definable code’ (See page 10).
d. The last two mandatory codes consisting of three digits for sheet file names shall consist of a one digit ‘sheet type designator’ and a two digit ‘sheet sequence number’ (See page 22).
e. Sheet file names shall contain no user definable characters.
3.1.4.4 Chapter 3, page 25-28, Presentation Graphics.
3.1.4.4.1 The template CAD files available upon request from the government utilize a named style pentable (drawing pstyles variable set to 0), meaning that line width and shading is NOT controlled by color.
a. The presentation graphics (line widths, line types, etc) set in these
CAD files must be modified to produce the desired readability of the final printed product. In general, drawings will be created using visual control that is manipulated by the layer; meaning color=’bylayer’, line weight=’bylayer’, line type=’bylayer’.
b. In almost all cases, if these setting do not work, the items should be on separate layers.
3.1.4.5 Chapter 3, page 26, Line types/styles:
01 35 13.20 00 - 5 1 DEC 2013, rev6
3.1.4.5.1 The use of any line types/styles not in the templates available upon request must be approved by 502 CES.
3.1.4.6 Chapter 3, page 27/28, Plotting:
3.1.4.6.1 Only the pentable(s) available upon request by 502 CES shall be used.
(The named plot style - aecbandw.stb (required) is designed to be used with drawings requiring a named plot style. It has several settings –
Black, Screen_40, Screen_50, Screen_60, Color, and Screen_50color, invisible).
3.1.4.7 Chapter 3, page 28-30, Text:
3.1.4.7.1 All projects shall use Arial font. Upon approval: special fonts; slanted text; and text styles may be used for business titles and logos in border sheets. If approved the font definition file must be supplied with the electronic files.
3.1.4.8 Chapter 3, page 28-30, Text Height:
3.1.4.8.1 Varying size of text for like items shall be avoided. Applications are:
a. 1/2" – 1” for COVER TITLE type text.
b. 1/4” for Sheet Title text, i.e., FLOOR PLAN.
c. 3/16" for Sheet Item Titles typ. text, i.e., LEGEND, GENERAL
NOTES, CURB DETAIL.
d. 1/8" for all new or demo work.
e. 3/32” for supportive text (i.e. contours, existing features).
3.1.4.9 Chapter 3, page 30, General Text Placement:
3.1.4.9.1 General, project wide, non-sheet specific text may be placed in the model file, but shall only be placed at predominate text height and not duplicated at varying scales (i.e. room numbers, street names, coordinates, topographic points, etc. may be placed in the model file; all other text shall be placed in specific sheets).
3.1.4.9.2 All text (with the exception of 3.1.4.9.1) shall be placed in the
Layout tab (Paper Space) of the Sheet file for which it pertains.
3.1.4.10 Chapter 3, page 31-32, Border Sheets:
3.1.4.10.1 Only those border files available upon request by 502 CES shall be used. Ansi D (22x34) shall be used to facilitate direct 50% reduction
01 35 13.20 00 - 6 1 DEC 2013, rev6 to 11x17. The actual file adds an additional 2” (making it 22x36) which can be used for binding paper prints.
3.1.4.10.2 The border file available upon request from 502 CES is intended to be used with AutoCAD Sheet Set Manager (SSM), in which sheet text information is controlled through the SSM via the use of fields.
a. The Sheet Set definition is supplied with the template and shall not be modified. Modified meaning creation of additional field, etc, and does not apply to the required input of data.
3.1.4.10.3 A border that is intended to be used without utilizing the SSM will not be supplied. If the Contractor desires to not use the SSM, the Contractor will be required to modify the supplied templates for use with attributed blocks. Modification shall be approved via direct coordination with 502
CES prior to its use.
3.1.4.10.4 All border sheets must contain the information “Joint Base San Antonio, TX”.
3.1.4.11 Chapter 3, page 32, Issue Block.
3.1.4.11.1 During Design, the revision number shall be represented with a
“Circle & Number” and a description that provides a general statement of the revision.
3.1.4.11.2 Upon 100% Design and released for construction, all revision marks are erased and a single entry made; mark “1” in a “Circle” and note as
“RELEASED FOR CONSTRUCTION.”
3.1.4.11.3 During construction, as modifications or differing conditions are found/made, the changes are reflected with a “Triangle & Number” and the description provides a general statement of the revision. The area of change is clouded and marked with a corresponding “Triangle &
Number”.
3.1.4.11.4 At end of construction and completion of As-Built, all triangle marks and clouds are removed and replaced with a single statement above the
“RELEASED FOR CONSTRUCTION” remark that reads “RECORD
DRAWING AS-BUILT”.
3.1.4.11.5 If a sheet is altered to the degree that it must be re-issued, the new sheet shall contain the number “1” in a “Circle” with the “RELEASED FOR
CONSTRUCTION” and original date mark with the next immediate mark being a number “1” with a “Triangle” and the remark “SHEET RE-
ISSUED” or “SHEET REPLACED BY” and include the new sheet number.
01 35 13.20 00 - 7 1 DEC 2013, rev6
3.1.4.11.6 All marks denoting a change shall include a modification, RFI, or change order number in the description.
3.1.4.12 Chapter 4, Page 44-53, Level/Layer Assignments:
3.1.4.12.1 Only the layers defined in Appendix A shall be used.
a. The layer attributes for color, line type, line weight, and plot style must be modified to produce visually acceptable final prints.
b. ISO format layer names shall NOT be used unless directly coordinated through 502 CES.
3.1.4.13 Chapter 4, page 50, Reference Files:
a. All reference files shall be on reference layers, i.e. X-XXXX-REFR.
b. All reference files shall be associated as a separate OVERLAY, meaning
NO nested references.
c. All reference files shall be associated using a RELATIVE PATH.
d. All reference names shall match the reference file name in its entirety;
ALIAS NAMES shall NOT be used.
e. All reference files shall be made in the Model Tab of the sheet drawing file, with the exception of the border sheet drawing. The Border sheet drawing shall be referenced in the Layout Tab (Paper Space) of the sheet drawing file. Border sheet drawing shall NOT be referenced in the Model Tab of a sheet drawing file.
f. All reference files shall be drawn at a scale of 1:1 (real size). Manipulation of the viewport in the Layout Tab (Paper Space) of the drawing sheet file shall be made to obtain the appropriate viewing/printing scale.
g. Changes to the drawing graphics shall be made to the external reference(s)
(any changes made to the reference(s) will be automatically updated in the sheet file).
3.1.4.14 Chapter 5, Symbology.
3.1.4.14.1 The A/E/C CAD standard, while supplying many symbols, does not meet current industry needs nor does it address the fundamental construction of block entities. The following guidelines shall be used in the creation of new blocks:
a. The Contractor shall fully document any custom made/used blocks in the files (meaning any block used that is not supplied by Joint
01 35 13.20 00 - 8 1 DEC 2013, rev6
Base San Antonio). Documentation shall include block name, description, and summary of use – i.e. how is it used and controlled.
This documentation must be supplied with any and/or all drawing submittals as a “READ ME” file.
b. All symbol blocks shall be made with all entities on layer 0; color, line type, and line weight shall be set to BYLAYER. Line type scale for all entities will be set to 1.
c. Attributes shall follow the same guidelines as text, but shall also be placed on layer zero. In some cases, it makes sense to have an attribute on a named layer – i.e., a survey control monument may have text on a monumentation text layer so that it’s id may be turned off without effecting the block visibility. If this situation is used, the
Contractor shall fully document the elements of a block that are not constructed on layer 0 and have this documentation of the block
APPROVED prior to use.
d. Block Symbols must be constructed with the insertion point set to
0,0,0. (the base point of all drawings shall be 0,0). Example, if the symbol is a manhole, the insertion point would be the center of the manhole, which would be at 0,0,0.
e. Block names shall follow layer naming conventions- i.e. a surveyed
Sanitary Sewer manhole would be V-SSWR-MNHL.
3.3 Contact by email: usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil. for any question or concerns in regards to A/E/C CAD Standard, CAD Drafting Standard, and/or this document.
SECTION 01 35 13.30 00
SPECIAL PROJECT PROCEDURES –GIS,
01 35 13.30 00 - 1 27 FEB 2014, rev6
PART 1: GENERAL: This Section covers the project requirements unique to Joint Base San
Antonio, Texas. These unique requirements relate to Geographic Information Systems (GIS)
Systems
1.1 REFERENCES: The publications listed below form a part of this specification to the extent referenced. The publications are referred to in the text by basic designation only.
1.1.1 U.S. ARMY REGULATIONS (AR) (NOT USED)
1.1.2 UNITED STATES ARMY CORPS OF ENGINEERS ENGINEERING MANUALS
(EM) – (NOT USED)
1.1.3 JOINT BASE SAN ANTONIO (JBSA) & OTHER PUBLICATIONS
a. JBSA Installation Design Guide, July 2006, (http://www.samhouston.army.mil/dpw/) obtain pending updates by email to usaf.jbsa.502-abw.mbx.502-ces-cad-manager@mail.mil
b. San Antonio Unified Development Code http://library.municode.com/index.aspx?clientId=14228&stateId=43&stateName=Te xas
c. Tri-Service A/E/C CAD Standards,…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .