The 3D ACIS® Modeler (ACIS) is Spatial’s prominent 3D solid modeling engine. 3D InterOp is a CAD data translation framework (Interoperability)
InterOp:Connect/Connect Representations
From DocR19
InterOp data exchange is based on the concept of document representation. A representation is a specific view of a document.
Contents |
Representation Concept
A Computer Aided Design (CAD) document can contain several different types of data, each of which fulfill a specific purpose. For example, a CATIA V5 document can contain BRep data, Visualization data, PMI data, and kinematic data. The InterOp document representation is filter, which can be applied to control the translation of specific data (representation) from a CAD document. InterOp connect also supports the combination of representations for translation, for example: "BRep+PMI" will allow the translation of BRep data and PMI data.
Representations in InterOp
BRep
The InterOp Connect representation "BRep" supports the translation of boundary representation data from a source document to a target document. BRep supports the translation of geometry and topology along with additional attribute information attached to geometry and topology. BRep representation supports the translation of these types of bodies:
- Solid bodies
- Surface bodies
- Wire-frame bodies
The following additional attribute information attached to the geometry and topology can be translated using the option TranslateAttributes:
- Color
- Name
- Layers And Filters
- Entity ID
- Work Planes
Assembly
InterOp Connect representation "Assembly" supports the translation of Assembly documents. Assembly representation also supports the translation of assembly product structures.
Currently the following modes of Assembly translation are supported:
- EBOM mode
- EBOM mode is used to convert an Assembly document to XML document. The XML file contains the assembly product structure as well as all the references to the instances of an assembly document.
- ASAT mode
- ASAT mode is used to convert an Assembly document to an ACIS Assembly ASAT document. Currently InterOp Connect supports translation of Assembly document to Monolithic ASAT format only. This ASAT document can be queried to retrieve the product structure of an assembly document.
- Flatten mode
- Flatten mode is used to convert an assembly document to a SAT document. Each instance of a part belonging to the assembly is translated as an individual ENTITY and written to the SAT document. The SAT document does not contain the product structure of an assembly document.
PMI
Product Manufacturing Information (PMI) is used in 3D CAD to capture and associate manufacturing requirements to the 3D CAD model. The InterOp Connect representation "PMI" currently supports the import of the following types of PMI data:
- Notes
- Flag Notes
- Dimensions
- Geometric Tolerances
- Surface Roughness
- Datum
- Datum Targets
- Datum Reference
- Datum Reference Frame
In addition to the above types of PMI data, InterOp Connect also provides display information associated with PMI data which can be used for rendering purposes. The types of display information include:
- Display point
- Display plane
- Display Primary direction
- Leader Information
- Leader Head Point
- Leader Tail point
Currently, PMI can be exported from the following formats:
- CATIA V5 Manufacturing Information
- ProE Manufacturing Information
- Unigraphics Manufacturing Information
PMI can be imported to the following formats:
Visualization
The InterOp Connect representation "Visualization" supports the translation of tessellation data from source document to target document. Connect uses the HOOPS Streaming Format (HSF) to support visualization representation. The Connect representation "Visualization" is supported for the following source documents and can be used to generate preview information:
- CATIA V5
Mesh
Collection of triangles that define a shape within the model. The Connect representation "Mesh" is supported for the following source documents.
- CATIA V5
Representation Option
In InterOp, representation is managed using options. Refer to the following topic for more details:
