Response Protocol Clause Samples

The Response Protocol clause outlines the procedures and timelines that parties must follow when responding to communications, requests, or notifications under the agreement. Typically, it specifies the acceptable methods of communication, the timeframe within which a response must be provided, and any required content or format for the response. For example, it may require written responses within five business days to any formal notice or request. This clause ensures that all parties are clear on how and when to reply, reducing misunderstandings and promoting efficient, timely interactions throughout the contractual relationship.
Response Protocol. The protocol for responding to events of interference will require the Company to provide the General Manager of Public Works and Natural Resources an interference remediation report that includes the following items:
View SourceView Similar (4)
Response Protocol. 3.1 The section outlines the response time obligation of CCS in handling Support Calls made by IMed under this SDA. 3.2 Pursuant to section 3 above, the severity classification must be established before Relief, Temporary Fix and Resolution of a Support Call. 3.3 All Support calls received will be handled in accordance with the response protocol in Table 2. 3.4 Table 2. Response Protocol for Complaint/Support calls
View SourceView Similar (3)
Response Protocol. Employees are expected to mobilize within a predefined time frame when on call, which will be detailed in the operational guidelines.
View SourceView Similar (2)
Response Protocol. EWS will use commercially reasonable efforts to respond to Software support requests from Premium Users based on the severity level of the issue (as determined in good faith by EWS). EWS does not guarantee resolution times, and a resolution may consist of a fix, workaround, service availability, or other solution to restore functionality. Customer acknowledges and agrees that the response protocol described herein does not apply to general usage questions, documentation errors, issues related to a non-production environment, or feature requests reported by Customer: Severity Level Definition Response 1 – Critical The Software is inaccessible or so severely impacted that Customer cannot reasonably use the Software. A Severity Level 1 issue could have the following characteristics: • More than 50% of Customer users cannot access the Software • Customer users cannot create or save I-9 records • Customer users cannot submit to E-Verify solely as a result of an error in the Software (i.e., issue is not caused by the E-Verify system itself) EWS will acknowledge the issue within two (2) business hours of receiving notification from Customer and handle as the highest priority until the issue is resolved. 2 – Significant Major functionality or performance of the Software is impacted and no reasonable workaround exists. A Severity Level 2 issue could have the following characteristics: • Severely degraded performance • Frequent interruptions in service • Functionality is unavailable but the Software is able to operate in a restricted fashion EWS will acknowledge the issue within four (4) business hours of receiving notification from Customer and commit full-time resources to resolve. If EWS delivers an acceptable workaround instead of a solution, the severity classification will drop to a 3 – Minimal. 3 – Minimal A Software feature is unavailable but a workaround exists and the majority of functions are still useable. A Severity Level 3 issue could have the following characteristics: • A particular feature (such as a dashboard) is not working properly, but Customer user can obtain the same information through a report • Minimal Software performance degradation • Questions on Software functionality or configuration during implementation EWS will acknowledge the issue within two (2) business days of receiving notification from Customer and use reasonable efforts to resolve.
View SourceView Similar (2)
Response Protocol. The protocol for responding to events of Interference will require the Company to provide the County Engineer an Interference remediation report that includes the following items:
View Source
Response Protocol. For the avoidance of doubt, [Name] shall be responsible for reasonable costs to the extent caused by a Security Incident, including those incurred by Credit Card Company related to investigation, remediation, monitoring and notification. Processing. [Name] shall Process Covered Data per Credit Card Company instructions. Material Modifications. [Name] shall provide Credit Card Company with 90 days prior notice of a material modification to the process, method or means by which Covered Data is Processed (including any geographic change). If Credit Card Company reasonably determines and notifies [Name] that such modification could materially degrade Covered Data security, then [Name] shall not make such modification. Data Transfers. [Name] shall encrypt Covered Data in compliance with Applicable Processing Law and in the following circumstances: (a) the Processing of Covered Data on any mobile device or mobile storage or removable media, including laptop computers, smart phones, USB devices (“thumb drives”) and tapes/DVDs, and (b) electronic transfers of Covered Data by [Name] outside of its network. VTA. If [Name] hosts an Internet-facing and/or mobile application capable of Processing Covered Data, then [Name] shall annually have a vulnerability threat assessment (“VTA”) performed by a reputable vendor (from the then-current Payment Card Industry Council Approved Scanning Vendor list) and provide Credit Card Company with a summary attestation of the VTA including: (a) a definition of how the vulnerabilities are rated (e.g., high / medium / low, serious / moderate / minimal), (b) evidence that the application has no open vulnerabilities at the high rating, and (c) the number of vulnerabilities at any below high ratings and evidence that such vulnerabilities have been promptly remediated.
View Source
Response Protocol. In the event that Customer reports to Provider an Error in the SaaS (the Severity Level to be reasonably determined by Provider), Provider shall respond to such reports as follows: Severity Level Definition Response
View Source
Response Protocol. The protocol for responding to events of interference will require Company to provide Licensor’s City Engineer an interference remediation report that includes the following items: Remediation Plan. Devise a remediation plan to stop the event of interference; Time Frame for Execution. Provide the expected time frame for execution of the remediation plan; and Additional Information. Include any additional information relevant to the execution of the remediation plan.
View Source

