Architectural Location for Execution Blocks

 
In ADR-33 How to handle SBI IDs when there is no SBI a proposed solution to the issue was the introduction of the concept of an Execution Block (EB). A key reason for this was to decouple the tracking of a data-taking "session" (sequence of commands to configure the system and use it to take data) from the concept of driving this data-taking using Scheduling Blocks (SBs). This ADR explores the new concept and its purpose, and in particular its relationship to the existing concept of the Scheduling Block Instance (SBI).

Why Now? We are starting to use eb_ids - we should understand what an EB represents

Scope: Integrated testing involving OMC and SDP

Quality: Testability.