Trouble Reports Clause Samples
The Trouble Reports clause establishes the procedures for reporting, documenting, and addressing issues or malfunctions related to a product or service. Typically, it outlines how users or customers should notify the provider of any problems, the information required in a report, and the expected response or resolution timeframe. By formalizing this process, the clause ensures that issues are communicated clearly and handled efficiently, minimizing downtime and misunderstandings between parties.
Trouble Reports. A “Trouble Report” means any report made by Customer relating to the Services that describes the time, location and nature of the outage. Vyve shall maintain a twenty-four
Trouble Reports. From time to time, failures in, or degradation of, Products may cause services provided by the System to be ad- versely affected. It is necessary that immediate assistance be provided by the Vendor to allow the Owner to restore the affected service. Critical ser- vice outages that cannot be resolved by the Owner's field technicians or techni- cal support engineers using procedures described in the Operating Manuals, Maintenance and Instruction Manuals and Training will be transmitted to the Vendor as a Trouble Report ("TR"). The Vendor will assign an identi- fying number to each TR to aid in tracking its resolution. TRs will be imme- diately addressed by the Vendor through Emergency Technical Assistance under guidelines set forth in subsection 2.26.3. TRs may not be considered conclud- ed until the solution is concurred upon by an employee of the Owner within the Owner's operations control center ("OCC"). The root cause of problems re- sulting in TRs may be Defects or Deficiencies which must be corrected through Product or procedure changes. Problems with the System requiring such changes will be referred to the Vendor for action through a Customer Ser- vice Request ("CSR"). The Vendor is authorized by the Owner to install and integrate, at the Vendor's expense, any Software Upgrade or Software Enhancement pursuant to mutual agreements reached between the Vendor and the Owner.
Trouble Reports. The Parties shall cooperatively plan and implement coordinated repair procedures for the Meet-Point Trunks and Local Interconnection Trunks and facilities to ensure trouble reports are resolved in a timely and appropriate manner.
Trouble Reports. Saddleback Communications shall maintain a twenty-four (24) hour, seven (7) day a week point-of-contact for Customers to report Service troubles, outages or Service Interruptions. For Customer support, Customer shall call Trouble Reports to ▇▇▇-▇▇▇-▇▇▇▇.
Trouble Reports. CLEC and PACIFIC will cooperatively plan and implement coordinated repair procedures for the Meet Point and Local Interconnection Trunks and facilities to ensure that trouble reports are resolved in a timely and appropriate manner consistent with procedures referenced in Section VI of this Attachment.
Trouble Reports. IdeaTek shall maintain a 24 hours a day 7 days a week point-of-contact for staff to report service troubles, outages or service interruptions. Trouble Reports received by IdeaTek will be responded to within one (1) hour after receipt of the Trouble Report. IdeaTek will endeavor to cure the issue addressed in the Trouble Report within two (2) hours after receipt of the Trouble Report.
Trouble Reports. From time to time, failures in or degradation --------------- of Products comprising the System may cause services provided by the System to be adversely affected. It is necessary that immediate assistance be provided by the Vendor to allow the Owner to restore the affected service. Critical service Outages which cannot be resolved by the Owner's field technicians or technical support engineers using procedures described in the Vendor's Operating Manuals, Maintenance and Instruction Manuals and Training will be transmitted to the Vendor as a Trouble Report ("TR"). The Vendor will assign an identifying number to each TR to aid in tracking its disposition. TRs will be immediately addressed by the Vendor through Emergency Technical Assistance under guidelines set forth in this subsection 2.26.2. TRs may not be considered concluded until the solution is concurred upon by an Owner's employee within the Owner's operations control center ("OCC"). The root cause of problems resulting in TRs may be System Defects or Deficiencies which must be corrected through Product or procedure changes. Problems with the System requiring such changes will be referred to the Vendor for action through a customer service request ("CSR"). The Vendor is authorized by the Owner to install and integrate, at the Vendor's expense, any Software Upgrade or Software Enhancement pursuant to mutual agreements reached between the Vendor and the Owner.
Trouble Reports. Imperva shall report to Seller any Defect for which Imperva requires repair, replacement or correction by using Trouble Reports as set out below. All Trouble Reports shall be sent to Seller’s office by telefax or by electronic mail. For Defects having priority Class A in accordance with Sub-article 5.2 of this Agreement, Imperva may report such Defects to Seller by email/fax. Such reporting by email/fax shall be considered and treated by Seller as a submitted Trouble Report. For such cases, also a normal Trouble Report shall be sent to Seller for notification purposes only. Each Trouble Report shall contain the following information:
Trouble Reports. X-1 ARTICLE XI NETWORK MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XI-1 ARTICLE XII SERVICE PROVIDER NUMBER PORTABILITY . . . . . . . . . . . . . . . . . . . . . . . XII-1 APPENDIX A SERVICE LOCATION MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ▇-▇ ▇▇▇▇▇▇▇▇ ▇ SERVICE ORDERING, PROVISIONING, BILLING AND MAINTENANCE . . . . B-1 APPENDIX C RATES-COMPENSATION ARRANGEMENTS . . . . . . . . . . . . . . . C-1 This Interconnection Agreement (the "Agreement"), is made effective as of January 28, 1997, by and between GTE South Incorporated, with its address for purposes of this Agreement at ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ ▇▇. ▇▇▇▇▇▇ ▇▇, ▇▇▇▇▇ ("GTE"), and ICG Telecom Group, Inc., (“ICG”) with its address for this Agreement at ▇▇▇▇ ▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇ ▇▇▇▇▇. GTE and ICG being referred to collectively as "the Parties" and individually as a "Party"). This Agreement covers services in the Commonwealth of Kentucky (“State”).
Trouble Reports. Customer shall notify DotParse' of Defects and requests for Problem solution by a Trouble Report. The Trouble Report shall be posted via DotParses' Support Portal and shall include the following information, as appropriate: Contact Person at Customer with contact information. Information about the latest product patches installed. Affected environment (system type). Suggestion for Defect/Problem classification and a description of the Defect/Problem, defining the classification of the Defect or Problem. Estimated number of Customers affected. A description of the command(s) and procedures that reveal the Defect/Problem. A short description of the fault and its impact on system performance. Whether the Customer/Supplier has created the non-functioning component/function. Which company in the system is affected? In which user interface does Customer experience the problem (Customer Portal, Technical interface, Service Provider or Customer Service) Name of the non-functioning component Whether the non-functioning component/function has previously functioned. If yes; has any changes been made by Customer/Supplier? If no: is the Defect/Problem previously reported? Step-by-step instruction of how the Defect/Problem is reproduced. If possible, The Customer should try to reproduce a Defect/Problem before sending a Trouble Report to DotParse.