Related to Response Protocol

  • Response to Objections Each Party retains the right to respond to any objection raised by a Participating Class Member, including the right to file responsive documents in Court no later than five court days prior to the Final Approval Hearing, or as otherwise ordered or accepted by the Court.

  • Impasse Procedure 5.1 If negotiations are not successfully concluded by the first day of school, impasse shall exist. At any earlier time either party may declare impasse. Upon reaching of impasse, the items causing the impasse shall be referred to a three-member committee. 5.2 The fact finding committee consisting of three (3) members shall be formed. One (1) member shall be selected by the Association, and one (1) member shall be selected by the Board within five (5) days. The third member shall be selected by the first two (2) members as follows: The parties shall notify the State Superintendent of Public Instruction that a Fact finder is needed and request a list of potential fact finders from the State Superintendent. If no name on the list is agreeable to both parties, a coin toss shall occur with the party winning the toss having the right to strike a name from the list until only one name remains. The person whose name remains on the list will serve as the chairperson of the fact finding committee. 5.3 Within five (5) days after the selection of the chairman, the representatives who have been negotiating for the Board and for the Association shall meet to exchange written language on each item at impasse. The exchanged documents shall also be furnished by each party to the chairman and other members of the committee. 5.4 The chairman shall convene the committee for fact finding. This committee shall meet with the representatives of both parties. Within twenty (20) days after the chairman is selected, the committee shall present written recommendations to the local Board and to the Association. 5.5 If either party decides it must reject any one or more of the committee's recommendations, said party must, within seven (7) days after the committee has presented its recommendations, request a meeting of the representatives who have been negotiating for the Board and for the Association. The parties shall meet within seven (7) days of the request, unless both parties deem it unnecessary. At such meeting, the representatives shall exchange written statements expressing each party's rationale for rejecting each recommendation found unacceptable and shall attempt to clarify any remaining differences. The representatives shall then resume good faith effort to resolve the remaining differences; provided, after fourteen (14) days after the exchange of the written statements, either party may discontinue such effort. 5.6 The costs for the services of the fact-finding committee, including per diem expenses if any, and actual and necessary travel expenses shall be shared in the following manner: the Board shall assume the expenses of the Board representative, the Association shall assume the expenses of the Association representative, and the expenses of the third member shall be shared equally by the Board and the association. 5.7 The Board shall file a copy of the fact finding report with the office of the State Superintendent of Public Instruction. If the effort to resolve differences is successful, the parties shall draft a written agreement and present the agreement to both parties for ratification, and upon ratification such agreement shall also be forwarded to the State Superintendent. If the effort to resolve differences is unsuccessful, the Board shall forward to the State Superintendent in writing its final disposition of the negotiations impasse process within thirty (30) days of the effective date of implementation.

  • Impasse Procedures Impasse proceedings shall be in accordance with § 6-408 of the Education Article to the Annotated Code of Maryland.

  • Notification Procedure (i) Each such notice shall be deemed to have been delivered: (A) when presented personally to the GOB; (B) when transmitted by facsimile; or (C) five (5) Days after being deposited in a regularly maintained receptacle for the postal service in Bangladesh, postage prepaid, registered or certified, return receipt requested, addressed to the GOB, at the address indicated in Section 17 of the Implementation Agreement (or such other address as the GOB may have specified by written notice delivered in accordance therewith). Any notice given by facsimile under this Section 4.6 shall be confirmed in writing delivered personally or sent by prepaid post, but failure to so confirm shall not void or invalidate the original notice if it is in fact received by the GOB.