Format of the MDF/MRF (Master Design File or Master Right-of-Way Files) DGN Reference Files and Map Sheet Naming Conventions Sample Clauses

Format of the MDF/MRF (Master Design File or Master Right-of-Way Files) DGN Reference Files and Map Sheet Naming Conventions. The recommended naming prefix for design files is MDF (Master Design File). Therefore, the prefix must be different for the right-of-way files because the location of the existing and proposed right-of-way in the design files from the schematic will change to some degree after an on the ground survey is made for right-of-way mapping. Therefore, the prefix could be MRF for Master Right-of-Way File. The corrected Master Right-of-Way Files shall be given to the design engineer to be used in the final PS&E so that all features of construction and the relocation of utilities shall be correctly placed in relation to the highway right-of-way and the right-of-way of cross streets or roadways. The Master Right-of-Way File naming convention is: “MRF ROW CSJ_Logical Name.dgn”, with examples as follows: MRF212104065_Schematic90.dgn (Schematic layout 90% submittal); DocuSign Envelope ID: 798F7E2C-0AE6-40EE-BFB4-3AB848988972 MRF212104065_Schematic100.dgn (Schematic layout 100% submittal); MRF212104065_SchemApprov.dgn (Final Approved [State & FHWA] Schematic); MRF212104065_PSEDesign.dgn (Final P.S.&E. Design); MRF212104065_ExROW.dgn (Existing right-of-way determined by RPLS); MRF212104065_PropROW.dgn (Proposed right-of-way of final design); MRF212104065_DeedPlot.dgn (Deed Record); MRF212104065_Planimetric.dgn (Aerial mapping topography); MRF212104065_ROWTopo.dgn (Improvements data collection); MRF212104065_DesignTopo.dgn (Design level data collection topography); MRF212104065_ExUtil.dgn (Existing utilities), etc. All sheet files with a plan view must have the MRF referenced to allow more than one sheet file to be worked on at the same time.
AutoNDA by SimpleDocs

Related to Format of the MDF/MRF (Master Design File or Master Right-of-Way Files) DGN Reference Files and Map Sheet Naming Conventions

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Loop Provisioning Involving IDLC 2.16.1 Where TWTC has requested an Unbundled Loop and AT&T uses IDLC systems to provide the local service to the customer and AT&T has a suitable alternate facility available, AT&T will make such alternative facilities available to TWTC. If a suitable alternative facility is not available, then to the extent it is technically feasible, AT&T will implement one of the following alternative arrangements for TWTC (e.g., hairpinning):

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!