IGSN 2040 Technical Model

This document is based on the outcomes of the workshop of the IGSN 2040 Technical
Steering Committee held in Canberra in May 2019 (see Klump et al. 2020) and the
discussions held at the workshop of the IGSN Organisational Steering Committee in
Tacoma, WA, in July 2019. At the technical workshop we started out from the architectural
design principles that should guide the development of the IGSN system architecture. In the
next step, we went through three common IGSN use scenarios and identified the personas1
involved in each step. Having identified the elements of some of the core processes, we
defined which elements were essential to the functioning of the IGSN system (Minimum
Viable Product, MVP).

The outcomes of the technical workshop in May 2019 were discussed at the organisational
workshop in July 2019. The organisational workshop analysed the value proposition of IGSN
and the requirements that have to be met to implement the value proposition.

The definition of an MVP does not mean that IGSN should not offer any services beyond the
MVP. Instead, the MVP should be seen as a starting point with further services added in the
future as additional resources become available.

In this document, we also want to make a clear distinction between different roles in the
IGSN system to define which functions should be core functions of the IGSN Organisation
(IGSN e.V.), of the IGSN Agents, and which functions are performed by the IGSN user
community. For IGSN e.V. this means that some functions are essential to its purpose, while
other functions can be added in the future, possibly as revenue-generating services.