General tab (part)

The General tab provides the basic information about the part: its name, its identifier number, who created it and when, the product families that use it, and its lifecycle phase.

Part
The item class icon indicates the current part iteration release status:
Pending part icon Pending
Released part icon Released
Canceled part icon Canceled
You can drag the icon and drop it onto a destination, such as another item's markup list or a change form's affected list.
Owner
This is the organization that is responsible for the design and construction of the part, and controls its technical content. Typically, your own organization is responsible for parts that are fabricated according to your designs, processes, and procedures. Partner organizations can own parts, which your organization then can use in your products or for supporting your production process.
Type
The type defines the part's attributes and behaviors (like numbering, revision format, custom attributes, etc.), which are controlled by its Part Types collection member.
The Type cannot be edited. If you want to apply a different part type, you must convert the part and let PDXpert copy whatever it can from the old part using the new Part Type's rules. You can then remove the unwanted part from your system or, if it's been released, cancel the released iteration.
Lifecycle phase
Independent of technical content revisions, a part is assigned a level of "business maturity." For instance, your initial design may be assigned a Preliminary lifecycle, intended for internal discussion. As your confidence in the part's accuracy and relevance develops, you may build a small quantity of Prototype parts to verify fit and performance. When the part is proven, you release it at an unrestricted, or Production, lifecycle. These lifecycle states represent business uses, and may include multiple technical revisions or a single design.
Lifecycle selections are defined in the Item lifecycle phases collection.
If the Part Types collection member specifies a Subsequent revision sequence, after selecting a new Lifecycle phase value, verify that the Revision is correct.
Number

The part number uniquely identifies a physical item located in a particular inventory location. The Owner and Type determine how part numbers are assigned:

  • Parts designed and controlled by your home organization are assigned a number based on the part type:

    • Manually: You can enter your own number or click the 123 button to assign a new number, and further edit the assigned value. The Number textbox and the 123 button are both enabled.

    • Automatically: The Number field, as well as the 123 "AutoNumber" button on the right-most end of the textbox, is locked and the part number is already present.

  • Parts designed and controlled by partner organizations are assigned part numbers by those organizations. The Number field is editable and the 123 button disabled.

The auto-number format and value are defined in a Sequences: Identifier collection member, which is then used by the current part type.

A part number uniquely identifies the item and represents a distinct inventory location. You should assume that home parts with the same number but different part types or revisions are freely mixed in the same inventory bin.

Data revision

A part revision identifies each step in the evolution of a part record's technical content.

Normally, a part iteration that results in significantly altered ("non-interchangeable") physical item is assigned a new part number. Modifications that simply add to the data record's content in minor ways, clarify technical information, or correct clerical errors likely retain the same part number, but require a new record revision identifier.

PDXpert automatically assigns the most recent released part record iteration to a parent assembly. If you do not want the current iteration to be assigned to previously released parent assemblies, you must create a new part number for the item and explicitly assign it to a new iteration of the parent, and then release these on a change form.

By convention, a physical part itself has no revision identifier. The PDXpert part Data revision field refers to a specific database metadata record, which may be revised without affecting part interchangeability. Parts with the same number but different metadata record revisions can be freely mixed with earlier parts in the same inventory bin. If a part iteration is not interchangeable with preceding iterations of that part, then the new iteration requires a separate inventory location, and therefore a new PDXpert part record. Although the revision identifier should never be considered relevant for inventory management, production or servicing, some organizations may mark a metadata revision on the part.

The revision's 123 button sets the revision value to the starting value of the current revision sequence.

Version
A version is any number of characters that you assign to distinguish parts with the same part number. The Version field may be displayed or hidden, depending on whether your administrator permits the selected part type to have versions.
A part version distinguishes earlier iterations of a part from later ones. Unlike a record revision, which is managed by PDXpert, the version is created by an outside entity - a person or another computer application, such as a software compiler - and manually entered here. If both revisions and versions are used for a part, creating a new version also changes the part record revision.
Part name
The part name provides an indexed, searchable description of the part's purpose and application.
The starting value is copied from the part type's Text template value. See the Collections reference > Documents > Part Types: Part name template help topic.
The Name{a} button merges the current values on the Custom tab into the part type's Text template. The button is visible only when custom attributes have been defined on the part type. To create a new part name, first enter the custom attribute values, and then click the Name{a} button to create the name. The new name completely replaces the previous name. You can edit the new name after the custom attributes have been merged.
Keep in mind any naming constraints of downstream computer systems, such as MRP/ERP. Export queries can, for example, convert the name to uppercase but can't always accurately trim part names that are too long.
Trustee
This is the person who has overall responsibility for the part's contents. The trustee can edit fields, build the part's BOM and assign sources or references, attach files, and add the part to a change form's Affected tab. The current trustee, as well an analyst, can re-assign the part to another user, who becomes the new trustee.
Revision area
If a part has been affected in a particular location (for example, "main valve", "power switch") or database attribute ("Default unit of measure") you can highlight that information here.
Language
The part may have labels or other nomenclature in this language, which need not be the same language as that used by PDXpert. When a new part is created, the owning organization's default language is copied to this field, but the value can be overridden.
Product families
Product families restrict who can work with the items based on permissions granted within a product family's collection member. If you do not specify a product family, then any user role with general part permissions can view the part.
Release description
The Release description summarizes how the current iteration has been changed, and is shown on the change form Affected list as a brief note to reviewers.
Released

The system marks the checkbox when the part iteration record is released for use.

  • If the iteration is not on any implementing change form's Affected list, then both the checkbox and the accompanying text field are empty.
  • If the iteration is assigned to an implementing change form but is not yet released, then the checkbox is empty. The accompanying text field displays the change form that will release the iteration.
  • If the iteration is released, then the system marks the checkbox and shows the change form that released it.

Double-click the change number to open the related change form.

Release date
This date indicates when the part record iteration was released on the releasing change form.
Canceled

The system marks the checkbox when the part iteration record is replaced by a later iteration, or the part is withdrawn from use.

  • If the iteration is not on any implementing change form's Affected list, then both the checkbox and the accompanying text field are empty.
  • If the iteration is assigned to an implementing change form but is not yet canceled, then the checkbox is empty. The accompanying text field displays the change form that will cancel the iteration.
  • If the iteration is canceled, then the system marks the checkbox and shows the change form that canceled it.

Double-click the change number to open the related change form.

Cancel date
This date indicates when the part iteration was canceled.
Effectivity
This value indicates when the items on the assembly BOM are used to produce the current assembly iteration. You can set the Effectivity value to allow for production lead times between the time that the assembly is released on a change form, and when the parts can be used on the assembly.
The Effectivity value is displayed only for assemblies (that is, where the BOM tab's Markup list is enabled), since an individual component is always effective on its Release date.
Snapshot from
If you've created the part by copying it from another item (Edit | Snapshot Duplicate...), then this textbox displays the original item. Double-clicking on the displayed item opens it.

1063

Learn More
Help Guide Contents [PDF]