What you get/Ranked improvements
A list of everything wrong with a process is not useful. A list of what to do first, with the reasoning attached, is the thing that actually moves the argument along.
Each improvement with what it would take, what it returns and what the study saw that led to it. Ordered by payback, so the conversation with a plant manager starts from the top of the list instead of from the middle of a spreadsheet.
Because the constraint is not how many CI engineers you have, it is that observation is serial. One person watches one station, on one shift, once. A second engineer doubles that and takes six months to become useful on your processes.
Observation is the part that stops being serial. A CI team shift covers 10x more of the plant minimally, and a supervisor can get answers as well. The engineer you already have spends the week deciding what to change rather than capturing and writing up.
One clip and an afternoon. There is no installation, no network work and nothing to schedule with IT before you know whether it is any good. Bring one process you already argue about and read what comes back.
Start at the top of the list. That is the whole idea.
Talk to an expert