Choice of the Exchange Mechanism Sample Clauses

Choice of the Exchange Mechanism. Unless otherwise agreed by the Parties in the in Bilateral-Spec., the default Exchange Mechanim is peer to peer file transfer through a Secure File Transfer Protocol ("SFTP"). Without any limitation, alternative solutions may include sending an electronic file over an internet or other electronic network connection or sending the electronic file stored on physical media or joining a centralised exchange mechanism.
AutoNDA by SimpleDocs

Related to Choice of the Exchange Mechanism

  • Purchase Mechanism If the Focus Investor exercises its rights provided in this Section 4.5, the closing of the purchase of the New Securities with respect to which such right has been exercised shall take place within 30 calendar days after the giving of notice of such exercise, which period of time shall be extended for a maximum of 180 days in order to comply with applicable laws and regulations (including receipt of any applicable regulatory or corporate approvals). The Company and the Focus Investor agree to use commercially reasonable efforts to secure any regulatory or corporate approvals or other consents, and to comply with any law or regulation necessary in connection with the offer, sale and purchase of, such New Securities.

  • Validation Mechanism To be eligible for articulation, the student must show evidence of their CompTIA A+ certification and it must have been issued within three (3) years prior to their enrollment in the program.

  • Alternative Dispute Resolution Limitations This is a requirement of the TIPS Contract and is non-negotiable. No Waiver of TIPS Immunity This is a requirement of the TIPS Contract and is non-negotiable. 5 5 Payment Terms and Funding Out Clause This is a requirement of the TIPS Contract and is non-negotiable. 6

  • Purpose of Consultation Procedure The purpose of the consultation procedure is to endeavor to resolve any failure to meet the provisions of the Service Level Agreement. If a consultation occurs under this Section V, all parties must negotiate in good faith to endeavor to: 1. implement changes which will enable the Service Level Agreement provisions to be met – such changes may include, but are not limited to, modification of either or both parties’ respective operational resources; 2. agree to alternative Service Level Agreement provisions which meet the parties’ respective business requirements; or 3. otherwise find a solution such that within a reasonable time after the consultation, the inability to meet the Service Level Agreement provision(s) is reasonably expected to be less likely to occur in the future.

  • Dispute Resolution Mechanism a. Any dispute regarding the administration of the Institute at the Company or plant level shall be subject to expedited resolution by the Chairs of the Union and Company Negotiating Committees and the Executive Director of ICD who shall apply the policies, rules and regulations of the Governing Board and the provisions of this Section in ruling on any such dispute. Rulings of the Executive Director may be appealed to the Governing Board, but shall become and remain effective unless stayed or reversed by the Governing Board. b. Within sixty (60) days of the Effective Date, the parties will develop an expedited dispute resolution mechanism that resolves disputes within two (2) weeks.

  • Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.

  • Layoff Procedure A. Once the University determines the need for a layoff exists, it shall employ the following procedure: 1. If at any time during the layoff process an employee submits his notice of retirement, resignation or volunteers for layoff, the University will review its layoff rationale. Where appropriate, the University may curtail staff reductions and/or recall laid-off employee(s). The University shall first lay off non-bargaining unit temporary employees with the same job classification and within the department(s) where the layoff(s) occurs. The University shall then lay off probationary employees with the same job classification and within the affected department(s). The University shall then lay off part-time employees with the same job classification and within the affected department(s). 2. If further reductions are required, employees in the affected job classification(s) shall be laid off as follows: a. any employees in the affected classification who have active discipline at the suspension (whether a working suspension or unpaid suspension) level or covered by a “last chance agreement” for conduct other than that covered by Article 41, or b. any employees who have an overall performance evaluation rating below standards (i.e. a “needs improvement” rating or below) for the two most recent performance evaluation rating periods, or c. in the inverse order of seniority. The remaining employees within the department or unit must be immediately qualified to perform the required work. For purposes of layoff, placement, bumping, and recall, “immediately qualified” shall be defined as meeting the minimum and preferred qualifications for the position to perform the work, with the exception of the Technology Scale, where “immediately qualified” shall be defined as meeting the minimum qualifications for the position to perform the required work. In determining whether the employee is immediately qualified, the University shall give consideration to ability, aptitude, skill, experience, qualifications as stated in the job description. The determination of qualifications is the responsibility of the University. If the University determines that an employee is not qualified, the employee shall have the right to grieve such decision. Part-time employees shall be laid off before full-time employees, and part-time employees cannot bump full-time employees. Similarly, temporary employees cannot bump regular or funds available employees, regardless of seniority. 3. Student employees shall not be used to perform significant components of the position of a laid off employee. It is agreed that this provision shall not apply to students, whether paid or unpaid, performing work in internships, graduate assistantships, practicums or through other programs whose primary purpose is to satisfy a degree requirement. 4. The University shall make available to laid-off employees, prior to their layoff date, job and career advising and information on benefits. Upon request, the University shall provide reasonable access to personal computers, and copiers for use in preparing resumes and cover letters. Employees shall also have access to EAP services during this time period to deal with any stress-related issues. 5. If the work force is to be reduced, it shall be accomplished by layoff and not by any hours reduction. Only by agreement between the employee, University and Union can the regular hours of employees be reduced. 6. If a layoff occurs during a period of unpaid leave, the employee on leave shall receive the same rights under this Agreement upon return to work as other employees. 7. Any employee scheduled to be laid off from his/her present job may request to be transferred into a posted vacant bargaining unit position for which the employee is immediately qualified to perform the required work. 8. Seniority will continue to accrue up to eighteen (18) months during time spent on layoff, and the employee shall retain all seniority accumulated prior to layoff. 9. Employees laid off while serving his/her initial probationary period or employees in a temporary position (an employee hired for a specific project or hired with a defined end date) will not be entitled to placement, bumping or recall rights.

  • PURPOSE/JUSTIFICATION OF RECOMMENDED ACTION The TTC will sell the properties in accordance with the provisions of Division 1, Part 6, Chapter 8 of the Revenue and Taxation Code (R&TC), and the Board of Supervisors' policy adopted on November 24, 1970. Exhibit A of the Chapter 8 Agreement Sale indicates the legal description and selling price of the properties. The Honorable Board of Supervisors 3/5/2019 The recommended action supports County Strategic Plan Strategy III.3 – Pursue Operational Effectiveness, Fiscal Responsibility, and Accountability.

  • Purpose; Incorporation by Reference of Auction Procedures and Settlement Procedures (a) The Statement for each series of MuniPreferred will provide that the Applicable Rate for such series for each Subsequent Rate Period thereof shall, except under certain conditions, be the rate per annum that a bank or trust company appointed by the Fund advises results from implementation of the Auction Procedures for such series. The Board of Directors or Board of Trustees, as the case may be, of the Fund has adopted a resolution appointing the Auction Agent as auction agent for purposes of the Auction Procedures for each series of MuniPreferred. The Auction Agent accepts such appointment and agrees to follow the procedures set forth in this Section 2 and the Auction Procedures for the purpose of determining the Applicable Rate for each series of MuniPreferred for each Subsequent Rate Period thereof for which the Applicable Rate is to be determined by an Auction. Each periodic implementation of such procedures is hereinafter referred to as an "Auction." (b) All of the provisions contained in the Auction Procedures and the Settlement Procedures are incorporated herein by reference in their entirety and shall be deemed to be a part hereof to the same extent as if such provisions were fully set forth herein.

  • PROCEDURE FOR APPROVAL OF SETTLEMENT Acceptance of this Settlement Agreement shall be sought at a hearing of the Central Regional Council of the MFDA on a date agreed to by counsel for Staff and the Respondent.

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