Submitting Incidents Sample Clauses

Submitting Incidents. In order to obtain technical support covered by this SMA, You have to report the issue or problem to ISC using the contact form provided by ISC or the online input screen on ISC’s online support system (JIRA) (contact details are mentioned hereunder in article 4) and following the support procedure and guidelines set forth in Exhibit I to this Addendum 2. Within the Initial Response Time, ISC shall confirm receipt by e- mail, mention the JIRA registration number, if necessary, ask You for clarification, documentation, description or additional information and, if possible, identify the person (support engineer of ISC) dedicated to delivering technical support. Support will be provided by ISC solely to the authorized individuals designated by You and who are qualified and trained on the Software or Add-On(s). You will be asked to designate a maximum of three authorized support contacts.
AutoNDA by SimpleDocs
Submitting Incidents. In order to obtain technical support covered by this Addendum 2, You have to report the issue or problem to ISA using the contact form provided by ISA or the online input screen on ISA’s online support system (JIRA) (contact details are mentioned hereunder in article 4) and following the support procedure and guidelines set forth in Exhibit I to this Addendum 2. Within the Initial Response Time, ISA shall confirm receipt by e- mail, mention the JIRA registration number, if necessary, ask You for clarification, documentation, description or additional information and, if possible, identify the person (support engineer of ISA) dedicated to delivering technical support. Support will be provided by ISA solely to the authorized individuals designated by You and who are qualified and trained on the Software or Add-On(s). You will be asked to designate a maximum of three authorized support contacts.
Submitting Incidents. 4.1. Who May Submit Incidents Customer must designate authorized Customer Technical Personnel at time of purchase (at least one), unless otherwise specified, who will be the person registering the license. That individual(s) may submit change requests to the list of authorized Customer Technical Personnel in writing through the channel(s) specified for the plan selected. Unless specified in an Order Form, Customer may have no more than 5 Customer Technical Personnel at once. Customer may substitute Customer Technical Personnel in its discretion.
Submitting Incidents. In order to obtain technical support covered by this Agreement, You have to report the issue or problem to ISC using the contact form provided by ISC or the online input screen on ISC’s online support system (JIRA) (contact details are mentioned hereunder in section 6) and following the support procedure and guidelines set forth in Exhibit I to this Agreement. Within the Initial Response Time, ISC shall confirm receipt by e-mail, mention the JIRA registration number, if necessary, ask You for clarification, documentation, description or additional information and, if possible, identify the person (support engineer of ISC) dedicated to delivering technical support. Support will be provided by ISC solely to the authorized individuals designated by You and who are qualified and trained on the Software or add-on(s). You will be asked to designate a maximum of three authorized support contacts.
Submitting Incidents. In order to expedite the resolution of any reported incident, to the extent available, you will provide to BPA (i) a full description of the problem, including any actions that initiate the problem state; (ii) the business impact of the problem; the version, edition and build numbers of all software components affected or involved in the affected system (for example, BPA products, Microsoft SharePoint products, Windows Server, including physical or virtual configuration, SQL Server, Internet Explorer); (iii) any applicable log files that help with diagnosis; (iv) any applicable screen capture images that help illustrate the problem Incident reports can only be entered by registered contacts in the BPA Community site.

Related to Submitting Incidents

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. Correction NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.

  • Determination of Responsiveness 28.1 The Procuring Entity's determination of a Tender's responsiveness is to be based on the contents of the Tender itself, as defined in ITT28.2.

  • Grievability Denial of a petition for reinstatement is grievable. The grievance may not be based on information other than that shared with the Employer at the time of the petition for reinstatement.

  • JOB EVALUATION The work of the provincial job evaluation steering committee (the JE Committee) will continue during the term of this Framework Agreement. The objectives of the JE Committee are as follows: • Review the results of the phase one and phase two pilots and outcomes of the committee work. Address any anomalies identified with the JE tool, process, or benchmarks. • Rate the provincial benchmarks and create a job hierarchy for the provincial benchmarks. • Gather data from all school districts and match existing job descriptions to the provincial benchmarks. • Identify the job hierarchy for local job descriptions for all school districts. • Compare the local job hierarchy to the benchmark-matched hierarchy. • Develop a methodology to convert points to pay bands - The confirmed method must be supported by current compensation best practices. • Identify training requirements to support implementation of the JE plan and develop training resources as required. Once the objectives outlined above are completed, the JE Committee will mutually determine whether a local, regional or provincial approach to the steps outlined above is appropriate. It is recognized that the work of the committee is technical, complicated, lengthy and onerous. To accomplish the objectives, the parties agree that existing JE funds can be accessed by the JE committee to engage consultant(s) to complete this work. It is further recognized that this process does not impact the established management right of employers to determine local job requirements and job descriptions nor does this process alter any existing collective agreement rights or established practices. When the JE plan is ready to be implemented, and if an amendment to an existing collective agreement is required, the JE Committee will work with the local School District and Local Union to make recommendations for implementation. Any recommendations will also be provided to the Provincial Labour Management Committee (PLMC). As mutually agreed by the provincial parties and the JE Committee, the disbursement of available JE funds shall be retroactive to January 2, 2020. The committee will utilize available funds to provide 50% of the wage differential for the position falling the furthest below the wage rate established by the provincial JE process and will continue this process until all JE fund monies at the time have been disbursed. The committee will follow compensation best practices to avoid problems such as inversion. The committee will report out to the provincial parties regularly during the term of the Framework Agreement. Should any concerns arise during the work of the committee they will be referred to the PLMC. Create a maintenance program to support ongoing implementation of the JE plan at a local, regional or provincial level. The maintenance program will include a process for addressing the wage rates of incumbents in positions which are impacted by implementation of the JE plan. The provincial parties confirm that $4,419,859 of ongoing annual funds will be used to implement the Job Evaluation Plan. Effective July 1, 2022, there will be a one-time pause of the annual $4,419,859 JE funding. This amount has been allocated to the local table bargaining money. The annual funding will recommence July 1, 2023.

Time is Money Join Law Insider Premium to draft better contracts faster.