Numerics |
|
| 3D state | See state, below. |
A |
|
| activity |
A discrete element of a process. For example, a process may begin with a welding or drilling activity. |
| assembly operation (AO) | These are the activities that transform input products to output products (manufacturing assemblies). An assembly operation can be assigned to a resource. |
| assembly specification graph (ASG) | This is a 2D representation of assembly operation(s). Its appearance is similar to a PERT chart. The ASG shows parent-child relationships (a.k.a. hierarchy structure) as well as precedence constraints. |
| assembly specification tree (AST) | This is a 2D representation of the assembly operation(s). Its appearance is similar to a PPR tree. The AST shows parent-child relationships (a.k.a. hierarchy structure). |
B |
|
| Behavior |
The actions taken by a resource. The behavior of a resource serves as the parent for task specification activities or TSAs. |
| bounding box | The volume formed by a 3D Box that encloses the geometry of the part. |
C |
|
| CATPart |
The default file type for a V5 part file. |
| CATProcess |
The default file type for a V5 process file. |
| CATProduct |
The default file type for a V5 product file. |
| control flow | Relation between activities describing successor and predecessor. |
| cross highlight | Cross highlighting highlights specified objects associated with a process or activity as the activity or process is shown. The specified objects are determined by the relation they have with the process. |
D |
|
| detailing |
V5-specific features (such as animation or simulation) added to a process that has been loaded from the Manufacturing Hub. |
E |
|
| Engineering Requirement |
Engineering Requirements are planned details of the part or product
including any design detail that must be completed in the manufacturing
process. This includes specific physical tasks and adherence to
tolerances that the design engineer has provided.
Automatic reconciliation allows the manufacturing engineer to confirm that the process has implemented all engineering requirements. It also allows the manufacturing engineer to check for partial or complete implementation of engineering requirements. |
F |
|
| Feature Tolerance & Annotation (FTA) |
FTA data consists of annotations that are associated with specific geometric entities. V5 offers several products for adding FTA data to CATProducts and CATParts. |
G |
|
| Gantt chart |
A Gantt chart is bar graph of a process. It shows start and stop times as well as dependencies. In V5, the Gantt chart is one of several available 2D views of the process. |
I |
|
| Interface Description Language (IDL) | The interface which defines APIs that can be used for a given object used in scripting language. |
L |
|
| links |
Shows the relationship or precedence between activities. |
| lock management |
Lock management refers to the edit status (read/write) behavior of objects loaded into DPM Process and Resource Definition via the Manufacturing Hub, and the tools provided to manage the status of objects by their owner. |
M |
|
| manufacturing hub | Database/Server repository for manufacturing data. |
| manufacturing context | Represents the products that are assembled before the loaded process. |
| manufacturing assembly | A product can be grouped in substructures that can be assembled separately. Normally these substructures, which are called manufacturing assemblies (MA), are assembled in separate lines. An MA is the collection of configurable (or non-configurable) products that define an end-item. A MA is a repository for parts. An MA does not store any position information. The positions of parts inside a MA are the positions of parts as seen in the Product List. |
| manufacturing kit | Manufacturing Kit is the collection of configurable (or non-configurable) products which define an end-item in "kit" form. |
O |
|
| operation |
Synonymous with activity. |
| output product |
DPM supports a Process Creates Product relationship that represents an output from a process. An output product can then be fed to another process using the Feed by Another Process command. |
P |
|
| partial read only mode | This mode is one loading mode from Manufacturing Hub. In this mode, objects can be modified, but only detailing and control flow are saved back to Manufacturing Hub. This mode enables more than one user to access process information. |
| parts | Parts, part models, part files, part geometry, and part
data are terms used interchangeably throughout this documentation.
Parts are used to create products. |
| PERT chart | A PERT chart is a graphical representation of a process.
Each activity within the process is represented by a box. Each box is
a node. Nodes may be labeled or unlabeled. The activities have
links to one another or to logical operators.
In V5, the PERT chart is one of the available 2D views of the process. |
| PPR tree | A 2D view of the process which lists all of the products
and resources required to make a specific product. It also lists, in
hierarchical form, the actions required to perform the process that
produces the product. In V5, PPR trees are stored in process documents and have a .CATProcess filename extension. |
| precedence constraints |
Rules defined in an activity's properties to guarantee that an activity cannot be linked unless prerequisite activities are already linked beforehand. If activity 1 has a precedence constraint with an activity 2, that implies that activity 1 has to be completed some unspecified time before activity 2 can proceed. |
| process |
A process is a series of actions or activities that alter parts. The end result of a process is the creation of a product or a part of a product. |
| product | Products consist of parts which may or may not be grouped
into assemblies. They appear in product structure documents; in V5,
these documents have a .CATProduct extension.
The difference between a product and a resource consists in how they are used with in a process. The end-result of the process should result in the creation of the product or products listed in the PPR tree. |
| product structure document | The product structure document is key component in V5. It
provides users with a way to organize product creation in a hierarchical
format. Each product structure document can contain parts, which make up
assemblies, which, in turn, make up products.
Product structure documents have a .CATProduct extension. |
R |
|
| relation | A relation describes a relationship between two objects - e. g. you can assign an activity to a resource by relation. |
| renumbering activities |
A command that, when executed, re-evaluates the activities and their current positions in the PPR tree and number them accordingly, as shown here. |
| resource | Resources consist of parts which may or may not be grouped
into assemblies. They appear in product structure documents; these
documents have a .CATProduct extension.
The difference between a product and a resource consists in how they are used within a process. The resources required during the process should be listed in the resource branch of the PPR tree. |
| resource behavior | See behavior. |
| reference process | Process object on which the Context has to be saved. |
| root process | A process object that is hierarchically above the reference process and identified by the user to be the scope under which the manufacturing context needs to be computed. |
| root product | A product object identified by the user to be the scope under which the manufacturing context needs to be computed. |
| root resource | A resource object identified by the user to be the scope under which the manufacturing context needs to be computed. |
S |
|
| state |
A state is an object that groups positions and other states in the context of a product or resource. A 3D state is used to display products and resources during process verification in a 3D position in the context of the verified process. |
| synchronization constraints | This term refers to the start/start and end/end relations defined between activities. |
T |
|
| task specification activities (TSA) | The discrete activities that make up a resource behavior. |
| two-dimensional (2D) views (or visualization) |
In addition to the PPR tree, V5 offers users several ways of visualizing their processes in 2D: e.g., via a Gantt chart and via a PERT chart. |
U |
|
| user rights |
A set of rules defined in Process Engineer which determine a particular user's ability to load, edit and save objects opened via the Manufacturing Hub. |
V |
|
| volumetric context | It reference products that define the context within which the planner authors the assembly process plan. |
| volume filter | Filter based on a volume of interest. |