Problem sources

Purpose §

Broadly classifies how the problem that caused a change was discovered, so that managers can assess development and production processes.

A Problem Source classifies how an issue was discovered. A Change Reason describes why you took action to make a change.

Where used §

Change form

Data fields §

Name §
This is the complete name for the problem source.
Description §
This describes the problem source and its function.
Active: users can select
Default member of collection
Permanent member of collection
For a description of these checkboxes, see the Collections reference > Managing collections 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 Change Reasons 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 process problems when there are groups with significant activity, rather than tens (or hundreds) of detailed problems with only one or two instances of each issue.

2010

Learn More
Help Guide Contents [PDF]