Local User Discount Scheme Vehicle Plan Terms
Local User Discount Scheme Vehicle Plan Terms Sample Clauses
Related to Local User Discount Scheme Vehicle Plan Terms
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
EPP query-‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-‐times or more the corresponding SLR, the RTT will be considered undefined.
Sale or Discount of Receivables Except for receivables obtained by the Borrower or any Subsidiary out of the ordinary course of business or the settlement of joint interest billing accounts in the ordinary course of business or discounts granted to settle collection of accounts receivable or the sale of defaulted accounts arising in the ordinary course of business in connection with the compromise or collection thereof and not in connection with any financing transaction, the Borrower will not, and will not permit any Subsidiary to, discount or sell (with or without recourse) any of its notes receivable or accounts receivable.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx 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 Xxxx. 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 Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.
RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-‐based-‐ WHOIS query RTT”.
WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-‐times or more the corresponding SLR, the RTT will be considered undefined.
PROPOSED MOBILITY PROGRAMME The proposed mobility programme includes the indicative start and end months of the agreed study programme that the student will carry out abroad. The Learning Agreement must include all the educational components to be carried out by the student at the receiving institution (in table A) and it must contain as well the group of educational components that will be replaced in his/her degree by the sending institution (in table B) upon successful completion of the study programme abroad. Additional rows can be added as needed to tables A and B. Additional columns can also be added, for example, to specify the study cycle-level of the educational component. The presentation of this document may also be adapted by the institutions according to their specific needs. However, in every case, the two tables A and B must be kept separated, i.e. they cannot be merged. The objective is to make clear that there needs to be no one to one correspondence between the courses followed abroad and the ones replaced at the sending institutions. The aim is rather that a group of learning outcomes achieved abroad replaces a group of learning outcomes at the sending institution, without having a one to one correspondence between particular modules or courses. A normal academic year of full-time study is normally made up of educational components totalling 60 ECTS* credits. It is recommended that for mobility periods shorter than a full academic year, the educational components selected should equate to a roughly proportionate number of credits. In case the student follows additional educational components beyond those required for his/her degree programme, these additional credits must also be listed in the study programme outlined in table A. When mobility windows are embedded in the curriculum, it will be enough to fill in table B with a single line as described below: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Mobility window … Total: 30 Otherwise, the group of components will be included in Table B as follows: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Course x … 10 Module y … 10 Laboratory work … 10 Total: 30 The sending institution must fully recognise the number of ECTS* credits contained in table A if there are no changes to the study programme abroad and the student successfully completes it. Any exception to this rule should be clearly stated in an annex of the Learning Agreement and agreed by all parties. Example of justification for non-recognition: the student has already accumulated the number of credits required for his/her degree and does not need some of the credits gained abroad. Since the recognition will be granted to a group of components and it does not need to be based on a one to one correspondence between single educational components, the sending institution must foresee which provisions will apply if the student does not successfully complete some of the educational components from his study programme abroad. A web link towards these provisions should be provided in the Learning Agreement. The student will commit to reach a certain level of language competence in the main language of instruction by the start of the study period. The level of the student will be assessed after his/her selection with the Erasmus+ online assessment tool when available (the results will be sent to the sending institution) or else by any other mean to be decided by the sending institution. A recommended level has been agreed between the sending and receiving institutions in the inter-institutional agreement. In case the student would not already have this level when he/she signs the Learning Agreement, he/she commits to reach it with the support to be provided by the sending or receiving institution (either with courses that can be funded by the organisational support grant or with the Erasmus+ online tutored courses). All parties must sign the document; however, it is not compulsory to circulate papers with original signatures, scanned copies of signatures or digital signatures may be accepted, depending on the national legislation. * In countries where the "ECTS" system it is not in place, in particular for institutions located in partner countries not participating in the Bologna process, "ECTS" needs to be replaced in all tables by the name of the equivalent system that is used and a weblink to an explanation to the system should be added. The section to be completed during the mobility is needed only if changes have to be introduced into the original Learning Agreement. In that case, the section to be completed before the mobility should be kept unchanged and changes should be described in this section. Changes to the mobility study programme should be exceptional, as the three parties have already agreed on a group of educational components that will be taken abroad, in the light of the course catalogue that the receiving institution has committed to publish well in advance of the mobility periods and to update regularly as ECHE holder. However, introducing changes might be unavoidable due to, for example, timetable conflicts. Other reasons for a change can be the request for an extension of the duration of the mobility programme abroad. Such a request can be made by the student at the latest one month before the foreseen end date. These changes to the mobility study programme should be agreed by all parties within four to seven weeks (after the start of each semester). Any party can request changes within the first two to five-week period after regular classes/educational components have started for a given semester. The exact deadline has to be decided by the institutions. The shorter the planned mobility period, the shorter should be the window for changes. All these changes have to be agreed by the three parties within a two-week period following the request. In case of changes due to an extension of the duration of the mobility period, changes should be made as timely as possible as well. Changes to the study programme abroad should be listed in table C and, once they are agreed by all parties, the sending institution commits to fully recognise the number of ECTS credits as presented in table C. Any exception to this rule should be documented in an annex of the Learning Agreement and agreed by all parties. Only if the changes described in table C affect the group of educational components in the student's degree (table B) that will be replaced at the sending institution upon successful completion of the study programme abroad, a revised version should be inserted and labelled as "Table D: Revised group of educational components in the student's degree that will be replaced at sending institution". Additional rows and columns can be added as needed to tables C and D. All parties must confirm that the proposed amendments to the Learning Agreement are approved. For this specific section, original or scanned signatures are not mandatory and an approval by email may be enough. The procedure has to be decided by the sending institution, depending on the national legislation.
Eligible Population 5.1 Program eligibility is determined by applicable law set forth in Program rules and the requirements established in the Program Policy Manual. 5.2 The unduplicated number of Clients for PHC services is 430. This represents the Grantee’s projected number of unduplicated Clients to be served during the Contract period. If during the Contract period it is foreseen that the Grantee might be unable to serve the contracted number of children, HHSC may reduce the Grantee’s grant award amount.
Two-‐character labels All two-‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-‐code manager of the string as specified in the ISO 3166-‐1 alpha-‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Tandem Transit Traffic 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that Xxxxx has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.
