Reporting and Monitoring Requirements a. The Subrecipient will comply with HUD’s standards for participation in a local Homeless Management Information System (“HMIS”) and the collection and reporting of client-level information. If Subrecipient is a Domestic Violence provider, Subrecipient must participate in a comparable database in terms of functionality, data collection and reporting capacity that can meet all reporting requirements that the local HMIS system is able to meet.
Reporting and Monitoring Requirements. (a) Within 28 days of each and every anniversary of the commencement of the term the Licensee shall provide to Council, a statutory declaration from an authorised officer of the Licensee, stating the hours and days during which activities were undertaken at the premises during the year then just completed, together with the proposed or intended hours and days for the then current year.
Reporting and Monitoring Requirements. 8.1. The Recipient shall provide ASHC with the following reporting and monitoring information with respect to the Project:
Reporting and Monitoring Requirements. Provide an administrative interface, accessible via a conformant API and via a dashboard, and accessible at a central location with the following functionality: • Restrict access to admin interface to only authorized persons • Stats and dashboards to understand how CCT’s APIs are being accessed and used: o Operational - The number of API calls, CPU, memory usage, response times, uptime etc o Business metrics – number of partners using API • Must have tools for monitoring resource utilization, system health, error logs, latency and the ability to start and stop processes • Must have the ability to configure alerts Functional Requirement Category Functional Requirement Full lifecycle API management • Management of the lifespan of an API from the planning stage to when an API is retired. This can include building, testing, publishing and ensuring the necessary security is in place and then monitoring the API thereafter. • The ability to publish multiple versions of an API through the API Gateway is required. • Transparent declaration of API specifications as code • Ability to import and export API specifications in a common, open serialization format such as JSON or Yaml Historical Data • Must have in place storage requirements to accommodate dynamic data growth of data generated by the API Gateway (e.g logs, configuration changes) • Said data should be made available to CCT on request at no additional cost On termination or completion of contract all Data will be returned to the CCT with no additional costs • Adherence to POPI act applies Legal or Regulatory Requirements • Must consider and adhere to laws, regulations from the government, and even internal policies that the organization and their systems must follow. • The following Acts apply o Electronic Communications and Transaction Act, Act No. 25 of 2002 (ECTA) o Minimum information Security Standards, 1996 (MISS) o Protection of Personal Information Act, Act No. 2013 (POPIA) o Protection of Information act, Act No. 84 of 1982 o Public Administration Management Act, Act No. 11 of 2014 o National Archives of South Africa Act, Act No. 43 of 1996 o Spatial Data Infrastructure Act, Act No. 54 of 2003 o Promotion of Access to Information Act, Act No. 2 of 2000 (PAIA) o South African Cybersecurity Framework, 2012 o National Integrated ICT Policy White Paper, 2016 o The General Data Protection Regulation 2016/679 Functional Requirement Category Functional Requirement Incident Management • Must be able to: o T...
Reporting and Monitoring Requirements. (clauses 1.1 and 12(c))
Reporting and Monitoring Requirements. A) Borrower shall submit financial and operational reports to Lender as Lender may reasonably request in addition to the following reporting requirements:
Reporting and Monitoring Requirements
