CommuniCity Technical Framework
The objective of CommuniCity’s technical framework is to provide a set of assets, such as specifications and software, to support the design and development of innovative solutions. This technical framework is to be implemented by the Piloting Teams, and experimented in the cities.
The main aim of the technical framework is twofold:
– Firstly, the assets help developers to speed up and simplify the implementation of the technological solutions that must be provided within the limited timeframe of the CommuniCity Open Call rounds.
– Secondly, tools must be provided to enable the interoperability between existent cities’ IT infrastructures/systems and developers’ solutions. Furthermore, most importantly, to achieve replicability of developed applications and services across different cities involved in the CommuniCity
To achieve these objectives CommuniCity proposes a high-level technical architecture that defines some logical elements that are developed and provided in different phases of the CommuniCity Open Calls:
Specification and API
Figure 1 – Communicity high level technical architecture
As seen above, the Specification and Application Programming Interface (API) layer represents the logical and functional specifications of the interoperability components of the technical architecture. Its scope is to provide common standards and building blocks to developers that deliver solutions for the cities during the CommuniCity Open Call rounds. The basic pillars of these specifications are represented by the OASC (Open & Agile Smart Cities) Minimal Interoperability Mechanisms (MIMs).
Minimal Interoperability Mechanisms are universal tools for achieving interoperability of data, systems, and services between cities and suppliers around the world. MIMs are based on a set of baseline specifications and references related to the different cities and communities that are part of the OASC (Open & Agile Smart Cities) network.
The MIMs are vendor-neutral and technology-agnostic, meaning that anybody can use them and integrate them in existing systems and offerings. MIMs are based on common specifications but the concrete technical implementation can be different, as long as crucial interoperability points in any given technical architecture use the same interoperability mechanisms.
The MIMs are governed through a specific process that starts from proposal from one partner of the OASC network followed by improvements by other members and finally approved by the Council of Cities (CoC), representing all OASC cities across 4 continents.
The toolbox is a compilation of concrete software components and services that are provided by CommuniCity project to be used by developers during the three rounds of CommuniCity Open Calls. It offers technical tools that comply with the specification and API layer as well as represent a reference implementation of the MIMs.
Different categories of technological assets are available in the Toolbox, including:
Software as a service (for example, AI algorithms) are available in a dedicated cloud environment and accessible via web applications, rest APIs or specific SDK (Software Development Kit).
The toolbox offers not only software and services based on MIMs but also other components that can be useful to achieve interoperability. Furthermore, it offers components to standardise applications in terms of data representation and API access to software capabilities.
The collection of technological assets included in the toolbox will expand over the course of the CommuniCity project to provide increasingly advanced and comprehensive resources tailored to the requirements and specificities of each open call round. In addition, already existing assets originated from relevant European projects and initiatives, open-source software, and CommuniCity consortium partners’ solutions are also included in the toolbox.
The sandbox is a cloud environment where developers can test if their solutions are in compliance with CommuniCity specifications. This allows them to incorporate and execute some of the key components of the toolbox using preconfigured “recipes”, as well as to interact with external application and services.
The main scope of the sandbox is:
Similar to the toolbox, the cloud resources and components available in the sandbox will be improved during the different phase of the project to better support the developers involved in the open calls.
Adeeb Sidani – Porto Digital
Martino Maggio – Engineering