Dear bi0SpaCE Consortium
Members,
Thank you all for
attending the virtual General Assembly meeting. It
was a pleasure to see so many of you engaged and
committed to the project — your active
participation is crucial to driving our project forward. I am following up
with some key activities and reflections from our
meeting.
Tasks
Related to Deliverable 2.1
As we
discussed over the last couple of days, we are in a critical
phase of
the bi0SpaCE project. A detailed and shared
understanding of the use case requirements across
all four pilots is essential for the successful
development of the technical architecture — and,
ultimately, for the success of our implementation.
With summer approaching and a deadline to finalise
the technical architecture by end of Month 9 (September 2025), it
is vital that we achieve clarity and alignment on
the use cases before the end of this month (June 2025).
To support this effort,
our technical partners have kindly agreed to
assist the pilot partners in their respective
regions:
- CARTIF
→ Naturae
- SSF
→ noriware
- AU
→ GreenLab and Fiskeby
The immediate next task
is to consolidate the user
stories into 1–3 use case descriptions per
pilot by the end of June (Month 6).
You can use the template shared on Miro (which will remain accessible)
to structure your inputs. As detailed in
the Miro template, each use case description should include:
- Title and Objective
- Products to be modelled
as DPPs: Specify the products,
descriptions, available data (e.g., product
sheets), and relevant supply chain details.
- Materials to be
monitored: List materials,
relevant data, how to obtain it, digitisation
status, links between materials and products, and
data access.
- Assets requiring
digital twins: Describe
machines/equipment, available data, data
protocols, and access methods.
- Sensors for real-time
monitoring: Detail the sensors
(e.g., pH, flow rate, temperature), technical
specifications, and new installations planned
during the project.
This
exercise should result in a ~1-page use case
description per pilot to be shared with Fraunhofer
for planning the technical architecture (deadline
30 July)
Following this, the technical support partners, with input
from the pilots, will expand these use cases into a more detailed 2-3 page document
by 15 July, covering:
- Relevant
bi0SpaCE technologies for each use case
- How
these technologies will be implemented
- Specific
sensors, APIs, or protocols used to collect data
- Which
project KPIs are addressed
Once again,
you can use the Miro Template for this
activity. I (Dev) will share a Word document template for this extended
description by the end of June. Please remember to enrich the detailed
description with photos, process plans, sensor details, and key data
collection points from the pilots where possible.
Consolidation
of Key
Takeaways from the General Assembly Meeting
- Closer
Communication: A clear
message from our discussions was the need for
better communication across partners and monthly meetings
alone are not sufficient. Therefore, I
urge technical partners to be proactive in
reaching out to the pilots, clarifying what data
is needed and when. The pilots are ready and
willing to help — they just need clear guidance.
- R&I
Mindset: Let
us also keep remembering that
bi0SpaCE is a Research and Innovation Action.
While pilots drive the technical outcomes, we are
not limited by them. Our ambition should be to
shape the vision of DPPs, digital twins, and data
spaces for bio-based industries. Let’s aim for
value-driven digitalisation for the circular
economy and sustainability, and explore
cutting-edge research methods to bridge real-world
data gaps.
- Sequencing
and Integration Risks: Tasks in
WP3 and WP4 are currently planned/running in
parallel, but some activities are inherently
sequential — e.g., sensor selection and data
collection. We must coordinate closely and
leverage the diversity across our pilots: some can
provide historical data, others are more suited to
primary data collection. Our final solutions
should reflect this diversity while working
towards a shared bi0S platform. As we progress, we
should also explore how pilot activities can be
‘synthetically’ combined to illustrate our future
vision.
Additionally, one of our key follow-up
activities after the summer break should be to revisit and refine the
bi0SpaCE technical architecture vision based on
our findings so far. There is a risk of
fragmentation if each task develops solutions in
isolation. I will set up a meeting with WP leaders
to discuss better coordination across this aspect.
Meeting
Videos and Slides:
Finally,
please note that the recordings of the General
Assembly meeting are available on Teams (
202506-bi0SpaCE-GA-recordings-and-slides).
Unforatunately the first part of Day 1
(Introduction and Administartaion) was not
recorded. As a follow up I would ask each partner to upload
any their presentations to the same folder.
Thank you once again for
your time, input, and commitment. I’m truly
excited to see the project moving forward with
such a strong and collaborative consortium. I look
forward to the next steps and to continuing our
impactful work together.
