Recall first, from memory. Then run one field change through the change-impact matrix. Then Riverside.
Answer from memory before you flip back.
The lane boundary: name one thing the engineer owns during execution and one thing the project manager owns.
When a change is requested in the field, what is your first question, and what is it never?
Why is an as-built a legal document, and who pays if it doesn't match what was actually built?
Run the change below through the matrix. For each element, write what you would check and whether the change touches it. The last two rows are blank: name elements the change reaches that aren't already listed.
A structural column is in the way of the conveyor run as drawn. Moving the run eighteen inches to the left clears it. The installer wants a yes. Evaluate it at the system level, not just at the column.
| Downstream element | What I check, and does the change touch it? |
|---|---|
| Curve geometry | |
| Accumulation zone length | |
| Sensor placement / PLC delay | |
| Pull-cord spacing | |
When your list stops growing, ask: did I find them all, or just the obvious ones? What design work has to happen before the field proceeds?