Data Vaults |
Identifies the data storage items for a workspace,
workspace template, project space, project template, project concept, or RFQ. To
side clone rule is Replicate. Prevent duplicates is enabled. Originally
named Project Vaults and therefore its symbolic name is relationship_ProjectVaults.
Named Workspace Vaults in AEF 9500 and then renamed to Data Vaults. This
relationship is used in an expression access so if its name changes,
the expression must change on the policy. See Administrative Objects Used in Expression (Filter) Accesses. |
Vault Access |
DCR Manufacturing Responsibility |
Connects a Deviation Change Request (DCR) type
to a Manufacturing Responsibility relationship. Prevent duplicates
is enabled. |
End Date MCO-In Plant ID Production
Make Buy Code RoHS Start Date |
DCR MBOM |
Connects a Deviation Change Request (DCR) type
to an MBOM relationship to define a temporary MBOM relationship. Prevent
duplicates is enabled. |
End Date Find Number MBOM Status MCO-In MCO-Out Original
Assembly Revision Plant ID Reference Designator Sequence Substituted |
DCR MBOM Deviation Substitute |
Connects a Deviation Change Request (DCR) type
to an MBOM Deviation Substitute relationship. Prevent duplicates
is enabled, |
End Date MCO-In Plant ID Start
Date |
DCR Part Revision |
Connects a Deviation Change Request (DCR) type
to a Part Revision relationship. Prevent duplicates is enabled. |
End Date MCO-In Plant ID Start
Date |
Decision |
Connects a Decision object to any other object
or to a Sub Requirement or Derived Requirement relationship. From
side revision rule is replicate. |
-- |
| Decision Applies To |
Connects a Decision to any type. From side revision rule is replicate. |
-- |
| Declaration Level |
Connects a variable amount of Compliance Definitions to Parts or Materials. |
-- |
Default Line Item Attribute Group |
Defines a default attribute group to be used
for all existing and new line items in the RFQ. From side revision
and clone rules are Replicate. Prevent duplicates is enabled. |
Attribute Filter |
Default Line Item UDA Miscellaneous |
Defines default miscellaneous UDAs for all existing
and new line items in the RFQ. From side revision and clone rules
are Replicate. |
UDA Mandatory UDA Name |
Default Line Item UDA Non-recurring Cost |
Defines default non-recurring cost UDAs for
all existing and new line items in the RFQ. From side revision
and clone rules are Replicate. |
UDA Name |
Default Line Item UDA Recurring Cost |
Defines default recurring cost UDAs for all
existing and new line items in the RFQ. From side revision and
clone rules are Replicate. |
UDA Name |
Default Region |
Identifies a person's default region. |
-- |
Default Specification Office |
Identifies a person's default spec office. |
-- |
Defect Action |
Connects a Defect Action to its parent Defect. |
-- |
| Defect Affected Item |
Connects a Defect Action to the object affected by the defect. |
-- |
Defect Environment |
Connects a Defect to an Environment to indicate
that is the environment under which this Defect was found. |
-- |
Defect Reported Against |
Connects a Defect to a Product to indicate where
that Defect was found. |
-- |
Defect Reported Against Product |
If the Defect is connected to multiple objects
using the Defect Reported Against relationship, this relationship indicates
the Product to use as the primary. |
-- |
Deleted Subtask |
Connects Project Management objects to Task
Management objects. |
Comments Date Deleted Sequence Order Task
WBS |
Department Employee |
Identifies employees of a department. To
side revision rule is Replicate. |
-- |
Dependency |
Defines dependencies across a single project.
Associates Project Management types and subtypes. Prevent duplicates
is enabled. |
Dependency Type Lag Time |
Dependent |
Connects 2 Defect Actions to indicate that the
fix for one depends on the fix for the other. |
-- |
Derived |
Connects a part to another part or a feature
to another feature to indicate one is derived from the other. Prevent
duplicates is enabled. |
-- |
Derived Component |
This relationship can be between any MCAD Model
and any other MCAD Model and is intended to capture general dependencies
among MCAD Models. |
-- |
Derived From |
Connects one Product Configuration to another
Product Configuration. |
-- |
Derived Output |
Viewable versions of the design, usually in
a format such as JT or jpg. |
CAD Object Name |
Derived Requirement |
Indicates the relationship where a requirement
is derived from another requirement. The From side Revision
rules is set to Replicate. |
Link Status Sequence Order |
Derived Viewable |
Connects Viewable types with Viewable types. |
-- |
| Design Baseline |
Connects a CAD Drawing or MCAD Model to a design baseline (DECBaseline). |
-- |
Design Responsibility |
Indicates the responsibility of an organization
for design of a part, CAD Drawing, CAD Model, Compliance Enterprise Part,
Compliance Plant Specific Part, Drawing Print, Part Specification, ECO,
Features, Products, Builds, Requirement, Source Code, Directory, Technical
Specification, ECR, Issue, PUE Change, or Requirement. To side
revision and clone rule is Replicate. Prevent duplicates is enabled. This
relationship is used in an expression access so if its name changes,
the expression must change on the policy. See Administrative Objects Used in Expression (Filter) Accesses. |
Agreed Unit Price Comments RTS ID Show
Sub Components Show Target Cost Source Qualification Status Source
Selection Status Sub Component Level |
Development Manager |
Identifies the person who manages a supplier. To
and From side revision rule is Float. Prevent duplicates is enabled. |
-- |
Directed By |
Connects a customer organization to directed
supplier. To and From side revision rule is Float. Prevent duplicates
is enabled |
-- |
Directed Item |
Connects a directed supplier to item. To
and From side revision rule is Float. Prevent duplicates is enabled. |
-- |
Directed To |
Connects directed supplier to supplier organization. To
and From side revision rule is Float. Prevent duplicates is enabled. |
-- |
Disallow External Access |
Connects an Organization to a Part. |
|
Distribution Available On |
Connects the Software Platform object to the
respective Distribution File object. From side revision rule is
Float. |
-- |
Distribution File |
The distribution file that will be ship with
the product or build. Prevent duplicates is enabled. |
-- |
Distribution List |
Identifies the distribution list for a technical
specification. From side revision rule is Float. |
-- |
Distribution Media |
Connects the Media object to the respective
Distribution File object. From side revision rule is Float. |
-- |
Division |
Indicates the business units within a company.
Allows for Business Units to be N levels. From and To side revision
rule is Float. |
-- |
Document Holder |
Connects a Company to a Holder object to support
documents. |
-- |
Document Sheets |
Connects a DOCUMENTS object to a Document Sheet
indicating the document has sheets. From and To side revision rule
is Replicate. To side clone rule is Replicate. Prevent duplicates is
enabled. |
-- |
Document Structure |
Connects document objects to other document
objects to represent assemblies and subassemblies within 3D JT files. |
-- |
Document Usage |
Connects a Download object to a DOCUMENTS object. |
Deleted Documents Design Name Design
Type Download Purpose State of Usage |
Download Context |
Connects a Download object to a Part. |
-- |
Download Document |
Connects a Download object and a DOCUMENTS object. |
Download End Date Download Files Download
Start Date Download Status Download Time |
Download Holder |
Connects the Person to the Download Holder object. |
-- |
DSCMessageError |
Connects an error message to the queue. |
-- |
DSCMessageSuccess |
Connects a success message to the queue. |
-- |
Duplicate |
Connects 2 Defects to indicate that one is a
duplicate of the other. Prevent duplicates is enabled. |
-- |
EBOM |
Engineering Bill of Material; indicates the
component parts of an assembly part or product configuration. From
side revision and clone rule is Replicate. The ENO_Effectivity
property is set to Unit. |
Component Location End Effectivity Date Find
Number Notes Quantity Reference Designator Spatial
Location Start Effectivity Date Usage |
EBOM Change |
Connects a Change object to an EBOM or EBOM
Pending relationship (between 2 parts). Prevent duplicates is enabled. |
BOM Operation |
EBOM Change History |
Connects a Change object to an EBOM or EBOM
Pending relationship (between 2 parts). Prevent duplicates is enabled. |
BOM Operation |
EBOM History |
Engineering Bill of Material; indicates the
component parts of an assembly part. Allows the system to keep track
of old EBOM connections. |
Component Location End Effectivity Date Find
Number Has Manufacturing Substitute Notes Quantity Reference
Designator Start Effectivity Date Usage |
EBOM Manufacturing Responsibility |
Connects a Manufacturing Reponsibility relationship
to an EBOM relationship. Prevent duplicates is enabled. |
End Date Start Date Stype Switch |
EBOM Markup |
Connects a part to an EBOM Markup. |
-- |
EBOM Pending |
Connects a part to a part to indicate an EBOM
is pending for that part. From side clone is replicate. From
and To side revision rule is float. The ENO_Effectivity property
is set to Unit. |
Component Location End Effectivity Date Find
Number Has Manufacturing Substitute Notes Quantity Reference
Designator Start Effectivity Date Usage |
EBOM Split Quantity |
Connects an EBOM relationship to a Split Quantity
type to store the Plant Specific quantity selection for a part. Prevent
duplicates is enabled. |
Switch |
EBOM Substitute |
Connects an EBOM or EBOM History relationship
to a Part defined as a substitute. Prevent duplicates is enabled. |
Component Location Find Number Quantity Reference
Designator Usage |
EC Affected Item |
Relationship between Software Changes and Engineering
Changes and the items which will be affected by the change. By default,
Requirements, Products, Features, Test Cases, Use Cases and Builds can
be added as affected items. Prevent duplicates is enabled. This
relationship is used in an expression access so if its name changes,
the expression must change on the policy. See Administrative Objects Used in Expression (Filter) Accesses. |
Reason For Change Requested Change |
EC Distribution List |
Relates Engineering Changes to a Member List.
Prevent duplicates is enabled. |
-- |
EC Impact Analysis |
Relationship between Engineering Changes and
Impact Analyses. Prevent duplicates is enabled. |
-- |
EC Implemented Item |
Relationship between Engineering Changes and
the implemented items. By default, Requirements, Products, Features,
Test Case, Use Case and Builds can be added as implemented items. Prevent
duplicates is enabled. This relationship is used in an expression
access so if its name changes, the expression must change on the policy.
See Administrative Objects Used in Expression (Filter) Accesses. |
-- |
EC Test Case |
Relationship between an Engineering Change and
Test Execution objects. Pevent duplicates is enabled. |
-- |
EC Test Execution |
Relationship between Engineering Changes and
Test Ececution. Prevent duplicates is enabled. |
-- |
ECO Change Request Input |
Indicates which ECRs are driving the ECO. Prevent
duplicates is enabled. |
-- |
ECR Holder |
Identifies the holder object for a company's
ECRs. |
-- |
ECR Main Product Affected |
Connects the product line that is most affected
to the ECR affecting it. |
-- |
ECR Originator Company |
Used to connect ECR to the creator's company. From
side revision and clone rules are Replicate. |
-- |
ECR Reference |
Identifies a supplier-suggested change to a
supplier line item or RFQ Quotiation that may eventually be used to start
a formal change against an engineering part or document. Prevent
duplicates is enabled. |
Line Item Key |
ECR Supporting Document |
Identifies objects that will support the ECR
details, such as markups and sketches. |
-- |
Effecting Out Deviation |
Connects a DCR to an MBOM under deviation by
connecting a DSR MBOM relationship to an MBOM relationship. Prevent
duplicates is enabled. |
-- |
Effectivity Usage |
Hidden. Connects a Named Effectivity type,
or various Requirement and Specification relationships or EBOM Pending relationship, to a Named Effectivity, Model, Product, or Requirement to indicate the usage of an effectivity expression. Parent of Named
Effectivity Usage. |
Effectivity Usage Index |
Effort |
Connects any object type to an Effort object
to track and estimate the effort. |
-- |
| Eligible Application |
Allows a Part to be associated with an eligibleproduct level exemption. Prevent duplicates is enabled. |
-- |
Employee |
List of employees in the organization. From
and To side revision rule is Float. This relationship is used in
an expression access so if its name changes, the expression must change
on the policy. See Administrative Objects Used in Expression (Filter) Accesses. |
-- |
Employee Representative |
Identifies the person who acts as the representative
for a company. To side revision rule is Replicate. Prevent duplicates
is enabled. |
-- |
Enterprise Part |
Connects a Compliance Plant Specific Part to
a Part or Compliance Enterprise Part. From side clone and revision
rule is Replicate. Both the Enterprise Part and Plant Specific
Part relationships connect the same pair of Compliance Enterprise Part
and Compliance Plant Specific Part objects to support fast where-used
expansions. |
-- |
Environment Characteristic |
Connects an Environment to its Environment Characteristic
Values to define the environment in which a Defect was found. |
Environment Characteristic Type |
eService Additional Object |
Connects the Object Generator for a primary
object to the Object Generator for an additional object. |
eService Connect Relation |
eService Number Generator |
Connects a Object Generator to its Number Generator. |
-- |
Exemption |
Indicates that the Compliance Application connected
to the Compliance Definition is exempted from threshold restrictions. Prevent
duplicates is enabled. |
-- |
Export Log |
Connects a Job to an Export Log that contains
messages about the job's export. |
-- |
Feature Breakdown |
Indicates subfeatures for a software feature.
From and To side revision rule is Float./- |
-- |
Feature Design Specification |
Design specification of the software feature,
which serves as implementation reference for software feature. From
side revision and clone rules are Replicate. To side revision rule is
Float. |
-- |
Feature Functional Specification |
Connects a functional specification to the software
feature it describes. From side revision and clone rules are Replicate.
To side revision rule is Float. |
-- |
| Feature Product Configuration |
Connects a Product with the configuration created for a technical feature. From side revision rule is replicate. Prevent duplicates is enabled. |
-- |
Feature Task Breakdown |
Connects a feature to its tasks. From
and To side revision rule is Float. |
-- |
Feature Test Case |
Connects the test case that is used to validate
the attached feature. From side revision and clone rules are Replicate.
To side revision rule is Float. Prevent duplicates is enabled. |
-- |
Feature Test Specification |
Connects a test specification to its software
feature. From side revision and clone rules are Replicate. To side
revision rule is Float. |
-- |
Feature Use Case |
Connects a use case to a feature. From
side revision and clone rules are Replicate. To side revision rule is
Float. Prevent duplicates is enabled. |
-- |
Features Specification |
Describes the feature and its requirements. From
side revision and clone rules are Replicate. Prevent duplicates is enabled. |
-- |
Finalized |
When a revision stream is finalized, the specific
version object chosen as the finalized version is connected to the major
object with this relationship. |
-- |
Financial Items |
Identifies cost and benefit items for a financial
item. |
-- |
Financial Sub Categories |
Identifies subcategories of Financial Cost Category
and Financial Benefit Category. |
-- |