Priority classes of Support Requests, Reaction Time Sample Clauses

Priority classes of Support Requests, Reaction Time. (a) The Customer shall classify each Support Request according to the following table and according to the impact/s to its business. If a priority class is not defined by the Customer, it is by default considered to be “Low”. Existing Priority Classes:  Critical This priority is reserved exclusively for situations in which the Customer’s production system is down or the Customer intends to initially start his production system very soon and this issue will prevent the production system to start operations.  High This priority shall be used for situations where there is a severe functionality loss, but the Customer’s production system remains operational and processing can continue.  Medium A functionality error has occurred but processing can still continue, or a non-business critical function is not performing properly.  Low Request for service or information or a problem of minor impact has been identified.
AutoNDA by SimpleDocs

Related to Priority classes of Support Requests, Reaction Time

  • Corresponding Class of Reference Tranches With respect to (i) the Class M-1 Notes, the Class M-1 Reference Tranche, (ii) the Class M-2 Notes, the Class M-2 Reference Tranche, (iii) the Class M-3A Notes, the Class M-3A Reference Tranche, (iv) the Class M-3B Notes, the Class M-3B Reference Tranche and (v) the Class B Notes, the Class B Reference Tranche.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Sole Source as Grounds for Rejection of a Change Order If a Change Order is submitted to Contractor for the purposes of adding a Bulletin to this Contract and said Bulletin designates a Sole Source from which Contractor is required to procure goods or services necessary to perform the Work, which Sole Source has not been designated previously, Contractor shall be entitled to reject the proposed Change Order if the designated Sole Source refuses to provide to Contractor the warranties, bonds, terms or schedule required under the Contract Documents, including any warranty or terms or schedule required by Bulletins referenced in the proposed Change Order. In such event, Contractor shall give written notice to the Owner rejecting the proposed Change Order and, if possible, shall accompany said written notice with a proposal from Contractor for changes or modifications to the Bulletin so as to eliminate the Sole Source designation but to achieve goods or services equal in quality or function. The Owner may then require the Design Professional to revise the subject Bulletin so as to eliminate the designation of the Sole Source by incorporation of Contractor's proposal or otherwise. Upon revision of the Bulletin by the Design Professional and approval thereof by the Owner, the Owner shall again submit to the Contractor a proposed Change Order for the purpose of adding the revised Bulletin to this Contract. If the Owner decides to retain the Sole Source in the Change Order and Contractor cannot acquire the full contractually required warranties from the Sole Source, Contractor shall be held only to the warranty terms and schedule obtainable from the Sole Source.

  • Requesting Price Increase/Required Documentation Contractor must submit a written notification at least thirty (30) calendar days prior to the requested effective date of the change, setting the amount of the increase, along with an itemized list of any increased prices, showing the Contractor’s current price, revised price, the actual dollar difference and the percentage of the price increase by line item. Price change requests must include H-GAC Forms D Offered Item Pricing and E Options Pricing, or the documentation used to submit pricing in the original Response and be supported with substantive documentation (e.g. manufacturer's price increase notices, copies of invoices from suppliers, etc.) clearly showing that Contractor's actual costs have increased per the applicable line item bid. The Producer Price Index (PPI) may be used as partial justification, subject to approval by H-GAC, but no price increase based solely on an increase in the PPI will be allowed. This documentation should be submitted in Excel format to facilitate analysis and updating of the website. The letter and documentation must be sent to the Bids and Specifications manager, Xxxxxxx Xxxxxx, at Xxxxxxx.Xxxxxx@x-xxx.xxx Review/Approval of Requests If H-GAC approves the price increase, Contractor will be notified in writing; no price increase will be effective until Contractor receives this notice. If H-GAC does not approve Contractor’s price increase, Contractor may terminate its performance upon sixty (60) days advance written notice to H-GAC, however Contractor must fulfill any outstanding Purchase Orders. Termination of performance is Contractor’s only remedy if H-GAC does not approve the price increase. H-GAC reserves the right to accept or reject any price change request.

  • Allocation of Subordinate Reduction Amount to the Reference Tranches On each Payment Date prior to the Termination Date, after allocation of the Senior Reduction Amount and the Tranche Write-down Amount or Tranche Write-up Amount, if any, for such Payment Date as described above, the Subordinate Reduction Amount will be allocated to reduce the Class Notional Amount of each Class of Reference Tranche in the following order of priority, in each case until its Class Notional Amount is reduced to zero:

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.

  • Allocation of Senior Reduction Amount to the Reference Tranches On each Payment Date prior to the Termination Date, after allocation of the Tranche Write-down Amount or Tranche Write-up Amount, if any, for such Payment Date as described above, the Senior Reduction Amount will be allocated to reduce the Class Notional Amount of each Class of Reference Tranche in the following order of priority, in each case until its Class Notional Amount is reduced to zero:

  • OGS Centralized Contract Modifications OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • Pricing Increase Requests Subsequent to the first twelve (12) months of the Contract term and in accordance with the schedule for price adjustments established by OGS, Contractor may request an increase in the pricing contained in the Centralized Contract by submitting an update request based on change in pricing level as contained in Appendix C, Contract Modification Procedure to the OGS Contract Administrator. With any price increase request, in addition to the requirements contained in Appendix C, the Contractor must certify in writing that the price change for the Services is the same as its pricing in its GSA Supply Schedule, and that Contractor documents the request to the satisfaction of the State.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

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