Regional Traffic Fee Sample Clauses

Regional Traffic Fee. Developer shall pay the ECCRFA regional traffic fee should it be imposed by the City in an amount equal to or less than the amount paid by projects in the Cities of Antioch, Brentwood, and Oakley or in accordance with the existing valid Memorandum of Understanding dated June 29, 2010, as amended, whichever is less.
AutoNDA by SimpleDocs
Regional Traffic Fee. Developer shall the ECCRFA Regional Transportation Development Impact Mitigation Fee (PMC Chapter 15.103) (the “RTDIM”) amount in effect when the Developer obtains a Building Permit. The RTDIM will be automatically increased or decreased on January 1 of each year based on the percent change in the Engineering News Record Construction Costs Index-San Francisco Bay Area between September 1 and September 1 of the preceding two calendar years. Developer shall pay the fees prior to issuance of a Building Permit. If no Building Permit is required, then Developer shall pay the fees at a time consistent with PMC Section 15.103 in the amount in effect when the Project commences pursuant to PMC Section 15.103.

Related to Regional Traffic Fee

  • INTERNATIONAL TRAFFIC 1. Profits from the operation of ships or aircraft in international traffic shall be taxable only in the Contracting State in which the place of effective management of the enterprise is situated.

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Traffic Control The Surveyor shall control traffic in and near surveying operations adequately to comply with provisions of the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI which can be found on the State’s internet site. In the event field crew personnel must divert traffic or close traveled lanes, a Traffic Control Plan based upon principles outlined in the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI shall be prepared by the Surveyor and approved by the State prior to commencement of field work. A copy of the approved plan shall be in the possession of field crew personnel on the job site at all times and shall be made available to the State’s personnel for inspection upon request.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting the HUB Program at 000-000-0000 or toll-free in Texas at 0-000-000-0000.

  • International Travel All international flights with the exception of flights between the U.S. and Canada should be reserved through TMC using the “lowest practical coach fare” with the exception of flights that are six (6) or more consecutive hours in length. In such event, the next available seating class above coach shall be reimbursed. When required to travel internationally for business, employees shall be reimbursed for photo fees, application fees, and execution fees when obtaining a new passport book, but fees related to passport renewals are not reimbursable. Visa application and legal fees, entry taxes and departure taxes are reimbursable. The cost of vaccinations that are either required for travel to specific countries or suggested by the U.S. Department of Health & Human Services for travel to specific countries, is reimbursable. Section 4, Meals & Incidental Expenses, and Section 2.b., Rental Car, shall apply to this section. Exhibit C Exhibit C Service Level Agreement

  • Export Administration Each party agrees to comply with all export laws and regulations of the United States (“Export Laws”) to assure that no software deliverable, item, service, technical data or any direct product thereof arising out of or related to this Agreement is exported directly or indirectly (as a physical export or a deemed export) in violation of Export Laws.

  • Export Control This Agreement is made subject to any restrictions concerning the export of products or technical information from the United States or other countries that may be imposed on the Parties from time to time. Each Party agrees that it will not export, directly or indirectly, any technical information acquired from the other Party under this Agreement or any products using such technical information to a location or in a manner that at the time of export requires an export license or other governmental approval, without first obtaining the written consent to do so from the appropriate agency or other governmental entity in accordance with Applicable Law.

  • Alternate Traffic Routing If CLEC has a LIS arrangement which provides two (2) paths to a CenturyLink End Office Switch (one (1) route via a Tandem Switch and one (1) direct route), CLEC may elect to utilize alternate traffic routing. CLEC traffic will be offered first to the direct trunk group (also referred to as the "primary high" route) and then overflow to the Tandem Switch group (also referred to as the "alternate final" route) for completion to CenturyLink End Office Switches.

  • Additional Training Should the introduction of new methods of operation create a need for the perfection or acquisition of skills requiring a training period longer than one (1) year, the additional training time shall be a subject for discussion between the Board and the Union.

Time is Money Join Law Insider Premium to draft better contracts faster.