Part types

Collection Explorer ◢ Parts group ◢ Part Types collection

Other users should not be using the system while you're working. Close all item records in your workspace before you begin. close the PDXpert client and start it again when you've finished.

Purpose §

Classifies parts according to their application, and defines their rules and custom properties.

A part type defines unique business rules and behaviors. It's not useful as a part category or search tag because, once assigned to a part, it can never be changed (the part must be canceled and replaced). If you want a simple category or searchable tag, use the part name or a custom attribute.

Where used §

Parts

Data fields §

Some data fields show a character counter in the upper right of the box. This is helpful for editing a custom label, and for data that may be exported to other systems that limit imported text length.

General §

Name §

This is the complete name for the part type.

Display name §

This is the name that is shown in lists and reports to save space. It should be as short as possible, preferably fewer than 10 characters.

Description §

This gives the part type and its function.

The following four checkboxes show or hide data lists on a part record. After making parts while a list is enabled, don't hide the list. Hiding the list does not delete any data on the part. A part's Appears On lists may identify parent items where the part is used, but hidden.

Show Materials list §

When this checkbox is marked, the Materials information is visible. Materials (chemical substances) can be added to the part.

The Part mass (weight) is available only when the Materials page is shown.

Show BOM list §

When this checkbox is marked, the BOM lists are visible. Component parts can be added to the part.

Show Sources list §

When this checkbox is marked, the Sources lists are visible. Approved manufacturer sources can be added to the part.

Show Files list §

When this checkbox is marked, the Files lists are visible. Revision files, item files and external links can be added to the part.

If any files have been attached to parts, and then this checkbox is cleared, the Files lists—and attached files—are hidden. The files are not deleted. To ensure visibility and access, this checkbox must remain marked after it is set.

Active: users can select
Default member of collection
Permanent member of collection §

See the Managing collections: Common attributes help topic.

Attributes §

Item number §

Use these settings to assign the part's Number value.

Identifier sequence §

This dropdown list lets you select an identifier sequence (number generator) for the part type. You can choose a single number sequence for all part types, or you can designate a separate sequence just for electrical components, a different one for mechanical components, etc. The selections for this are managed in the Sequences: Identifier collection.

User cannot edit assigned number §

When this checkbox is marked, a new part identifier cannot be modified after it is set. When this checkbox is cleared, the creator/trustee can (a) manually enter an identifier and/or (b) request a new identifier string and edit it after the system sets it.

See note at Administrator Override command.

Revision/version §

These settings define rules for the part's Revision and Version.

Initial revision sequence §

This lets you specify the revision format for the part type. The selections for this are managed in the Sequences: Revision collection.

Subsequent revision sequence §

This lets you specify a production revision format that's different from the initial revision sequence.

When an item moves to a lifecycle with relative maturity value of 0 or greater (for instance, Production or Service), the subsequent revision sequence format is used.

If one revision format is used for the entire part lifecycle, leave this field empty so that the initial revision continues into production.

Using a subsequent revision sequence may confuse vendors and employees with unnecessary data changes. Instead of changing the revision when the part's maturity has changed, rely on the lifecycle phase to specify when it's ready for production.

Warn on duplicate revision §

When this is marked, a warning is shown if the pending iteration's revision identifier has been used for an earlier revision. Setting this encourages users to assign a unique revision value for all item iterations, even when there's no change to the technical content – for example, the lifecycle has changed.

User cannot edit assigned revision §

This checkbox sets whether users can modify the revision given by the system, or whether the value is permanent.

Let users edit revisions to items owned by partner organizations, since the item revision is not controlled within PDXpert.

Show Version field §

When this checkbox is marked, the version attribute is shown on the part window, in lists and on reports. When this checkbox is cleared, the version attribute is hidden.

The item's Revision area expands when this field is not shown.

A part typically won't have versions. However, if the part type is closely related to an electronic file (for instance, it is a masked ROM), and that file is identified by version, you may want to enable the version field for the related part type.

