Defect Reporting Sample Clauses

Defect Reporting. The Review Team communicates the results of process, product, and test evaluations and inspections, status of non-compliances, and issues. Defect reporting is used to ensure program awareness of process and product quality performance and issues. These reports provide the feedback, status, and data needed to ensure effective corrective and preventive actions.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Defect Reporting. The Operator shall comply with any reasonable defect-reporting procedure which may be introduced either by the Company or by any change in legislation or regulations.
Sample 1
Defect Reporting. Any defects found in the Licensed Software Product may be reported by calling the Seller's Call Receipt function. An assistance request will be entered into the AR tracking database and referred to Seller's technical support.
Sample 1Sample 2
Defect Reporting. Any defects found in the Software Product may be reported by calling Supplier's Call Receipt function. A tracking report will be entered into the AR tracking database and referred to Supplier's technical support.
Sample 1Sample 2
Defect Reporting. Deviations
Sample 1Sample 2
Defect Reporting. Licensee shall use all means necessary at its disposal to attempt to reproduce and diagnose all Defects with the System before contacting Licensor for technical support. Upon discovering a Defect, Licensee shall report the Defect to Licensor by electronic mail or facsimile in which report Licensee shall use its reasonable business judgment to classify the Defect in accordance with the classifications set forth in Section 1 above. In addition, Licensee agrees to supply Licensor with detailed hardware configuration for duplicating the problem, if requested by Licensor. If the System or Licensed Software is purchased from an Envivio Reseller or Distributor, the licensee must report any Defects to the Reseller or Distributor from whom the purchase was made.
Sample 1
Defect Reporting. To comply with any defect reporting procedure which may be carried out by the Company.
Sample 1
AutoNDA by SimpleDocs
Defect Reporting. When contacting the Licensor to initiate a help desk ticket, Licensee shall provide the following information: • Incident Number (if existing) • Licensee Name • Product version • Detailed description of the issue including relevant linked URLs to any affected apps and job errors • Name and email address of the person reporting the defect In the event Licensee reports to Licensor a defect in the Software, Licensor, acting reasonably, shall categorize and respond to requests as listed below. Note that initial responses will happen during support hours. Critical Business-critical processes not functional < 1 hour < 1 hour < 24 hours Serious Production processes not functional or business-critical processes impaired < 2 hours < 6 hours < 2 business days Moderate Development workflow(s) impaired < 8 hours < 2 business day < 5 business days Minor Software defects not falling into the above categories and cosmetic issues affecting the Software < 2 business day Future Release Future Release Licensee shall work in conjunction with Licensor to determine business-critical processes. The above time- frames are conditioned on Licensee providing Licensor with all information and assistance necessary for Licensor to diagnose and trouble-shoot the issue. Licensor shall ensure that its response to a request for Support Services shall include the following information (to the extent such information is relevant to the request): • Acknowledgement of receipt of the request • Initial diagnosis in relation to any reported error, where applicable • Anticipated timetable for action in relation to the request In effort to aid in ensuring properly functioning and optimized processing pipelines that complete in a timely manner, Licensor produces and continuously collects job status and application status data for support purposes. Licensor will collect only data produced by the Licensor application, at no time will Licensor be collecting any personal, customer, or enterprise data. If Licensee does not want Licensor to collect the job status data, Licensee must request in writing to be removed from the job status monitoring service.
Sample 1

Related to Defect Reporting

  • 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

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

  • Project Reports The Recipient shall monitor and evaluate the progress of the Project and prepare Project Reports in accordance with the provisions of Section 4.08 of the General Conditions and on the basis of the indicators agreed with the Association. Each Project Report shall cover the period of one calendar semester, and shall be furnished to the Association not later than one month after the end of the period covered by such report.

  • Accident Reporting 25.1 If You or an Authorised Driver has an Accident or if the Vehicle is stolen You must report the Accident or theft to Us within 24 hours of it occurring and fully complete an Accident/Theft report form. 25.2 If the Vehicle is stolen or if You or an Authorised Driver of the Vehicle has an Accident where: (a) any person is injured; (b) the other party has failed to stop or leaves the scene of the Accident without exchanging names and addresses; or (c) the other party appears to be under the influence of drugs or alcohol, You or the Authorised Driver must also report the theft or Accident to the Police. 25.3 If You or an Authorised Driver has an Accident You and the Authorised Driver must: (a) exchange names and addresses and telephone numbers with the other driver and drivers licence details; (b) take the registration numbers of all vehicles involved; (c) take as many photos as is reasonable showing: (i) the position of the Vehicles before they are moved for towing or salvage; (ii) the Damage to the Vehicle; (iii) the damage to any third party vehicle or property; and (iv) the general area where the Accident occurred, including any road or traffic signs; (d) obtain the names, addresses and phone numbers of all witnesses; (e) not make any admission of fault or promise to pay the other party's claim or release the other party from any liability; (f) forward all third party correspondence or court documents to Us within 7 days of receipt together with a fully completed Accident Report Form (if not already submitted); and (g) co-operate with Us in the prosecution of any legal proceedings that We may institute or defence of any legal proceedings which may be instituted against You or Us as a result of an Accident, including: (i) attending Our lawyer's office; and (ii) any Court hearing.

  • Litigation Reporting If Contractor is served with a pleading or other document in connection with an action before a court or other administrative decision making body, and such pleading or document relates to this Participating Addendum or may affect Contractor’s ability to perform its obligations under this Participating Addendum, Contractor shall, within 10 days after being served, notify the State of such action and deliver copies of such pleading or document to the State’s primary contact identified in §5 of the Participating Addendum .

  • Final Project Report Prepare a Final Project Report that addresses, to the extent feasible, comments made by the Grant Manager on the Draft Final Project Report. Submit one (1) reproducible master and an electronic copy of the final. Upload an electronic copy of the final report in pdf format to the FAAST system.

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

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

  • Incident Reporting Transfer Agent will use commercially reasonable efforts to promptly furnish to Fund information that Transfer Agent has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

  • Additional Reporting Within seven days after the date of this Agreement, the Recipient shall register in XXX.xxx, and thereafter maintain the currency of the information in XXX.xxx until at least October 1, 2022. The Recipient shall review and update such information at least annually after the initial registration, and more frequently if required by changes in the Recipient’s information. The Recipient agrees that this Agreement and information related thereto, including the Maximum Awardable Amount and any executive total compensation reported pursuant to paragraph 38, may be made available to the public through a U.S. Government website, including XXX.xxx.

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