Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to Government of Rwanda Projects
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

Side Menu

  • Overview
  • Activity
  • Work packages
  • Boards
  • Project library
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showProject library
        • Expanded. Click to collapseCollapsed. Click to show00 Scope
          • Hierarchy leaf00 Project charter (empty)
        • Expanded. Click to collapseCollapsed. Click to show10 Requirements
          • Hierarchy leaf00 Requirements assessment
          • Hierarchy leaf10 Requirements traceability matrix
        • Expanded. Click to collapseCollapsed. Click to show20 Stakeholders & Communication
          • Hierarchy leaf00 Stakeholder analysis (empty)
          • Hierarchy leaf10 Communication plan
        • Hierarchy leaf30 Team & Resources
        • Hierarchy leaf40 Architecture
        • Hierarchy leaf50 Reporting
        • Hierarchy leaf60 Risks (empty)
        • Hierarchy leaf70 Contract Documents
        • Expanded. Click to collapseCollapsed. Click to show80 Deliverables
          • Hierarchy leafSome deliverable
        • Expanded. Click to collapseCollapsed. Click to show90 templates
          • Hierarchy leaf010 project charter
          • Hierarchy leaf020 reporting template
          • Hierarchy leaf030 Default ToR for Government of Rwanda IT projects
        • Expanded. Click to collapseCollapsed. Click to show95 Standards & Processes
          • Expanded. Click to collapseCollapsed. Click to show00 PM methodology at RISA
            • Hierarchy leafMeeting Structure
          • Hierarchy leaf01 Standards for the "Definition of Done" (DoD)
          • Hierarchy leaf04 Severity of Incidents
          • Hierarchy leaf05 Acceptance procedure
          • Hierarchy leaf10 Architecture principles
          • Hierarchy leaf20 Service Digitization Guideline
          • Hierarchy leaf30 Service request process
          • Hierarchy leaf40 Test Management
          • Hierarchy leaf50 Version Managment
          • Hierarchy leaf60 CI/CD
          • Hierarchy leaf70 Contract Management
You are here:
  • Project library
  • 95 Standards & Processes
  • 04 Severity of Incidents

Content

04 Severity of Incidents

  • More
    • Print
    • Table of contents

Incidents will be classified with the following severities:

  • (1) Critical:
    • Incident critically affects the primary business service, major application or function
    • Characteristics of a Severity 1 case include but are not limited to:
      • Business service or function is not operational
      • Production system crashes
      • Data integrity at risk
      • Production backup and recovery operations fails
  • (2) Major:
    • The business service, major application, function, or system is seriously affected
    • No acceptable workaround is available
    • Documentation not available
  • (3) Medium:
    • The business service, major application, function or system is moderately impacted
    • No data has been lost
    • The business service, application, or system is still functioning
    • Documentation needs explanation
    • The case may be temporarily circumvented using an available workaround
  • (4) Minor:
    • Non-critical cases
    • Minor documentation cases
  • (5) Enhancements:
    • Enhancement requests
Loading...