PCB Design Data Synchronization via a Shared Message Server

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for designing printed circuit boards (PCBs) are inefficient and error-prone due to the need for manual data conversion and interface programs between different software applications, leading to time-consuming and inconvenient workflows when multiple applications are used simultaneously.

Innovation Solution

Implementing a method where multiple PCB application programs share data using compatible data models, allowing seamless integration and automatic data exchange through a message server, eliminating the need for manual conversion and interface programs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple PCB design applications are used simultaneously, then design capability and functionality are improved, but data conversion complexity and error rates increase

Engineering Contradiction:
Improvedesign capabilityVSAvoiddata conversion complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a message server as an intermediary component that mediates communication between multiple PCB design applications. The message server receives data from one application, automatically converts it to the appropriate format, and delivers it to the target application. This eliminates the need for direct interface programs between each application pair, reducing overall system complexity while maintaining multi-application functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message server is designed as a universal intermediary that can handle data conversion between any pair of applications in the system. Rather than creating specific interface programs for each application combination, a single multi-functional message server handles all conversion needs, significantly reducing the number of interface programs required and simplifying the system architecture.

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

2Reliability

If manual data conversion between applications is performed, then data compatibility is achieved, but time consumption and productivity loss increase

Engineering Contradiction:
Improvedata compatibilityVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables automatic self-service data conversion where the message server autonomously performs data format conversion without requiring manual intervention from the designer. When one application generates data, the message server automatically detects the data type, converts it to the appropriate format for the target application, and delivers it seamlessly. This eliminates the time-consuming manual conversion process while ensuring data compatibility.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The message server performs data conversion in advance before the designer needs to use the data in another application. By automatically converting and preparing data in the background, the system eliminates waiting time and ensures that data is ready for immediate use when the designer switches applications, thereby reducing overall time consumption.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If interface programs are written for each application pair, then data communication is enabled, but maintenance burden and error-proneness increase

Engineering Contradiction:
Improvedata communicationVSAvoidnumber of interface programs
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The message server acts as a central intermediary that consolidates the function of numerous individual interface programs. Instead of having separate interface programs for each application pair (creating a complex web of interfaces), all data communication passes through the single message server, which simplifies the system architecture and reduces the number of interface programs to one.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message server is designed as a universal data communication hub that can handle conversions between any application pair in the system. This multi-functional approach replaces the need for multiple specialized interface programs, reducing maintenance burden and minimizing error-proneness while maintaining ease of operation.

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

4Adaptability or versatility

If designers switch between multiple applications manually, then different design functions are accessed, but workflow efficiency and productivity decrease

Engineering Contradiction:
Improvedesign function accessVSAvoidworkflow efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The message server enables continuous data flow between applications without interrupting the designer's workflow. As the designer switches between applications to perform different design functions, the message server continuously converts and delivers relevant data in the background, ensuring that data is always available when needed. This maintains the continuity of useful action and prevents workflow interruptions, thereby improving productivity while preserving access to multiple design functions.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS7590963B2Integrating multiple electronic design applications
Publication Date: 2009.09.15 SIEMENS INDUSTRY SOFTWARE INC
  • US7590963B2 patent drawing
  • US7590963B2 patent drawing
  • US7590963B2 patent drawing

AI summary

Multiple printed circuit board (PCB) application programs simultaneously execute on a computer. Each application stores data regarding a PCB design in a separate database. The databases are based on compatible data models such that each application is able to receive data from other applications and understand what is to be done with that data. When an edit to a PCB design is made by an application, data for the edit is stored in that application's database. The data for the edit is also automatically provided, via a message server program, to other PCB applications. Each PCB application then stores that edit data in its own database.