Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
4.5 CEN TC278 – Interoperable Public Transport Fare Management System<br />
Architecture (IFMSA)<br />
4.5.1 Description <strong>of</strong> the Standard<br />
CEN TC278 provides the basis for the development <strong>of</strong> a multi-operator/multi-modal<br />
interoperable<br />
Public Transport Fare Management System (IFM). The IFM system<br />
provides a reference functional architecture for electronic fare payment systems and<br />
identifies<br />
requirements that are relevant to ensure interoperability between the entities<br />
in the system.<br />
The IFM system addresses all the functions involved in the fare management<br />
process<br />
including:<br />
• Management <strong>of</strong> application(s)<br />
• Management <strong>of</strong> products<br />
• Security management<br />
• Customer management<br />
• Inspection/enforcement<br />
• Reporting and monitoring<br />
When<br />
<strong>com</strong>pleted, this standard will <strong>com</strong>prise several parts; currently only Part 1 is<br />
available in draft format. Part 1 describes the following main elements:<br />
• Identification <strong>of</strong> the different functional entities in relation to the overall fare<br />
management system<br />
• Definition <strong>of</strong> a generic model <strong>of</strong> IFM system describing the logical and<br />
functional architecture and the interfaces within the system and with other IFM<br />
systems<br />
• Use cases describing the interactions and data flows between the entities<br />
• Definition <strong>of</strong> the security requirements<br />
4.5.2 Applicability<br />
to UTFS Effort<br />
Although IFM provides a well-defined<br />
model for the management <strong>of</strong> an interoperable<br />
transit fare collection system, it is an in<strong>com</strong>plete draft as <strong>of</strong> today. In its current<br />
form,<br />
IFM is a high level document and does not include the<br />
level <strong>of</strong> detail that APTA is<br />
looking for and therefore is not applicable to APTA’s scope <strong>of</strong> work.<br />
On a higher level, this document is useful in defining the <strong>com</strong>ponents and entities<br />
involved in an electronic fare payment system as illustrated in Exhibit 4.5-1.<br />
Page 46