Automated Activity Object Generation and Consistency Checking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software systems face complexity in managing relationships between collection objects and activity objects, leading to challenges in scheduling and ensuring data consistency, especially in large-scale production processes where different individuals manage different phases using disparate software systems.

Innovation Solution

The method involves creating activity object instances from collection object instances, populating them with relevant data, and conducting consistency checks to ensure that each collection object is associated with a corresponding activity object, with automated creation of activity objects reducing manual effort and error, and implementing graphical user interfaces for user input on sequencing and precedence.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If activity object instances are manually created and managed, then user control over sequencing and precedence is maintained, but manual effort and error rate increase

Engineering Contradiction:
Improveuser controlVSAvoidmanual effort
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system automatically creates activity object instances from collection object instances, populates them with relevant data, and establishes sequencing and precedence relationships without requiring manual intervention. This self-service approach eliminates repetitive manual tasks while preserving user control through automated consistency checking and validation mechanisms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system copies structural information from collection object instances to create corresponding activity object instances. This copying mechanism preserves the hierarchical and relational structure of the data while transforming it into the activity-oriented format needed for scheduling, thereby reducing manual creation effort.

Inventive Principle:
Principle #26Copying

2Reliability

If consistency checks are performed manually, then data accuracy can be verified, but time consumption increases

Engineering Contradiction:
Improvedata consistencyVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements automated consistency checking that provides immediate feedback on data accuracy. Consistency checks verify that activity object instances correctly reflect their corresponding collection object instances, ensuring data integrity without requiring manual verification time.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Manual consistency verification is replaced with automated computer-based checking mechanisms. The system automatically compares activity object instances against collection object instances and validates sequencing and precedence relationships, substituting manual mechanical verification with automated electronic validation.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If disparate software systems are used for different process phases, then flexibility in managing individual phases is maintained, but overall process complexity increases

Engineering Contradiction:
Improvephase-specific flexibilityVSAvoidsystem integration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system provides a universal framework that handles multiple process phases through a consistent object-oriented model. Collection object instances and activity object instances serve as universal data structures that can represent different process phases while maintaining consistent relationships and sequencing mechanisms across the entire process.

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

Solution Approach 2:

The system merges the management of different process phases into a unified framework. By consolidating collection and activity objects into a single integrated system with consistent sequencing and precedence mechanisms, the patent reduces the complexity of coordinating disparate systems while preserving phase-specific flexibility.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11243760B2Automated generation and consistency checking of software objects
Publication Date: 2022.02.08 SAP SE
  • US11243760B2 patent drawing
  • US11243760B2 patent drawing
  • US11243760B2 patent drawing

AI summary

Technologies are described for creating activity object instances corresponding to collection object instances, and for conducting tests between activity object instances and collection objects instances, and within a set of activity object instances. Tests can include determining whether collection object instances have counterpart activity object instances, and evaluating a collection object instance with respect to a corresponding activity object instance. Activity object instances can be set to be performed in a sequence, and a test can determine whether the sequence is consistent with sequencing rules. When activity object instances are automatically created from collection object instances, a user can be presented with a graphical user interface that includes representations of activity object instances, and the user can manipulate the graphical user interface to provide precedence information.