Caching The Participating Institutions and the Authorized Users are authorized in the course of an automatic process of an internet browser or any other software to make temporary local digital copies of the Licensed Materials in order to ensure proper operation and use of such internet browser or for proper functioning of such software. For the avoidance of doubt, the cached copy is not a derivative work.
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.
Filtering Company may employ various filtering methods to reduce unwanted content, such as SPAM e-mail, from reaching Your Company Account. You acknowledge and agree that such methods may prevent legitimate content from reaching Your Account and that Company will not be liable therefor.
Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity
Supply Chain Monitoring A copy of the supply chain monitoring process, which should include details of the process for monitoring the financial viability of the supply chain (including timing), together with any known risks to supply chain stability and material changes to the supply chain. This should include extracts from Board level meetings, risk registers etc where any of the above items have been discussed. Annex 1 1 Information from Contractors who are not required to submit form AR01 to Companies House
Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.
Service Monitoring Customer gives express consent for Vodafone to monitor Customer’s use of the Service (and disclose and otherwise use the information obtained) only to: (a) the extent allowed by Applicable Law; (b) comply with Applicable Law; (c) protect the Network from misuse; (d) protect the integrity of the public internet and/or Vodafone’s systems and Networks; (e) the extent necessary to determine if Customer has breached any conditions or restrictions on use of the Service; (f) provide the Service; and/or (g) take other actions agreed or requested by Customer.
SITE MANAGEMENT We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.
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.