Dispatch/Transfer Tracking Sample Clauses

Dispatch/Transfer Tracking. Xxxx shall maintain call logs that show each time a particular Public Safety Responder type is Dispatched as a result of a call or when a call is Transferred to the Secondary PSAP.
AutoNDA by SimpleDocs
Dispatch/Transfer Tracking. Cary shall maintain call logs that show each time a particular Public Safety Responder type is Dispatched as a result of a call or when a call is Transferred to the Secondary PSAP.

Related to Dispatch/Transfer Tracking

  • Dark Fiber Transport Dark Fiber Transport is defined as Dedicated Transport that consists of unactivated optical interoffice transmission facilities without attached signal regeneration, multiplexing, aggregation or other electronics. Except as set forth in Section 6.9.1 below, BellSouth shall not be required to provide access to Dark Fiber Transport Entrance Facilities pursuant to this Agreement.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Network Interconnection Methods 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct.

  • Interconnection Request The Interconnection Customer’s request, in accordance with the Tariff, to interconnect a new Small Generating Facility, or to materially increase the capacity of, or make a material modification to the operating characteristics of, an existing Small Generating Facility that is interconnected with the New York State Transmission System or the Distribution System. For the purposes of this Agreement, this definition of Interconnection Request shall supersede the definition of Interconnection Request set out in Attachment X to the ISO OATT. Interconnection Study – Any study required to be performed under Sections 32.2 or 32.3 of the SGIP. Material Modification – A modification that has a material impact on the cost or timing of any Interconnection Request with a later queue priority date. New York State Transmission System – The entire New York State electric transmission system, which includes: (i) the Transmission Facilities under ISO Operational Control; (ii) the Transmission Facilities Requiring ISO Notification; and (iii) all remaining transmission facilities within the New York Control Area. NYISO Deliverability Interconnection Standard – The standard that must be met, unless otherwise provided for by Attachment S to the ISO OATT, by (i) any generation facility larger than 2MW in order for that facility to obtain XXXX; (ii) any Class Year Transmission Project proposing to interconnect to the New York State Transmission System and receive Unforced Capacity Delivery Rights; (iii) any entity requesting External XXXX Rights, and (iv) any entity requesting a XXXX transfer pursuant to Section 25.9.5 of Attachment S to the ISO OATT. To meet the NYISO Deliverability Interconnection Standard, the Interconnection Customer must, in accordance with the rules in Attachment S to the ISO OATT, fund or commit to fund any System Deliverability Upgrades identified for its project in the Class Year Deliverability Study. NYISO Minimum Interconnection Standard – The reliability standard that must be met by any generation facility or Class Year Transmission Project that is subject to NYISO’s Large Facility Interconnection Procedures in Attachment X to the ISO OATT or the NYISO’s Small Generator Interconnection Procedures in this Attachment Z, that is proposing to connect to the New York State Transmission System or Distribution System, to obtain ERIS. The Minimum Interconnection Standard is designed to ensure reliable access by the proposed project to the New York State Transmission System or to the Distribution System. The Minimum Interconnection Standard does not impose any deliverability test or deliverability requirement on the proposed interconnection. Operating Requirements – Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards. Party or Parties – The NYISO, Connecting Transmission Owner, Interconnection Customer or any combination of the above. Point of Interconnection – The point where the Interconnection Facilities connect with the New York State Transmission System or the Distribution System. Reasonable Efforts – With respect to an action required to be attempted or taken by a Party under this Agreement, efforts that are timely and consistent with Good Utility Practice and are otherwise substantially equivalent to those a Party would use to protect its own interests. Small Generating Facility – The Interconnection Customer’s facility, no larger than 20 MW for the production and/or storage for later injection of electricity identified in the Interconnection Request if proposing to interconnect to the New York State Transmission System or Distribution System, but shall not include (i) facilities proposing to simply receive power from the New York State Transmission System or the Distribution System; (ii) facilities proposing to interconnect to the New York State Transmission System or the Distribution System made solely for the purpose of generation with no wholesale sale for resale nor to net metering; (iii) facilities proposing to the New York State Transmission System or the Distribution System made solely for the purpose of net metering; (iv) facilities proposing to interconnect to LIPA’s distribution facilities; and (v) the Interconnection Customer’s Interconnection Facilities. A facility will be treated as a single Small Generating Facility if all units within the facility are behind a single facility meter, even if such units are different technology types. System Deliverability Upgrades – The least costly configuration of commercially available components of electrical equipment that can be used, consistent with Good Utility Practice and Applicable Reliability Requirements, to make the modifications or additions to the existing New York State Transmission System that are required for the proposed project to connect reliably to the system in a manner that meets the NYISO Deliverability Interconnection Standard for Capacity Resource Interconnection Service. System Upgrade Facilities – The least costly configuration of commercially available components of electrical equipment that can be used, consistent with Good Utility Practice and Applicable Reliability Requirements to make the modifications to the existing transmission system that are required to maintain system reliability due to: (i) changes in the system, including such changes as load growth and changes in load pattern, to be addressed in the form of generic generation or transmission projects; and (ii) proposed interconnections. In the case of proposed interconnection projects, System Upgrade Facilities are the modification or additions to the existing New York State Transmission System that are required for the proposed project to connect reliably to the system in a manner that meets the NYISO Minimum Interconnection Standard. Tariff – The NYISO’s Open Access Transmission Tariff, as filed with the FERC, and as amended or supplemented from time to time, or any successor tariff. Trial Operation shall mean the period during which Interconnection Customer is engaged in on- site test operations and commissioning of the Small Generating Facility prior to Commercial Operation. Upgrades – The required additions and modifications to the Connecting Transmission Owner’s portion of the New York State Transmission System or the Distribution System at or beyond the Point of Interconnection. Upgrades may be System Upgrade Facilities or System Deliverability Upgrades Distribution Upgrades. Upgrades do not include Interconnection Facilities.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

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

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Ymax shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Ymax and Verizon. Ymax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx- Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and Xxxx shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’s performance in connection with these Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Ymax will route its traffic to Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the Verizon End Office.

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