Kiri

Carrier Working Group March 21 2024 Carrier meetings - Calendar Handling instructions for SENSITIVE information are given at https://europa.eu/!qG39Vd Carrier meetings: January – June 2024 Dates February 2024 April 2024 June 2024 • 27th of Feb: Carrier • 25th of April: Carrier • 27th of June: Carrier Working Group Day Working Group Day Working Group Day January 2024 March 2024 May 2024 • 30th of Jan: Ad-hoc • 4th of March: Ad-hoc with • 29th of May: Carrier with Carnival UK on IRU members on Working Group Day CI return values registration process • 25th of Jan: Carrier • 14th of March: CLIA Working Group Day European Summit Week • 21st of March: Carrier Working Group Day 2  eu-LISA Carrier Meetings • Dates are finalized through June 2024: ✓ The Carrier Working Group: • Land and Sea: 10:00 to 12:00 CET * and • Air session: 13:30 to 16:00 CET * (* subject to changes) ✓ Ad-hoc troubleshooting calls are scheduled frequently for all the systems to support on the connectivity aspects. • In addition, ad-hoc meetings can be organized upon request after submission of an agenda to eu- LISA, for evaluation 3 THANK YOU! eu-LISA European Union Agency for the Operational Management of Large-Scale IT Systems in the Area of Freedom, Security and Justice Vesilennuki 5, 10415 Tallinn, Estonia www.eulisa.europa.eu  30th Carriers Working Group: Technical updates March 2024 Table of content: 1. Carrier Implementations Figures 2. Carrier Technical Guidelines – New version and updates 3. Carrier Interface Overview - Reminder 4. Carrier Web Portal – Deep Dive 5. Lessons Learned Carrier Implementations Figures March- 2024  Carrier Registration by channel March 2024 – Week 11 Carriers by Sys2Sys Choice 557 Carriers for System to System Yes System to System No 503 Carriers for The Mobile app 470 480 490 500 510 520 530 540 550 560 570 and Web Portal No Yes Total 503 557 Mobile Application and Web Portal 14/12/2022 4  Carrier Status – System to System March 2024 – Week 11 127 • Did not yet complete all Status of all Carriers – S2S Carriers required forms 02. Registered 2 03. Waiting for NDA 81 345 • Ready for tests (but systems not 05. Waiting for F03 46 Carriers yet compliant) 08b. Compliant (CT OK) 06. Service Provider declared 07a. CT slot proposed 416 06. Service Provider declared 07a. CT slot proposed 4 8 05. Waiting for F03 03. Waiting for NDA 63 • To be certified 08b. Compliant (CT OK) 02. Registered Carriers (system compliant) 0 100 200 300 400 500 08b. Compliant (CT OK) 07a. CT slot proposed 06. Service Provider declared 05. Waiting for F03 03. Waiting for NDA 02. Registered 8 • Certified or Yes 8 4 416 46 81 2 Carriers exempted 5 Carrier Status – System to System March 2024 – Week 11 127 • Did not yet ➢ Sign the form F07 (Security Convention) complete all and provide the F03 Carriers required forms ( System declaration) ➢ Systems to complete the 345 • Ready for tests (but connection and get systems not yet compliant (193 carriers Carriers compliant) are connected to PGD environment) 63 • To be certified ➢ Carrier to send the Carriers (system compliant) waiver form or schedule a slot for CT 8 • Certified or Carriers exempted 6  System Status March 2024 – Week 11 • Not ready to start the System 45 Systems Status of all Service Providers to System Connectivity 03. Waiting for F04 23 09. Waiting for F04c/d • Connectivity 22 23 Systems 10. PGD Documentation ok 2 testing ongoing 10a. Connectivity Planned 7 10b. Connectivity in Progress 14 11. Connected to PGD 5 • Ready for CT ( 6 Systems 12a. CT slot proposed 1 Connectivity OK) 13. CT Completed 2 0 5 10 15 2 Systems • Compliant Total # of Service Providers: 76 20 Recorded as of: 10/03/2024 25 7 Carrier’s System Status March 2024 – Week 11 • Not ready to start the System ➢ Send the forms F04, 45 Systems F04c/F04d for to System connectivity setup Connectivity ➢ After the reception of • Connectivity certificate + F04c/d 23 Systems completed, send a test testing ongoing message to confirm the connection • Ready for CT ( 6 Systems ➢ Schedule a CT slot Connectivity OK) 2 Systems • Compliant 8  Carrier’s System to System progress Carrier Compliance - Trend Chart • The current trend for System Current vs Mean values Connectivity is slow and eu-LISA 350 wants to support all 300 carriers/Service Providers to 250 increase the trend of these 200 activities 150 100 • Regular troubleshooting calls are 50 scheduled with the technical 0 teams to facilitate the connectivity challenges Systems ready for CT (connectivity OK) • Any other suggestion? Systems compliant Mean Value Systems ready for CT (connectivity OK) Mean Value Systems Compliant 9  Carrier Status – Web Portal/Mobile Application Mars 2024 – Week 11 Status of all Carriers • Carriers did not 02. Registered 1 228 yet complete all Carriers required forms 03. Waiting for NDA 227 No 04. Enc. Keys + Tech. doc shared 275 • Carriers ready to 0 275 get the Web 50 Total # of Carriers: 1,060 100 150 200 Carriers portal/Mobile Recorded as of: 10/03/2024 250 300 app access 04. Enc. Keys + Tech. doc shared 03. Waiting for NDA 02. Registered No 275 227 1 10 Carrier Technical Guidelines – New version and updates Carrier Technical Guidelines – Part 1: System to System (S2S) • New Carrier Technical Guidelines version Part1 for System to System will be published under the Revision Status 25_00_00 on Q1 2024 • The updated version of the document is shared with all Carriers SPOCs with ‘System to System’ selection, to be shared with the authorised staff and declared service providers • The new version of the CTG S2S takes into consideration: ✓ Variable Geometry scenarios and transit handling in PAXLST based on the outcome of the analysis done with the air industry ✓ A table of countries where EES and ETIAS are applied ✓ ETIAS Limited Territorial Validity (LTV) based on the recent legal updates ✓ Information about FNU when missing first name ✓ Information about dummy expiry date when missing in travel document 12 Carrier Technical Guidelines – Part 2: Web Portal and Mobile Application • New Carrier Technical Guidelines version Part 2 for Web portal and Mobile Application will be published under the Revision Status 5_01_00 on Q1 2024 • The updated version of the document is shared with all Carriers SPOCs with ‘Web Portal or Mobile Application’ selection, to be shared with the authorised staff • The new version of the CTG Web portal and Mobile Application takes into consideration: ✓ User Management and User authentication guidance ✓ Business Errors updates ✓ Updated screen shots of the user interfaces 13 Carrier Interface Overview - Reminder Carrier Interface Overview EU Central System System to System EES and ETIAS The Carrier Interface Read only DB Web Portal and Mobile for carriers Application Response time: Carrier’s query up Response for each ... Carrier’s query up Response for each • 2 s for 1 passenger per to 99 passengers passenger: to 99 passengers passenger: message • OK • OK • 4 s for up to 99 passengers • NOK EES • NOK EES • NOK ETIAS • NOK ETIAS • NA • NA BOOKING H - 48 DEPARTURE TIME ARRIVAL BORDER CONTROL Carrier’s Carrier Carrier’s Carrier System Authorised Staff System Authorised Staff 15 Carrier Interface – Query/Reply Query – Passenger Data # Attribute description Mandatory (M) or Optional (O) 1 Surname (family name) M 2 First name or names (given names) M 3 Date of birth M 4 Sex M 5 Nationality M 6 Type of the Travel Document M 7 Number of the Travel Document M 8 Three letter code of the issuing country of the TD M 9 Date of expiry of the validity of the TD M Query – Itinerary Data # Attribute description Mandatory (M) or Optional (O) 10 Scheduled location of entry M 11 Scheduled local date and time of arrival at a location M 12 Scheduled local date and time of departure M 13 Identification number of scheduled means of transportation M 14 Carrier operator M ( applicable for Sys2Sys channel) 15 Traveller in transit flag O (if applicable) 16 Traveller out of scope flag O (if applicable) 17 Query submission date and time in UTC time M ( applicable for Sys2Sys channel) 18 Passenger request identifier M ( applicable for Sys2Sys channel) 19 Notification request identifier M ( applicable for Sys2Sys channel) 20 Multiple entries required M (if applicable) for land and maritime carriers only Traveller classification as per EES and ETIAS EU regulations Travelers in scope of ETIAS Nationals from visa exempt countries and Travelers with visa in scope of EES not holders of any ETIAS out of scope category (reference to Article 2(2)) Third country nationals and holders of single or double entries visas Travelers from countries with visa requirements in scope of ETIAS Third country nationals exempt from the visa requirement as described in Article 2(1) b and c of the ETIAS Regulation (e.g. school pupils etc.) Travelers - out of scope of EES Third country nationals as per article 2 (3) of EES regulation, such us: ▪ Holders of a residence card or residence permit ▪ Holders of a Long-stay visa ▪ Holders of Diplomatic passport or laissez-passer ETIAS out of scope ▪ Persons exempt as per Article 6a(3) of the Regulation (EU) 2016/399 Third country nationals as per article 2 (2) of ETIAS ▪ EU nationals regulation, such us: ▪ Nationals of Andorra, Monaco and San Marino ▪ Holders of a residence card or residence permit and holders of a passport issued by the Vatican ▪ Holders of long-stay visa City State or the Holy See ▪ Refugee or stateless persons ▪ Holders of diplomatic passport or laissez-passer ▪ EU nationals ▪ Nationals of Andorra, Monaco and San Marino and holders of a passport issued by the Vatican City State or the Holy See For more details, please refer to EES and ETIAS regulations 19  Carrier Interface replies Before ETIAS entry into operation In scope - EES Visa single or double entries Response : OK or NOK EES The Carrier Interface System to System In scope - ETIAS Web Portal and Mobile Exempt from the Nationals Application visa requirement as from visa per article 2(1) of exempt ETIAS regulation countries* (ex: School pupil) Response : NA * Nationals from visa exempt countries and not under any of ETIAS out of scope cases 20  Carrier Interface replies After ETIAS entry into operation In scope - EES Visa single or double entries Response : OK or NOK EES The Carrier Interface System to System In scope - ETIAS Web Portal and Mobile Exempt from the Nationals Application visa requirement as from visa per article 2(1) of exempt ETIAS regulation (ex: School pupil) countries* Response : OK or NOK ETIAS * Nationals from visa exempt countries and not under any of ETIAS out of scope cases 21 Carrier Interface replies Nationality checks Out of scope – EES and ETIAS Nationals from AND, MCO, SMR and VAT Response : NA The Carrier Interface Out of scope – System to System EES and ETIAS Web Portal and Mobile Application Nationals from Member States Response : NA 22 Carrier’s queries during the online check-in Proposed option by no means Option 1 required by legal base • During the online check-in, carriers may decide to send all passengers data to the carrier interface and receive a Not OK EES or Not OK ETIAS for out of scope passengers • In case a Not OK EES or Not OK ETIAS is returned, carriers need to check the travel documents of the passengers to clarify if they fulfil the conditions to enter the Schengen area • If verification of travel documents reveal that traveller has no such documents (example: Resident Permit, Long stay Visa…etc), meaning traveller is in the scope of the carrier interface. And by receiving a previous Not OK, it would mean that the traveller has neither a single and double entry visa nor ETIAS and therefore not able to enter the Schengen area Carrier online Carrier’s All passengers check-in system interfaces All passengers The Carrier Interface Response : • NA • NOK EES • NOK ETIAS • OK 23 Carrier’s queries during the online check-in Proposed option by no means Option 2 required by legal base • During the online check-in, carriers may decide to ask the passenger if he/she is out of scope before submitting the query to the carrier interface • Carriers may decide to submit or not queries with out of scope passengers. If the carrier sends a query for out of scope passengers, the query should include the out of scope indicator Carrier online Carrier’s Out of scope Passenger out system indicator check-in interfaces of scope The Carrier Interface Response : Not applicable 24 Carrier Interface Web portal and Mobile Application Carrier Web Portal and Mobile Application Input Data Carrier’s query up to 99 passengers Passenger details can be provided: - Manual data input - Via an import of csv file - Via MRZ scanner (optical The Carrier Interface Carrier scanning) for ICAO Response for each Web Portal and Mobile Authorised Staff Passports passenger: Application • OK • NOK EES • NOK ETIAS • NA 26 Carrier Web Portal and Mobile Application Input Data Carrier Authorised Staff Carrier Web Portal Home Page Carrier Mobile Application on iOS (left) and Android (right) Home Page 27  Carrier Web Portal and Mobile Application Option 1: Manual Data Input Travel information The carrier ’s authorised users provide manually the Travel information for all concerned passengers: Passenger Data Carrier 1 Authorised Staff Passenger Data 2 Carrier Web Portal New Travel Itinerary Carrier Mobile Application iOS (left) and Passenger Data Android (right) New Travel Information 3 (i.e., about the Itinerary) Passenger Data 4 28  Carrier Web Portal and Mobile Application Option 1: Manual Data Input Passenger information The carrier’s authorised users provide manually the passenger travel document details : Surname, First name Date of birth Sex Carrier Authorised Staff Nationality Number of travel document Type of travel document Carrier Web Portal Manual Input Carrier Mobile Application iOS (left) and Android (right) Manual Input Issuing country Date of expiration 29 Carrier Web Portal and Mobile Application Option 2: Import Passenger List From a File Surname;Given_names;Date_of_birth;Sex;Nationality ;Travel_document_number;Travel_document_type;Is suing_country_of_travel_document;Expiry_date_of_ travel_document;Target_country;Arrival_scheduled_ date;Transport_idenditication_number;Departure_sc heduled_datetime;Transit;Out_of_scope;Double_ent Carrier ry_required Authorised Staff Maximum of 99 passengers are allowed to be submitted in one CSV file Carrier Web Portal and mobile app CSV Upload Screen 30 Carrier Web Portal and Mobile Application Option 3: Input using MRZ Scanner The Carrier’s Authorised users are able to input passenger information by scanning the Travel Document using a MRZ scanner. Imported data Carrier can then be manually Authorised Staff edited before verification. The MRZ Scanner is limited to ICAO Standards Travel documents 31 Carrier Web Portal and Mobile Application Browse Results of Verification Carrier Authorised Staff Verification Results in the Carrier Web Portal Verification Results in Carrier Mobile Application iOS (left) and Android (right) Results of the verification can be exported to a CSV file 32 Carrier Web Portal and Mobile Application User Management – First Access Eu-LISA Carrier Administrator Carrier SPOC Carrier 1 2 3 Authorized Staff Eu-LISA Carrier Administrator The carrier’s authorized staff Carrier Authorised Users define start the log-in to the Web will allocate 10 anonymous a new password either through portal and the Mobile user* IDs to each Carrier’s SPOC the Carrier Web Portal or the Application using the url, user requesting the Web Carrier Mobile Application ID and password provided to Portal/Mobile app connection the Carrier SPOC How to get access to the Carrier Web Portal and mobile application? (*) Additional users can be added on demand. 33  Carrier Web Portal and Mobile Application User Management – First Access Carrier Authorized Staff The carrier authorized staff start the log-in to the Web portal and the Mobile Application using the url, user ID and password provided to Initial Password Setup Page the Carrier SPOC (*) The password must contain at least 14 characters and meet at least three of the following requirements: ◼ UPPER CASE LETTERS (A, B, C, … Z); ◼ LOWER CASE LETTERS (A, B, C, ... Z); First Connection page to update the Password* ◼ NUMBERS (0, 1, 2, ... 9); ◼ SPECIAL CHARACTERS (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~). 34  Carrier Web Portal and Mobile Application User Management – Carrier SPOC View The two-factor authentication using a TOTP-compatible application or a FIDO2- compatible device must be activated for Carrier SPOC to get the access to the User Management Interface: Carrier SPOC • TOTP: a QR code is provided by the Web Portal to initialise the TOTP compatible application; • FIDO2: the SPOC must provide the credentials to initialise the FIDO2- Carrier SPOC users are able to browse the list of users under compatible device. their management Selection of Strong Authentication Method For more details about the authentication Method, please refer to the Carrier technical Guidelines Part 2 section 5 35  Carrier Web Portal and Mobile Application User Management – Carrier SPOC View Carrier SPOC Carrier SPOC users are able to browse the list of users under their management Carrier SPOC Users User Management Screen ✓ The Carrier SPOC is able to reset an enable the users under his or her organization. ✓ The password reset for authorized staff is to be managed by the Carrier SPOC and not eu-LISA ✓ The creation or the deletion of authorized Staff users need to be handled by eu-LISA Carrier administrator upon a reception of the request ▪ Before EES EiO, the request of the creation or the deletion of a user is to be sent to the EULISA Carriers Onboarding [email protected] ▪ After EES EiO, the request of the creation or the deletion of a user is to be sent via the Carrier Onboarding and Support Tool 36 Lessons learned from the pilot phase Lessons Learned during the Pilot Phase – Episode 2 Active interactions between the REST/JSON testing experts help shortening the CT Certification (one hour) Important PAXLST notes about the MQ/EDIFACT message structure to be re-enforced, avoiding 400 Error Check the templates provided in the TDD document to ensure that you do not get 422 Error Use the CorrelationID attribute to follow more easily the test executions (including versioning of Test Cases) Annex to TDD (SoapUI) and a “template” DTP (Detailed Test Plan) will be provided to clarify the mapping of attributes to respective message structure and format. 38 Carrier IDs and Service Provider IDs Name PAXLST Input JSON Correlation identifier RFF+TN correlationId NAD+DDU+++ Passenger in transit inTransit = true DDU indicates that passenger is in transit Passenger out of scope GEI+4+176 outOfVerificationScope= true Passenger Nationality NAT+2+ nationality Travel Document Type DOC+ documentType Travel Document Number DOC+P+ number Reference ID of passenger RFF+ABO: tcnNo Expiry date of travel document DTM+36: expiryDate Issuing country of travel document LOC+91: issuingCountry Arrival date DTM+232: arrivalLocalDay Departure date and time DTM+189: departureDateTime Target MS of entry LOC+87+ airportOfEntry Identifier of means of transport (flight TDT+20+ scheduleNo number) TDT+34+ (if overflight) 3rd value of the UNB header Service provider ID UNB+UNOA:4+Sxxx: serviceProviderId Where bolded value is the service provider ID at the end of TDT+20 TDT+20+6X8912+++6X, where 6X is the Carrier ID carrierId Carrier ID (up to 3 characters), in its absence two first characters from Flight ID are used 39 Carrier IDs and Service Provider IDs REST Channel Carrier The Carrier Interface Carrier’s System Authorised Staff Traveller Status Verification with • carrierID (required) in message body • serviceProviderID (optional) in message body System ID (or Internal System ID) linked with • serviceProviderID (required) in HTTP header Carrier TLS Certificate must be the same as X-IBM-Client-Id serviceProviderID from HTTP header Access Control based on: • carrierID from message body • servideProviderID from HTTP header 40 Carrier IDs and Service Provider IDs MQ Channel Carrier The Carrier Interface Carrier’s System Authorised Staff Traveller Status Verification with • carrierID (required) in message body • serviceProviderID (required) in message body Access Control based on: • carrierID from message body • servideProviderID from message body 41 THANK YOU! eu-LISA European Union Agency for the Operational Management of Large-Scale IT Systems in the Area of Freedom, Security and Justice Vesilennuki 5, 10415 Tallinn, Estonia www.eulisa.europa.eu facebook.com/agencyeulisa/ twitter.com/EULISA_agency linkedin.com/company/eu-lisa/ youtube.com/c/euLISAagency  ETIAS – ACU Assistance Centre Unit Assistance to Carriers 30th Carriers Working Group 21st March 2024 Author: Assistance Centre Unit  AGENDA ✓Assistance Centre Unit-ACU ✓ Assistance Mechanisms ✓Digital Tools in support of carriers ✓Standard Operating Procedures for Carriers’ Assistance 2  Assistance Centre Unit-ACU ➢ A dedicated unit within ECU, ETIAS Central Unit in FRONTEX (Warsaw) ➢Main responsible for the support to Carriers and Travellers when filling ETIAS form ➢Entry into operations when EES goes live (Q4 2024) ➢ Operational 24 hours a day/7 days a week ➢ Support provided in English 3  Assistance Mechanisms ➢First level support : FAQs ➢Second level support: For registered carriers, To send a request via a web form 4  Second level support ➢The Carrier Onboarding and Support Tool-COBST (provided by eu-LISA) is an automated tool consisting of a self-service web portal (web form) with ticketing functionalities 5  Carrier Onboarding and Support Tool-COBST ➢Ticketing tool ➢ Access through the EES and ETIAS public website ➢ Support available only to registered carriers ➢The main communication channel between Carriers and ACU/eu-LISA ➢To be used by duly authorised carrier’s staff 6 Backup solution Emergency Phone Line only when COBST is unavailable For operational requests, For technical issues, ACU provides the FAQ ACU creates a request on relevant information behalf of the carrier & forwards to eu-LISA Please, can you provide the carrier 24/7 support PIN? Only in English ETIAS ACU 7 Standard Operating Procedures for Carriers’ Assistance 8  SOP for Carriers’ Assistance ➢Mandatory requirement from ETIAS Regulation (Art 45.5 EU 1240/2018) ➢It contains issues that carriers may face when fulfilling EES and ETIAS Regulation ➢Procedures and processes for resolution agreed between ACU and eu-LISA ➢It describes roles and responsibilities of carrier’s actors involved: Carrier SPoC/ Backup ,duly authorised staff, carrier legal representative 9  SOP for Carrier’s Assistance ACU will ➢Reply to the operational requests ➢Facilitate the handling of technical requests ➢Handle notifications on Technical Impossibility to send verification queries via the Carrier Interface, due to: ❖Failure at Central System, eu-LISA responsibility ❖Failure on Carrier’s side, carrier ‘s responsibility 10  SOP for Carrier’s Assistance Eu-LISA will ➢Reply to/Resolve the technical requests ➢Handle the requests on: *Registration for new carries *User Management of the COBST *Deregistration *Security incidents ➢Resolve the failure at Central System 11 Thank you Assistance Centre Unit  DRAFT AGENDA 30th Carriers Working Group Air Session Video conference meeting 21 March 2024 13:00 to 13:30 (CET): Setting up connection 13:30 to 16:00 (CET): Working Session 1. Introduction a. Agenda b. Carriers meeting calendar 2. Updates from the European Commission 3. Technical updates (eu-LISA) 4. Carriers and Travellers Support - Operational updates (Frontex) 5. Q&A End of the meeting EUROPEAN UNION AGENCY FOR THE OPERATIONAL MANAGEMENT OF LARGE-SCALE Vesilennuki 5, 10415 Tallinn, Estonia IT SYSTEMS IN THE AREA OF FREEDOM, SECURITY AND JUSTICE www.eulisa.europa.eu  DRAFT AGENDA 30th Carriers Working Group Sea and Land Session Video conference meeting 21 March 2024 09:30 to 10:00 (CET): Setting up connection 10:00 to 12:00 (CET): Working Session 1. Introduction a. Agenda b. Carriers meeting calendar 2. Updates from the European Commission 3. Technical updates (eu-LISA) 4. Carriers and Travellers Support - Operational updates (Frontex) 5. Q&A End of the meeting EUROPEAN UNION AGENCY FOR THE OPERATIONAL MANAGEMENT OF LARGE-SCALE Vesilennuki 5, 10415 Tallinn, Estonia IT SYSTEMS IN THE AREA OF FREEDOM, SECURITY AND JUSTICE www.eulisa.europa.eu Saatja: "EULISA CARRIERS" <[email protected]> Saaja: "EULISA CARRIERS" <[email protected]> Teema: Carriers WG: Invite to the 31st Working Group for Carriers meeting on 25/04/2024 Kuupäev: 2024-04-09 15:00 Tähelepanu! Tegemist on välisvõrgust saabunud kirjaga. Tundmatu saatja korral palume linke ja faile mitte avada. Dear members of the Carrier community, We have the pleasure of inviting you to the 31st meeting of the Working Group for Carriers jointly organised by the European Commission (DG HOME) and eu-LISA. The meeting will take place online on 25 April 2024 and will include two consecutive sessions per business area as follows: 10:00 – 12:00 (CEST*) Sea and Land Carriers 13:30 – 16:00 (CEST*) Air Carriers *CEST - Central European Summer Time Please note that you must confirm your participation via the following link: EUSurvey - Survey (europa.eu) <https://ec.europa.eu/eusurvey/runner/31thCWGenrolment> . The deadline to confirm your attendance is 18 April 2024, EoB! Enrolments past that date will not be accepted! Connection details and meeting agenda will be shared, only with the confirmed and validated participants, prior to the meeting. Kindly note that the participation is limited to registered Carriers with their declared Service Providers (as per registration process) as well the Carriers Associations. We advise a maximum of 1-2 representatives per enterprise. For your reference, please find attached the meeting materials of the 30th Working Group meeting that took place on 21 March 2024. The summary of the meeting is under revision, and once available, will be published on eu-LISA <https://www.eulisa.europa.eu/About-Us/Organisation/working-group-for-carriers> Carrier Working Group Website. Please keep in mind that information provided by eu-LISA and the European Commission is considered sensitive, and can be distributed only on a need-to-know basis; it is not to be released outside of the information stakeholders. In addition, as mentioned previously, please note that a number of carrier related presentations have been published on the eu-LISA <https://www.eulisa.europa.eu/About-Us/Organisation/working-group-for-carriers> Carrier Working Group Website. There you will find the latest version of the FAQ document, which includes answers to the most frequently asked questions, as well as several Explanatory Presentations. Please feel free to make reference to the presentations or share the link further as you find relevant. Should you have any questions please contact <mailto:[email protected]> [email protected]. We are looking forward to having a pleasant and productive meeting. Kind regards, on behalf of the eu-LISA Carrier team <mailto:[email protected]> [email protected] <http://www.eulisa.europa.eu/> www.eulisa.europa.eu ----------------------------- Disclaimer: This message is sent in confidence and is only intended for the named recipient. If you received this message by mistake, you may not use, copy or distribute this message or any part of its contents or rely upon the information contained in it. Please kindly notify the sender immediately by e-mail and delete the relevant e-mails from any computer. This message does not constitute a commitment by eu-LISA unless otherwise indicated.