Use of Transmodel

As Transmodel is a reference standard, it is not necessary for individual systems or specifications to implement Transmodel as a whole.

It needs to be possible to describe (for those elements of systems, interfaces and specifications which fall within the scope of Transmodel):

  • the aspects of Transmodel that they have adopted;

  • the aspects of Transmodel that they have chosen not to adopt.

Transmodel may prove of value to:

  • organisations within the public transport industry that specify, acquire and operate information systems;

  • organisations that design, develop and supply information systems for the public transport industry.

For an organisation within the public transport industry wishing to specify, acquire and operate information systems, Transmodel may be distilled, refined, or adapted to form a comprehensive data model for the organisation. This will enable the organisation to specify its database structures and/or its system interfaces, in such a way that separate modules can be tendered openly but will still integrate easily. The organisation also has a greater likelihood that information exchange interfaces with external organisations will be achieved easily.

For an organisation wishing to design, develop and supply information systems for the public transport industry, Transmodel may be distilled, refined, or adapted to form a comprehensive data model for the product suite. This will enable the organisation to develop its products in such a way that separate modules will integrate easily, but so that they also may be sold separately to clients seeking Transmodel-compliant systems.

Transmodel is a large and complex model, and allows for great flexibility. Consequently it takes some skills and resources to apply it effectively in order to develop the physical data model and its implementations for a particular aspect. For instance it might be applied to :

  • one particular functional domain such as vehicle scheduling or fare management; or

  • a particular interface, such as between a ticket machine and a management system; or

  • a particular organisational boundary, such as between two connecting transport operators.

For such situations, Transmodel provides a wider setting and a starting point. The specific elements of Transmodel have to be refined, and attributes and data formats will have to be completed, for a specific sub-model of the Transmodel data model. The resulting specification, although specific, will facilitate the build of a coherent overall systems framework, since it will coexist more readily with other Transmodel-based specifications.

For all of these potential users, the adoption of Transmodel as a basis for development means that a common language is being used. Thus users will understand and assess the claims of suppliers better, and specification developers will be more likely to be working in alignment with each other.