Lightweight CAD Viewer Integration for Interface Requirements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computer-Aided Design (CAD) systems generate large files that impede transfer to other computing systems, necessitating a more efficient method to share and view CAD models without the original CAD model data.
Innovation Solution
A lightweight tessellated representation of CAD models is generated, stored in a file format like PDF, and viewed using a lightweight viewer, which includes geometric objects, annotation objects, and content objects to depict interface requirements and non-geometric performance requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the original CAD model is transferred to other computing systems, then complete design information is available, but the file size becomes large and transfer is impeded
Solution Approach 1:
The patent segments the CAD model information into two distinct parts: geometric data (visual representation) and non-geometric data (design information, annotations, interface requirements). This segmentation allows the geometric model to be transmitted in a lightweight format while the complete design information is preserved through separate data structures that can be accessed and displayed alongside the visual model.
Solution Approach 2:
The patent introduces an intermediary system that acts as a bridge between the lightweight geometric model and the complete design information. This intermediary contains data structures that store non-geometric information and automatically retrieve and display it in context with the corresponding geometric features, enabling complete information access without transmitting the full original CAD model.
2Quantity of substance
If a lightweight tessellated representation is generated, then file size is reduced and transfer is efficient, but complete CAD model data is excluded
Solution Approach 1:
The patent applies preliminary action by pre-organizing and storing non-geometric design information in structured data containers that are associated with specific geometric features before transmission. This preparation ensures that when the lightweight model is viewed, the complete design information can be instantly retrieved and displayed without requiring the original heavy CAD model files.
Solution Approach 2:
The patent implements a nested structure where non-geometric information is embedded within or associated with the lightweight geometric model through nested data containers. These containers are organized hierarchically to match the geometric structure, allowing complete information storage in a compact format that travels with the lightweight model.
3Adaptability or versatility
If interface requirements definition is integrated into the tessellated model, then collaboration among entities is enabled, but model complexity increases
Solution Approach 1:
The patent creates a universal data structure that serves multiple functions: storing geometric information, managing non-geometric design data, tracking interface requirements, and enabling multi-entity collaboration. This multi-functional structure consolidates what would otherwise require separate systems, reducing overall complexity while enhancing collaboration capabilities across different stakeholder groups.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A user interface (48) for a lightweight viewer (46) may include a viewing window (52-1) operable to display geometry (33) established by geometric objects (54) of a tessellated model (36). Groups (54G) of the geometric objects (54) may be associated with the geometry (33) of respective components (C) of an assembly (A). Annotation objects (64) of the tessellated model (36) may be operable to depict annotation information associated with the tessellated model (36) as graphical annotations in the viewing window (52-1). The groups (54G) of the geometric objects (54) may be assigned to two or more responsible entities according to an interface requirements definition (43). The annotation information may be associated with one or more interfaces between adjacent components of the assembly according to the interface requirements definition (43).