Automation Routine Collaboration for Shared Object Bug Diagnosis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Multiple industrial automation software engineers often work on overlapping hardware components and software logic simultaneously, leading to inefficiencies in diagnosing and fixing bugs in industrial automation routines, as there is no effective mechanism for direct user collaboration on shared elements.

Innovation Solution

A system and method for facilitating user communication and collaboration through electronic messaging and real-time communications among users working on overlapping automation routines and software objects, allowing users to flag issues, leave comments, and receive notifications on shared software automation objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple engineers work on overlapping hardware components and software logic simultaneously, then productivity is improved through parallel development, but diagnostic efficiency deteriorates due to lack of collaboration mechanisms

Engineering Contradiction:
Improveparallel development speedVSAvoidbug diagnosis time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent introduces a collaboration platform as an intermediary system that connects multiple engineers working on overlapping automation routines. This platform enables real-time communication, issue flagging, and collaborative debugging without requiring engineers to directly interrupt each other's work, thus maintaining parallel productivity while reducing diagnostic time through coordinated problem-solving

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where engineers can flag issues, leave comments, and receive notifications about problems in shared automation objects. This continuous feedback loop allows parallel developers to quickly identify and resolve conflicts in overlapping code sections, reducing the time lost to debugging while maintaining high parallel development speeds

Inventive Principle:
Principle #23Feedback

2Device complexity

If engineers work independently on shared software objects, then device complexity is reduced through individual focus, but information loss increases due to lack of direct communication

Engineering Contradiction:
Improvecollaboration system complexityVSAvoidcollaboration information
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent merges individual engineering workspaces with a centralized collaboration platform, allowing engineers to maintain their independent focus on specific automation objects while simultaneously accessing shared information about overlapping components. This integration enables information exchange without requiring complex direct communication protocols between engineers

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The collaboration platform serves multiple functions including issue tracking, real-time messaging, code annotation, and notification distribution within a single system. This multi-functionality reduces the need for multiple separate communication tools, minimizing system complexity while preventing information loss through comprehensive collaboration capabilities

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3629266B1Multi-user collaboration across domains for industrial automation design
Publication Date: 2025.11.12 ROCKWELL AUTOMATION TECH INC
  • EP3629266B1 patent drawingFigure 1
  • EP3629266B1 patent drawingFigure 2
  • EP3629266B1 patent drawingFigure 3

AI summary

The present disclosure is directed to systems, methods and devices for facilitating user communication for industrial automation system design. A first user's input for flagging an issue for review by a second user may be received in relation to a software object integrated in an industrial automation routine. A flag may be associated with the software object. A request to access the flagged issue may be received from the second user, and a location in the industrial automation routine corresponding to the flagged issue and the software object may be caused to be displayed on a computing device associated with the second user.