PDXpert PLM Software
On-line Help Guide
This help topic describes the current PDXpert PLM release. Earlier releases may be different. To view your release's version of this topic, open PDXpert and press the F1 key or select the Help menu.
Items: Common elements
Items are system records that contain information about your products. PDXpert has three classes of items:
- A document record describes a part or process, or contains supporting information to assist with procurement, manufacture, test, inspection, or maintenance and repair.
- A part record represents a physical object that is fabricated, purchased, assembled or consumed to produce other parts and, ultimately, final products. The record describes physical properties (such as unit of measure, mass, components) as well as non-physical attributes (regulatory requirements, test procedures or other references).
- A change form identifies a set of part and document records and (a) acts on their current release status (for example, "change notice") or (b) proposes a future action ("change request") or business rules modification ("deviation").
Identification: owner, type, identifier number, description—
Regardless of its purpose, an item always has an owning organization, an item type, an identifier number and a title or description.
Organizations create and manage items; their intellectual and financial investment establishes their ownership in the item.
The organization that licenses and operates PDXpert is defined as the home organization. The home organization owns all original product documentation, part information and design files. The home organization owns all change forms.
Partner organizations — such as suppliers, regulatory agencies, and customers — create and control their own documents and parts, and provide these to the home organization. PDXpert doesn't allow partners to be change form owners.
An item's type defines its properties and behavior — in other words, the rules that it follows.
Once you've selected the type, the defined properties are also selected. If you choose to later change the item type, much of the data that you've entered may be lost as the item re-configures itself to accept the new type's properties and behaviors. Item properties that are not affected by the item type definition are retained.
The item number is a single string of characters, and may be composed of one or more item number components: a static prefix string (which represents, for instance, a part category), a sequential value called the root or base number, and a suffix string.
An item type may subscribe to an identifier sequence, which represents the set of rules for how an item number format is constructed. A sequence can be used by one or more item types.
Name (parts) / Title (documents) / Description (change forms)—
These fields describe the item's purpose and characteristics, and typically use an agreed-upon descriptive format (which can be suggested by assigning an appropriate Text Template value).
Custom attributes are administrator-specified extensions to item properties. These attributes can be defined for all items (documents, parts, changes) and item types (e.g., document Specification, part Assembly, change form Change Notice). Custom attributes are created within the item class or type. Each attribute defined for a specific class/type can have its own properties and user-entered value.
Attached files: Revision / Item / External—
You can attach electronic files that contain design, procurement, process, or other information to an item. Revision files are strictly controlled when the item iteration is released, while item files and external links can be freely added and deleted regardless of the item release state. Revision and item files are managed within PDXpert, and external links point to outside resources.
Change forms do not have revisions, and therefore don't display a revision files list.
This is an item's scratchpad of general information which users with appropriate permissions can modify.
You can see both system-assigned tasks (to correct rule and guideline violations) and trustee- or analyst-assigned tasks. Tasks assigned to you also appear in the Item Explorer's Tasks tab.
Help Guide Contents [PDF]
- 0001. Welcome!
- 0002. Help conventions
- 0100. PDXpert Application Server
- 0101. Server overview
- 0200. How to...
- 0300. Console reference
- 0400. How to start the PDXpert client
- 0500. Program concepts
- 0600. How to set up PDXpert
- 0700. How to use the Item Explorer
- 0800. How to use the Collection Explorer
- 0900. How to work with documents
- 0901. Manage documents
- 1000. How to start a document
- 1003. Fill in the new document
- 1004. Add a document's references
- 1005. Save your document
- 1006. Remove your document
- 1007. Release your document
- 1008. Manage a released document
- 1009. Revise a released document
- 1010. Cancel a released document
- 1100. How to work with parts
- 1101. Manage parts
- 1200. How to start a part
- 1203. Fill in the new part
- 1204. Add, modify or remove BOM parts
- 1205. Import a CAD BOM
- 1206. Add or remove approved sources
- 1207. Add a part's references
- 1208. Save your part
- 1209. Remove your part
- 1210. Release your part
- 1211. Revise a released part
- 1212. Manage a released part
- 1213. Cancel a released part
- 1300. How to revise multiple markups
- 1400. How to work with change forms
- 1401. Processing a change
- 1402. Originate a new change form
- 1403. Analyze a submitted change
- 1404. Fix change processing errors
- 1405. Remove your change form
- 1406. Review a routed change
- 1407. Resolve an on-hold change
- 1408. Analyze an accepted change
- 1409. Use a released change
- 1410. View a completed change
- 1411. Analyze a stopped change
- 1412. View a rejected change
- 1413. Remove a canceled change
- 1414. Return a submitted change
- 1500. How to work with file attachments
- 1600. How to report, import & export
- 1601. Create a report
- 1602. Export a PDX package
- 1603. Use the Report/Export Wizard
- 1700. Import & update items
- 1701. Initialize your PLM database
- 1702. Use the External Data Importer
- 1703. Item Master import
- 1704. Iteration-level relational imports
- 1705. Bill of materials import
- 1706. References import
- 1707. Revision files import
- 1708. Sources import
- 1709. Item-level relational imports
- 1710. Item files & links import
- 1711. Materials import
- 1712. Groups collection import
- 1713. Materials collection import
- 1714. Organizations collection import
- 1715. Persons collection import
- 1716. Custom collection import
- 1800. View & export via ODBC
- 1801. View database objects
- 1802. Create an ODBC connection
- 1803. ItemViews reference
- 1804. ReferencePairViews reference
- 1805. SourcePairViews reference
- 1806. SourceItemMasterView reference
- 1807. StructurePairViews reference
- 1808. ChangeViews reference
- 1809. ChangePairViews reference
- 1810. FilePairMasterView reference
- 1900. How to perform other tasks
- 2000. Menu reference
- 2100. Item Explorer reference
- 2200. Document window reference
- 2300. Part window reference
- 2400. Change Form window reference
- 2500. System Rules reference
- 2501. System Rules window
- 2502. General: Copy files to snapshot
- 2503. General: Item uniqueness definition
- 2504. General: Reviewer's comment required
- 2505. Default File Access
- 2506. Password Policy
- 2507. References Tabs
- 2508. BOM: Allow duplicate parts
- 2509. BOM: Lock part default unit of measure
- 2510. BOM: Allow partner parts
- 2600. Collections reference
- 2601. Managing collections
- 2602. Custom attributes
- 2700. Places/Organizations/Persons
- 2800. General
- 2900. Documents
- 3000. Parts
- 3100. Changes
- 3108. Custom collections
- 3200. Other reference topics
- 3300. Software licenses & legal notices