Deliverable 4.1: OVERALL REQUIREMENTS OF THE PILOTS SPECIFICATION OF ENHANCEMENTS OF TRANSMODEL V.4.1.1

Executive Summary

This report summarises the requirements expressed by users at the three pilot test sites, that is the decision makers and operating staff who rely on computerised information systems for running their business and the site developers and administrators of these systems.

For each site, internal reports were prepared describing the current state of the art. Assessments of the strengths and weaknesses of the existing information architectures and individual applications have been made.

Outline strategies are described for the future evolution of these systems to overcome perceived weaknesses, provide new functionality and generally keep information systems in step with changes in management processes and technological developments, especially the architectural setting for integrating systems.

Some key components of these strategies are being piloted and evaluated within the context of the Titan project, in particular the extent to which the Transmodel conceptual data model contributes to the understanding of the enterprise information requirements and the design of an integrated information system.

All three pilot sites want to interface several application systems by getting them to exchange shared data via a database implementation based on Transmodel. Transmodel does not mandate an implementation as a relational database, but all three pilot sites are doing so.

The pilot site implementations will validate the semantics of the existing Transmodel V.4.1 and amend as necessary. The process of validation will determine whether the entities, attributes and relationships in the model adequately express the user requirements of the sites.

They will also verify that the complete information architecture behaves correctly, in other words, that the database implementation and its interfaces do allow different application programs to share common data as specified in this user requirement.

The data structures within application programs may sometimes differ from those used for storing information in a relational database, and be based on a different conceptual model from Transmodel. Therefore it will be necessary to design interfaces for these application programs to communicate with the database.

Application programs serving the following functional areas have been selected for interfacing with the Transmodel based database at one or more sites:

- Study passenger behaviour and determine the demand (FA 1),

- (Re)design the network (FA 2),

- Plan the service to be offered (FA 3),

- Plan detailed journeys (FA 5),

- Schedule vehicle blocks (FA 6),

- Schedule driver duties (FA 7),

- Prepare driver rosters (FA 8),

- Manage driving personnel (FA 9),

- Automatic vehicle monitoring /AVM,

part of Perform and control the driving process (FA 11),

- Provide passenger information on the planned service (FA 13),

- Provide passenger information on the actual service (FA 14),

- Manage statistical results / MIS (FA 25),

- Manage personnel (FA 26), and

- Manage and represent geographical information.

Ultimately, the companies would like to integrate all their applications into this common framework. However, this is beyond the scope of the project, and therefore the above is a list of the highest priority needs.

The quality of the resulting system architecture will be evaluated using the CORD guidelines and in particular the "Evaluation Plan" as defined in TITAN Work Package 91.

Reference is made to a transport object modelling activity within the Titan project. Some operators are beginning to introduce object-oriented business models and applications within their companies and want O-O models and architectures to be registered as a user requirement. Object modelling is however not one of the expressed requirements of the three existing pilot sites.

top