Manufacturing Data Object Generation via Definition File Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for generating and managing data objects in organizations are resource-intensive due to a focus on customization, disregarding similarities between processes, leading to increased time and cost in business operations by managing and storing different data objects in separate databases.

Innovation Solution

A method and system for generating Manufacturing Data Objects (MDOs) by creating a definition file, generating a database table, establishing a mapping between the definition file and the database table, linking the definition file to a data source, executing queries to extract attributes, and storing the definition file, database table, and attributes for efficient data object generation and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If customized application programs and systems are generated for each organization, then adaptability to specific organizational needs is improved, but resource consumption and time for business operations increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoidbusiness operation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent creates a universal data object model that can serve multiple organizations and purposes. By defining standardized data objects with common attributes and relationships that can be reused across different organizations, the system eliminates the need to create custom data objects for each organization, thereby reducing resource consumption while maintaining adaptability through configuration rather than customization

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

Solution Approach 2:

The patent enables copying and reusing of data object definitions across different organizations. Once a data object is defined with specific attributes and relationships, it can be copied and instantiated multiple times with minimal modification, significantly reducing the time and resources required for business operations while maintaining the ability to adapt to specific needs through instance-level configuration

Inventive Principle:
Principle #26Copying

2Ease of operation

If different data objects are stored in separate databases, then data organization and management for each organization is improved, but time and cost for business operations increase

Engineering Contradiction:
Improvedata management organizationVSAvoiddata access time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent merges data objects from different organizations into a unified database structure. By consolidating previously separate databases into a single unified database that can store multiple instances of the same data object type, the system enables faster data access and reduces the time required for cross-organizational operations while maintaining logical separation through the object model

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments the unified database into logically independent data object instances that can be independently managed. Each organization's data is segmented into distinct instances of standardized data objects, allowing for organized management within the unified database structure while enabling efficient access without the overhead of separate physical databases

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8145681B2System and methods for generating manufacturing data objects
Publication Date: 2012.03.27 SAP SE
  • US8145681B2 patent drawing
  • US8145681B2 patent drawing
  • US8145681B2 patent drawing

AI summary

Systems and methods consistent with the invention may include generating, using a processor of the computer system, a definition file of a first format for the data object, generating a database table, generating a mapping between the definition file and the database table, linking the definition file to a data source by including a path of the data source in the definition file, the data source including an attribute, executing, using the processor, a query to extract the attribute from the data source, importing the extracted attribute into the database table using the mapping between the definition file and the database table, and storing, in the memory device, the definition file, the database table, and the attribute for generation of the data object with the attribute.