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 ▇▇▇▇▇'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 ▇▇▇▇▇'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.
View SourceView Similar (2)

Related to SYSTEM BENCHMARKING

  • Benchmarking 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:

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