NAPCORE

Material Hub

M2.1 Typology of NAPs based on the description of levels of service and assessment of associated costs and benefits
This milestone describes the development of the NKLF as well as the “why”, “for whom” and “how” the NLKF tool can be used in the context of NAPCORE NAP LoS harmonization activities. The milestone takes input from Work Item 2.1.1 the main goal of which was to support the understanding of the current state of play within the European NAP ecosystem as well as the recording of existing best practices and common NAP features. Finally, this milestone sets the basis for the listing of gaps and actions needed towards NAP interoperability and minimum level of service, which is the focal point of Work Item 2.1.3.

NAP LoS KPI Framework
The main outcome of the works carried out under this task is a tool to assess a NAP LoS based on a
framework of Key Performance Indicators (KPIs), which are related to the offered NAP interoperability
features and services. The “NAP LoS KPI Framework tool” (NLKF) is used by NAP operators as a self-assessment survey in periodic (yearly) scoring exercises, started in 2023 and continued in 2024 and 2025.

M2.2 Overview of gaps and actions needed
This internal report is aimed at achieving several objectives.
Firstly, it identifies and documents gaps as well as necessary actions pertaining to interoperability (including technical, legal, and organizational aspects) and Levels of Service essential for the adoption of NAPs by diverse Member States.
Secondly, the report aims to develop recommendations for a phased approach to assist Member States in navigating towards more sophisticated NAP architectures.
Lastly, it seeks to lay out an initial framework for a potential European NAP or a federation of European NAPs, in close collaboration with T2.4, WG1, and SWG4.4.

M2.4 List of gaps and used standards

M2.6 Interoperable NAP demonstrator with real world use of the NAP information
This report presents the idea and reasoning behind the interoperability demonstrator making use of real-time safety related transport information cross border.
It describes why the use of the Improved Interface (II) and Basic Interface (BI) capabilities of the interchange makes it easy for service providers to find and access transport-related data using the NAPs, and afterwards describes the result of the demonstration carried out to “test” the idea with a real service provider.
The report also lists implementation possibilities resulting in NAP improvements and increased level of service.

M2.7 An updated list of requirements concerning the use of data standards, profiles and metadata
This report investigates crucial interoperability aspects of the mobility domain, namely data standards, recommended profiles, and metadata. Through comprehensive analysis of existing efforts, it identifies gaps in these areas and explores strategies to address them. Drawing from targeted research and expert review, the report offers recommendations to enhance interoperability and streamline mobility data exchange, particularly those listed in the ITS directive delegated regulations.

M2.9 Harmonisation of EU NAP architectures and first layout of potential NAP federation
This report outlines the harmonization activities, technical procedures, and developmental steps taken to achieve a NAP reference architecture. The architecture consolidates all NAPCORE National Access Point harmonization activities. While this document does not describe the final architecture due to ongoing developments in NAP harmonization, it does include and represent all achievements and results currently available within NAPCORE. Future results and further harmonizations from ongoing NAPCORE developments will be continuously integrated into the architecture, as outlined in the maintenance procedure.

M2.9 Annex A – NAP Reference Architecture

M2.9 Annex B – Interoperability Documents
The interoperability document is any type of document that could be beneficial in implementation or upgrade of NAP. The benefit lies in the recommended / practiced approach to do something. It spans from recommendations to use terminology, naming conventions of data sets, keywords, used metadata catalogues, profiles, protocols or data location content.

M2.9 Annex C – Porto workshop on NAP Reference Architecture

M2.10 Interoperability demonstrators with real-world use of data and different Levels of Service – 2nd round
This document presents four interoperability demonstrators aimed at improving cross-border mobility data exchange and ITS service continuity. The demonstrators include (meta)data solutions for topics of common interest, such as interchanges, marketplaces, metadata and alternative fuels. The document summarises the demonstrators’ scopes, architectures, and key outcomes. Organized into four sections, the report highlights findings and lessons learnt, with further technical details provided in the Annexes.

M2.10 Annex A – Interoperable NAP demonstrator of a marketplace or clearing house NAP
This document describes the development of a cross-border ‘marketplace demonstrator’ as part of NAPCORE Work item 2.4.3 which is part of task 2.4.
In this document, the functional operation of the demonstrator is described in detail. Based on the functional operation, it is explained which technical solution has been developed.

M2.10 Annex B – Metadata demonstrator with real-world use of data and different Levels of Service
This report provides insights on NAP interoperability regarding the use of metadata across NAPs. It goes specifically about the limitations of the current NAP Architecture regarding metadata extraction and dissemination. Recommendations to improve the general scenario of MS’s NAPs interoperability and harmonisation are tackled in this document.

M2.10 Annex C – Alternative Fuels demonstrator with real-world use of data and different Levels of Service
This report provides insights on NAP interoperability regarding the exchange of Alternative Fuels data. It comprises the several steps of work of the development of an Alternative Fuels Demonstrator using the NAPs. The analysis identified important aspects needed to increase the availability of AF data throughout the NAPs. Moreover, it draws the current scenario of NAPs in the context of Alternative Fuels, providing some baseline for other EU-initiatives that aim to enhance the adoption of AF infrastructure by road users, particularly to the discoverability of AF data.

M2.10 Annex D – Scoping of Demonstrators Expectations
This internal document compiles information related to the scoping of the four interoperability demonstrators that are part of NAPCORE WG2 (Task 2.4). It aims to define the overall scope of each demonstrator, outline their expected outcomes, and specify how the documentation should be structured. The document sets goals and objectives for the demonstrators, along with their prerequisites and anticipated challenges. It is intended to be used throughout the development and evaluation of the demonstrators.

M2.11 NAPCORE harmonised EU NAP architectures
The deliverable describes the crucial parts of the final version 2 of the Reference Architecture of National Access Points (NAP). The developed NAP Reference Architecture (NRA), including full descriptions and a model available via NAPCORE website, serves as a technical, organizational, and functional blueprint for creating and harmonizing NAP activities.
This milestone extends the milestone M2.9 “Harmonisation of EU NAP architectures and first layout of potential NAP federation” where the underlying processes, work steps and status of the NRA were described. Therefore, the main purpose of this deliverable is to provide a thorough description of the NRA version 2.0 developed by NAPCORE.
The document outlines the NAPCORE approach and describes specific guidelines created by NAPCORE for the development and maintenance of the NRA.

The updates and releases can be found at: https://github.com/NAPCORE/NAP-Reference-Architecture