Permit Application Process Sample Clauses

Permit Application Process. To apply for a Permit under this Agreement, Licensee shall submit to the District a Pole Attachment ticket through NJUNS (“PA Ticket”) with the District’s Permit Application Exhibit (A), Radio Interference Test Report, and a Pole Load Analysis report (“PLA Report”) attached thereto. The Permit Application form may be revised from time to time in the reasonable discretion of the District. Licensee may cancel a Permit issued under this Agreement pursuant to Section 10.
AutoNDA by SimpleDocs
Permit Application Process. 1) The application for a permit shall be submitted in such form as the County Toll Road Operator may prescribe and shall be accompanied by drawings and descriptive data to verify compliance with these Regulations. Every application shall be executed by the owner of the Premises upon which the Sign is to be or has been constructed, or by the owner’s authorized agent. If the Sign's plans and specifications conform to all requirements of these Regulations, the County Toll Road Operator shall issue the permit. Notwithstanding the foregoing, a permit issued under these Regulations does not authorize construction of a Sign in violation of any other land use restriction, ordinance, regulation, or statute. 2) Permit applications may be submitted and processed online via the following website: 3) Sign permit applicants shall provide such information as may be required by the County Toll Road Operator.
Permit Application Process. 3.1 A person applying for a permit to alter grades on the Lands shall submit the following to the Director: (a) a complete application in the form prescribed by the Director; (b) the applicable permit fee calculated in accordance with Schedule "A" which forms part of this by-law; (c) an accurate plan of the lands showing: (i) the property lines of the lands with dimensions; (ii) existing elevations in the form of contours at 0.5 metre intervals or less, with spot elevations along the property lines and 3.0 metres beyond the property line at sufficient intervals to clearly show the existing drainage patterns on the lands and on the abutting lands; (iii) all existing storm sewers, ditches, xxxxxx, creeks and watercourses on the lands and on abutting lands and public highways; (iv) all existing buildings, the species and size in caliper of all trees greater than 75 mm, the location of all shrubs and driveways on the lands and all easements and rights-of-way over, under, across or through the lands; (v) proposed sediment and erosion controls that will be installed prior to alteration of the lands; (vi) proposed final elevations and drainage system to be used upon completion of the site alteration operation, and (vii) a description of the proposed fill or topsoil removal operation; (d) a plan showing the design details, to proper scale, with an Engineer’s signature and stamp, of any retaining wall that may be required, and the size, type and location of all material to be used in construction of such retaining wall; and (e) security in a form and amount as set out in Schedule “A” to this by-law to secure performance of the work for which the permit was obtained, which security shall be available to recover the cost of the Town of Fort Erie performing any required work which the Owner has failed to perform to the Town's satisfaction. 3.2 In addition to the requirements set out in subsection 3.1, the Director may require a person applying for a permit to provide an environmental audit of the fill material at the applicant’s expense. PAGE SIX
Permit Application Process. Effective April 1, 2014, every vehicle parked on the Masthead campus must display the appropriate parking permit. Employees will complete one registration form for each motor vehicle they wish to park on the campus lot. Registration forms can be completed via email or hard copy. Hardcopy forms will be available at each guard station and break rooms in each Masthead building. Electronic forms will be sent to Masthead employees via the Public Distribution List (pdl) at FS-pdl asc masthead. Completed registration forms will be distributed as follows: One copy with attached permit/s/ will be returned to employee, original registration form will be secured in a locked box at the guard station in 3900 Masthead, one copy of registration form will be secured by Internal Operations Facility POC. Information from registration forms will be entered into a secured database. Employees are responsible for keeping vehicle information up to date by reporting changes to the Internal Operations Facility POC.
Permit Application Process 

Related to Permit Application Process

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Application Procedure 7.4.1. Application Priority........................................ 7.4.2. [Reserved].................................................. 7.4.3. Advance Payments............................................

  • Application Procedures i) An employee applies for a listing on the system-wide registry through the employee’s Human Resources Department by completing the form in Appendix A. ii) The institution will immediately forward the completed form to the PSEA who will list eligible employees on the system-wide registry. iii) A registrant is responsible to ensure the information is current and to immediately notify the Employer and the local Union if the registrant is no longer available for employment through the Registry.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

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