Problem sources

Collection Explorer Changes group Problem Sources collection

Purpose§

Classifies how the problem that caused a change was discovered, so that managers can assess design, production, quality and service procedures.

A Problem Source tells how an issue was found. A Change Reason tells why you need to make a change.

Where used§

Change form

Data fields§

Name§
This is the complete name for the problem source.
Description§
This gives the problem source and its function.
Active: users can select
Default member of collection
Permanent member of collection§
See the Managing collections: Common attributes help topic.

Setup§

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.

This collection can grow large and unwieldy. Try to limit the number of members to get "big picture" trends that can help your product management procedure. It's easier to spot trends using several broad categories, rather than offering users many detailed reasons with only a few instances of each.

2010

Help Guide Contents [as PDF]