Monitoring and Evaluation a. The AGENCY shall expeditiously provide to the COUNTY upon request, all data needed for the purpose of monitoring, evaluating and/or auditing the program(s). This data shall include, but not be limited to, clients served, services provided, outcomes achieved, information on materials and services delivered, and any other data required, in the sole discretion of the COUNTY, that may be required to adequately monitor and evaluate the services provided under this Contract. Monitoring shall be performed in accordance with COUNTY’S established Noncompliance Standards, a copy of which is attached hereto and incorporated by reference as Attachment “C”.
Screening 3.13.1 Refuse containers located outside the building shall be fully screened from adjacent properties and from streets by means of opaque fencing or masonry walls with suitable landscaping.
Program Monitoring and Evaluation (c) The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”
Vulnerability Management BNY Mellon will maintain a documented process to identify and remediate security vulnerabilities affecting its systems used to provide the services. BNY Mellon will classify security vulnerabilities using industry recognized standards and conduct continuous monitoring and testing of its networks, hardware and software including regular penetration testing and ethical hack assessments. BNY Mellon will remediate identified security vulnerabilities in accordance with its process.
Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.
SAFEGUARDING CHILDREN AND VULNERABLE ADULTS 8.1 The Service Provider will have ultimate responsibility for the management and control of any Regulated Activity provided under this agreement and for the purposes of the Safeguarding Vulnerable Groups Xxx 0000.
Scaling “Scaling,” as used herein, involves:
REPORTING AND EVALUATION The Provider agrees to comply with 7 AAC 81.120, Confidentiality and 7 AAC 81.150, Reports, and other applicable state or federal law regarding the submission of information, including the provisions of Section VI of this Agreement. The Provider agrees to submit any reporting information required under this Agreement and to make available information deemed necessary by DHSS to evaluate the efficacy of service delivery or compliance with applicable state or federal statutes or regulations. The Provider agrees to provide state officials and their representatives access to facilities, systems, books and records, for the purpose of monitoring compliance with this Agreement and evaluating services provided under this Agreement. On-site Quality Assurance Reviews may be conducted by DHSS staff to ensure compliance with service protocols. The Provider will ensure that DHSS staff has access to program files for the purposes of follow-up, quality assurance monitoring and fiscal administration of the program.
Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards.
Scoring The number of routes each company operates (Route # 0001-2999, 8000-8199) will be multiplied by 2 to determine the daily number of trips. (Only accidents, breakdowns and service reports related to routes falling in this range will be used for the evaluation). The daily number of trips will be multiplied by 175 to arrive at the annual number of trips. The number of accidents, breakdowns and service complaints will be divided by the total number of trips to calculate a percent figure. Each company’s percentage will be compared to the total average. See below for a sample. BUS COMPANY NUMBER OF TOTAL BKDN PERCENT ACCIDENTS PERCENT2 SERVICE PERCENT3 ROUTES TRIPS BKDN ACCIDENTS REPORTS COMPLAINTS TO TRIPS TO TRIPS TO TRIPS A 360 58680 3 0.01% 27 0.05% 46 0.08% B 48 7824 3 0.04% 4 0.05% 39 0.50% C 123 20049 11 0.05% 9 0.04% 27 0.13% D 91 14833 0.00% 10 0.07% 11 0.07% E 124 20212 20 0.10% 19 0.09% 18 0.09% TOTALS 746 121598 37 0.03% 69 0.06% 141 0.12% To score, if a company’s percentage is less than or equal to the total percentage for that category, the company will be awarded 6 points per category. Percentages greater than the total percentage for each distinct category (Accident, Breakdown, Service Complaints) will be scored according to the following scale: Vendor Category Percent Points Less than-Equal to Ave. 6 points 0-3% above average 5 points 4-7% above average 4 points 5-8% above average 3 points 9-12% above average 2 points 13-16% 1 points Greater than 17% 0 points Example: Company A had a lower percent of breakdowns than the average total, and would receive 6 points for breakdowns. If a company has a higher percentage than the average total, 0 point will be added to their score. Company B would not receive 6 points for breakdowns. The same calculation would be performed for accidents and service complaints. Any circumstance whereby a Breakdown or Accident is found by PTS to be ‘Non Reported’ by vendor within the required timeframe (see G-36) will count as (20) ‘Reported’ instances for the purpose of this Contractor Evaluation Scoring.
