WatchPAT ONE Scoring. The scoring method will be produced in accordance with the device operating manual.
WatchPAT ONE Scoring Sample Clauses
Related to WatchPAT ONE Scoring
Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.
Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.
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.
Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS
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.
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.
Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.
Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
