Common use of Platform Architecture Clause in Contracts

Platform Architecture. This category covers the general requirements for the entire PLATOON platform reference architecture that defines its scope and characteristics: for instance, PLATOON architecture must avoid vendor lock-in providing a technologically agnostic environment leveraging open source components and public standard. The PLATOON reference architecture will be also compliant with other public initiative as the COSMAG reference architecture (3), FIWARE (2), SGAM (4) and IDS (1). In particular IDS reference architecture ensures data sovereignty, security and privacy when sharing data/tools among platform users. In order to be compatible with IDS, PLATOON reference architecture must be able to integrate the main mandatory components of IDS reference architecture, i.e. the connector and the identity provider (a.k.a DAPS). The PLATOON reference architecture must allow some of the components of the reference architecture to be hosted at the component level (e.g. edge computing), on premise and in the cloud. Finally, the PLATOON reference architecture must enable the exploitation of digital services (both data and data analytics tools) through a Marketplace.

Platform Architecture. This category covers the general requirements for the entire PLATOON platform reference architecture that defines its scope and characteristics: for instance, PLATOON architecture must avoid vendor lock-in providing a technologically agnostic environment leveraging open source components and public standard. The PLATOON reference architecture will be also compliant with other public initiative as the COSMAG reference architecture ([3)], FIWARE ([2)], SGAM ([4) ] and IDS ([1)]. In particular IDS reference architecture ensures data sovereignty, security and privacy when sharing data/tools among platform users. In order to be compatible with IDS, PLATOON reference architecture must be able to integrate the main mandatory components of IDS reference architecture, i.e. the connector and the identity provider (a.k.a DAPS). The PLATOON reference architecture must allow some of the components of the reference architecture to be hosted at the component level (e.g. edge computing), on premise and in the cloud. Finally, the PLATOON reference architecture must enable the exploitation of digital services (both data and data analytics tools) through a Marketplace.