Fault Reporting Process Sample Clauses

Fault Reporting Process. If the ISP suspects that a fault has occurred, or the Service is not available, the ISP must complete a diagnostic check of the ISP Equipment to ensure that the fault is not due to the ISP Equipment. The ISP may then report the fault to TransACT Capital’s Network Operations Centre and provide the following information: (a) location of the fault (if known); (b) name of the person reporting the fault; (c) description of the fault; (d) name of the site and technical contact; and (e) service ID affected by the fault. Each time a fault is reported by the ISP, TransACT Capital will issue the fault a unique identifier (Trouble Ticket), which shall be logged by TransACT Capital and quoted by the parties to assist in management of the fault and future analysis and reporting.
Sample 1Sample 2
AutoNDA by SimpleDocs
Fault Reporting Process. Upon suspecting that a fault has occurred, the Customer should initially complete a diagnostic check of all internal equipment and cables. If the Customer is satisfied that the fault is not due to a condition on their own network, a fault should be reported to Nextgen’s 24x7 Service Management Centre (SMC) by dialling 1800 099 299 in Australia or +00 0 0000 0000 internationally. Customers should provide the following information: (1) Customer Name and Service ID affected by the fault (2) Description of the fault (3) Name and contact details of the person reporting the fault (4) Name and location of the site Nextgen will issue a unique identifier (“Trouble Ticket”) to be used in all subsequent communications regarding that fault.
Sample 1
Fault Reporting Process. Customer reported faults 16.1. ProSystem requires that The Customer provides first line support to make initial assessment of any fault raised by their user base to determine if the issue is related to hardware and software supported by ProSystem within this Agreement. Having assessed the problem and determined that the fault is (or could be) related to hardware and or software supported within this service level agreement then the customer shall report all faults to ProSystem Technical Support Helpdesk. • The ProSystem Technical Support Helpdesk shall receive all fault, problem or incident reporting calls placed by the customer • The Technical Support Helpdesk shall log and issue a support case reference • Support case references will be logged against The Company with relevant details recorded of The Customer representative who reports the call and the fault, problem or incident details • Progress for resolution any recorded fault or problem and provide updates and confirm resolution for test and closure The following information should be provided when reporting the fault: • Details of The Customer representative reporting the fault, including name, location, mobile telephone number and return contact number. • Device or devices affected; User or users affected, service or functionality/ application affected, full address information and any access restrictions. • A comprehensive statement pertaining to the problem, including the type of fault, e.g. loss of network connectivity, inability to connect to application/ total loss of service, hardware failure. This should also include any error indications identifies by the users and also the service impact upon the customer’s ability to carry out its normal business • Any specific requests or instructions • Any other information felt relevant 16.2. ProSystem Technical Support Helpdesk shall issue a fault reference (cross referred to the customer’s fault reference where applicable). This shall constitute fault acknowledgement. In the event that a priority 1 or 2 fault cannot be cleared remotely, ProSystem shall make arrangements for a Technical Support representative to attend site. Site attendance is solely at ProSystem discretion.
Sample 1

Related to Fault Reporting Process

  • Fault Reporting 5.1 We are responsible for correcting faults in supplying the Voice Services. You must provide all necessary assistance to enable us to locate and repair any fault which is our responsibility. 5.2 We are not responsible for any fault which is on your side of the network termination point, except in relation to Purchase Equipment, or Other Equipment that we are maintaining. 5.3 We are not responsible for any fault which is within the network of a Supplier. However, we will notify that Supplier of the fault and request that the fault be corrected promptly.

  • Reporting Procedures Enter in the XXX Entity Management area the information that XXX requires about each proceeding described in paragraph 2 of this award term and condition. You do not need to submit the information a second time under assistance awards that you received if you already provided the information through XXX because you were required to do so under Federal procurement contracts that you were awarded.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Testing Procedures Testing will be conducted by an outside certified Agency in such a way to ensure maximum accuracy and reliability by using the techniques, chain of custody procedures, equipment and laboratory facilities which have been approved by the U.S. Department of Health and Human Services. All employees notified of a positive controlled substance or alcohol test result may request an independent test of their split sample at the employee’s expense. If the test result is negative the Employer will reimburse the employee for the cost of the split sample test.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Contract Reporting The Contractor shall report information on orders received from Customers associated with this Contract. No price adjustments will be considered for any Contractor who has outstanding reports, or any other documentation required under this Contract. The Contractor shall submit reports in accordance with the following schedule: MFMP Transaction Fee Report Calendar month 15 calendar days after the end of each month Quarterly Sales Report State’s Fiscal Quarter 30 calendar days after close of the period Diversity Report(submitted to the Customer) State Fiscal Year 30 Business Days after close of the period Preferred Pricing Affidavit (in accordance with the Special Contract Conditions) Annual Contract Anniversary Date

  • Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.

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