Since 2004 Italy runs DATEX data exchange aiming at automatic VMS management between Traffic Control Centres. Autostrade per l'Italia and Padova Venezia agreed on a common interpretation of old DATEX phrases that were mapped to VMS messages and pictograms to be displayed on VMS.
This work was more and more refined in the framework of the first results of the European and National Mare Nostrum project results that was launched in those years
The result of this work was the need to exchange the information of VMS Status (displayed messages and failures) between the centres in order to check how the information exchanged by DATEX was used to manage VMS messages based on the agreed rules..
This request was solved with a simplified solution for Italy but the claim for such a feature was more and more addressed to former DATEX TC and SMC, but at that time more pressing needs for launching and managing DATEX2 projects outputs and further refinements needed, led to a model containing a simplified modeling that was used mostly by UK implementers.
Since 2007 Italy and UK cooperated in proposing a model to manage most of functionalities of known VMS, based of a large knowledge of Variable Signs in the 2 countries with some experience of other VMS managed in the Mare Nostrum Project.
The result is the model that you may find at the deployments Extensions section on this website (http://www.datex2.eu/content/vms-publication-extension) , that can be further refined but is a good point of start to model VMS information exchange in most of use cases.
The aim of this forum is to improve the proposed model, clarifying its usage and illustrate at best the choices that are underneath in order to finalize a ultimate VMS modeling for CEN submission in decembre 2009.
A variable message sign, often abbreviated VMS, CMS, or DMS, and in the UK known as a matrix sign, is an electronic traffic sign often used on roadways to give travelers information about special events. Such signs warn of traffic congestion, accidents, incidents, roadwork zones, or speed limits on a specific highway segment. In urban areas, VMS are used within parking guidance and information systems to guide drivers to available car parking spaces. They may also ask vehicles to take alternative routes, limit travel speed, warn of duration and location of the incidents or just inform of the traffic conditions. A complete message on a panel generally includes a problem statement indicating incident, roadwork, stalled vehicle etc, a location statement indicating where the incident is located; an effect statement indicating lane closure, delay, etc and an action statement giving suggestion what to do traffic conditions ahead. These signs are also used for AMBER Alert and Silver Alert messages.
I am a student of microsoft training and i am so much specialties in the network solution's.
The French partners of the mirror-group have analysed the WMS publication proposal as know beginning of April.
Several comments have be issued and are grouped into a document (VMS publication_FRcomments_20090617.doc) which will be uploaded on this website.
Some comments deal with details but others are more fundamental.
One of our main issues is about the fact to combine in the same publication "static data" and "dynamic data". We consider it had better separate these two kinds of data and then create two publications as for "measured data".
Most of VMS are static and this publication could take advantage of a more limited message size like in case of periodic publication. However in case of mobile VMS, it should be possible to add a location to the information as for any piece of data.
Of course a better alignment with was is already described in SituationPublication is necessary.
One can also imagine to add this type of information in Traffic Views.
I agree that there is a need of a new VMS Publication that allows publishing simple VMS messages. However I think that is also important to merge this need with the current Sign Setting Record on Situation Publication.
On the current Situation Publication, the existent of a Sign setting class allows us to publish VMS Messages related to other situation records. I think it is important to merge the two needs, i.e., change the sign setting situation record to point to the new data model proposed, and be able to publish VMS Message both with Situation Publication and publish VMS publication.