Provider Credentialing Contractor shall perform, or may delegate activities related to, credentialing and re-credentialing Participating Providers in accordance with a process reviewed and approved by State Regulators.
LETTERS OF REPRIMAND AND ACCESS TO FILES 9.01 Any letter of reprimand or suspension will be removed from the record of an employee eighteen (18) months following the receipt by the employee of such letter or suspension provided that the employee’s record has been discipline free for such eighteen (18) month period. Leaves of absence in excess of thirty (30) calendar days will not count towards the eighteen (18) month period.
Certification for Federal-Aid Contracts Lobbying Activities A. The CONSULTANT certifies, by signing and submitting this Contract, to the best of its knowledge and belief after diligent inquiry, and other than as disclosed in writing to the LPA prior to or contemporaneously with the execution and delivery of this Contract by the CONSULTANT, the CONSULTANT has complied with Section 1352, Title 31, U.S. Code, and specifically, that:
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.
PROVISIONAL AGREEMENT RESULTING FROM INTERINSTITUTIONAL NEGOTIATIONS Subject: Proposal for a regulation of the European Parliament and of the Council on a Pan- European Personal Pension Product (PEPP) (COM(2017)0343 – C8-0219/2017 – 2017/0143(COD)) The interinstitutional negotiations on the aforementioned proposal for a regulation have led to a compromise. In accordance with Rule 69f(4) of the Rules of Procedure, the provisional agreement, reproduced below, is submitted as a whole to the Committee on Economic and Monetary Affairs for decision by way of a single vote. AG\1177088EN.docx PE634.848v01-00 EN United in diversity EN REGULATION (EU) 2019/... OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of ... on a pan-European Personal Pension Product (PEPP) (Text with EEA relevance) THE EUROPEAN PARLIAMENT AND THE COUNCIL OF THE EUROPEAN UNION, Having regard to the Treaty on the Functioning of the European Union, and in particular Article 114 thereof, Having regard to the proposal from the European Commission, After transmission of the draft legislative act to the national parliaments, Having regard to the opinion of the European Economic and Social Committee1, Acting in accordance with the ordinary legislative procedure2,
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Texas Education Code Chapter 22 Contractor Certification for Contractor Employees Introduction Texas Education Code Chapter 22 requires entities that contract with school districts to provide service s to obtain criminal history record information regarding covered employees. Contractors must certify to the district t hat they have complied. Covered employees with disqualifying criminal histories are prohibited from serving at a sch ool district. Definitions: Covered employees: Employees of a contractor or subcontractor who have or will have continuing dutie s related to the service to be performed at the District and have or will have direct contact with students. The District will be the final arbiter of what constitutes direct contact with students. Disqualifying criminal history: Any conviction or other criminal history information designated by the District, or one of the following offenses, if at the time of the o ffense, the victim was under 18 or enrolled in a public school: (a) a felony offense under Title 5, Texas Penal Code; (b) an offense for which a defendant is required to register as a sex offender under Chapter 62, Texas Code of Criminal Procedure; or (c) an equivalent offense under federal law or the laws of another state. I certify that: NONE (Section A) of the employees of Contractor and any subcontractors are covered employees, as defined abo ve. If this box is checked, I further certify that Contractor has taken precautions or imposed conditions to ensure tha t the employees of Contractor and any subcontractor will not become covered employees. Contractor will maintain t hese precautions or conditions throughout the time the contracted services are provided. OR SOME (Section B) or all of the employees of Contractor and any subcontractor are covered employees. If this box is checked, I further certify that: (1) Contractor has obtained all required criminal history record information regarding its covered employees. None of the covered employees has a disqualifying criminal history. (2) If Contractor receives information that a covered employee subsequently has a reported criminal history, Contra ctor will immediately remove the covered employee from contract duties and notify the District in writing within 3 busi ness days. (3) Upon request, Contractor will provide the District with the name and any other requested information of covered employees so that the District may obtain criminal history record information on the covered employees. (4) If the District objects to the assignment of a covered employee on the basis of the covered employee's criminal h istory record information, Contractor agrees to discontinue using that covered employee to provide services at the District. Noncompliance or misrepresentation regarding this certification may be grounds for contract termination. None Texas Business and Commerce Code § 272 Requirements as of 9-1-2017 SB 807 prohibits construction contracts to have provisions requiring the contract to be subject to the laws of anothe r state, to be required to litigate the contract in another state, or to require arbitration in another state. A contract wit h such provisions is voidable. Under this new statute, a “construction contract” includes contracts, subcontracts, or agreements with (among others) architects, engineers, contractors, construction managers, equipment lessors, or materials suppliers. “Construction contracts” are for the design, construction, alteration, renovation, remodeling, or repair of any building or improvement to real property, or for furnishing materials or equipment for the project. The t erm also includes moving, demolition, or excavation. BY RESPONDING TO THIS SOLICITATION, AND WHEN APPLI CABLE, THE PROPOSER AGREES TO COMPLY WITH THE TEXAS BUSINESS AND COMMERCE CODE § 272 WH EN EXECUTING CONTRACTS WITH TIPS MEMBERS THAT ARE TEXAS GOVERNMENT ENTITIES. 7 5 Texas Government Code 2270 Verification Form Texas Government Code 2270 Verification Form Texas 2017 House Xxxx 89 has been signed into law by the governor and as of September 1, 2017 will be codified as Texas Government Code § 2270 and 808 et seq. The relevant section addressed by this form reads as follows: Texas Government Code Sec. 2270.002. PROVISION REQUIRED IN CONTRACT. A governmental entity may not ent er into a contract with a company for goods or services unless the contract contains a written verification from the c ompany that it: (1) does not boycott Israel; and (2) will not boycott Israel during the term of the contract.engaged by ESC Region 8/The Interlocal Purchasing System (TIPS) 0000 Xxxxxxx 000 Xxxxx Xxxxxxxxx,XX,00000 verify by this writing that the above-named company affirms that it (1) does not boycott Israel; and (2) will not boycot t Israel during the term of this contract, or any contract with the above-named Texas governmental entity in the futur e. I further affirm that if our company’s position on this issue is reversed and this affirmation is no longer valid, that t he above-named Texas governmental entity will be notified in writing within one (1) business day and we understand that our company’s failure to affirm and comply with the requirements of Texas Government Code 2270 et seq. shall be grounds for immediate contract termination without penalty to the above-named Texas governmental entity. AND our company is not listed on and we do not do business with companies that are on the the Texas Comptroller of Pu blic Accounts list of Designated Foreign Terrorists Organizations per Texas Gov't Code 2270.0153 found at xxxxx://x xxxxxxxxxx.xxxxx.xxx/xxxxxxxxxx/xxxx/xxxxxxx-xxxxxxxxx.xxx I swear and affirm that the above is true and correct. YES
END USER AGREEMENTS (“EUA H-GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
