SYSTEM BENCHMARKING Sample Clauses

SYSTEM BENCHMARKING. Operational Measurements will be set-up and monitored by a member of the Seller's design team at least one week prior to initial drive testing. This will allow the RF Engineering team to evaluate the existing system performance metrics and establish a baseline prior to initiating any design efforts. The specific OM groups (as applicable) to be monitored will be at the sole discretion of Seller. In order to properly benchmark the system, a team of Seller's engineers with the assistance of Xxxxx's engineers will drive test coverage areas prior to the installation of the switch. This survey will take note of special physical elements that could affect the design such as unsuitable soil conditions, arenas or other large public buildings where traffic could be concentrated, and density of buildings and surrounding geographical situations for more precise application of the clutter models. Seller's and Xxxxx's engineers will jointly determine the drive route in these areas. Data will be collected to establish the current operating performance condition of the network in the covered area prior to commencement of design work. Data from this survey will be used to make corrections to the standard models used in the design analysis work.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to SYSTEM BENCHMARKING

  • Benchmarking 19.1 The Parties shall comply with the provisions of Framework Schedule 12 (Continuous Improvement and Benchmarking) in relation to the benchmarking of any or all of the Goods and/or Services.

  • 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.

  • Benchmarks 2.1 Benchmarks set forth the overall scope and level of responsibility and the typical duties by which jobs or positions are distinguished and classified under the Classification System. 2.2 Benchmarks also set forth the range or level of qualifications appropriate for a position classified to the level of the benchmark(s). 2.3 Benchmarks do not describe jobs or positions. They are used to classify a wide diversity of jobs by identifying the scope and level of responsibilities.

  • GSA Benchmarked Pricing Additionally, where the NYS Net Price is based upon an approved GSA Supply Schedule:

  • System for Award Management (XXX) Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a XXX.xxx proof of registration and Commercial and Government Entity (CAGE) number. Grantee will continue to maintain an active XXX registration with current information at all times during which it has an active award under this Agreement.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition. 13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!