Keep in mind that if a part number has multiple versions, all versions may be put into a single inventory bin and freely mixed in production. If versions are not interchangeable, give each version its own unique part number.

Default lifecycle phase §

The selected Item Lifecycle Phase collection member is used when a new part is made.

Purchased parts and their manufacturer sources are always set at Production lifecycle. You cannot alter a source part's technical content, but must accept or disqualify the content offered by the manufacturer.

Show a Person #1 role §

Marking the checkbox lets users identify a person with some responsibility for the part. Each new part iteration can show a different person. For example, you may want trustees to identify the designer responsible for the part.

If this checkbox is cleared, then the person #1 dropdown list isn't shown on the part window.

These Person #1 / #2 controls are useful if your company has adopted the Institute for the Process Excellence (ipxhq.com) change management process.

Each item is the exclusive responsibility of the item's (1) creator-designer, and (2) consumer-user-implementer (for example, the design engineer and the production supervisor). The goal is that if these two people agree, no others are needed to approve changes, eliminating non-essential change reviewers. These persons are identified for each new iteration.

Maintaining this data can be somewhat burdensome in practice, so consider enabling these fields only for selected types. Reviewing groups can also be limited using the change workflow.

Person #1 role label §

This textbox shows the person's function. For example, you can use Designer or Specified by as the label on the part window.

Show a Person #2 role §

Marking the checkbox lets users identify a person with some responsibility for the part. Each new part iteration can show a different person. For example, you may want trustees to identify the part's production user or field service engineer.

If this checkbox is cleared, then the person #2 dropdown list isn't shown on the part window.

Person #2 role label §

This textbox shows the person's function. For example, you can use Prototyped by or Validated by as the label on the part window.

The item's Release description area expands when both Person #1 and Person #2 fields are not shown.

Default unit of measure §

The selected Unit of Measure collection member is used when a new part is made.

Default make/buy §

The selected Make/Buy Category collection member is used when a new part is made.

User cannot edit assigned make/buy value §

When this checkbox is marked, the value given by the Default make/buy (above) cannot be modified. For example, standard purchased components will typically be marked (since it's very likely that, say, a standard machine screw will always be bought), while custom fabrications and in-house assemblies will typically be cleared to enable outsourcing.

Show compliance checkbox §

For parts that are subject to regulatory requirements, show a checkbox that tells whether the part is in compliance.

Compliance label §

This textbox lets you label the compliance standard(s) that must be met by parts based on this type. You can leave it rather generic, such as Meets regulatory requirements or more specific to the part type, such as Meets RoHS/WEEE regulations.

Part name template §

When a new part is first made, the part's Name (description) field will automatically be loaded with this text value, which the user can then edit. Defining a useful part name template enhances consistency, which makes items easier to locate.

Suggest information that the user should enter as [hint], such as [power rating]. Consistent part names are more predictable, and easier to search.

A text template can include custom attribute names as {custom attribute name}. After making a new part record, clicking the Name{a} button replaces the custom attribute's name with its actual value. For example, a custom attribute named Length, with an actual value of 50 mm, can be inserted using a text template like SCREW, {Length} {Length++@U}, PLATED to obtain a part name SCREW, 50 MM, PLATED. See the Custom attributes: Inserting custom attribute values into an item name help topic.

Custom list §

You can define custom attributes (or "properties" or "extensions") to the system-supplied attributes for each part type. When a new part is made, any custom attributes are shown on the part's Custom page.

Before working with custom attributes, refer to the Custom attributes help topic for important information.

Setup §

Limit the number of part types to broad easily-distinguished categories. Your users shouldn't have to puzzle over whether to categorize a machine screw as hardware or a fastener, or an LED as a diode or a display device.

Part types should be used to make computer searches easier with distinct names and abbreviations. For example, let users search for the Assembly part type using a simpler abbreviation like Assy.

2035