{"id":231163,"date":"2024-10-19T15:03:07","date_gmt":"2024-10-19T15:03:07","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iso-24014-12015\/"},"modified":"2024-10-25T09:21:01","modified_gmt":"2024-10-25T09:21:01","slug":"bs-en-iso-24014-12015","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iso-24014-12015\/","title":{"rendered":"BS EN ISO 24014-1:2015"},"content":{"rendered":"
This part of ISO 24014<\/span> <\/span> provides the basis for the development of multi-operator\/multi-service Interoperable public surface (including subways) transport Fare Management Systems (IFMSs) on a national and international level.<\/p>\n This part of ISO 24014<\/span> <\/span> is applicable to bodies in public transport and related services which agree that their systems need to interoperate.<\/p>\n While this part of ISO 24014<\/span> <\/span> does not imply that existing interoperable fare management systems need to be changed, it applies so far as it is practically possible to extensions of these.<\/p>\n This part of ISO 24014<\/span> <\/span> covers the definition of a conceptual framework which is independent of organisational and physical implementation. Any reference within this part of ISO 24014<\/span> <\/span> to organisational or physical implementation is purely informative.<\/p>\n The objective of this part of ISO 24014<\/span> <\/span> is to define a reference functional architecture for IFMSs and to identify the requirements that are relevant to ensure interoperability between several actors in the context of the use of electronic tickets.<\/p>\n The IFMS includes all the functions involved in the fare management process such as<\/p>\n management of application,<\/p>\n<\/li>\n management of products,<\/p>\n<\/li>\n security management, and<\/p>\n<\/li>\n certification, registration, and identification.<\/p>\n<\/li>\n<\/ul>\n This part of ISO 24014<\/span> <\/span> defines the following main elements:<\/p>\n identification of the different set of functions in relation to the overall fare management system;<\/p>\n<\/li>\n a generic model of IFMS describing the logical and functional architecture and the interfaces within the system and with other IFMSs;<\/p>\n<\/li>\n use cases describing the interactions and data flows between the different set of functions;<\/p>\n<\/li>\n security requirements.<\/p>\n<\/li>\n<\/ul>\n This part of ISO 24014<\/span> <\/span> excludes consideration of the following:<\/p>\n the physical medium and its management;<\/p>\n<\/li>\n the technical aspects of the interface between the medium and the medium access device;<\/p>\n<\/li>\n the data exchanges between the medium and the medium access device;<\/p>\n The data exchanges between the Medium and the Medium Access Device are proposed by other standardization committees.<\/p>\n<\/p><\/div>\n<\/li>\n the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).<\/p>\n<\/li>\n<\/ul>\n Public transport. Interoperable fare management system – Architecture<\/b><\/p>\n\n
\n
\n
PDF Catalog<\/h4>\n
\n
\n PDF Pages<\/th>\n PDF Title<\/th>\n<\/tr>\n \n 4<\/td>\n Foreword
Endorsement notice <\/td>\n<\/tr>\n\n 7<\/td>\n Foreword <\/td>\n<\/tr>\n \n 8<\/td>\n Introduction <\/td>\n<\/tr>\n \n 9<\/td>\n 1\tScope <\/td>\n<\/tr>\n \n 10<\/td>\n 2\tTerms and definitions <\/td>\n<\/tr>\n \n 12<\/td>\n 3\tAbbreviated terms
4\tRequirements <\/td>\n<\/tr>\n\n 13<\/td>\n 5\tConceptual framework <\/td>\n<\/tr>\n \n 14<\/td>\n 5.1\tDescription of IFM-roles <\/td>\n<\/tr>\n \n 16<\/td>\n 5.2\tBasic framework of the generic IFM functional model <\/td>\n<\/tr>\n \n 17<\/td>\n 6\tUse Case description for the IFM functional model
6.1\tCertification <\/td>\n<\/tr>\n\n 18<\/td>\n 6.1.1\tCertification of Organization
6.1.2\tCertification of Components
6.1.3\tCertification of Application Specification and Template <\/td>\n<\/tr>\n\n 19<\/td>\n 6.1.4\tCertification of Product Specification and Template
6.2\tRegistration
6.2.1\tRegistration of Organization <\/td>\n<\/tr>\n\n 20<\/td>\n 6.2.2\tRegistration of Component
6.2.3\tRegistration of Application Template
6.2.4\tRegistration of Application
6.2.5\tRegistration of Product Template <\/td>\n<\/tr>\n\n 21<\/td>\n 6.2.6\tRegistration of Product
6.3\tManagement of Application
6.3.1\tDissemination of Application Template <\/td>\n<\/tr>\n\n 22<\/td>\n 6.3.2\tAcquisition of Application
6.3.3\tTermination of Application Template <\/td>\n<\/tr>\n\n 23<\/td>\n 6.3.4\tTermination of Application <\/td>\n<\/tr>\n \n 24<\/td>\n 6.4\tManagement of Product
6.4.1\tDissemination of Product Template <\/td>\n<\/tr>\n\n 25<\/td>\n 6.4.2\tTermination of Product Template
6.4.3\tManagement of Action List <\/td>\n<\/tr>\n\n 26<\/td>\n 6.4.4\tAcquisition of Product
6.4.5\tModification of Product parameter <\/td>\n<\/tr>\n\n 27<\/td>\n 6.4.6\tTermination of Product
6.4.7\tUse and inspection of Product <\/td>\n<\/tr>\n\n 28<\/td>\n 6.4.8\tCollection of data <\/td>\n<\/tr>\n \n 29<\/td>\n 6.4.9\tForwarding data
6.4.10\tGeneration and distribution of clearing reports <\/td>\n<\/tr>\n\n 30<\/td>\n 6.5\tSecurity management
6.5.1\tMonitoring of IFM processes and IFM data life cycle <\/td>\n<\/tr>\n\n 31<\/td>\n 6.5.2\tManagement of IFM security keys
6.5.3\tManagement of security lists <\/td>\n<\/tr>\n\n 33<\/td>\n 6.6\tCustomer Service Management (optional) <\/td>\n<\/tr>\n \n 34<\/td>\n 7\tSystem interface identification
8\tIdentification
8.1\tGeneral
8.2\tNumbering scheme
8.3\tPrerequisites <\/td>\n<\/tr>\n\n 35<\/td>\n 9\tSecurity in IFMSs
9.1\tProtection of the interests of the public
9.2\tAssets to be protected <\/td>\n<\/tr>\n\n 36<\/td>\n 9.3\tGeneral IFM security requirements <\/td>\n<\/tr>\n \n 37<\/td>\n Annex\u00a0A (informative) Information flow within the IFM <\/td>\n<\/tr>\n \n 47<\/td>\n Annex\u00a0B (informative) Examples of implementation <\/td>\n<\/tr>\n \n 56<\/td>\n Annex\u00a0C (informative) List of terms which are defined both in this part of ISO\u00a024014 (IFMSA) and in APTA \u2014 UTFS <\/td>\n<\/tr>\n \n 57<\/td>\n Annex\u00a0D (informative) Example of Action List processes <\/td>\n<\/tr>\n \n 62<\/td>\n Annex\u00a0E (informative) Security domain, threats, and Protection Profiles <\/td>\n<\/tr>\n \n 66<\/td>\n Annex\u00a0F (informative) Media centric management and back-office centric management <\/td>\n<\/tr>\n \n 68<\/td>\n Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" \n\n
\n Published By<\/td>\n Publication Date<\/td>\n Number of Pages<\/td>\n<\/tr>\n \n BSI<\/b><\/a><\/td>\n 2015<\/td>\n 72<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":231167,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[698,2641],"product_tag":[],"class_list":{"0":"post-231163","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-35-240-60","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/231163","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/231167"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=231163"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=231163"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=231163"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}