Maintenance of Review Materials It will maintain copies of any Review Materials, Review Reports and other documents relating to a Review, including internal correspondence and work papers, for a period of at least two years after any termination of this Agreement.
Delivery of Software 1. SAP will deliver the Software as described in the Documentation and the Price List and will also provide the appropriate license key for the relevant End User. With regard to the features, quality and functionality of the Software the product description in the Documentation and the Price List is solely decisive. SAP does not own any additional features, quality or functionality. Distributor can, in particular, not assert any additional feature, quality or functionality from any public statements, publications or advertisements by SAP except to the extend SAP has expressly confirmed such additional feature, quality or functionality in writing. Any representation, warranty, undertaking or guarantee regarding additional features, quality or functionality is effective only if expressly confirmed by SAP’s management in writing.
2. After acceptance of an order, SAP will deliver to Distributor one copy of the relevant Software:
a) on discs or other data media (“Physical Shipment”); or
b) by making it available for downloading through the internet (usually on the SAP ServiceMarket Place (xxxx://xxxxxxx.xxx.xxx/swdc)) (“Electronic Delivery”).
3. The relevant Software and Documentation will be deemed delivered (including but not limited for the purpose of fixed delivery dates or timely delivery) and the risk passes to Distributor:
a) in case of Physical Shipment, when the relevant disc or other data media thereof is handed over to the freight carrier (FCA - Free Carrier (named place of delivery), Incoterms 2010); or
b) in case of Electronic Delivery, when SAP has made an electronic copy thereof available for downloading and has informed Distributor accordingly, (“Delivery”).
4. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant Open Ecosystem Partner instead (“Open Ecosystem Partner Delivery”). In case of Open Ecosystem Partner Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the Open Ecosystem Partner.
5. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant End User instead (“End User Delivery”). In case of End User Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the End User.
6. SAP might be entitled to suspend the delivery of the Software, Maintenance Services, applicable license key or both to Distributor, Open Ecosystem Partner or End User or both as further set out in this Sell On Premise Distribution Model as well as the Distribution GTCS.
7. If Distributor receives a new copy of the Software, Documentation and/or other SAP Materials that replaces previously provided Software, Documentation and/or other SAP Materials, Distributor must distribute that newest copy provided and either destroy or upon SAP’s request return previous copies.
8. Distributor must not make the Software, Documentation and/or other SAP Materials available to the Open Ecosystem Partner or End User by any means other than by delivering the Software, Documentation and/or other SAP Materials as originally provided by SAP. Distributor’s right to pass on the Software, Documentation and/or other SAP Materials is subject to the provisions of this Agreement.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Telephone Monitoring/Recording From time to time we may monitor and/or record telephone calls between you and us to assure the quality of our customer service or as required by applicable law.
SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.
11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses.
11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.
Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27
Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.
Electronic Visit Verification ("EVV A. To ensure:
1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor;
2. only authorized people access the Contractor's EVV account;
3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim;
4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and
5. service delivery documentation is immediately available for review by HHSC when requested.
B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above.
C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook.
D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable.
E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim.
F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied.
G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook.
H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter.
I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.
Access to Review Materials The Servicer will give the Asset Representations Reviewer access to the Review Materials for all of the Subject Receivables within sixty (60) calendar days after receipt of the review notice in one or more of the following ways in the Servicer’s reasonable discretion: (i) by electronic posting of Review Materials to a password-protected website to which the Asset Representations Reviewer has access, (ii) by providing originals or photocopies of documents relating to the Subject Receivables at one of the properties of the Servicer or (iii) in another manner agreed by the Servicer and the Asset Representations Reviewer. The Servicer may redact or remove PII from the Review Materials so long as all information in the Review Materials necessary for the Asset Representations Reviewer to complete the Asset Review remains intact and unchanged.
Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").
