Purpose: The purpose of this exercise is to group together similar parts. This can be useful when querying for specific parts. It is possible to connect a document requirement profile to a class. This will require that the profile is fulfilled before the part can be released.
Windows:
Product Basic Data/Classes
Purpose: The purpose of this exercise is to group similar parts together at a high level. This can be useful when querying for specific parts.
Windows:
Product Basic Data/Main Groups
Purpose: The purpose of this exercise is to describe the current development stage of a part revision. The development level is for information only. (This is not the same as part status.)
Windows:
Product Basic Data/Develop Levels
Purpose: The purpose of this exercise is to learn about the default values that are specific for each installation.
Windows:
Product Basic Data/Defaults
UNIT_CODE: The engineering part’s initial setting for unit of measurement. The value specified here is the default value when creating new parts. This value must also be registered in Application Services/Units of Measure. |
DEVELOP_LEV: The initial setting for the development level of a part revision. The value specified here must also be registered in the Product Basic Data/Develop Levels tab. |
PART_REV: The default engineering part’s revision name. If the default is set to A, the initial revision gets the default value A, the next revision is B, etc. If the default is set to R01, the initial revision gets the default value R01, the second revision R02, etc. |
PDMCON_SITE: Specifies which site to retrieve standard part cost and lead time information from Inventory when running the "Update Cost and Leadtime" from Inventory function. |
POS: Default pos number. This parameter is used only by the CAD Interface. |
REPLACE_REVISION: The engineering part’s replace revision level. This value controls the statuses in which a part revision can be replaced. Choose Replace Revision in Engineering Part Revision/Revision from the right mouse button menu. See the help documentation for the description of the valid values. |
Purpose: The purpose of this exercise is to categorize a product into different product types. This is used to classify the different Main Groups in the Product and Model functionality.
Windows:
Product Basic Data/Product Type
Purpose: The purpose of this exercise is to to assign functions/systems to product models. This is used in the engineering structure definition. The purpose is to organize the product structure in a way familiar to multiple disciplines and to provide help with the construction of a product without having to immediately decide all its properties. The engineering function structure is a conceptual level of product construction. Functions can be arranged in a structure, and each function on the bottom/last level can also have parts and their respective part structures attached.
Windows:
Product Basic Data/Functions
Purpose: The purpose of this exercise is to be able to translate standard names to different languages. This is for standardization and translation purposes. When running PDM-Configuration, the values in Std. Names fields will be translated to the language you are using, if that language is registered in this window.
Windows:
Product Basic Data/Std.Name Lang
Purpose: The purpose of this exercise is to establish the engineering units of measurement that are in use for products and parts.
Windows:
Product Basic Data/Unit Relationships Base
Product Basic Data/Unit Relationsships/Derived
Product Basic Data/Unit Relationsships/Conversion
Purpose: The purpose of this exercise is to enable electronic approval of documents. Each step must be linked to either a person or a group.
Windows:
Product Basic Data/Approval Template
Purpose: The purpose of this exercise is to determine the type of document(s) that must be connected to an object. A document of each document class must be connected to the object before the document requirements are considered met. The direction indicates whether the document is required when the part arrives or if it is required when sending the part for production or construction or to customer.
Windows:
Product Basic Data/Document Req
Purpose: The purpose of this exercise is to define people that may be used in the design/project environment so that they may be associated to relevant information in IFS Engineering. When a person is registered here the person will be available in the 'list of values' in other forms. For example as a project manager. An UserID can be connected to a person. One UserID can only be connected to one person. It is not necessary to connect an UserID, but to be able to use the person in an approval routing, or distribution of documents, the field User must be defined.
Windows:
Persons
Purpose: The purpose of this exercise is to be able to enter a manufacturer for an engineering part, the manufacturer must be registered here. Multiple manufacturers may be listed for a part. The manufacturer is added as a Party with a Party ID into IFS Enterprise. A default language and country code may be associated using the List of Values. These languages and countries need to have been previously enabled in Application Services ISO codes.
Windows:
Manufacturers