| |
|
 |
|
Thursday 20th 2008f November 2008
http://www.imm.dtu.dk/~db/colognet/train
|
Highlights
|
|
|
|
What is the TRain Effort?
The TRain Effort
is a proposal put forward for the
- formation, worldwide,
- of an Open, Free Consortium of
- railway people and institutions (companies, industries),
- of academics (ie., people, researchers, scientists),
and of research centres, within
- computer & computing science, and software engineering,
- transportation science & engineering,
- reliability and safety engineering, and
- operations research,
- on the subject of
- exploring,
- creating, ie., researching, and
- freely propagating (publishing, on the net, etc.),
- A Domain Theory for
the Railway Infrastructure.
Key Points:
Key points are:
- Research into the domain, not requirements,
not algorithms, not software,
- of "all things" railways (see below).
- Building up a public repository of railway system models.
Of course it is unavoidable that research into domains, result also
from research into and development of requirements and the design
of algorithms and software. Hence the TRain Effort will, obviously,
see research results, ie., reports, papers, etc., that contain
material on domains and requirements, or domains, requirements and
algorithms, or domains, requirements and software design.
TRain is more a group of people "gathered" around
- joint research,
- reports,
- workshops,
- conferences,
- a railway formalisations repository,
- a web-based TRain newsletter,
- and possibly a web journal,
than it is an
organisation.
The organisation, ie., the TRain Consortium, is needed as
a "mid-wife", to help secure and to help "magnify", a focused
collaboration.
The TRain Working
Groups are expected, in a sense,
- to be where "the real" work is being done (by its members)
- and co-ordinated (by its committee cum working group members).
It is through working groups that the TRain Effort will be
"kick-started".
The Basic Idea: The Overall Goals
The idea is that railways:
- that rail nets,
- their static (ie., topological) and
- dynamic (ie., signaling and switching ) properties,
- net development and maintenance, etc.,
- that rolling stock, its maintenance, deployment, etc.,
- that trains, their movement along the rails, that
is: Train traffic, etc.,
- that passenger ticketing, inquiries, ticket
cancellation, etc.,
- that freight handling: Reception, transfer,
tracing, delivery, etc.,
- that scheduling & allocation of
- timetables,
- rolling stock,
- staff,
- etc.,
- that net planning & development (construction),
- that entirely new forms of train service,
- etc.,
- that is, that all aspects of railways: Strategic,
tactical and operational management as well as operations
can all be both informally and formally fully adequately
described - but that such models need be developed individually,
and, formally, in rather different formal specification languages, and
harmonised (ie., "integration of formal methods"), as
well as communicated to all stake-holders.
The idea is to call for a "human
genome"-like, worldwide R&D, open
and free effort among university and railway
industry R&D centres to achieve the above.
|
|
|
Why this Train Effort?
The Railway Industry Justification:
The Whys
- Because IT, ie., computing systems, for all aspects of railways,
and especially for integrated, cross-related tactical and operational
management, monitoring and control, etc. applications, become more and
more important.
- Because the design of these computing systems is hard, to very hard: Often fraught with cost overruns, late deliveries, and erroneous software, etc.
- Because requirements for such systems are usually badly
formulated.
It is claimed that a proper, widely accepted Domain Theory for
Railways can help ameliorate the above situation.
- Before computing systems can be designed
one must understand the requiremements
- Before requirements can be formulated
one must understand the domain
Todays computing systems for the railway infrastructure are not
developed on the basis of anywhere near a reasonable understanding of
the railway domain.
The Computing Science Justification:
The Whys
- Because we need a grand challenge project in order to gather
enough momentum to make progress along the road to industrially
scalable and useful, integrated formal techniques.
The Science Justification:
The Whys
- Because there is no domain theory for such an important domain as
that of railways.
- The natural sciences, so reveals "their name", has domain
theories: Physics (mechanics, thermodynamics, electrivity, ...),
biology, etc.
- Is it not time for man-made structures to have their domain theories ?
Towards a Science of Man-made Infrastructure Components:
The Whys
- We deploy the name 'infrastructure' - really without knowing its
deeper, possible meanings.
- Transportation is one such infrastructure component.
- There are other infrastructure components:
- Financial service industry,
- health-care,
- public administration, etc.
- It seems high time someone started !
Sociologically and Psychologically:
The Whys
- Because it can be done.
- And because it is fun !
|
|
|
Who Should Participate
in the TRain Effort?
Rail infrastructure owners, train operators, rail and train technology industries,
mathematicians, operations researchers, computing scientists ! ?
Where to do it?
Geographic Places:
- In Australia and New Zealand.
- In Europe, across most countries of Europe.
- In India and the Far East: China and Japan.
- In North America: The US and Canada.
- In South America.
Institutional Places:
- In Universities.
- In Railway Infrastructure Companies.
- In Railway Operators.
- In Railway Technology Supply Industries.
- Etc.
|
|
|
How to Do It?
- Individuals, interested in the TRain Effort, should
- Working Group individuals should study the railway domain, and
describe
parts of it, informally
(but precisely) and formally, using any number of one or more formal
techniques.
- It is
neither
a matter of research into and development of
requirements engineering
nor software design:
But
it is research of the domain, the
basis for -
what goes before any
- requirements engineering and
software design.
- Researchers of the TRain Open Consortium should
co-ordinate
their efforts across the TRain Open Consortium - at least by
announcing: We are researching "such and such" a TRain area.
- Researchers of the TRain Open Consortium
should endeavour to
report,
at least yearly, with
one or more documents (reports or publications).
- Researchers of the TRain Open Consortium are expected to put their
research results, that is formal models of repective aspects of the
railway domain,
in the open, for free consumption.
- The TRain Secretariat shall endeavour to maintain a
TRain Repository
of
as many already existing and all future such "modelisations" - free
for anyone to use.
- Such research results are then expected to serve as
"patterns"
that can be used freely by anyone, in particular by the rail
technology industry, when developing new technologies for the railway
domain.
- Possibly the TRain Open Consortium should, preferably in
collaboration with one or more railway institutions - some of which
are listed in External Links -
organise special research events
(seminars, workshops, symposia, conferences,
congresses)
where results are presented and where "open problem"
challenges are identified.
- Generally: The TRain Open Consortium should encourage
publication, training,
education events
(summer schools, courses,
etc.), etc.
- The TRain Open Consortium could
influence
national and
international rail organisations toward deployment of published domain
formalisation in national and international development projects.
- The TRain Open Consortium shall
not advocate special techical approaches
- but, and this is, of course, important:
Advocate
the use of
carefully (informal language) narrated (annotated)
formalisations.
When to Do It?
- Now, as from 2004, as a co-ordinated TRain Open Consortium effort.
- And the next 10-20 years !
|
|
|
What is meant by "A Grand Challenge"?
This section is an edited quote of 17 grand challenge criteria reported by Tony Hoare:
- The Verifying Compiler: A Grand Challenge for Computing Research.
- Journal of the ACM, Vol.50, No.1, January 2003, pp 63-69.
We edit, while in the process of seeking formal permission, our quote -
where 'it' normally refers to any proposed grand challenge -- into:
- Fundamental: It relates strongly to foundations, and the nature and limits of a discipline.
- Astonishing: It implies constructing something ambitious, heretofore not imagined.
- Testable: It must be objectively decidable whether a grand challenge project endeavour is succeeding or failing.
- Revolutionary: It must imply radical paradigm shifts.
- Research-oriented: It can be achieved by methods of academic research -- and is not likely to be met sôlely by commercial interests.
- Inspiring: Almost the entire research community must support it, enthusiastically -- even while not all may be engaged in the endeavour.
- Understandable: Comprehensible by - and captures the imagination of - the general public.
- Challenging: Goes beyond what is initially possible and requires insight, techniques and tools not available at the start of the project.
- Useful: Results in scientific or other rewards - even if the project as a whole may fail.
- International: It has international scope: Participation would increase the research profile of a nation.
- Historical: It will eventually be said: It was formulated years ago, and will stand for years to come.
- Feasible: Reasons for previous failures are now understood and can now be overcome.
- Incremental: Decomposes into identified individual research goals.
- Co-operative: Calls for loosely planned co-operation between research teams.
- Competitive: Encourages and benefits from competition among individuals and teams - with clear criteria on who is winning, or who has won.
- Effective: General awareness and spread of results changes attitudes and activities of scientists and engineers.
- Risk-managed: Risks of failure are identified and means to meet will be applied.
We believe that the TRain project meets the above criteria.
|
|
|
What is meant by "An Open, Free Consortium"?
By an open consortium is meant a loosely knit collection of
individuals: Researchers, software engineers, railway technologists,
etc., and of their host institutions: Universities, railway companies,
research centres, etc. The "loose knit" is The TRain Consortium.
At any time individuals and institutions may
enter (or leave) the open consortium.
Individuals: People and Institutions
Each individual (person) or institution acts individually.
There is no
legal or financial, contractual relationship between any two distinct
institutions nor individuals from distinct institutions, binding them in
any other by way than their offering one another the fruits of their
individual research on TRain related matters.
By "acting" together, as the TRain Open, Free Consortium", it is
expected that each individual, each institution will be spurred on to
a more concerted effort, including even joint efforts, towards
"modelisation" of "all things" railways.
No Common/Shared Funding
By an open and free consortium of the kind proposed here is also meant that
there is no central funding source, no shared or common capital from which
TRain research and other TRain activities may be funded.
TRain individuals and institutions are themselves to secure any needed
funding.
Research Funding
Although the TRain Consortium will and shall not act as a funding
agency, it may well decide to support identified national or
international railway domain research projects. This support is not
financial. Rather it could be support, say in the form of written
recommendations to national or international funding agencies, of
proposed research efforts.
How such support can manifest itself remains to be formulated.
Possibility of Joint Research
The TRain Consortium shall be pro-active in encouraging and in helping to
arrange joint research efforts.
"Blue Seals" of "Approval"
Whether the TRain Consortium can otherwise issue "blue seals" of
approval of individual or joint research efforts remains to be seen.
Our current "thinking" is: Rather not. We would rather like to see
research efforts emerge and survive, ie., attract attention, on
their own scientific merits.
We would like to believe that subscribing to the TRain Consortium
Charter suffices as a qualifier.
|
|
|
What is meant by
"A Formal Technique cum Method"?
- An attempt is made to encircle the concept of `Formal Method' as it
has become known in Computing.
- We put forward our own view of this.
- We discuss, briefly, whether the term `formal method' is an
appropriate term in the contexts in which it is being commonly used.
- To balance our views off, we bring references to other `Formal Method'
delineating statements.
- We also refer, here, to a "subjective", ie., not necessarily
complete, List of Some Formal
Techniques cum Methods.
-
What is a Method ?
- By a method is meant a set of
principles
that are used in
selecting and applying a number of
techniques
and
tools
in order to
identify and analyse a problem and
synthesize (construct) a solution to the problem.
- Normally one would expect a good method to be ``efficient'' and
result in ``efficient'' solutions.
-
What is meant by Formal ?
In the context of software (hardware) development, the term `Formal'
is usually considered to imply the following:
- There is a
language,
a so-called
formal
language,
for expressing problem characterisations and/or
problem solutions, at various levels of abstraction.
- We usually refer - interchangeably -
to such a language as a specification, a design, or a
programming language.
- That language must have the following three properties in order to
qualify as a formal specification (design or programming) language:
- It must have a precise, ie., a mathematically well defined
syntax
- something which defines all such
sentences and/or
diagrams (or other) which are members of the language.
- It must have a precise, ie., a mathematically well defined
semantics
- something which to every
syntactically well-formed
sentence and/or diagrams (or other) which are members of the
language ascribe a precise meaning in terms of some mathematical
structure.
- It must have a
proof system:
That is,
a set of axioms and proof
(ie., inference and/or deduction) rules by means of which one can reason over
all syntactically well-formed sentence and/or diagrams (or other)
of the language.
- It is expected that the Language Semantics have been shown to be
a Model of the Proof System.
-
What, then, is a Formal Method ?
A `Formal Method', then, is a `Method' some of whose main `Techniques' and
main `Tools' depend crucially upon the use of Formal Languages.
-
Some Observations:
- A major Tool, in development (ie., in analysing problems and in
synthesising problem solutions), is that of language.
- Major Techniques, in development, are then various calculi that
apply to fragments or whole specifications and yield sentences in
some formal language.
- Derivative Tools then support the use of languages and calculi.
-
Whither Formal Method ? -- Why not just Formal
Techniques ?
- Now, since a `Method' is taken to be used by humans, and since we take
it, as a dogma, that the selection and application of method principles
is to be decided upon by these humans, from case to case, as inspired
by the complexities and/or novelties (or familiarities) of the
problem, we conclude that a method cannot be formal !
- Instead we resolve that some method Techniques and some method
Tools (to support, or express) these Techniques, can, indeed, be
formal, respectively be based on formal languages.
Other views of what `Formal Methods'
are:
|
|
|
List of Some Formal Techniques cum Methods
- ACL2:
Applicative Common Lisp, a Computational Logic
- Action
Systems:
A
refinement calculus for parallel and reactive systems
- ASM:
Abstract-State Machines
-
B, event-B:
B
France, or
B:
UK - for
Bourbaki
- CafeOBJ:
A rewrite logic and hidden algebra OBJ-like specification and
programming language
- CASL:
Common Algebraic Specification Language
- Coq:
A proof
assistant. Coq, as a project, has been dissolved, 2000. Now see
LOGICAL
- CSP:
Communicating Sequential Processes
- Duration
Calculi:
A continuous time interval
temporal logic
- Esterel:
Synchronous teactive programming
- HOL:
Higher Order Logic
- HyTech:
Hybrid Technology -- an automatic tool for the analysis of embedded systems
- Isabelle:
A generic theorem proving environment
- Interval Temporal
Logic
- Linear Temporal
Logic
- LSCs:
, and
Live Sequence
Charts
- LOGICAL:
Logic and computing
- Maude:
Algebraic semantics based equational and rewriting logic
specification and programming language
- MSCs:
,
and Message Sequence
Charts, or
even
this !
- Model-checking @ CMU
- Nqthm:
The Boyer-Moore prover
- nuprl:
A proof & program refinment logic.
- Petri Nets
- Pi-Calculus:
Calculi for Mobile Processes
- PVS:
Prototype
Verification System
- Refinement
Calculus
- RAISE:
Rigorous Approach to Industrial Software Engineering
- REACT:
The
specification, verification and
synthesis
of
concurrent, reactive, real-time and hybrid systems.
See also
STeP:
Stanford Temporal Prover.
- SpecWare
- SPIN:
On-the-fly Linear Temporal Logic Model Checking
- Statecharts
- TLA /
TLA+
Temporal Logic of Actions
- UNITY:
A programming notation and a logic to reason about parallel and
distributed programs.
- UppAal:
An integrated tool environment for modeling, validation and
verification of real-time systems
- VDM:
Vienna Development Method
- Z
- for Zermelo
|
|
|
The TRain Charter
By the TRain Charter we shall mean a document which spells out:
- Aims & Objectives:
- What does the TRain Consorium wish to achieve, why, how, by whom, etc.
- Instrumentation:
- The way in which the TRain Effort is instrumented - how it is going to
achieve its aims & objectives - by computing as well as transportation
scientists, rail infrastructure owners, train operators, railway
technologists, operations researchers, international rail-related
associations, etc.
The TRain is thus expected to spell out :
- The organisational structure of the TRain Consortium:
- Presidium - its role
- Board - its role
- Membership - their roles
- Committees - their roles
- Secretariat - its role
- TRain activities:
- Individual and joint research
- Publications: Reports, proceedings, books, possibly a journal (?)
- Workshops - as organised and sponsored by one or more Committees
- ...
- National and International Liasion:
- With national and international rail infrastructyre owners
- With national and international train operators
- With national, regional and international railway related R&D projects
- With regional and international standards organisations
- With national, regional and international railway associations...
- Etcetera
The TRain Charter is like "The Constitution" of the
TRain Consortium, something to which members "swear allegiance~!".
More text - as well as The Charter itself to become available soon.
We should strive for an "ultra-short" Charter document!
|
|
|
The TRain By-laws
By the TRain By-Laws we shall mean a document which
spells out:
- How to become
- a member of the TRain Consortium
- elected to, ie., a member of the TRain Presidium
- elected to, ie., a member of the TRain Board
- elected to, ie., a member of a TRain Committee
- Rules concerning decision making
- in the Presidum
- in the Board
- In the Committees
- ...
- Etcetera
The TRain By-Laws are like "The
Rules & Regulations" of the TRain Consortium.
More text - as well as The By-Laws themselves
to become available "sometime" in 2004.
We should strive for an "ultra-short" By-Laws document!
|
|
|
Presidium
General
The Presidium is a body of possibly 30 to 50 members of the TRain
Consortium.
It is like a "parliament", a "general assembly".
The Presidium, in a sense, represents the broader interests of the
Membership:
- Computing Scientists & Software Engineers,
ransportation Scientists & Engineers, and
Operations Researchers:
- Computing and transportation technology scientists and operations
researchers, in universities, and in public and private research
centres, are expected to be the main "carriers" of the main TRain
effort: The research.
- Rail Infrastructure Owners, and Train Operators
- The infrastructure owners and the operators are the
end-target users of the results of the TRain effort.
- Railway Technology Industry
- The railway technology industry includes R&D departments,
consultancy firms and software houses, the latter usually under contract
to the larger rail technology industries, Together they have an
interest in deploying the "modelisations" emerging from the TRain Effort.
- Railway-related Intl. Associations
- Etcetera.
The Presidium is responsible for formulating the long term strategy
and tactics. The Presidium then asks the TRain Board to carry out this
strategy and those tactics.
The Board is elected out of the Presidium.
The Presidium is (somehow) elected out of the Membership.
The composition and size of the Presidium shall reflect the
stake-holders, as listed above, and should reflect a geo-political
balance, as needed.
The Presidium is expected to primarily deliberate through the use of
the Internet technology: Internal, access controlled web pages as well
as by e-mail.
The Presidium is expected to otherwise meet every 18 months, or
so, in connection with major TRain Effort Events: Symposia,
Conferences, Congresses, etc. - or similar.
More text to follow here, and otherwise in the
TRain Charter and By-Laws.
Initial Presidium Members
- Dines Bjorner, Denmark
- Ted C. Giras, USA
- Yuji Hirao, Japan
- Takahiko Ogino, Japan
- Martin Penicka, Czech Republic
- Wolfgang Reif, Germany
- Denis Sabatier, France
- Eckehard Schnieder, Germany
- Miroslav Vlcek, Czech Republic
- Alistair A. McEwan, UK
- Xiao GuiPing, China
|
|
|
The TRain Board
General
The TRain Consortium Board is a body of initially 10-12 people.
The Board is elected by the TRain Presidium.
The Board should reflect the composition of the Membership (cum Presidium):
- The rail infrastructure owners,
- the train operators,
- the rail technology industry,
- the international rail/train organisations,
- the transportation science community,
- the mathematical cum operations research community, and
- the computing science community.
Roles, rules & regulation concerning the Board is otherwise (to be)
described by the TRain Charter and By-Laws.
The Board shall carry out the TRain Consortium strategy (and
tactics) as formulated by the Presidium, shall guide the Committees,
and report, otherwise, to the Presidium and Membership.
Individual Board members have designated roles to play. Some of
these roles are
sketched below. Others will emerge later and from the TRain Charter.
The Initial TRain Board
Chair (Europe)
Dines Bjorner
Dept. of Computer Science and Engineering, Institute of Informatics
and Mathematical Modeling, Building 322, Technical University of Denmark.
DK-2800 Kgs.Lyngby, Denmark.
E-mail: db "ad" imm.dtu.dk
-
Initial Role:
Get the "ball" rolling. General "whip".
Vice-Chairs (Asia)
Mr. Takahiko Ogino (Shared with Hirao-san)
Chief Researcher, Transport Information Technology Division,
Railway Technical Research Institute, 2-8-38 Hikari-cho, Kokubunji-shi, Tokyo, 185-8540 Japan
Phone: +81-42-573-7309, Fax: +81-42-573-7305,
E-mail: ogino "ad" rtri.or.jp
Mr. Yuji Hirao (Shared with Ogino-san)
Gen.Mgr., Signalling & Telecommunications Technology Development Dept.,
Railway Technical Research Institute, 2-8-38 Hikari-cho, Kokubunji-shi, Tokyo, 185-8540 Japan
Phone: +81-42-573-7326, Fax: +81-42-573-7321,
E-mail: hirao "ad" rtri.or.jp;
Prof., Dr. Xiao GuiPing
Transportation Safety,
School of Traffic and Transportation, Northern JiaoTong Univ., Beijing
100044, China
Phone: +86-1.365.111.9107, Fax: +86-10-5148-0080,
E-mail: gpxiao "ad" center.njtu.edu.cn
-
Initial Role of Asian Board Members:
Propagate awareness about and secure Asian (China, Japan) rail
infrastructure
owner, train operator, and rail technology
industry interests in the TRain Effort.
Vice-Chair (North America)
Prof. Ted C. Giras
ECE Department, Thornton Hall, 351 McCormick Rd., P.O. Box 400743,
Charlottesville,
VA, 22904-4743, USA
Tel:(434) 924-6986
E-mail: tcg6f "ad" virginia.edu
-
Initial Role:
Propagate awareness about and secure North American
(US and Canada) rail infrastructure
owner, train operator, and rail technology
industry interests in the TRain Effort.
Intl.Rail-Relations Chair
Prof., Dr.ing. Eckehard Schnieder
Institute of Transportation Safety and Automation, Technical University of
Braunschweig, Langer Kamp 8, D-38106 Braunschweig, Germany
Phone: +49-531/391-3317, Fax:
+49-531/391-5197,
E-mail: sek "ad" iva.ing.tu-bs.de
-
Initial Role:
Propagate awareness of in secure interest, by the international
rail-related associations, etc., and the German
railway industry, in the TRain Effort.
Operations Research Chair
Prof., Dr. Miroslav Vlcek
Vice-rector for International Relations, Head of the Department of
Applied Mathematics,
Faculty of Transportation Sciences, Czech Technical University, Na
Florenci 25, CZ-11000 Prague 1,
The Czech Republic.
E-mail: vlcek "ad" fd.cvut.cz, vlcek "ad" vc.cvut.cz
-
Initial Role:
Propagate awareness of and secure the interest of the
operations research community in the TRain Effort.
Computing Science Chair - I
Dr. Denis Sabatier
ClearSy, 1330, rue Guilibert Gauthier de la Lauziere, Europarc de Pichaury,
Bâtiment C2, F-13856 Aix en Provence,
Cedex 3, France
Phone: 04.42.37.12.70 Fax :04.42.37.12.71,
E-mail: denis.sabatier "ad" clearsy.com
-
Initial Role:
Propagate awareness of and secure the interest of the
computing science (etc.) community and the French railway
industry in the TRain Effort.
|
|
|
The TRain Committees cum Working Groups
The TRain Effort is (possibly most effectively, most visibly)
carried by the works of individuals of working groups.
The TRain Working Groups
each handle a cluster of TRain domain research
issues, for example:
- Rail net: statics and dynamics (incl. signaling),
- traffic planning: Scheduling and allocation,
- train and traffic operations (overlaps with first above),
- train and net maintenance, staff rostering, etc.
- net planning and development,
- safety-critical assessment,
- etc., etc.
Committees may "come and go": They are set up, by requests from
active researchers of the TRain Membership. They "report" to the
biennial (or so) Presidium Assemblies.
Individuals, researchers of TRain Domain
Issues,
- set up a working group,
- around a more-or-less narrowly defined topic,
- start researching that topic,
- gather colleagues, from around the world,
- to also work on that topic,
- arrange workshops,
- etc.
The committees shall help register
- past and
- ongoing research.
The committees shall interact with the Secretariat in maintaining
an electronic Repository of TRain-related documents:
- Reports,
- manuals,
- standards,
- journal articles,
- proceedings, and
- books.
The committees shall, individually, or as a group, arrange
- workshops,
- symposia,
- conferences and
- congresses.
Each committee shall endeavour to sketch research agendas:
- Open issues,
- outstanding/unsolved problems,
- etc.
The group of committee shall (if need be) investigate need for a
Proposed Committees
Any overlap in the work of the below sketched/proposed committees
is seen as purely beneficial.
- "Modelisation" of Railway Signalling Issues
Interlocking, line block management, line direction management, etc.
- "Modelisation" of Time Tabling and Net
Development Issues
Passenger statistics versus (long term) net planning
- "Modelisation" of Train and Net Maintenance
Issues
Scheduled, and unscheduled maintenance of cars, rails, signals, etc.
- "Modelisation" of Passenger Handling Issues
Information, inquiries, ticket sales, journey planning, ticketing, etc.
- "Modelisation" of Freight Handling Issues
Information, inquiries, freight receipt, handling, delivery, tracing
- "Modelisation" of Strategic Railway System Issues
- Etcetera ...
Initial Working Groups
Railway Net Topology:
Dines Bjorner, Martin Penicka, ...
Interlocking:
Martin Penicka, Dines Bjorner, ...
Signals:
Martin Penicka, Dines Bjorner, ...
Time Tabling and Nets:
Martin Penicka
Train Composition & Decomposition:
Martin Penicka
Train Maintenance:
Martin Penicka
Line Direction Agreement Protocols:
Martin Penicka
Automatic Line Signalling Systems:
Martin Penicka
Axiomatic Safety-Critical Assessment
Ted C. Giras, ...
...
...
|
|
|
A Consortium Secretariat
Mr. Martin Penicka
Faculty of Transportation Sciences, Czech Technical University, Na Florenci 25,
CZ-11000 Prague 1, The Czech Republic.
Phone: +420 224 890 718; Fax: +420 224 890 702
E-Mail: penicka "ad" fd.cvut.cz
|
|
|
International Rail Organisations
and undoubtedly many more.
|
|
|
Other Railway Research Sites
- EURNEX
EURNEX is the European Rail Research Network of Excellence and
aims to integrate a fragmented research landscape, promote the
railways contribution to sustainable development and improve the
competitiveness and economic stability of the European rail sector.
- CyberRail
CyberRail is an implementable concept for railway transport: It
introduces a "tour conductor concept" which relies on
applying IT to the construction
of the environment (humans etc.)
for intermodal transport. CyberRail then realises seamless
movement and tailor-made travel by rail and other transport modes.
- The railML.org
Initiative
The railML.org was founded in early 2001. Its main
objective is to enable a heterogeneous set of railway applications
to communicate with each other. The purpose of this website is to
find, discuss and present systematic, XML-based solutions for the
simplified data exchange between railway applications. Such
standardised data is based on a collection of XML schemes, which
together form the Railway Markup Language "railML" the product
of the railML initiative.
- AMORE
Algorithmic Methods for Optimizing the Railways in Europe
- EU Rail
Transport - Seems outdated ?
The EU Transport RTD Programme's Transport Research Projects
|
|
|
|
|
http://www.imm.dtu.dk/~db/colognet/train
|
| TRain Web Site |
Copyright © 2004 | martin@imm.dtu.dk |
