In graphics automation projects, the component carrying the most time and risk is not the graphics templates but the data layer. Settling the following points before the project begins allows sound architectural decisions to be made.
1. Data format and delivery method
The format in which the provider supplies data (JSON, XML, proprietary protocol), the delivery method (push, pull, WebSocket) and the update frequency and volume directly determine the design of the integration layer.
2. Latency tolerance
A delay of a few seconds may be acceptable for live scores, whereas market data may require tighter limits. Tolerance determines where caching and validation steps are positioned.
3. Outage scenario
The system's behaviour when the provider fails must be defined in advance: preserving the last validated value, taking the graphic off air or switching to a fallback source.
4. Validation responsibility
To prevent erroneous data from going on air, it must be determined whether rule-based checks, human approval or a combination of both will be applied.
5. Operator intervention
The degree to which the production desk can intervene in the automation — manual correction, temporary hold, scenario change — shapes the interface design.
Dekart Creative begins every broadcast automation project with an analysis phase in which these points are documented and agreed.