Creation of Regulatory Compliance Unit Sample Clauses

Creation of Regulatory Compliance Unit. No later than the Implementation Date, the Parent Company shall form a new Regulatory Compliance Unit of officers or employees of the Parent Company or its subsidiaries who shall not be members of the Claim Reassessment Unit discussed below. The Regulatory Compliance Unit shall report directly to the Regulatory Compliance Committee (or to the Board of Directors until such Committee is appointed) with respect to all market­conduct matters and ERISA requirements. The responsibilities of the Regulatory Compliance Unit shall include (i) monitoring compliance with applicable laws concerning market conduct and ERISA requirements, (ii) monitoring compliance with the Plan (including the functions of the Claim Reassessment Unit) through the performance of periodic audits, (iii) providing assistance to claimants upon request that will ease and facilitate the claim submission process, and (iv) gathering data to facilitate the Lead Regulators’ and the DOL’s ongoing monitoring of the Companies’ compliance with the Plan. The Regulatory Compliance Unit shall be managed by an officer who is an experienced insurance professional, whose experience includes compliance related matters. Employees of the Parent Company and all of its subsidiaries shall be provided with a toll free hotline number to confidentially report concerns respecting claim handling, such reports to be provided to the manager of the Regulatory Compliance Unit. Claimants shall be provided with a toll free hotline number for assistance throughout the claim handling process, the performance of which will be monitored by the Regulatory Compliance Unit. A log of all telephone calls to both hotline numbers shall be maintained, and quarterly reports concerning such logs shall be provided to the Regulatory Compliance Committee.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs

Related to Creation of Regulatory Compliance Unit

  • Regulatory Compliance a. Monitor compliance with the 1940 Act requirements, including:

  • Financial Viability and Regulatory Compliance 4.6.1 The Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. The Contractor further warrants and represents that it owes no outstanding delinquent federal, state, or local taxes or business assessments.

  • Statutory Compliance ‌ The Union and the Employer agree to cooperate fully in matters pertaining to the prevention of accidents and occupational disease and in the promotion of the health and safety of all employees. There shall be full compliance with all applicable statutes and regulations pertaining to the working environment.

  • Statutory and Regulatory Compliance Contractor shall comply with all laws and regulations applicable to the Community Development Block Grant-Disaster Recovery funds appropriated by the Disaster Relief Appropriations Act, 2013 (Pub. L. 113-2), including but not limited to the applicable Office of Management and Budget Circulars, which may impact the administration of funds and/or set forth certain cost principles, including the allowability of certain expenses.

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

  • Certification of Compliance The Owner may permit the use, prior to sampling and testing, of certain materials or assemblies when accompanied by manufacturer's certificates of compliance stating that such materials or assemblies fully comply with the requirements of the contract. The certificate shall be signed by the manufacturer. Each lot of such materials or assemblies delivered to the work must be accompanied by a certificate of compliance in which the lot is clearly identified. Materials or assemblies used on the basis of certificates of compliance may be sampled and tested at any time and if found not to be in conformity with contract requirements will be subject to rejection whether in place or not. The form and distribution of certificates of compliance shall be as approved by the Owner. When a material or assembly is specified by "brand name or equal" and the Contractor elects to furnish the specified "brand name", the Contractor shall be required to furnish the manufacturer's certificate of compliance for each lot of such material or assembly delivered to the work. Such certificate of compliance shall clearly identify each lot delivered and shall certify as to:

  • Declaration of Compliance Within 90 days of the HSP’s fiscal year-end, the Board will issue a Compliance Declaration declaring that the HSP has complied with the terms of this Agreement. The form of the declaration is set out in Schedule G and may be amended by the LHIN from time to time through the term of this Agreement.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

Time is Money Join Law Insider Premium to draft better contracts faster.