A Change specialization that groups the related records and current context of change work. It helps users consider connected problems, tasks, assessments, and product information together.
When to use it
Use it when a change process needs an overall context.
Key information
- Completion percentage records reported progress; review it with the actual work and evidence.
- Due date records when the work is expected to be due.
- Instructions describe what users are expected to do or review.
Common relationships
- Change Context – Project Template (Structure): Places a Project Template within a Change Context’s associated planning structure.
- Change Coordinator (Non-structure): Identifies the Person or Group coordinating an eligible change, issue, or problem record.
- Change Context (Non-structure): Connects a Change Context to related change, problem, assessment, item, document, or phase records. It brings the connected scope of work together.
Working with this record
Use the Change Cockpit as the main UI to manage the Change Context and related change records. Review the connected problems, assessments, plans, and engineering information together; follow the available process for progressing the change.
Example
Seal Improvement Change Context brings together the leakage report, assessment, change request, and implementation work.
Choosing the right type
Choose Change Context for the overall connected change context. Change Request proposes a change, Change Order coordinates implementation, and Change Task identifies an individual activity.
