Embedded Debugging Modules for Industrial Software Incident Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current debugging methods for software programs executed in industrial environments controlled by manufacturing operation management systems (MOM systems) are complex, requiring deep knowledge of debugging tools, software architecture, and access to source code repositories, which can lead to inefficiencies and longer incident resolution times.

Innovation Solution

A method that involves source-coding software routines with additional code sections that generate retrievable outputs, allowing for easier debugging by providing structured information on the execution of software routines without requiring deep knowledge of debugging tools or software architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual debugging methods using generic functionalities are used to inspect parameters and information, then debugging capability is achieved, but the process requires high debugging knowledge, deep understanding of software architecture, access to source code repository, and becomes a huge problem during software maintenance

Engineering Contradiction:
Improvedebugging capabilityVSAvoiddebugging process complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the debugging process by introducing specialized debugging modules that are integrated into specific software routines. Instead of using generic debugging functionalities that require deep knowledge, the system divides the software architecture into modular components with embedded debugging capabilities. Each debugging module handles specific debugging tasks within its routine, eliminating the need for operators to understand the entire software architecture or access source code repositories.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces debugging modules as intermediary components between the software routines and the debugging process. These modules act as mediators that automatically collect, process, and present debugging information in a standardized format. Operators interact with these intermediaries through simplified interfaces rather than directly with complex debugging tools, reducing the knowledge required while maintaining precise debugging capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If high skilled operators use debugging tools with access to source code repository to perform incident root cause analysis, then proper analysis is achieved, but the process requires high level of knowledge and becomes inefficient during software maintenance

Engineering Contradiction:
Improveincident root cause analysis accuracyVSAvoidoperator skill requirement
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service debugging capabilities where the software system automatically performs incident root cause analysis through embedded debugging modules. When incidents occur, the relevant debugging modules automatically collect execution data, analyze the incident context, and generate diagnostic information without requiring human operators to manually investigate. This self-service approach maintains high analysis accuracy while eliminating the need for operator expertise in debugging tools and software architecture.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies preliminary action by pre-configuring debugging modules within software routines during the software development and deployment phase. These modules are prepared in advance to automatically capture execution data and incident information. When incidents occur, the preliminary setup allows immediate automated analysis without requiring operators to manually configure debugging tools or access source code, thus maintaining reliability while improving ease of operation.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If production logs are used for incident analysis, then basic information is available, but the logs are not detailed enough to allow for efficient analysis

Engineering Contradiction:
Improveinformation availability for analysisVSAvoidincident analysis efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent applies local quality by enhancing information collection at specific local points within the software architecture. Debugging modules are embedded in individual software routines to capture detailed execution data locally at the point where incidents occur. This localized detailed logging provides rich information exactly where needed, unlike generic production logs that provide only broad, undifferentiated information. The local quality approach ensures both complete information availability and efficient analysis by capturing relevant data at the source.

Inventive Principle:
Principle #3Local quality

4Ease of operation

If generic functionalities are used to inspect parameters over the execution engine, then debugging is possible, but it requires deep knowledge of debugging techniques and software program architecture

Engineering Contradiction:
Improvedebugging accessibilityVSAvoiddebugging capability
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The patent merges the debugging functionality directly into the software routines by embedding debugging modules within the execution flow. Instead of separating debugging as a standalone generic function that requires deep knowledge, the debugging capabilities are combined with the business logic in modular units. This merging allows operators to access precise debugging information through the same interface used for normal operations, improving ease of operation while maintaining measurement precision through the integrated nature of the debugging modules.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20250045187A1Method for enhancing the debugging capability for a software program
Publication Date: 2025.02.06 SIEMENS AG
  • US20250045187A1 patent drawing
  • US20250045187A1 patent drawing
  • US20250045187A1 patent drawing

AI summary

A method enhances the debugging capability for a software program being executed on a resource of an industrial environment that is controlled by a manufacturing operation management system that enables a faster and easier debugging and interpretation functionality on software incidents occurring during the execution of the business logic. The method includes the steps of: a) source-coding a number of software routines to achieve under execution of the software routine a logical result; b) adding to each software routine a code section indicative for the achievement of the logical result wherein the code section generates a retrievable output in response to the execution of the software routine; c) controlling the resource to execute the number of software routines; and d) running an analysis tool enabled to provide the retrievable outputs deducted from the execution of the number of software routines in a separate analysis report.