Priority Codes Sample Clauses

Priority Codes. The Priority Code indicates the urgency with which SUPPLIER must respond to the TR. DGC will use the nature of the problem and the business situation to determine the Priority Code. The TR Priority Code may be reclassified by SUPPLIER upon consent by DGC. This may occur, for example, if SUPPLIER provides a satisfactory Workaround for the problem or determines that the problem arises from a faulty understanding of the original TR. The Priority Codes are as follows: Priority Description Code # 10 URGENT PROBLEM - System or major application is not functional or seriously impacted and there is no reasonable Workaround currently available. 20 MODERATE PROBLEM - System or application is moderately impacted. There is no Workaround currently available or the Workaround is cumbersome to utilize.
Sample 1
AutoNDA by SimpleDocs
Priority Codes. PRIORITY CODES ---------------------------------------- ----------------------------------------------------- LICENSEE CLASSIFICATION CRITERIA ---------------------------------------- ----------------------------------------------------- P1 Critical A `Fatal' or `Showstopper' condition. ---------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------- Precludes all useful work from being done, a problem in critical functionality without a workaround, emergency condition that causes the end user to be unable to use the program and that has a critical impact on such end user's operations.This condition requires an immediate solution. ---------------------------------------- ----------------------------------------------------- P2 Urgent A `Severe Impact' condition. Precludes one or more major functions from being performed. A problem in critical functionality with a workaround, a condition that severely restricts the End User's operation but such user can continue to use the program, or a condition, which makes the performance of any or more functions difficult. This problem cannot be readily circumvented or avoided on a temporary basis by the End User and requires a rapid solution. ---------------------------------------- ----------------------------------------------------- P3 Normal A `Degradation' condition. Disables one or more non-essential functions. Problem in a non-critical functionality without a workaround, a limited condition that cannot be readily circumvented or avoided on a temporary basis by the End-User. ---------------------------------------- ----------------------------------------------------- P4 Low A `Minimal Impact' condition. Any condition, which requires rectification and is not classified as P1, P2, or P3. A problem in a non-critical functionality with a workaround, a minor condition that can be readily circumvented or avoided on a temporary basis by the End User. Insignia shall have no obligation to rectify code modified or provided by anyone other than Insignia. ---------------------------------------- -----------------------------------------------------
Sample 1
Priority Codes. The Priority Code indicates the urgency with which SUPPLIER must respond to the TR. DGC will use the nature of the problem and the business situation to determine the Priority Code. The TR Priority Code may be reclassified by SUPPLIER upon consent by DGC. This may occur, for example, if SUPPLIER provides a satisfactory Workaround for the problem or determines that the problem arises from a faulty understanding of the original TR. The Priority Codes are as follows:
Sample 1
Priority Codes. The level of service and order of priority shall be determined by the priority codes assigned. BofA, working with 724, shall determine the relative merit of 'bumping' out other scheduled requests for service and development of requested Improvements. If 724 receives a telephone support call for an Improvement or for a lower priority service request, service for such item will be scheduled after all higher priority service calls have been addressed.
Sample 1
Priority Codes. A - Catastrophic System or module failures that do not have a viable detour or workaround available. B - Problems that have been substantiated as a serious inconvenience to users, including any Priority A Error for which a viable detour or workaround is available.
Sample 1
Priority Codes. A critical priority is given to an issue that renders the Software inoperable or substantially degrades the performance thereof or adversely affects Customer’s business operations or causes financial liability due to operational or informational deficiency. In the event that Domino personnel are required to travel to Customer’s location to fix a critical issue problem, Domino will send such personnel at no additional out-of-pocket expense to Customer, provided such problem is a result of the Software or actions of Domino. A high priority is given to an issue that is not adversely affecting Customer’s business operations or causing financial liability, but is repeatedly affecting Customer’s usage of the Software or data integrity or degrading performance of the Software. A standard priority is given to an issue which does not impact Customer’s operation or use of the Software. Response Times. Domino will respond to requests from Customer for Software support within the following response time frames: Domino will respond to a Critical priority within four (4) hours after Customer has reported the problem to Domino, and Domino will diligently work to resolve the problem until resolution of the problem. Domino will respond to a High priority within eight (8) hours after Customer has reported the problem to Domino, and Domino will diligently work to resolve the problem. Domino will respond to a Standard priority within two (2) business days after Customer has reported the problem to Domino and will diligently work to resolve the problem and Domino will follow up with Customer on the next scheduled contact time. Unless otherwise agreed by the Parties, Domino will use commercially reasonable efforts to correct any Standard priority issues in the next Maintenance Release of the Software.
Sample 1

Related to Priority Codes

  • Junior Liens It being understood that B notes secured by the same Mortgage as a Mortgage Loan are not subordinate mortgages or junior liens, except for any Mortgage Loan that is cross-collateralized and cross-defaulted with another Mortgage Loan, as of the Cut-off Date there are no subordinate mortgages or junior mortgage liens encumbering the related Mortgaged Property other than Permitted Encumbrances, mechanics’ or materialmen’s liens (which are the subject of the representation in paragraph (7) above), and equipment and other personal property financing. The Mortgage Loan Seller has no knowledge of any mezzanine debt secured directly by interests in the related Mortgagor other than as set forth on Exhibit C-32-1.

  • Priority and Liens (a) Each of the Borrower and each Guarantor hereby covenants, represents and warrants that, upon entry of the Interim Order, the Obligations of the Borrower and such Guarantor hereunder and under the Loan Documents: (i) pursuant to section 364(c)(1) of the Bankruptcy Code, shall at all times constitute an allowed Superpriority Claim; (ii) pursuant to section 364(c)(2) of the Bankruptcy Code, shall at all times be secured by a perfected first priority Lien on all unencumbered tangible and intangible property of the Borrower and such Guarantor and on all cash maintained in the L/C Cash Collateral Account and any investments of the funds contained therein, including any such property that is subject to valid and perfected Liens in existence on the Petition Date, which Liens are thereafter released or otherwise extinguished in connection with the satisfaction of the obligations secured by such Liens (excluding any avoidance actions under the Bankruptcy Code or the proceeds therefrom); (iii) pursuant to section 364(c)(3) of the Bankruptcy Code, shall be secured by a perfected Lien upon all real, personal and mixed property of the Borrower and such Guarantor that is subject to valid and perfected Liens in existence on the Petition Date, junior to such valid and perfected Liens (other than Liens securing the Pre-Petition Secured Indebtedness) and (iv) pursuant to section 364(d)(1), shall be secured by a perfected priming Lien upon all tangible and intangible property of the Borrower and such Guarantor that presently secure the Pre-Petition Secured Indebtedness; provided that the foregoing shall be subject in all respects to the Carve-Out. Each of the Borrower and each Guarantor hereby covenants, represents and warrants that, upon entry of the Final Order, the Obligations of the Borrower and such Guarantor hereunder and under the Loan Documents: (i) pursuant to section 364(c)(1) of the Bankruptcy Code, shall at all times constitute an allowed Superpriority Claim; (ii) pursuant to section 364(c)(2) of the Bankruptcy Code, shall at all times be secured by a perfected first priority Lien on all unencumbered tangible and intangible property of the Borrower and such Guarantor and on all cash maintained in the L/C Cash Collateral Account and any investments of the funds contained therein, including any such property that is subject to valid and perfected Liens in existence on the Petition Date, which Liens are thereafter released or otherwise extinguished in connection with the satisfaction of the obligations secured by such Liens (excluding any avoidance actions under the Bankruptcy Code (but including the proceeds therefrom)); (iii) pursuant to section 364(c)(3) of the Bankruptcy Code, shall be secured by a perfected Lien upon all real, personal and mixed property of the Borrower and such Guarantor that is subject to valid and perfected Liens in existence on the Petition Date, junior to such valid and perfected Liens (other than Liens securing the Unrolled Pre-Petition Secured Indebtedness), and (iv) pursuant to section 364(d)(1), shall be secured by a perfected priming Lien upon all tangible and intangible property of the Borrower and such Guarantor that secure the Unrolled Pre-Petition Secured Indebtedness; provided that the foregoing shall be subject in all respects to the Carve-Out.

  • Priority Indebtedness The Company will not, and will not permit any Subsidiary to, create, incur, assume or permit to exist any Priority Indebtedness other than:

  • Priority Debt The Company will not permit Priority Debt to exceed 15% of Consolidated Total Assets (as of the end of the Company’s then most recently completed fiscal quarter) at any time.

  • Lien Documents At Closing and thereafter as Lender deems necessary, Borrower shall execute and/or deliver to Lender, or have executed and delivered (all in form and substance satisfactory to Lender and its counsel):

  • Junior Financing Documentation (i) Any of the Obligations of the Loan Parties under the Loan Documents for any reason shall cease to be “Senior Indebtedness” (or any comparable term) or “Senior Secured Financing” (or any comparable term) under, and as defined in any Junior Financing Documentation or (ii) the subordination provisions set forth in any Junior Financing Documentation shall, in whole or in part, cease to be effective or cease to be legally valid, binding and enforceable against the holders of any Junior Financing, if applicable.

  • Priority of Distributions On each Distribution Date, the Indenture Trustee shall first reimburse itself for all amounts due under Section 6.7 of the Indenture and then shall make the following deposits and distributions in the amounts and in the order of priority set forth below:

  • Priority Tax Claims Except to the extent that a Holder of an Allowed Priority Tax Claim agrees to a less favorable treatment, in full and final satisfaction, settlement, release, and discharge of and in exchange for each Allowed Priority Tax Claim, each Holder of such Allowed Priority Tax Claim shall be treated in accordance with the terms set forth in section 1129(a)(9)(C) of the Bankruptcy Code.

  • Subordination of Junior Financing The Obligations are “Senior Debt,” “Senior Indebtedness,” “Guarantor Senior Debt” or “Senior Secured Financing” (or any comparable term) under, and as defined in, any Junior Financing Documentation.

  • Priority If the Managing Underwriter or Underwriters of any proposed Underwritten Offering of Common Units included in an Underwritten Offering involving Included Registrable Securities advises the Partnership that the total amount of Common Units that the Selling Holders and any other Persons intend to include in such offering exceeds the number that can be sold in such offering without being likely to have an adverse effect on the price, timing or distribution of the Common Units offered or the market for the Common Units, then the Common Units to be included in such Underwritten Offering shall include the number of Registrable Securities that such Managing Underwriter or Underwriters advises the Partnership can be sold without having such adverse effect, with such number to be allocated (i) first, to the Partnership and (ii) second, pro rata among the Selling Holders who have requested participation in such Underwritten Offering and any other holder of securities of the Partnership having rights of registration that are neither expressly senior nor subordinated to the Registrable Securities (the “Parity Securities”). The pro rata allocations for each Selling Holder who has requested participation in such Underwritten Offering shall be the product of (a) the aggregate number of Registrable Securities proposed to be sold in such Underwritten Offering multiplied by (b) the fraction derived by dividing (x) the number of Registrable Securities owned on the Closing Date by such Selling Holder by (y) the aggregate number of Registrable Securities owned on the Closing Date by all Selling Holders plus the aggregate number of Parity Securities owned on the Closing Date by all holders of Parity Securities that are participating in the Underwritten Offering.

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