Production Program Creating System Database Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing production program creating systems require extensive modifications and reduced reliability when new types of component mounting or feeding devices are introduced, as device-specific processing information is scattered across multiple modules, necessitating updates across the entire system.
Innovation Solution
A system where component mounting and feeding devices are modeled and their configuration information is stored in a database, allowing for generalized processing that can dynamically acquire and update information without requiring changes to specific device-dependent processes, thus reducing the number of steps needed when new devices are added or existing ones changed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If device-specific processing information is scattered across multiple modules, then the system can handle various device types, but the system requires extensive modifications when new devices are introduced
Solution Approach 1:
The patent introduces a database as an intermediary layer between the processing modules and device-specific information. The database stores device configuration information and processing parameters in a centralized manner, allowing modules to access device-specific data without containing it within their code. This mediator approach enables the system to adapt to new devices by simply updating the database rather than modifying multiple processing modules.
Solution Approach 2:
The patent segments the system into two distinct parts: generic processing modules that handle production logic, and a database that stores device-specific configuration information. This segmentation separates device-independent processing from device-specific data, allowing each component to be developed and maintained independently. When new devices are added, only the database needs to be updated while the processing modules remain unchanged.
2Ease of manufacture
If device-specific processing information is stored within each module, then each module is self-contained, but reliability deteriorates when modifying the whole system
Solution Approach 1:
The database serves as a centralized intermediary that stores all device-specific processing information, eliminating the need for each module to contain its own device-specific code. This centralization improves reliability because modifications are confined to a single location (the database) rather than being scattered across multiple modules, reducing the risk of introducing errors during system updates.
3Adaptability or versatility
If the entire system is modified to support new devices, then all modules can work with new device types, but the number of steps required increases
Solution Approach 1:
The patent extracts device-specific information from the processing modules and places it into a separate database. This extraction allows the processing modules to remain generic and unchanged while the database is updated with new device information. The time-consuming task of modifying multiple modules is replaced by the simpler task of updating database entries, significantly reducing the steps required to support new devices.
Solution Approach 2:
The system performs preliminary action by establishing a standardized database structure that can accommodate various device types. By pre-defining the data model and access interfaces, the system prepares in advance for device additions, so that when new devices are introduced, only data entry is required rather than structural modifications or extensive programming.
4Ease of operation
If configuration information is scattered throughout the system, then each module has access to needed data, but the complexity of integration increases
Solution Approach 1:
The patent merges all device-specific configuration information into a single centralized database, which is then accessible by all processing modules. This merging maintains data accessibility for all modules while reducing integration complexity by providing a unified interface and consistent data structure that all modules can use, eliminating the need for each module to implement its own data access logic.
Data Source
AI summary
A production program creating system creates a production program having a module in which a processing for producing a board is described. The board is produced by mounting an electronic component supplied from a component feeding device onto the board by means of a component mounting device. The component mounting device is described in model form, and a configuration information of the component mounting device is stored in a database. The module is created such that the module works with respect to the component mounting device that is described in model form, and such that the module performs a generalized processing by acquiring the configuration information of the component mounting device from the database.


