Start with the package boundary
Coordination reference
Group shutdown work so participants can see which packages affect the same line, shared service, access window, supplier, or restart dependency. Record assignments and execution details only in the authorized work system. The matrix below is an authored planning example, not a work queue or approved scope.
When a task crosses a package boundary, identify the affected owner roles and carry the dependency to the interfaces review.
Illustrative scope matrix
Fictional Harbor Plant example; owner labels are roles, not assigned people.
| Area or boundary | Example work package | Coordination interface | Planning owner role |
|---|---|---|---|
| Packaging line | Planned inspection and component replacement | Shared access window with the utilities package | Maintenance planner |
| Shared utilities | Planned service work affecting two production lines | Sequence alignment with packaging and assembly teams | Shutdown coordinator |
| Assembly line | Planned equipment work and post-work review | Supplier staging must not conflict with shared access | Area operations lead |
Separate shared dependencies from local tasks
A coordination example, not an execution instruction
Shared shutdown dependency
In the fictional example, a utilities package affects both packaging and assembly planning. Record the dependency and affected owner roles in the authorized system, then review the sequence together.
- Name each affected area.
- Identify who owns the planning handoff.
- Carry unresolved conflicts to the local shutdown coordination route.
Line-specific task
A fictional packaging-line component replacement may belong to one work package while its timing still depends on a shared service window. Keep the task and cross-package dependency distinct.
- Keep assignment and execution details in the authorized work system.
- Bring shared timing questions to the interface review.