16614 (NeTEx) is composed of a series of standards: - Part 1: Description of the public transport network topology exchange format. - Part 2: Description of the scheduled timetables exchange format. - Part 3: Description of the fare information exchange format. - Part 4: Description of the passenger information European profile (EPIP). - Part 5: Description of the alternative modes exchange format. - Part 6: Description of the accessibility European profile (EPIAP). The present update concerns Part 4. All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency. The updated version of TS 16614 is going to be published as NeTEx v2. The global updates consist in the following main extensions/enhancements: - Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features), - Physical layout of compound vehicles (e.g. train composition), - Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926 Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision. This document is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information. NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems. As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.