Simple, flexible product lifecycle management software for growing companies™
Simple, flexible product lifecycle management software for growing companies™
The Changes collections define the attributes and workflow for changes that affect your parts and documents.
Change classifications: You can use this collection to specify the impact of a change and which business rules are affected. A typical choice might be to indicate a "non-interchangeable" versus "interchangeable" (backward compatible) change. In a contract-driven or custom-products company, you may prefer to specify whether a change that affects performance, cost and/or schedule requires customer approval.
Change priorities: A change can have significant cost impact. Change costs are often determined by how fast the change must be executed. By setting a change priority, users can control the urgency of implementation, and propose that the change be synchronized to a specific date or serial number.
Change reasons: You can classify the reasons why you decided to make a change. For instance, if you're frequently making changes because your production team has trouble finding specified parts or is constantly discovering lower-cost suppliers, perhaps this indicates a problem in how your designers are choosing vendors.
Disposition actions: Item dispositioning activities, which identify what needs to be done to support the release or cancellation of an item, can be classified beyond what is provided in the default collection.
Disposition locations: You can classify item disposition locations or expenses incurred during the release or cancellation of an item.
Problem sources: A problem source classifies who or what brought an issue to your attention. This can help identify the point at which repeated design, production, and customer issues are occurring.
Reviewer responses: This collection defines PDXpert's internal reviewer responses, and doesn't usually require modification.
Change forms: Smaller companies typically need just a few change types: perhaps a change notice and a deviation/waiver. Larger organizations, or those who work within a regulatory environment, may require the addition of change requests, stop ships, corrective and preventative actions, etc. You may also create change forms based on department responsibilities (production engineering change order, purchased part release, supplier request and others). The ideal is to use as few change forms as possible, each having as few reviewers as possible, coupled to the simplest acceptable workflow.
1207-20100516.1311