25:
281:(2001-2005, now the UK standard for bus PT timetables), and the French Trident standard (1999-2003). Its provision of a uniform conceptual framework, consistent terminology and well grounded abstractions make it especially valuable for comparing, harmonising and modernising legacy standards and systems and for international cooperation.
307:, the European Commission recognised NeTEx as a strategic standard for the cross-border exchange of data to enable the provision of EU-wide multi-modal travel information services. It aims to make data available in NeTEx format at National Access Points (government-designated open databases) in all European countries.
187:
principles to separate different concerns into independent information layers, using node and link concepts to describe individual transport layers. It supports the reuse of transport information entities for different applications. It can represent multi-modal, multi-operator transport systems and
289:
Transmodel based applications are now in widespread use through many parts of Europe for exchanging timetable and real-time data. A revised V6.0 version of
Transmodel incorporating additional capabilities and breaking the specification into eight separate modules is underdevelopment. Parts 1, 2
191:
The
Transmodel standard also establishes consistent terminology for public transport concepts, providing definitive equivalents for use in the national languages of each participant nation. In cases where vernacular words related to public transport could have more than one possible meaning or
290:& 3, covering respectively common concepts, network descriptions, and timetables were published in 2015. Parts 4 to 8, covering operational actions, fares, passenger information services, driver management, and management information and statistics were published in 2019.
144:
to uniformly represent common public transport concepts, facilitating the use of data in a wide variety of public transport information systems, including for timetabling, fares, operational management, real-time data, and journey planning.
302:
schema. It was developed as
Standard by CEN/TC 278/WG 3 (public transport working group) between 2009 and 2014 as a format for exchanging inter-modal stop, timetable, and fare data for public transport Europe-wide. In 2017, under the
192:
overlap in meaning, it establishes a precise and unambiguous technical term for use in information systems. For example, the terms 'trip', 'journey', and 'service', are overlapping concepts that in
Transmodel have specific usages.
220:
DRIVE programme. The results of
Cassiope were then developed further by the EuroBus and Harpist (Drive II) projects. This produced Transmodel V4.1 ENV 12896 with a E/R “Oracle” formalism.
232:
242:(SITP) (Information System for Public Transport), which began in 1999 under the sponsorship of the French Ministry of Transport, developed Transmodel 5.1, adding a UML
204:(DGXIII), and national public institutions, in particular the French Ministry of Transport (Direction des Transports Terrestres), as well as several private companies.
265:
Transmodel has been fundamental to the development of a number of concrete national data models and
European Standards, including both European standards
200:
Transmodel was originally developed within a range of
European projects under several European Programmes (Drive I, Drive II, TAP) with the support of the
336:
274:
216:
project (Computer Aided System for
Scheduling Information and Operation of Public Transport in Europe, 1989-1991), carried out under the initial
183:(UML), accompanied by detailed descriptions of the concepts, elements and attributes needed to represent transport information. It uses modern
491:
342:
266:
156:
Transmodel provides a comprehensive conceptual model for public transport information systems, covering multiple subdomains including
250:
89:
61:
188:
complex fare models, bringing together data from many different organisations with different standard and practices.
326:
298:(NETwork EXchange) is a concrete XML scheme implementing the central components of the Transmodel model as a modular
108:
68:
46:
235:
ENV 12896. This led to
Transmodel V5.0: with multi-modality, real-time control, layers, and data versioning
75:
501:
227:(1996-1998) continued to validate and enhance Transmodel, implementing it in three European pilot sites.
42:
496:
57:
180:
176:
184:
35:
169:
391:
Comité Européen de
Normalisation (CEN), Reference Data Model For Public Transport, EN12896
8:
413:
Public Transport Reference Data Model - Part 3: Timing Information and Vehicle Scheduling
277:(2006-2007), now assimilated into Transmodel v6.0 Part 2, and national standards such as
201:
161:
137:
82:
448:
Public Transport Reference Data Model – Part 8: Management Information & Statistics
231:
accompanied the standardisation process of Transmodel, which was chosen in 1997 as the
157:
129:
321:
133:
420:
Public Transport Reference Data Model – Part 4: Operations Monitoring and Control
165:
141:
270:
243:
485:
316:
278:
406:
Public Transport Reference Data Model - Part 2: Public Transport Network
394:
EN 12896:2006, Public Transport Reference Data Model (“Transmodel v5.1”)
364:
434:
Public Transport Reference Data Model – Part 6: Passenger Information
305:
Intelligent Transport Systems Priority Action A Directive (2010/40/E)
24:
207:
455:
Public Transport Reference Data Model – Informative documentation
441:
Public Transport Reference Data Model – Part 7: Driver Management
427:
Public Transport Reference Data Model – Part 5: Fare Management
399:
Public Transport Reference Data Model - Part 1: Common Concepts
249:
In 2006, version 5.1 of Transmodel was formally adopted by the
16:
European Reference Data Model for Public Transport Information
331:
294:
466:
476:
299:
269:(SIRI: 2001-2005, now a CEN technical specification) for
217:
471:
260:
148:
As of 2021, the current version of Transmodel is 6.0.
284:
126:
Reference Data Model For Public Transport (EN 12896)
337:
Identification of Fixed Objects In Public Transport
275:
Identification of Fixed Objects In Public Transport
49:. Unsourced material may be challenged and removed.
483:
208:Initial development & first generation uses
240:Système d'Information pour le Transport Public
223:The Telematics Applications Programme project
343:Service Interface for Real Time Information
267:Service Interface for Real Time Information
109:Learn how and when to remove this message
484:
362:
251:European Committee for Standardization
492:Public transport information systems
168:, fares, fare validation, real-time
47:adding citations to reliable sources
18:
365:"A Review of Trip Planning Systems"
363:Tizani, W. M. K. (September 1992).
261:Second generation (Transmodel v5.1)
13:
285:Third generation (Transmodel v6.0)
14:
513:
460:
327:Transport standards organisations
23:
385:
253:(CEN) as the European Standard
34:needs additional citations for
356:
1:
349:
212:Transmodel originated in the
132:for modelling and exchanging
7:
310:
172:, and operational systems.
136:information. It provides a
10:
518:
233:European Experimental Norm
195:
181:Unified Modeling Language
177:entity-relationship model
453:PD CEN/TR 12896-9:2019,
273:exchange for buses, and
185:information architecture
151:
170:passenger information
43:improve this article
502:Transport in Europe
369:www.its.leeds.ac.uk
202:European Commission
160:infrastructure and
138:standard data model
497:Travel technology
450:(“Transmodel v6”)
446:EN 12896-8:2019,
443:(“Transmodel v6”)
439:EN 12896-7:2019,
436:(“Transmodel v6”)
432:EN 12896-6:2019,
429:(“Transmodel v6”)
425:EN 12896-5:2019,
422:(“Transmodel v6”)
418:EN 12896-4:2019,
415:(“Transmodel v6”)
411:EN 12896-3:2016,
408:(“Transmodel v6”)
404:EN 12896-2:2016,
401:(“Transmodel v6”)
397:EN 12896-1:2016,
175:Transmodel is an
158:transport network
130:European Standard
119:
118:
111:
93:
509:
379:
378:
376:
375:
360:
322:Transport Direct
166:journey planning
140:and specialised
134:public transport
124:, also known as
114:
107:
103:
100:
94:
92:
51:
27:
19:
517:
516:
512:
511:
510:
508:
507:
506:
482:
481:
463:
388:
383:
382:
373:
371:
361:
357:
352:
313:
287:
263:
210:
198:
154:
142:data structures
115:
104:
98:
95:
52:
50:
40:
28:
17:
12:
11:
5:
515:
505:
504:
499:
494:
480:
479:
474:
469:
462:
461:External links
459:
458:
457:
451:
444:
437:
430:
423:
416:
409:
402:
395:
392:
387:
384:
381:
380:
354:
353:
351:
348:
347:
346:
340:
334:
329:
324:
319:
312:
309:
286:
283:
271:Real-time data
262:
259:
209:
206:
197:
194:
153:
150:
117:
116:
31:
29:
22:
15:
9:
6:
4:
3:
2:
514:
503:
500:
498:
495:
493:
490:
489:
487:
478:
475:
473:
470:
468:
465:
464:
456:
452:
449:
445:
442:
438:
435:
431:
428:
424:
421:
417:
414:
410:
407:
403:
400:
396:
393:
390:
389:
370:
366:
359:
355:
344:
341:
338:
335:
333:
330:
328:
325:
323:
320:
318:
315:
314:
308:
306:
301:
297:
296:
291:
282:
280:
276:
272:
268:
258:
256:
252:
247:
245:
241:
236:
234:
230:
226:
221:
219:
215:
205:
203:
193:
189:
186:
182:
178:
173:
171:
167:
164:, schedules,
163:
159:
149:
146:
143:
139:
135:
131:
127:
123:
113:
110:
102:
91:
88:
84:
81:
77:
74:
70:
67:
63:
60: –
59:
55:
54:Find sources:
48:
44:
38:
37:
32:This article
30:
26:
21:
20:
454:
447:
440:
433:
426:
419:
412:
405:
398:
386:Bibliography
372:. Retrieved
368:
358:
317:TransXChange
304:
293:
292:
288:
279:TransXChange
264:
254:
248:
239:
237:
228:
224:
222:
213:
211:
199:
190:
174:
155:
147:
125:
121:
120:
105:
99:January 2024
96:
86:
79:
72:
65:
58:"Transmodel"
53:
41:Please help
36:verification
33:
486:Categories
467:Transmodel
374:2021-10-26
350:References
122:Transmodel
69:newspapers
244:formalism
311:See also
255:EN 12896
214:Cassiope
162:topology
339:(IFOPT)
196:History
128:, is a
83:scholar
345:(SIRI)
85:
78:
71:
64:
56:
472:NeTEx
332:NeTEx
295:NeTEx
229:TITAN
225:TITAN
152:Scope
90:JSTOR
76:books
477:OpRa
238:The
62:news
300:W3C
218:EEC
179:in
45:by
488::
367:.
257:.
246:.
377:.
112:)
106:(
101:)
97:(
87:·
80:·
73:·
66:·
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
