PRIORITY LEVEL DESCRIPTION Sample Clauses

The "Priority Level Description" clause defines and categorizes the levels of urgency or importance assigned to specific tasks, services, or issues within an agreement. It typically outlines several priority tiers—such as critical, high, medium, or low—and describes the criteria or conditions that determine which category applies to a given situation. For example, a critical priority might be assigned to system outages, while a low priority could apply to minor user requests. This clause ensures that all parties have a shared understanding of how issues are classified and addressed, thereby streamlining response times and resource allocation to match the severity of each situation.
PRIORITY LEVEL DESCRIPTION. Critical A critical service is non-operational, impacting the Customer’s business, multiple End Users or multiple Sites; or severe functional error or degradation of Service(s) affecting production, demanding immediate attention. Business Risk is High Priority 2 Major The Customer’s business is experiencing failure or performance degradation that impairs the operation of a critical business Service, although a work around may exist; or Application functionality is lost; or significant number of End Users or major Site is affected. Business Risk is Medium Priority 3 Minor The Customer is experiencing a problem that causes moderate business impact. The impact is limited to an End User or a small Site; or incident has moderate, not widespread impact; or involves partial loss with minimal impact which is non- critical in nature. Business Risk is Low Priority 6 Change Request Standard service request (e.g. End User guidance and Change Requests); or updating documentation. Business Risk is Minor localised
PRIORITY LEVEL DESCRIPTION. Urgent An instance where customer’s production use of the software purchased is stopped or so severely impacted that the customer cannot reasonably continuebusiness operations using the software purchased. It may result in a material and immediate interruption of customer’s business operation that will cause a loss of customer data and/or restrict availability to such data and/or cause a significant operational impact to the customer. High An instance where one or more important functions of the software purchased are unavailable with no acceptable alternative solution. Customer's implementation or production use of the service is continuing but not stopped; however, there is a serious impact on the customer's business operations. Normal An instance where: (a) important software features are unavailable, but an alternative solution is available, or (b) less significant software feature is unavailable with no reasonable alternative solution; Customers experience a minor loss of business operation functionality and/or an impact on implementation resources. Low An instance that has a minimal impact on business operations or basicfunctionality of the software, or where customers ask questions regarding basic functionality of the software.

Related to PRIORITY LEVEL DESCRIPTION

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • COLLATERAL DESCRIPTION The word “Collateral” as used in this Agreement means the following described property, whether now owned or hereafter acquired, whether now existing or hereafter arising, and wherever located, in which Grantor is giving to Lender a security interest for the payment of the Indebtedness and performance of all other obligations under the Note and this Agreement: In addition, the word “Collateral” also includes all the following, whether now owned or hereafter acquired, whether now existing or hereafter arising, and wherever located:

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Work Description T-804 Opening Roads - Removal of closure devices, cleaning ditches, removing berms, and blading the traveled-way T-811 Closing Roads - Entrance treatment for 150' cross-rip; debris block (slash, earth, berm, rocks, etc.) + seed + water bar T-811 Closing Roads - Water bar frequency per BMPs for remainder of road T-811 Closing Roads - Engineering Rep. or Construction Inspector must be notified prior to performing closeout 9314A Single Lane / Level 1 NFSR 9314 0.00 END 0.20

  • Topic Description Severability If any provision of this Agreement is declared invalid or unenforceable, then, to the extent possible, all of the remaining provisions of this Agreement will remain in full force and effect.