SOT
    • 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
  • Smart Operations Toolkit
    • Deviation Processor
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Process Quality
    • AI Services
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
  • Enterprise & Shopfloor Integration
    • Information Router
    • Master Data Management

SOT Learning Portal

  • Ticket Management
  • Operations manual
  • System Architecture and Interfaces
7.22.2 7.22.0

System Architecture and Interfaces

Dependencies

Building Block View of Ticket Management
Component Ticket-Service

Technology

  • Backend: Java, Spring Boot (i.e. Web MVC, Actuator, Spring-Cloud-Stream, Spring-Data-JPA, Websocket Stomp)

  • Frontend: JavaScript, TypeScript, Angular

Purpose

  • Manage life cycle of deviations in form of tickets, including

    • Time-based escalation for tickets (due time exceeded)

    • Track history of ticket actions

  • Shadowing master data (devices, facilities) in database and consuming changes from MMPD

  • Manage solution groups

Interfaces

  • HTTP/HTTPS (REST)

  • MACMA for authentication and fetching Access Control List information

  • MDM for master data: devices and facilities

  • Portal for registration of views, widgets, context contributions

  • Deviation Processor for registration of TM as a reactor module to enable automatic ticket creation based on deviation

  • Notification Service for enabling email notification in case of ticket status changes

  • Relational DB for storage of data

  • RabbitMQ

    • incoming device master changes from MDM

    • outgoing ticket state changes

  • Websockets providing ticket-live-view

Network Connections Overview

Source Destination Protocol

Ticket Management Web UI

Ticket Management

https

Ticket Management

MACMA

https

Ticket Management

Master Data Management

https

Ticket Management

IAS Portal

https

Ticket Management

Deviation Processor

https

Ticket Management

Notification Service

https

Ticket Management

RabbitMQ

AMQP 0.9.1 with TLS

Ticket Management

RDBMS

TCP/IP with SSL

Deployment and Bootstrapping Process in Nexeed Industrial Application System

Deployment and Bootstrapping Process

First MACMA must be setup, that the modules can use the authentication of MACMA. After that all modules (TM, MDM, Deviation Processor, Notification Service, and Portal need to register at MACMA to get client credentials, which are needed to configure the module. After that the modules can be started. Then roles and resources of the modules can be registered at MACMA, that they are available afterwards. After successful startup, TM can register at Portal and checks the presence of TM and other module roles in MACMA, that they can be used by TM. If all roles are available, TM can call the endpoints of the modules to pull data from MDM, register as reactor module in Deviation Processor and register event types in Notification Service.

Deployment View for Cloud Deployment

DeploymentViewCloud

TM Namespace View for Cloud Deployment

TMNamespaceDeploymentView

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses