A moving arrow can stand for a command, a prediction or an observed response. If a film uses the same arrow for all three, viewers may assume that requesting a movement proves the movement occurred. The visual brief should identify which information each element represents before the animation is approved.
MathWorks’ feedback-system example distinguishes the controller's input to the represented plant from the plant's output. That narrow relationship is useful context. The film should not infer actual machine position or performance from a command graphic alone.
Give each information route a name
Ask the expert to identify the requested quantity and the reported quantity in the proposed explanation. They may use different units or refer to different points in a system. Do not merge them simply because both can be drawn beside the same physical component.
A conceptual film can use separate labelled tracks rather than an elaborate technical schematic. The labels should remain visible when the camera moves into a detail view. Otherwise a clear overview can become ambiguous once the audience sees only one animated value.
Allow the response its own behaviour
In a fictional position-display illustration, a desired marker changes while a separately labelled reported marker follows the approved conceptual response. The animation does not need to simulate a real device. It needs to preserve the distinction between what was requested and what the represented measurement reports.
The subject owner should approve any lag, mismatch or stopping point shown. Do not add a dramatic overshoot because it looks dynamic, or make the response perfectly coincide with the request because that looks reassuring. Either choice can imply a performance claim absent from the brief.
Keep observation separate from visualisation
If the film uses actual recorded data, identify its source and context through the approved evidence process. If it uses an illustrative response, label it accordingly. A photorealistic model can make a fictional trace feel measured unless the distinction is explicit.
The production team should also avoid using a display value as proof of physical position without the expert's account of what that value represents. The film explains a supplied information relationship; it does not independently verify the installation.
Review the source of each assertion
Ask a reviewer which element expresses the request and which expresses the reported result. Then ask what evidence the film provides that the result occurred. Their answer should remain within the approved conceptual or measured scope.
If the same visual treatment encourages them to treat the request as confirmation, separate the tracks more clearly. The finished passage should make the information chain intelligible without turning a command into a guarantee, a model into a measurement or a polished animation into proof of real-system behaviour.
Discuss the proposed explanation with Live Images and confirm suitability, production scope and the content owner’s review responsibilities. This unpublished draft uses a fictional example, not a claimed client project.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.