Monitoring In Lieu of Routine Data Requests by the Fund Company Sample Clauses

Monitoring In Lieu of Routine Data Requests by the Fund Company. (a) As long as Intermediary is complying with the Frequent Trading Monitoring policies and procedures set out herein, the Fund agrees not to make routine requests for data from Intermediary. Intermediary will, however, provide reports and information to the Fund, in accordance with the terms of this Agreement as requested in writing for due diligence or audit purposes. (b) If the Fund identifies a Contractholder that has been subject to the Purchase Restriction Period more than once because of repeated Frequent Trading, the Fund may provide written direction to Intermediary to implement special restrictions on such Contractholder as the Fund deems necessary. Intermediary will use reasonable efforts to impose such restrictions to the extent they are administratively feasible. (c) Intermediary will provide the Fund with a quarterly report summarizing the total number of Contractholders who were restricted from purchasing during the previous calendar quarter.
AutoNDA by SimpleDocs
Monitoring In Lieu of Routine Data Requests by the Fund Company. (a) As long as Intermediary is complying with the Frequent Trading Monitoring policies and procedures set out herein, the Fund agrees not to make routine requests for data from Intermediary. Intermediary will, however, provide reports and information to the Fund, in accordance with the terms of this Agreement as reasonably requested in writing for due diligence or audit purposes. The Fund agrees that in the absence of extraordinary circumstances, such requests will not be made more frequently than quarterly. (b) If the Fund identifies a Participant that has been subject to the Purchase Restriction Period more than once because of repeated Frequent Trading, the Fund may provide written direction to Intermediary to implement special restrictions on such Participant as the Fund deems necessary. Such written direction will include a short explanation to be provided to the Plan and Participant regarding the special action. Intermediary will use reasonable efforts to impose such restrictions to the extent they are administratively feasible. (c) Intermediary will provide the Fund with a quarterly report summarizing the total number of Participants who were restricted from purchasing during the previous calendar quarter.

Related to Monitoring In Lieu of Routine Data Requests by the Fund Company

  • Mail Order Catalog Warnings In the event that, the Settling Entity prints new catalogs and sells units of the Products via mail order through such catalogs to California consumers or through its customers, the Settling Entity shall provide a warning for each unit of such Product both on the label in accordance with subsection 2.4 above, and in the catalog in a manner that clearly associates the warning with the specific Product being purchased. Any warning provided in a mail order catalog shall be in the same type size or larger than other consumer information conveyed for such Product within the catalog and shall be located on the same display page of the item. The catalog warning may use the Short-Form Warning content described in subsection 2.3(b) if the language provided on the Product label also uses the Short-Form Warning.

  • 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

  • Grievance Processing Union stewards or Union officials shall be permitted to have time off without loss of pay for the investigation and processing of grievances and arbitrations. Requests for such time off shall be made in advance and shall not be unreasonably denied. The Union will furnish the Employer with a list of Union stewards and their jurisdictions. The Union shall delineate the jurisdiction of Union stewards so that no xxxxxxx need travel between work locations or sub-divisions thereof while investigating grievances. Grievants shall be permitted to have time off without loss of pay for processing their grievances through the contractual grievance procedure, except that for class action grievances no more than three (3) grievants shall be granted such leave.

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

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

  • Processing of a Grievance It is recognized and accepted by the Union and the Employer that the processing of grievances as hereinafter provided is limited by the job duties and responsibilities of the employees and shall therefore be accomplished during normal working hours only when consistent with such employee duties and responsibilities. The aggrieved employee and a Union representative shall be allowed a reasonable amount of time without loss of pay when a grievance is investigated and presented to the Employer during normal working hours provided that the employee and the Union representative have notified and received the approval of the designated supervisor who has determined that such absence is reasonable and would not be detrimental to the work programs of the Employer.

  • Log Reviews All systems processing and/or storing PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must have a routine procedure in place to review system logs for unauthorized access.

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

  • Qualified Medical Child Support Order A child who would otherwise meet the eligibility requirements and is required to be covered by a Qualified Medical Child Support Order (QMCSO) is considered an eligible dependent.

  • Procedures for LNP Request The Parties shall provide for the requesting of End Office LNP capability on a reciprocal basis through a written request. The Parties acknowledge that Verizon has deployed LNP throughout its network in compliance with FCC 96-286 and other applicable FCC Regulations. 15.4.1 If Party B desires to have LNP capability deployed in an End Office of Party A, which is not currently capable, Party B shall issue a LNP request to Party A. Party A will respond to the Party B, within ten (10) days of receipt of the request, with a date for which LNP will be available in the requested End Office. Party A shall proceed to provide for LNP in compliance with the procedures and timelines set forth in FCC 00-000, Xxxxxxxxx 80, and FCC 97-74, Paragraphs 65 through 67. 15.4.2 The Parties acknowledge that each can determine the LNP-capable End Offices of the other through the Local Exchange Routing Guide (LERG). In addition, the Parties shall make information available upon request showing their respective LNP-capable End Offices, as set forth in this Section 15.4.

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