Browse Repository Sample Clauses

Browse Repository 
Sample 1
AutoNDA by SimpleDocs

Related to Browse Repository

  • Monitoring and Risk Assessment of Securities Depositories Prior to the placement of any assets of the Fund with a non-U.S. Securities Depository, the Custodian: (a) shall provide to the Fund or its authorized representative an assessment of the custody risks associated with maintaining assets within such Securities Depository; and (b) shall have established a system to monitor the custody risks associated with maintaining assets with such Securities Depository on a continuing basis and to promptly notify the Fund or its Investment Adviser of any material changes in such risk. In performing its duties under this subsection, the Custodian shall use reasonable care and may rely on such reasonable sources of information as may be available including but not limited to: (i) published ratings; (ii) information supplied by a Subcustodian that is a participant in such Securities Depository; (iii) industry surveys or publications; (iv) information supplied by the depository itself, by its auditors (internal or external) or by the relevant Foreign Financial Regulatory Authority. It is acknowledged that information procured through some or all of these sources may not be independently verifiable by the Custodian and that direct access to Securities Depositories is limited under most circumstances. Accordingly, the Custodian shall not be responsible for errors or omissions in its duties hereunder provided that it has performed its monitoring and assessment duties with reasonable care. The risk assessment shall be provided to the Fund or its Investment Advisor by such means as the Custodian shall reasonably establish. Advices of material change in such assessment may be provided by the Custodian in the manner established as customary between the Fund and the Custodian for transmission of material market information.

  • Compliance Support Services Provide compliance policies and procedures related to services provided by BNY Mellon and, if mutually agreed, certain of the BNY Mellon Affiliates; summary procedures thereof; and periodic certification letters. · Such Compliance Support Services are administrative in nature and do not constitute, nor shall they be construed as constituting, legal advice or the provision of legal services for or on behalf of a Fund or any other person, and such services are subject to review and approval by the applicable Fund and by the Fund’s legal counsel. · Provide access to Fund records so as to permit the Fund or TRP to test the performance of BNY Mellon in providing the services under this Agreement. · Such Compliance Support Services performed by BNY Mellon under this Agreement shall be at the request and direction of the Fund and/or its chief compliance officer (the “Fund’s CCO”), as applicable. BNY Mellon disclaims liability to the Fund, and the Fund is solely responsible, for the selection, qualifications and performance of the Fund’s CCO and the adequacy and effectiveness of the Fund’s compliance program.

  • Money Market Fund Compliance Testing and Reporting Services Subject to the authorization and direction of the Trust and, in each case where appropriate, the review and comment by the Trust’s independent accountants and legal counsel, and in accordance with procedures that may be established from time to time between the Trust and the Administrator, the Administrator will:

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • 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).

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Monthly MWBE Contractor Compliance Report A. In accordance with 5 NYCRR § 142.10, Contractor is required to report Monthly MWBE Contractor Compliance to OGS during the term of the Contract for the preceding month’s activity, documenting progress made towards achievement of the Contract MWBE goals. OGS requests that all Contractors use the New York State Contract System (“NYSCS”) to report subcontractor and supplier payments made by Contractor to MWBEs performing work under the Contract. The NYSCS may be accessed at xxxxx://xx.xxxxxxxxxxxxxx.xxx/. This is a New York State- based system that all State agencies and authorities will be implementing to ensure uniform contract compliance reporting throughout New York State. B. When a Contractor receives a payment from a State agency, it is the Contractor’s responsibility to pay its subcontractors and suppliers in a timely manner. On or after the first day of each month, the Contractor will receive an email or fax notification (“audit notice”) indicating that a representative of its company needs to log-in to the NYSCS to report the company’s MWBE subcontractor and supplier payments for the preceding month. The Contractor must also report when no payments have been made to a subcontractor or supplier in a particular month with entry of a zero dollar value in the NYSCS. Once subcontractor and supplier payments have been entered into the NYSCS, the subcontractor(s) and supplier(s) will receive an email or fax notification advising them to log into the NYSCS to confirm that they actually received the reported payments from the Contractor. It is the Contractor’s responsibility to educate its MWBE subcontractors and suppliers about the NYSCS and the need to confirm payments made to them in the NYSCS. C. To assist in the use of the NYSCS, OGS recommends that all Contractors and MWBE subcontractors and suppliers sign up for the following two webinar trainings offered through the NYSCS: “Introduction to the System – Vendor training” and “Contract Compliance Reporting - Vendor Training” to become familiar with the NYSCS. To view the training schedule and to register visit: xxxxx://xx.xxxxxxxxxxxxxx.xxx/events.asp D. As soon as possible after the Contract is approved, Contractor should visit xxxxx://xx.xxxxxxxxxxxxxx.xxx and click on “Account Lookup” to identify the Contractor’s account by company name. Contact information should be reviewed and updated if necessary by choosing “Change Info.” It is important that the staff member who is responsible for reporting payment information for the Contractor be listed as a user in the NYSCS. Users who are not already listed may be added through “Request New User.” When identifying the person responsible, please add “- MWBE Contact” after his or her last name (i.e., Xxxx Xxx – MWBE Contact) to ensure that the correct person receives audit notices from the NYSCS. NYSCS Technical Support should be contacted for any technical support questions by clicking on the links for “Contact Us & Support” then “Technical Support” on the NYSCS website. E. If Contractor is unable to report MWBE Contractor Compliance via the NYSCS, Contractor must submit a Monthly MWBE Contractor Compliance Report on Form MWBE 102 to OGS, by the 10th day of each month during the term of the Contract, for the preceding month’s activity to: OGS MWBE Office, 00xx Xxxxx Xxxxxxx Xxxxx, Xxxxxx Xxxxx Xxxxx, Xxxxxx, XX 00000. Phone: 000-000-0000; Fax: 000-000-0000. F. It is the Contractor’s responsibility to report subcontractor and supplier payments. Failure to respond to payment audits in a timely fashion through the NYSCS, or by paper to OGS, may jeopardize future payments pursuant to the MWBE liquidated damages provisions in clause IX below.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

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