A Change Request proposes a change to product information or another managed definition. It records why the change is needed and what should be considered before implementation work is organized.
When to use it
- Use it when a proposed modification needs review and evaluation.
- Use it to connect the reason for change to affected records, requirements, risks, and assessments.
Key information
- Proposal identity: change request ID, name, description, and title.
- Reason and scope: change reason, synopsis, summary, category, and classification.
- Coordination: priority, owner, state, due date, and review date.
Common relationships
- Affected Item identifies the managed information the proposal may change.
- Change – Impact connects an Enterprise Change Assessment to the proposal.
- Change Request – Change Order links the proposal to implementation coordination.
Working with this record
Explain the need, identify the affected records and revisions, and connect the information needed for evaluation. Follow the available review process before treating the proposal as an implementation decision. Keep the proposal distinct from the resulting changes to engineering records.
Example
A Change Request proposes improving Seal S-10 after leakage testing. It identifies the affected seal and drawing, links an assessment of the impact, and can connect to a Change Order that coordinates the agreed implementation work.
Choosing the right type
Choose Change Request for the proposal. Choose Change Order for implementation coordination and Change Task for an individual change activity. A proposed change and a revised engineering record serve different purposes.
