Common use of Conceptual Model Clause in Contracts

Conceptual Model. ‌ ESAP, in and of itself, provides no compute or analysis capabilities (beyond a simple ability to view tabular data and preview images). Rather, it acts as a broker between users and the various query and analysis services which are available to them. These might include, for example: • bulk data query systems, which can help the user locate and access data files (images, visibility data, etc) in archives, data lakes, or similar bulk storage systems; • tabular data query systems, which can help the user find relevant entries in source catalogues and similar relational systems; • Interactive Data Analysis (▇▇▇) systems, which provide the user compute and visualization tools in a convenient environment with access to relevant datasets (for example, a Jupyter [7] notebook, or con‐ tainerized analysis application); • bulk data processing systems, which provide batch (non‐interactive) processing of data at‐scale in HPC or HTC environments; • scientific software repositories, which provide access to specialist analysis tools and workflows; A given instance of ESAP is configured with information about available services1. When a user connects, the ESAP instance should: • help the user select services which are relevant to them (for example, by clearly presenting the available services; by making clear what science cases those services support, by taking account of the user’s access privileges, etc); • facilitate authentication and authorization with the various services, as necessary; • provide a consistent and convenient way for the user to access services (for example, by providing the user with a single way to enter a particular query, and then automatically translating that to the requirements of each individual service); • mediate data flow between services (for example, by enabling the user to locate data with an archive query, dispatch the data to the processing facility, and schedule processing of the data on a bulk data processing system). This relationship is illustrated schematically in Fig. 1: this shows the end user communicating directly with ESAP, which mediates their interactions with a range of other services, deployed across a variety of different infrastructures. Note that the user communicates with a single ESAP instance, while that instance mediates interactions with a range of different services from a variety of infrastructure providers.