Designated Homeless Management Information System Lead Sample Clauses

Designated Homeless Management Information System Lead. 1. Given that Subrecipient is the CoC designated Homeless Management Information System (HMIS) lead, receives HUD grant/s and in compliance with HEARTH Act and CoC guidance, Subrecipient will: • Accept HUD HMIS Lead Grants for the implementation of all required HMIS systems per HUD requirements, and direction from the CoC Board and County Staff. • Fund develop for additional funding to support continued HMIS functions and HUD match requirements. • Submit to HUD all reports in the HUD Data Exchange (HDX) as required, including but not limited to the Housing Inventory Count (HIC), Annual Homeless Assessment Report (AHAR), System Performance Report and Point-In-Time (PIT), in coordination with the CoC Collaborative Applicant. Due dates to be coordinated with County staff to allow for timely presentation to the CoC Board. • Produce analysis and annual reports that communicate service usage, performance and client profiles as part of HMIS Lead Responsibilities, including Dashboard Reports.Reports will be presented to the CoC Board and shared with the public. • Under the direction of the CoC Board and County/County, assist in the development and implemention of a Regional Service Planning Area (SPA) approach for CES and HMIS that allows for a regionally responsive street outreach, engagement, assessment and housing placement protocols. • Modify, change or improve HMIS operating system/software as directed by the CoC Board to meet local objectives and support local homeless initiatives such as creating dashboard reports in accordance with additional funding from the County, while adhering to HUD standards and requirements. • Subrecipient will provide reports on Whole Person Care Grant contract participation. • All HMIS Policies and Procedures and related documents be updated this upcoming contract year with new system documents. • Submit an annual HMIS Annual Performance Report (APR) to the CoC Board prior to submission to HUD. • Obtain prior approval from the CoC Board for any HMIS fees charged to CoC agencies and HMIS participants. • Other responsibilities as identified for HMIS lead agency per HUD and under their contract. • Provide at least three Administrator User Licences to the County to access HMIS. • Release of aggregate data for the purpose of system administration, technical support, program compliance and analytical use is at the discretion of the CoC Board.Subrecipient will present to the CoC Board a sample list of typical data requests for pre-appro...
Sample 1See All (4)
AutoNDA by SimpleDocs
Designated Homeless Management Information System Lead. 1. Given that Contractor is the CoC designated HMIS lead, receives HUD grant(s) and in compliance with HEARTH Act and CoC guidance, Contractor shall:
Sample 1Sample 2

Related to Designated Homeless Management Information System Lead

  • Management Information System The M&E Plan will describe the information system that will be used to collect data, store, process and deliver information to relevant stakeholders in such a way that the Program information collected and verified pursuant to the M&E Plan is at all times accessible and useful to those who wish to use it. The system development will take into consideration the requirement and data needs of the components of the Program, and will be aligned with existing MCC systems, other service providers, and ministries.

  • Management Information Systems A. The CONTRACTOR shall maintain a process that collects, analyzes, integrates, and reports data. (42 C.F.R. § 438.242(a); Cal. Code Regs., tit. 9, § 1810.376.) This process shall provide information on areas including, but not limited to, utilization, claims, grievances, and appeals. (42 C.F.R. § 438.242(a).)

  • DEFECTIVE MANAGEMENT INFORMATION 5.1 The Supplier acknowledges that it is essential that the Authority receives timely and accurate Management Information pursuant to this Framework Agreement because Management Information is used by the Authority to inform strategic decision making and allows it to calculate the Management Charge.

  • Management Information To be Supplied to CCS no later than the 7th of each month without fail. Report are to be submitted via MISO CCS Review 100% Failure to submit will fall in line with FA KPI CONTRACT CHARGES FROM THE FOLLOWING, PLEASE SELECT AND OUTLINE YOUR CHARGING MECHANISM FOR THIS SOW. WHERE A CHARGING MECHANISM IS NOT REQUIRED, PLEASE REMOVE TEXT AND REPLACE WITH “UNUSED”.

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Monitoring and Management Information C10.1 The Contractor shall comply with the monitoring arrangements set out in the Monitoring Schedule including, but not limited to, providing such data and information as the Contractor may be required to produce under the Contract.

  • Access Management The Engineer shall coordinate and evaluate access management within the project limits in accordance with the latest State Access Management Manual or as directed by the State.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Information Systems The Official Agency in conjunction with the Authority will meet the relevant requirements of Articles 131 to 136 of Regulation (EU) 2017/625 and Implementing Regulation (EU) 2019/1715 as appropriate to the Official Agency. The Official Agency shall record appropriate data in the Official Agency Premises Inspection database (OAPI), which will be further developed over the life of the contract. Data should be entered into the database on an ongoing basis but shall be entered within one month of the activity taking place, unless otherwise agreed with the Authority.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

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