Nexeed
    • Introduction
    • User manual
      • General Descriptions
        • Fine-grained access control
        • Ticket Management Groups
      • Ticket Management
        • Filter options
        • Ticket details
        • Ticket archiving
        • Ticket anonymization
        • Notifications
        • Ticket escalation mapping
      • Maintenance status widget
    • Operations manual
      • Overview
      • System Architecture and Interfaces
      • System Requirements
        • tm/ticket-service
      • Migration from Previous Versions
        • Migration to 7.3.0+
        • Migration to 7.4.0+
        • Migration to 7.4.1+
        • Migration to 7.8.0+
        • Migration to 7.9.0+
        • Migration to 7.10.0+
        • Migration to 7.11.0+
        • Migration to 7.12.0+
        • Migration to 7.13.0+
        • Migration to 7.13.1+
        • Migration to 7.14.0+
        • Migration to 7.16.0+
        • Migration to 7.17.0+
        • Migration to 7.20.0+
      • Setup and Configuration
        • Setup
          • Installation guide
        • Recommendations
        • Helm Configuration
        • Ticket Management global variables
        • tm/ticket-service
        • Ticket Management IAS dependencies
      • Start and Shutdown
      • Regular Operations
      • Failure Handling
      • Backup and Restore
      • Logging and Monitoring
        • Module Health Verification Endpoints and K8S Probes
      • Known Limitations
        • Maximum 2100 parameter support of MSSQL can lead to query failure
        • Users from different tenants can have issues when calling MACMA/MDM concurrently
        • Lost messages of Notification service if maximum retry is exceeded
    • Developer documentation
      • Getting Started
      • How-Tos
        • Domain Context Registration
        • Integrating Ticket Management Views
      • Failure Handling
        • Embedded View Blocked by Content Security Policy (CSP)
    • API documentation
      • HTTP API
    • Glossary
Ticket Management
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Ticket Management
  • User manual
  • General Descriptions
  • Ticket Management Groups

Ticket Management Groups

This document defines the different types of user groups used within the Ticket Management system: Solution, Delegation, and Escalation Groups. These groups are fundamental to routing tickets, controlling visibility, and managing the ticket lifecycle.

Group Types and Descriptions

The system utilizes three distinct types of groups to manage tickets.

Group Type Description

Solution Group

The primary group responsible for a ticket at any given time. It is the modern replacement for the "Qualification" concept.

  • Every ticket is always assigned to exactly one Solution Group.

  • Solution Groups are managed in MACMA.

  • When a ticket is created, it is assigned to an initial Solution Group.

Delegation Group

Any Solution Group to which a ticket can be transferred. During ticket creation, you can specify one or more potential Delegation Groups to pre-configure the ticket’s workflow.

Escalation Group

A designated group that handles tickets that have been escalated. When a ticket is escalated, it becomes visible to and actionable by the members of the assigned Escalation Group.

Hierarchical Visibility for Solution Groups

Solution Groups can be organized in a hierarchy. This structure dictates which users can view which tickets. A user assigned to a group can see tickets belonging to their own group and any groups nested beneath it.

Example 1. Hierarchical Group Example
  • Maintainer Champion

    • Maintainer Expert

      • Maintainer Beginner

A user in the Maintainer Champion group can view tickets assigned to Maintainer Champion, Maintainer Expert, and Maintainer Beginner. In contrast, a user in Maintainer Beginner can only see tickets assigned to that group.

Group Configuration and Mapping

The system determines which Escalation Group to use based on the ticket’s current Solution Group. This is configured via Escalation Mapping view. In the configuration screen, "Resolving Group" is synonymous with "Solution Group".

If a Solution Group does not have a specific Escalation Group mapped, the system will assign escalated tickets to a predefined DEFAULT_ESCALATION_GROUP.

Escalation Groups do not have hierarchical visibility. Only users who are direct members of an Escalation Group can see tickets escalated to it.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses