[Pixeurope-mct] D3.2 – Operations, Interoperability and Training (M12) – Structure and Next Steps

Sat May 9 12:00:19 CEST 2026

It is a good idea.
I think we can submit by end of June.
Ana, please confirm.

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Pixeurope-mct <pixeurope-mct-bounces at lists.icfo.es> on behalf of Padraic Morrissey via Pixeurope-mct <pixeurope-mct at lists.icfo.es>
Sent: Friday, May 8, 2026 4:49:33 PM
To: 'pixeurope-mct at lists.icfo.es' <pixeurope-mct at lists.icfo.es>
Subject: Re: [Pixeurope-mct] D3.2 – Operations, Interoperability and Training (M12) – Structure and Next Steps

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi all,

I was thinking a bit more about the D3.2 timeline and wondering whether it might make more sense to pause work on the deliverable until after the GA and Ecosystem event.

Given how busy everyone is with preparations at the moment, it may be difficult to coordinate inputs and reviews in parallel, and we would probably benefit from incorporating discussions from the GA into the deliverable anyway.

What do you think?

@Valerio/Ana, if we were to submit at the end of June, would that still be OK from a ChipJU perspective?

Thanks all and have a good weekend.

Kind regards,

Padraic

From: Padraic Morrissey <padraic.morrissey at tyndall.ie>
Sent: Wednesday 8 April 2026 11:11
To: Elisabeth Wintersteller <Elisabeth.Wintersteller at tyndall.ie>; 'pixeurope-mct at lists.icfo.es' <pixeurope-mct at lists.icfo.es>
Subject: RE: [Pixeurope-mct] D3.2 – Operations, Interoperability and Training (M12) – Structure and Next Steps

Hi Liz, all,

Thanks for the feedback.

I’m conscious that everyone’s schedules may be tight in the run-up to the PIXEurope GA and event, so coordinating this over the next few weeks could be challenging. With that in mind, it might be more practical to aim for a solid first draft by the end of the month, we keep May clear (where possible) then finalise and submit in early June.

Let me know if this approach works for everyone.

Proposed timeline:

  *   Inputs from each section lead by Thursday 30 April (section leads)
  *   First draft ready for review by Friday 8 May (compiled by Tyndall)
  *   Feedback on draft by Friday 29 May (all partners)
  *   Final draft for submission by Friday 5 June (compiled by Tyndall)

Also, I have placed a template for the deliverable on the SharePoint. You can find it here: D3.2 - Operations, Interoperability and Training<https://icfo.sharepoint.com/:f:/r/sites/PIXEurope/Shared%20Documents/General/04.%20DELIVERABLES/01.%20WORKING%20DOCS/WP3%20DEP/D3.2%20-%20Operations,%20Interoperability%20and%20Training?csf=1&web=1&e=wNdkJj>

Thanks everyone.

Kind regards,

Padraic

From: Elisabeth Wintersteller <Elisabeth.Wintersteller at tyndall.ie<mailto:Elisabeth.Wintersteller at tyndall.ie>>
Sent: 02 April 2026 14:51
To: Padraic Morrissey <padraic.morrissey at tyndall.ie<mailto:padraic.morrissey at tyndall.ie>>; 'pixeurope-mct at lists.icfo.es' <pixeurope-mct at lists.icfo.es<mailto:pixeurope-mct at lists.icfo.es>>
Subject: RE: [Pixeurope-mct] D3.2 – Operations, Interoperability and Training (M12) – Structure and Next Steps

Hi Padraic,

Thanks for sending the outline for D3.2 and detailing next steps. The proposed deliverable structure works well for me.

For the training component, I can coordinate partner input and will also align with D2.1 PIXEurope Training Courses & Future Planning (which is led by us) to ensure the contribution in D3.2 is complementary to the other deliverable.

Could you please let me know by when you would like the input collected for your final review?

I’m happy to clarify any details over email, and I’m equally available for a short meeting if preferred.

Kind regards,

Liz

Elisabeth (Liz) Wintersteller

Programme Manager
Training & Operations, Advanced Packaging Group

Tyndall National Institute

t  +353 21 234 6594

From: Pixeurope-mct <pixeurope-mct-bounces at lists.icfo.es<mailto:pixeurope-mct-bounces at lists.icfo.es>> On Behalf Of Padraic Morrissey via Pixeurope-mct
Sent: Tuesday 31 March 2026 07:03
To: 'pixeurope-mct at lists.icfo.es' <pixeurope-mct at lists.icfo.es<mailto:pixeurope-mct at lists.icfo.es>>
Subject: [Pixeurope-mct] D3.2 – Operations, Interoperability and Training (M12) – Structure and Next Steps

[EXTERNAL] This email was sent from outside of UCC.

Dear all,

Following our discussion at the last MCT meeting, I said I would follow up by email regarding the next steps for Deliverable D3.2, which is due in M12. The deliverable is titled “Operations, Interoperability and Training” and is intended to provide a progress update on how PIXEurope will operate in practice, including the centralised Gateway, Open Access and operational procedures, KPI monitoring, interoperability between partners, and training and knowledge transfer to ensure that all partners are working to common procedures.

Operations is quite a broad topic, so my suggestion is that we structure the deliverable into three main sections:

  1.  Operations (with sub-sections on Gateway, Open Access, and Data Management)
  2.  Interoperability
  3.  Training

I believe we can pull quite a bit of material for this deliverable from the intermediate reports and other existing documents, but we will probably need some new content, particularly around the plans for the Gateway, as I don’t think this has been described in detail anywhere yet.

In terms of gathering the content, I was thinking we could divide responsibility roughly as follows, with one lead partner per section and specific partners supporting and contributing to those sections:

  *   Gateway: ICFO to lead, with support and input from Tyndall, TU/e and AMIRES
  *   Open Access: TU/e to lead, with support and input from ICFO, Tyndall and AMIRES
  *   Data Management: AMIRES to lead (this was my understanding from the Steering Committee discussion in Barcelona, but please correct me if I have that wrong), with support and input from ICFO, Tyndall and TU/e
  *   Interoperability: Tyndall to lead, with support and input from ICFO, TU/e and AMIRES
  *   Training: Tyndall to lead, with support and input from ICFO, TU/e and AMIRES

Tyndall would then take responsibility for pulling the full deliverable together and submitting it, based on the inputs from each section lead and supporting partners.

Could you let me know if you are happy with:

  1.  The overall structure
  2.  The proposed leads for each section, and whether specific inputs are needed from any other partners
  3.  Whether you think anything important is missing at this stage

If it would be helpful, I am happy to set up a short meeting to align on the content and responsibilities. I know everyone is busy, so it may be easier to handle this over email, but I am very happy to arrange a call if that would be useful.

Once we are aligned on this, I will draft an outline of the report from one of the recent templates and will contact the relevant section leads so that we can start gathering the material.

Thanks all.

Kind regards,

Padraic

Padraic Morrissey

Senior Technology Programme Manager

Photonics Packaging and Systems Integration Group | Tyndall National Institute

Phone: (+353) 021-234 6106

Email: padraic.morrissey at tyndall.ie<mailto:padraic.morrissey at tyndall.ie>

LinkedIn: www.linkedin.com/in/padraicm<http://www.linkedin.com/in/padraicm>

www.tyndall.ie <http://www.tyndall.ie >  |  Lee Maltings, Dyke Parade, Cork, Ireland. T12 R5CP

[cid:image002.jpg at 01DCDF0A.A492BFA0]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.icfo.es/pipermail/pixeurope-mct/attachments/20260509/5f58f983/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 470 bytes
Desc: image001.png
URL: <http://lists.icfo.es/pipermail/pixeurope-mct/attachments/20260509/5f58f983/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4937 bytes
Desc: image002.jpg
URL: <http://lists.icfo.es/pipermail/pixeurope-mct/attachments/20260509/5f58f983/attachment-0001.jpg>