Documentation Requirements ODM shall pay the MCP after it receives sufficient documentation, as determined by ODM, detailing the MCP’s Ohio Medicaid-specific liability for the Annual Fee. The MCP shall provide documentation that includes the following:
1. Total premiums reported on IRS Form 8963;
Subsidy Requests and Reporting Requirements 1. The Grantee or Management Company shall complete a CRF Subsidy Request Report - Recap of Tenant Income Certification, which provides a unit-by-unit listing of all units in the Development for whom assistance is being requested and gives detailed information including the occupants’ eligibility, set-aside requirements, amount of household rent paid, utility allowance and amount of CRF Rental Subsidy requested.
2. The CRF Subsidy Request Report - Recap of Tenant Income Certification shall be prepared as of the last day of each calendar month during the period of performance and shall be submitted to XXXXxxxxxxxx@XxxxxxxXxxxxxx.xxx and Florida Housing’s monitoring agent no later than the 15th day of the following month. The December 2020 request will be due on or before December 15th. The Grantee will submit executed Coronavirus Relief Fund Rental Assistance Applications and supporting documentation to Florida Housing’s monitoring agent within 5 days upon the monitoring agent’s request.
SMALL BUSINESS PARTICIPATION AND DVBE PARTICIPATION REPORTING REQUIREMENTS a. If for this Contract Contractor made a commitment to achieve small business participation, then Contractor must within 60 days of receiving final payment under this Contract (or within such other time period as may be specified elsewhere in this Contract) report to the awarding department the actual percentage of small business participation that was achieved. (Govt. Code § 14841.)
b. If for this Contract Contractor made a commitment to achieve disabled veteran business enterprise (DVBE) participation, then Contractor must within 60 days of receiving final payment under this Contract (or within such other time period as may be specified elsewhere in this Contract) certify in a report to the awarding department: (1) the total amount the prime Contractor received under the Contract; (2) the name and address of the DVBE(s) that participated in the performance of the Contract; (3) the amount each DVBE received from the prime Contractor; (4) that all payments under the Contract have been made to the DVBE; and (5) the actual percentage of DVBE participation that was achieved. A person or entity that knowingly provides false information shall be subject to a civil penalty for each violation. (Mil. & Vets. Code § 999.5(d); Govt. Code § 14841.)
DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:
(1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute;
(2) Limit unsuccessful logon attempts;
(3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions;
(4) Authorize wireless access prior to allowing such connections;
(5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity;
(6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions;
(7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles;
(8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services;
(9) Enforce a minimum password complexity and change of characters when new passwords are created;
(10) Perform maintenance on organizational systems;
(11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance;
(12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1;
(13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital;
(14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse;
(15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas;
(16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems;
(17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems;
(18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception);
(19) Protect the confidentiality of Student Data at rest;
(20) Identify, report, and correct system flaws in a timely manner;
(21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems;
(22) Monitor system security alerts and advisories and take action in response; and
(23) Update malicious code protection mechanisms when new releases are available.
Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.
Other Required Documentation All other documents and legal matters in connection with the transactions contemplated by this Amendment shall have been delivered or executed or recorded and shall be in form and substance satisfactory to Agent.
Performance of Services in Accordance with Regulatory Requirements; Furnishing of Books and Records In performing the services set forth in this Agreement, the Manager:
A. shall conform with the 1940 Act and all rules and regulations thereunder, with all other applicable federal, state and foreign laws and regulations, with any applicable procedures adopted by the Trust’s Board of Trustees, and with the provisions of the Trust’s Registration Statement filed on Form N-1A as supplemented or amended from time to time;
B. will make available to the Trust, promptly upon request, any of the Fund’s books and records as are maintained under this Agreement, and will furnish to regulatory authorities having the requisite authority any such books and records and any information or reports in connection with the Manager’s services under this Agreement that may be requested in order to ascertain whether the operations of the Trust are being conducted in a manner consistent with applicable laws and regulations.
Entitlements and Purchasing Requirements You must purchase the appropriate number of Software Subscription(s), based on the number of Socket-pairs for all Managed Nodes being managed by the Red Hat CloudForms Software. A “Socket-pair” is up to two sockets each occupied by a CPU on a Managed Node. Red Hat CloudForms Software is configured to manage virtual machines on certain public clouds (a “Red Hat CloudForms Enabled Cloud”). You must purchase the appropriate number of Red Hat CloudForms for Public Cloud Software Subscriptions based on the number of Managed VMs instantiated on a Red Hat CloudForms Enabled Cloud. Please confirm that a specific public cloud is a Red Hat CloudForms Enabled Cloud prior to purchasing. A Red Hat Enterprise Linux Software Subscription is bundled with the Red Hat CloudForms Software Subscription and the fees for the Red Hat CloudForms Subscription are based on such bundled use. Any use of the Red Hat Enterprise Linux other than to run the Red Hat CloudForms Software is subject to Red Hat’s standard Software Subscription fees for such use.
