Trouble Reporting Sample Clauses
Trouble Reporting. In order to facilitate trouble reporting and to coordinate the repair of interconnection facilities, trunks, and other manners of interconnection provided by the Parties under this Agreement, each Party has established a single point of contact available 24 hours per day, seven days per week, at telephone numbers to be provided by the Parties. Each Party shall call the other at these respective telephone numbers to report trouble with connection facilities, trunks, and other manners of interconnection, to inquire as to the status of trouble ticket numbers in progress, and to escalate trouble resolution. Before either Party reports a trouble condition, it must first use its reasonable efforts to isolate the trouble to the other Party's facilities, service, and connection. Each Party will advise the other of any critical nature of the inoperative facilities, service, and connection and any need for expedited clearance of trouble. In cases where a Party has indicated the essential or critical need for restoration of the facilities, services or connections, the other Party shall use reasonable efforts to expedite the clearance of trouble.
Trouble Reporting. 15.10.1 In order to facilitate trouble reporting and to coordinate the repair of Interconnection Facilities, trunks, and other interconnection arrangements provided by the Parties under this Agreement, each Party has established contact(s) available 24 hours per day, seven days per week, at telephone numbers to be provided by the Parties. Each Party shall call the other at these respective telephone numbers to report trouble with connection facilities, trunks, and other interconnection arrangements, to inquire as to the status of trouble ticket numbers in progress, and to escalate trouble resolution.
15.10.2 Before either Party reports a trouble condition, it must first use its reasonable efforts to isolate the trouble to the other Party’s facilities, services and arrangement. Each Party will advise the other of any critical nature of the inoperative facilities, service, and arrangements and any need for expedited clearance of trouble. In cases where a Party has indicated the essential or critical need for restoration of the facilities, services or arrangements, the other Party shall use its best efforts to expedite the clearance of trouble.
Trouble Reporting. Subscribers of each Party shall be instructed to report all cases of trouble to that Party. Each Party shall handle trouble reporting and advise the other Party , after thorough investigation, in accordance with the procedures established in Attachment III. Each Party shall be provided with a telephone number to which it can call twenty-four (24) hours a day, seven (7) days a week in order to report and receive resolution of trouble reports.
Trouble Reporting. 12.3.14.1 CLEC may submit trouble reports through the Electronic Bonding or GUI interfaces provided by CenturyLink. Trouble tickets created electronically in CEMR may be viewed at any time after creation.
Trouble Reporting. 15.1 In order to facilitate trouble reporting and to coordinate the repair of Interconnection Facilities, trunks, and other interconnection arrangements provided by the Parties under this Agreement, each Party has established contact(s) available 24 hours per day, seven days per week, at telephone numbers to be provided by the Parties. Each Party shall call the other at these respective telephone numbers to report trouble with connection facilities, trunks, and other interconnection arrangements, to inquire as to the status of trouble ticket numbers in progress, and to escalate trouble resolution.
Trouble Reporting. The Parties will cooperatively plan and implement coordinated repair procedures for the CMRS Interconnection Trunks and Facilities to ensure trouble reports are resolved in a timely and appropriate manner.
Trouble Reporting. When reporting a fault to the Genuity GNOC, Xxxx Atlantic shall supply as much diagnostic information as it reasonably has available. Genuity will initiate fault reporting directly when it is reasonably able to do so. Genuity shall utilize industry-standard fault detection tools. When a fault is detected, such fault will be logged by Genuity GNOC staff. Genuity shall also utilize industry standard fault management tools, and will notify Xxxx Atlantic from time to time of any modification to the tools it is deploying. The Genuity GNOC shall be responsible for resolving the fault, and shall maintain auditable records of all such resolutions. At all stages during the fault resolution process, the Genuity GNOC shall remain the single point of contact for Xxxx Atlantic. The Genuity GNOC will provide regular status updates, according to accepted industry standards, as a reported fault progresses toward resolution. Genuity shall categorize all faults in accordance with the severity levels indicated in the Severity Level Matrix below. Upon identifying a fault or a non-conforming condition, the Genuity GNOC will categorize the incident according to its agreed severity in accordance with the Severity Level Matrix. Where appropriate, Xxxx Atlantic will consult with the Genuity GNOC as to the potential business impact and may verbally or electronically require a modification to the severity level accordingly. Fault tickets shall only be closed by Genuity when Xxxx Atlantic has confirmed trouble resolution. Fault summaries and Fault status will be provided to Xxxx Atlantic on a daily, weekly and monthly basis by the Genuity GNOC. Severity Level Matrix The severity matrix below indicates the level of urgency for an event: -------------------------------------------------------------------------------------------------------------------- Level Classified Nature Interval -------------------------------------------------------------------------------------------------------------------- 0 Emergency The problem is having a major adverse effect on Telephone call Xxxx Atlantic or Xxxx Atlantic End User(s)' notification within 15 business, preventing users from accessing the minutes of the time the network or their target application. ticket is opened; status will be available every 15 minutes via an ongoing conference call hosted by Genuity until the trouble is resolved; Genuity GNOC will notify Xxxx Atlantic within 15 minutes after the ticket is closed. ---------------------...
Trouble Reporting. Provider shall maintain a twenty-four (24) hour a day, seven (7) day a week point-of-contact for MCI to report Services troubles. Provider shall furnish MCI with periodically updated lists for Network management.
2.6.1 Each party shall furnish the other with a list of its personnel authorized to issue trouble reports under this Agreement. Each party shall accept trouble reports without delay from these personnel whenever, after the performance of appropriate tests, trouble is located in the facilities provided by such party under this Agreement and shall cause further testing and sectionalization to be done to determine whether the trouble is located in the provider's facilities, switching vehicle, equipment or another source. If such testing is ineffective, each party will work with the other to assist with the localization of the trouble. Such cooperative testing will normally be limited to continuity testing under a party's existing practices. If the trouble is sectionalized to a party's facilities, switching vehicle or equipment, such party shall take all necessary steps to clear the trouble and restore the Services.
2.6.2 If a party becomes aware of any condition, circumstance or failure that could adversely affect the Services, such party shall immediately notify the other. A party may, upon obtaining consent from the other party, temporarily interrupt the Services to perform needed testing.
2.6.3 When troubles are reported by either party, specific trouble tracking information will be exchanged with the other party. To facilitate the exchange of information, each party will maintain a trouble log of all trouble reports. The trouble log shall include the following information:
1. serialization of each trouble report; 2. the nature of the reported trouble; 3. date and time of the trouble report; 4. name and telephone number of the person reporting trouble; 5. name and telephone number of the person receiving the trouble report; 6. diagnosis of trouble; 7. date and time of trouble clearance; 8. name and telephone number of the person reporting trouble clearance; and 9. name and telephone number of the person receiving trouble clearance.
2.6.4 Each party shall furnish to the other status reports of each trouble report with thirty (30) minutes of the initial report and periodically thereafter.
2.6.5 Whenever a party designates a recurring trouble to be chronic in nature, each party shall immediately perform an investigation of the recent trouble history ...
Trouble Reporting. Each party will directly notify the other party of system performance issues. Each party agrees to respond with commercially reasonable efforts upon notification of problems affecting this service. Notification shall be sent in accordance with the procedures to be established by the Operations Council.
Trouble Reporting. Upon creation of a trouble ticket, SSN shall report the trouble and all applicable progress to FPL’s Project Manager. FPL and SSN will jointly use the following definitions to document and respond to errors or deficiencies that may exist. If FPL determines that an error or deficiency exists in the programs supported by the maintenance fees under this Agreement, FPL will provide notification to SSN of such error or deficiency, along with supporting data and programs that document such error or deficiency. SSN shall respond as indicated.
1.2.1 Critical – Severity 1 Error