RCS SYSTEM CAPACITY AND RCS SYSTEM LOAD Clause Samples

RCS SYSTEM CAPACITY AND RCS SYSTEM LOAD. The Program Manager/▇▇▇▇▇▇▇▇▇▇ County shall be charged with the collection of trunked system radio traffic data. Data collected each month shall be such so that a statistically valid sample is obtained. System loading data shall be collected and stored. The Program Manager/▇▇▇▇▇▇▇▇▇▇ County shall consult with the Advisory Board regarding the most appropriate method of presentation. One such method can be a “channel activity” graph that illustrates the number of transactions on each channel. Another such method can be a traffic profile chart that includes, among other items, the calls per hour, duration of call, and calls per unit per hour. Such data shall be used to determine the Grade of Service, which shall be metric used to determine system performance in regards to the system’s ability to adequately serve the users. If the collected data, plotted on a monthly basis, indicates a trend where the GOS exceeds one percent (1%) and the queue (wait for a channel grant) time exceeds one (1) second over a period of three (3) consecutive months, steps shall be taken to increase capacity once any potential anomalous occurrences or conditions have been examined and adequately explained. The Program Manager/▇▇▇▇▇▇▇▇▇▇ County shall ensure that the proper system management processes are in place to maximize the system’s capacity before trunked radio channel resources are added to the system. In the event the RCS System Capacity is increased to meet the needs of an out-of-county RCS Associate, such out-of-county RCS Associate shall be solely responsible for all initial and implementation costs, maintenance costs, operational costs, and recurring costs. Such costs shall not be included in the Annual Assessments apportioned to all RCS Parties and Associates.
View SourceView Similar (2)

Related to RCS SYSTEM CAPACITY AND RCS SYSTEM LOAD

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

  • 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

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the ISO OATT.

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

  • Contract Capacity The electric power producing capability of the Generating Facility which is committed to Edison.