{"id":581,"date":"2024-03-08T15:47:50","date_gmt":"2024-03-08T14:47:50","guid":{"rendered":"http:\/\/localhost\/?page_id=581"},"modified":"2024-09-17T08:21:36","modified_gmt":"2024-09-17T06:21:36","slug":"standards-for-implementation","status":"publish","type":"page","link":"https:\/\/transmodel-cen.eu\/index.php\/standards-for-implementation\/","title":{"rendered":"Standards for implementation"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Standard for implementation<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Link functions vs. data<\/h2>

The domain of Public Transport may be\u00a0 described in terms of functions or functional areas. One of the problems related to the definition of a domain in terms of the functional areas is to be independent from the organisational aspects of Public Transport companies and from time aspects.<\/p>

The functional areas defined in Transmodel can be understood as objectives of the system being defined<\/b>.<\/p>

Twenty eight (28) functional areas have been identified by Transmodel, as shown in the following table:<\/p>

Not all functional areas have been studied during the development of Transmodel (shaded areas are outside the scope of Transmodel). For some of the studied functional areas the data necessary has been defined for <\/span>all functions<\/b><\/span> in such a functional area (Y). Some areas are only <\/span>partly covered<\/b><\/span> (P) by the data model, which means that <\/span>all <\/b><\/span>data are described for <\/span>some of the functions only<\/b><\/span>.<\/span><\/p>

\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Transmodel area number<\/th>Transmodel area name
\n<\/th>		Covered by Transmodel<\/th>\n<\/tr>\n<\/thead>\n
1<\/td>Study passenger behaviour and determine the demand <\/td><\/td>\n<\/tr>\n
2<\/td>(Re)design the network<\/td><\/td>\n<\/tr>\n
3<\/td>Plan the service to be offered
\n<\/td>		P<\/td>\n<\/tr>\n
4<\/td>Define a fare policy<\/td>P<\/td>\n<\/tr>\n
5<\/td>Plan detailed timetables
\n<\/td>		Y<\/td>\n<\/tr>\n
6<\/td>Schedule vehicle blocks<\/td>Y<\/td>\n<\/tr>\n
7<\/td>Schedule driver duties<\/td>Y<\/td>\n<\/tr>\n
8<\/td>Prepare driver rosters<\/td>Y<\/td>\n<\/tr>\n
9<\/td>Manage drivers<\/td>Y<\/td>\n<\/tr>\n
10<\/td>Manage vehicles<\/td>P<\/td>\n<\/tr>\n
11<\/td>Perform and control the driving process<\/td>Y<\/td>\n<\/tr>\n
12<\/td>Plan and organise passenger information<\/td><\/td>\n<\/tr>\n
13<\/td>Provide passenger information on the planned service<\/td>Y<\/td>\n<\/tr>\n
14<\/td>Provide passenger information on the actual service<\/td>Y<\/td>\n<\/tr>\n
15<\/td>Plan maintenance work<\/td><\/td>\n<\/tr>\n
16<\/td>Plan and process maintenance orders<\/td><\/td>\n<\/tr>\n
17<\/td>Control maintenance work<\/td><\/td>\n<\/tr>\n
18<\/td>Manage incidents<\/td>P<\/td>\n<\/tr>\n
19<\/td>Analyse maintenance actions<\/td><\/td>\n<\/tr>\n
20<\/td>Manage material<\/td>P<\/td>\n<\/tr>\n
21<\/td>Organise sales<\/td>P<\/td>\n<\/tr>\n
22<\/td>Operate sales<\/td>P<\/td>\n<\/tr>\n
23<\/td>Validate\/check and charge<\/td>Y<\/td>\n<\/tr>\n
24<\/td>Manage money transactions<\/td><\/td>\n<\/tr>\n
25<\/td>Manage statistical results<\/td>P<\/td>\n<\/tr>\n
26<\/td>Manage personnel<\/td>P<\/td>\n<\/tr>\n
27<\/td>Define marketing policy<\/td><\/td>\n<\/tr>\n
28<\/td>Improve and maintain the relation with the public<\/td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/span><\/p>

Table 1: Functional areas identified by Transmodel<\/em><\/span><\/p>

Transmodel documentation provides indications as regards the functional coverage of each functional area.<\/p>

Conceptual model vs. implementation<\/h2>

Transmodel describes the domain of public transport in terms of data structures for a range of functional areas in an implementation-independent way<\/b>.<\/p>

This means in particular, that Transmodel may be implemented as<\/b> a data repository (data base, e. DDL schema) or used for the exchange of data (definition of a data exchange format, e.g. XML).\u00a0 (See figure below, source NeTEx \u2013 1).<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t
Figure 1: UML model to XML <\/figcaption>\n\t\t\t\t\t\t\t\t\t\t<\/figure>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In any case, for the design of a data base or of a data exchange format, if intended to be derived from Transmodel<\/a>, the steps are as follows:\u00a0<\/p>