Skip to main content
D4Temp — Advanced digital infrastructure for harmonised temperature metrology D4Temp
WP2

Work Package 2

Workflow definition and library development

WP2 establishes the foundation for sharing software solutions across NMIs/DIs — harmonising processes and enabling smart specialisation. It identifies in-scope resources, defines a common database structure, and populates a shared repository with libraries for temperature-related software, designed for ISO 17025, DCC, and FAIR compliance.

NSAI logo WP Leader NSAI

Objectives

What this work package will deliver

  1. 1

    Map the equipment and software resources available across the consortium and capture current workflows.

  2. 2

    Define a common database structure for raw, analysed, and processed temperature data.

  3. 3

    Populate a shared repository of libraries that participants can combine to build digital workflows.

Tasks & activities

Breakdown of work

3 tasks · 16 activities
Task 2.1

Identify scope and resources

Months 2–24

Surveys equipment (manufacturers, models) and existing workflows at each participant institute — including links with administrative applications — so developed solutions are compatible with all partner equipment.

Activities (4)

A2.1.1

Equipment survey at participant facilities

Deadline: M4

Surveys equipment used for temperature measurement and dissemination at each participant — listing manufacturer, model, and documentation explaining current laboratory use.

Participants: NSAI FSB BFKH CEM SMD UL VINS SMU CMI UNISA
A2.1.2

Remote-communication workshops

Deadline: M24

Organises at least four workshops (in-person, hybrid, or remote) for the consortium on establishing remote communication with equipment to facilitate data gathering and analysis.

Participants: NSAI FSB BFKH CEM UL IMBIH VINS SMU
A2.1.3

Workflow charts in 4 participant institutes

Deadline: M6

Develops workflow charts covering existing key workflows at JV, FSB, IMBiH, and NSAI — designed using an agreed format and supporting digital infrastructure for data gathering and analysis.

Participants: NSAI FSB BFKH Random Red TUBITAK CEM SMD UL VINS JV ISTE IMBIH UNISA
A2.1.4

Software-repository framework

Deadline: M9

Determines a common framework for sharing developed resources across at least 4 participant labs and selects an adequate software repository considering compatibility and available resources.

Participants: NSAI Random Red UL TUBITAK VINS SMD
Task 2.2

Defining a common database structure

Months 1–30

Determines the structure and contents of an ideal database for raw and processed temperature data, designed to be easily implementable by partners without an active database.

Activities (5)

A2.2.1

Survey of existing participant databases

Deadline: M4

Surveys participants who have already implemented databases at their institutes — identifying database structure and application.

Participants: NSAI CEM IMBIH ISTE
A2.2.2

Essential field list for the database

Deadline: M6

Compiles a list of essential fields a functional database needs — raw data, analysis data, processed data, metadata, and associated DCC requirements — FAIR-compliant.

Participants: NSAI BFKH CEM UL SMD JV VINS
A2.2.3

Standardised database template

Deadline: M12

Produces a standardised database template and documentation stored in the repository from A2.1.4 — of an agreed database type for maximum compatibility with participant databases.

Participants: NSAI CEM UL SMD JV
A2.2.4

Database API for integration

Deadline: M18

Designs and develops an API to the standard database to enable participants to integrate it with existing databases and link with project software libraries.

Participants: NSAI SMD UNISA
A2.2.5

Database adoption in participant labs

Deadline: M30

Coordinates integration of the API at JV/SMD, adoption of the database template at FSB/PTB, and database deployment in collaboration with IMBiH/UNIBL/UL — based on the outcomes of A2.1.1–A2.2.4.

Participants: NSAI JV FSB PTB SMD IMBIH UNIBL UL
Task 2.3

Compilation of repository contents

Months 6–36

Populates the shared repository with libraries grouped by category, so each participant can pick the libraries that match their equipment and workflows, combine them, and establish a functional digital workflow with minimal adaptation.

Activities (7)

A2.3.1

Code gathering & library categorisation

Deadline: M36

Gathers new or existing software code from participants and organises it into categorised libraries covering distinct steps of the temperature calibration process.

Participants: NSAI All participants
A2.3.2

Administrative & DCC libraries

Deadline: M24

Develops libraries for gathering administrative details and for generating DCCs — compatible with the harmonised DCC format from A3.1.3 and the verifiable-credential approach in A4.2.3/A4.2.4.

Participants: NSAI TUBITAK ISTE UL PTB CEM JV UNIBL CMI
A2.3.3

Data acquisition libraries

Deadline: M24

Develops libraries for data acquisition, temperature medium control, reference equipment selection, and measurement stability assessment — ensuring interoperability with common instruments identified in A2.1.1.

Participants: JV BFKH CMI FSB IMBIH CEM NSAI UL PTB UNIBL
A2.3.4

Data processing & uncertainty libraries

Deadline: M24

Develops libraries for data processing and uncertainty estimation — encapsulating calibration calculation algorithms and uncertainty budgets, consistent with ISO/IEC 17025.

Participants: SMD BFKH CMI JV IMBIH CEM PTB UL NSAI UNIBL VINS FSB ISTE TUBITAK
A2.3.5

Repository quality & version control

Deadline: M36

Administers the software repository — quality, documentation, unit tests, dependency descriptions, and version control of all participant contributions.

Participants: Random Red All participants
A2.3.6

Library validation

Deadline: M24

Prepares validation plans for the libraries developed in A2.3.1–A2.3.4, then performs validation and produces a standardised validation report verifying functionality.

Participants: UL FSB BFKH JV TUBITAK ISTE
A2.3.7

Repository publication & paper

Deadline: M36

Places the software, validation files, and documentation in the repository for sharing across participants, and drafts a paper on the developed libraries and the shared-library approach.

Participants: NSAI All participants

Timeline

WP2 Gantt chart

Task spans and individual activities across the 36-month project plan (Jun 2026 — May 2029).

WP2 Gantt chart — tasks and activities across 36 project months