BETA

8 Amendments of Jeroen LENAERS related to 2016/0357A(COD)

Amendment 325 #
Proposal for a regulation
Recital 55
(55) The revenue generated by the payment of travel authorisation fees should be assigned to cover the recurring operational and maintenance costs of the ETIAS Information System, of the ETIAS Central Unit and of the ETIAS National Units. In view of the specific character of the system, it is appropriate to treat the revenue as external assigned revenue. Where revenue generated by the payment of travel authorisation fees exceeds the costs of the ETIAS Information System, of the ETIAS Central Unit and of the ETIAS National Units, this Regulation should re-allocate the amount to a fund for the protection of critical infrastructure. The fund should be used to enhance protection of those infrastructures that have been identified or designated as European critical infrastructures under the Council Directive 2008/114/EC on the identification and designation of European critical infrastructures and the assessment of the need to improve their protection.
2017/10/04
Committee: LIBE
Amendment 350 #
Proposal for a regulation
Article 3 – paragraph 1 – point d
(d) 'travel authorisation' means a decision issued in accordance with this Regulation indicating that there are no factual indications or reasonable grounds to conclude that the presence of the person on the territory of the Member States poses anis contrary to the required approach to address security, irregular migration, security or public health risks and which is a requirement for third country nationals referred to in Article 2 to fulfil the entry condition laid down in Article 6(1)(b) of Regulation (EU) 2016/399.
2017/10/04
Committee: LIBE
Amendment 531 #
Proposal for a regulation
Article 16 – paragraph 1
1. A travel authorisation fee of EUR 510 shall be paid by the applicant for each application.
2017/10/04
Committee: LIBE
Amendment 593 #
Proposal for a regulation
Article 20 a (new)
Article 20a Support of the objectives of the Schengen Information System 1. For the purposes of Article 4(e), the ETIAS Central System shall compare the data referred to in Article 15(2)(a),(b) and (d) to the data present in the SIS in order to determine whether the applicant is subject to one of the following alerts: (a) an alert on missing persons; (b) an alert on persons sought to assist with a judicial procedure; (c) an alert on persons for discreet checks, inquiry checks or specific checks. 2. Where the comparison referred to in paragraph 1 reports one or several hit(s), the ETIAS Central Unit shall verify whether the applicant personal data corresponds to the personal data contained in the alert having triggered that hit and, upon confirmation, the ETIAS Central System shall send an automated notification to the SIRENE Bureau of the Member State that issued the alert. The ETIAS Central System shall also send an automated notification to the SIRENE Bureau of the Member State that issued an alert having triggered a hit against the SIS during the automated processing referred to in Article 18 where, following verification by the ETIAS Central Unit as referred to in Article 20, such alert led to manual processing of the application in accordance with Article 22. 3. The notification provided to the SIRENE Bureau of the Member State that issued the alert shall contain the following data: (a) surname(s), first name(s) and, if any, alias; (b) place and date of birth; (c) sex; (d) nationality(ies); (e) address of the first intended stay or, in case of transit, Member State of first intended transit; (f) travel authorisation status information, indicating whether a travel authorisation has been issued, refused or whether the application is subject to a manual assessment pursuant to Article 22; (g) a reference to the hit(s) obtained in accordance with paragraphs 1 and 2, including the date and time of the hit. 4. The ETIAS Central System shall add a reference to any hit obtained pursuant to paragraph (1) to the application file.
2017/10/04
Committee: LIBE
Amendment 617 #
Proposal for a regulation
Article 21 a (new)
Article 21a Responsible Member State 1. The Member State responsible for the manual processing of applications as referred to in Article 22 (the 'responsible Member State') shall be identified by the ETIAS Central System as follows: (a) where only one Member State is identified as having entered or supplied the data that triggered the hit pursuant to Article 18, that Member State shall be the responsible Member State; (b) where several Member States are identified as having entered or supplied the data that triggered the hits pursuant to Article 18, the Member State that has entered or supplied the most recent data corresponding to points (a) to (c) of Article 18(2), shall be the responsible Member State, unless the hits occur in the same information system such as the SIS where an order of prioritisation of hits is agreed upon. In such cases the prioritisation of hits prevails; (c) where several Member States are identified as having entered or supplied the data that triggered the hits pursuant to Article 18, but none of that data corresponds to points (a) to (c) of Article 18(2), the responsible Member State shall be the one that entered the most recent data, unless the hits occur in the same information system such as the SIS where an order of prioritisation of hits is agreed upon. In such cases the prioritisation of hits prevails; (d) for the purposes of paragraphs (a) and (c), hits triggered by data not entered or supplied by a Member State shall not be taken into account in order to identify the responsible Member State. Where the manual processing of an application is not triggered by data entered or supplied by a Member State, the responsible Member State shall be the Member State of first intended stay or, in case of transit, the Member State of first intended transit as declared by the applicant in accordance with Article 15(2)(j); (e) a consulted Member State can request the ETIAS Central Unit to be the responsible Member State for reasons of national interest. 2. The ETIAS Central System shall indicate the Member State responsible in the application file.
2017/10/04
Committee: LIBE
Amendment 629 #
Proposal for a regulation
Article 22 – paragraph 4 – point a
(a) where the hit corresponds to one or several of the categories laid down in Article 18(2)(a) to (c), assess the security, irregular migration or public health risks and decide whether to issue or refuse a travel authorisation.
2017/10/04
Committee: LIBE
Amendment 660 #
Proposal for a regulation
Article 23 – paragraph 1
1. Where the information provided by the applicant one or several Member States are identified as having entered or supplied the data having the application form does not allow the ETIAS National Unit of the responsible Member State to decide whether to issue or refuse a travel authorisation,riggered a hit in accordance with Article 18(2) and (4), the ETIAS Central Unit shall notify the ETIAS National Unit of the Member State(s) involved, thereby launching a consultation process between them and the ETIAS National Unit of the responsible Member State. The ETIAS Central Unit shall notify thate ETIAS National Unit may request the applicant for additional information or documentationof the consulted Member State(s) if the Central Unit has sent a notification to the SIRENE bureau as laid down in article 20a(2).
2017/10/04
Committee: LIBE
Amendment 1061 #
Proposal for a regulation
Article 75 – paragraph 1
The revenues generated by the ETIAS shall constitute external assigned revenue in accordance with Article 21(4) of Regulation (EU, EURATOM) No 966/2012. Where revenues generated by the ETIAS exceed the costs of the ETIAS, that surplus amount shall be re-allocated to the fund to be established for the protection of European critical infrastructures that have been identified or designated as European critical infrastructures under the Council Directive 2008/114/EC.
2017/10/04
Committee: LIBE