This topic is contained in the PDXpert help file: select Contents from the application's Help menu.
Change reasons
Purpose
Classifies the rationale for making a change, so that managers can assess the design and development process.
A Change Reason describes why you took action to make a change. A Problem Source classifies how an issue was discovered.
Where used
Change form
Data fields
- Name
- This is the complete name for the change reason.
- Description
- This describes the change reason in more detail.
- Compatibility code
- Specifies the required database code for EIA-649 environments. This field may be safely ignored or used for other purposes in other environments.
- Active: users can select
- Default member of collection
- Permanent member of collection
- For a description of these checkboxes, see the Collections reference > Common properties & attributes help topic.
Setup suggestions
This collection may need to reflect aerospace/military contractor or regulatory requirements.
Without crisp definitions and clear categories, this collection can become confusingly similar to the Problem Sources collection. Ensure that your users can easily distinguish between a problem source and its change reason, or simply use only one of these collections.
In addition, this collection can grow large and unwieldy. Try to restrict the number of members in order to get "big picture" trends that can help your product management process. It's easier to spot significant drivers of change when there are fewer groups with significant activity, rather than offering users tens (or hundreds) of detailed reasons with only one or two instances of each.
2011
Help topics describe the most current PDXpert PLM software release, and may differ from earlier releases.
