Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
An integrated application suite forTraffic Control Centers<br />time Q32009<br />durationtwomonths<br />
About VCV<br />VerkeerscentrumVlaanderenmonitors Flemish (highway)  traffic to ensure traffic safety and traffic informati...
Design challenge<br />The rapid expansion of VerkeerscentrumVlaanderenrequires a thorough revision of its processes and ap...
Approach<br />define<br />understand<br />explore<br /><ul><li>Field study
Link analysis
Design requirements & constraints
Scenarios of use
Conceptual design
Prototyping
Style guide</li></li></ul><li>understand<br />
understand               explore                define<br />Field Study (1)<br />Several observations on site allowed us t...
understand               explore                define<br />Field Study (2)<br />A one-day observation in a Dutch TCC prov...
understand               explore                define<br />Link analysis (1)<br />To identify all actors and lines of com...
understand               explore                define<br />Reporting<br />The field study findings were consolidated in a...
understand               explore                define<br />Design requirements <br />Results from the field study were re...
 Should have
 Could have
 Would have</li></li></ul><li>understand               explore                define<br />Design constraints<br />The boun...
 Working methods
 Representation of the traffic situation
Upcoming SlideShare
Loading in …5
×

An integrated application suite for Traffic Control Centers

1,342 views

Published on

  • Be the first to comment

An integrated application suite for Traffic Control Centers

  1. 1. An integrated application suite forTraffic Control Centers<br />time Q32009<br />durationtwomonths<br />
  2. 2. About VCV<br />VerkeerscentrumVlaanderenmonitors Flemish (highway) traffic to ensure traffic safety and traffic information reliability for an increasing number of vehicles on the road. Operators in the Traffic Control Centre monitor and guide traffic in real time by controlling traffic messages and signalization on the roads. <br />business b2b<br />
  3. 3. Design challenge<br />The rapid expansion of VerkeerscentrumVlaanderenrequires a thorough revision of its processes and applications. <br />Namahn was asked to redesign the basic traffic monitoring functionality and to provide a basis for future integration of traffic monitoring tools. <br />discipline interaction design<br />
  4. 4. Approach<br />define<br />understand<br />explore<br /><ul><li>Field study
  5. 5. Link analysis
  6. 6. Design requirements & constraints
  7. 7. Scenarios of use
  8. 8. Conceptual design
  9. 9. Prototyping
  10. 10. Style guide</li></li></ul><li>understand<br />
  11. 11. understand explore define<br />Field Study (1)<br />Several observations on site allowed us to gain insights in the operators’ working processes, their needs and habits within the current application context.<br /> “I regularly check whether traffic information appears correctly on our website.”<br />While discussing ongoing traffic events, operators actively used the live footage. Sometimes they even walk over to the video wall and point out a specific event on one of the monitors.<br /> “I prefer controlling traffic events manually to ensure that the information we send out is accurate.”<br />During the night shift, the operator on duty moves from desk to desk to manage the complete Flemish region.<br />
  12. 12. understand explore define<br />Field Study (2)<br />A one-day observation in a Dutch TCC provided a good basis for comparing work processes, best practises and insights from a broader perspective.<br />Traffic jams are monitored and managed automatically, based on counters. The operators rarely need to intervene in this automated monitoring system.<br />Operators focus mainly on defining and managing traffic diversions (whereas for the Flemish operators, this is of secondary importance).<br />Operators are “always” on the phone coordinating the road inspectors. Sometimes, they even compete with the traffic police to be the first on the incident scene.<br />
  13. 13. understand explore define<br />Link analysis (1)<br />To identify all actors and lines of communication within the control center, we performed a link analysis.<br />This analysis provided information for exploring the possible physical setup of the control room and focus points for task- and process flows.<br />
  14. 14. understand explore define<br />Reporting<br />The field study findings were consolidated in a written document.<br />Learnings were grouped thematically, and illustrated using pictures and diagrams.<br />
  15. 15. understand explore define<br />Design requirements <br />Results from the field study were reformulated into prioritised design requirements, so the scope and focus of the design became clearer.<br />For prioritising the requirements, we applied the MOSCOW-matrix:<br /><ul><li> Must have
  16. 16. Should have
  17. 17. Could have
  18. 18. Would have</li></li></ul><li>understand explore define<br />Design constraints<br />The boundary conditions were captured in design constraints. These focused on technological, organisational and process-oriented constraints.<br />Both the constraints and requirements defined the design space for exploration.<br />Constraints focused also on: <br /><ul><li> The control room
  19. 19. Working methods
  20. 20. Representation of the traffic situation
  21. 21. Technology</li></li></ul><li>explore<br />
  22. 22. understand explore define<br />Scenarios of use<br />We described future interaction flows in a series of scenarios, focussing on the daily routine at the traffic center, including critical flows for the operator. <br />We wrote three scenarios:<br /><ul><li> A day in the control centre
  23. 23. Dealing with a new traffic event
  24. 24. A crisis situation</li></ul>In each scenario, we focused on the various aspects that come into play: the organisation of the room, the work place, the software interactions and the human interactions.<br />
  25. 25. understand explore define<br />Conceptual design<br />We explored design alternatives by means of low-fidelity sketches and verified the main design principles by illustrating the descriptions of the scenarios in the wireframes.<br />Due to the multiple monitor set-up, we did not solely focus on the screen design of the individual work monitors. The concept also defined organisation of, relations between and interactions with video monitors.<br />
  26. 26. understand explore define<br />Detailed design (1)<br />Based on the stakeholder’s feedback we refined the conceptual design introducing custom controls and added realistic details. <br />Each task flow was illustrated by a sequence of static screen samples.<br />
  27. 27. understand explore define<br />Detailed design (1)<br />Based on the stakeholder’s feedback we refined the conceptual design introducing customized controls and added realistic details. <br />Each task flow was illustrated by a sequence of static screen samples.<br />
  28. 28. understand explore define<br />Detailed design (1)<br />Based on the stakeholder’s feedback we refined the conceptual design introducing customized controls and added realistic details. <br />Each task flow was illustrated by a sequence of static screen samples.<br />
  29. 29. understand explore define<br />Link analysis (2)<br />Based on the link analysis, we explored how the future control room could be organised so as to optimally support the new workflow, processes and roles within the control center.<br />
  30. 30. understand explore define<br />Detailed design (2)<br />During the design workshop, the designs were verified and refined for the specific tasks at hand. <br />We focused on collaboration, exchanging and sharing information and situation awareness of the operator team.<br />
  31. 31. define<br />
  32. 32. understandexploredefine<br />Style guide<br />The design patterns were defined in the style guide.<br />This document helps the developers to build the application correctly and to add future functionalities in a consistent way. <br />
  33. 33. Outcome <br />During the design process, we focused on consistency in design and efficiency in use. As a result, the legacy applications that will be integrated share interaction patterns and information design, increasing the learnability and familiarity.<br />The explorations for control room organisation proved valuable for defining the view on future possibilities. The design verification confirmed the extensibility of the design and its potential to support an increasing flexibility in work flow procedures when monitoring road traffic.<br />
  34. 34. Grensstraat 21 rue de la Limite<br />B-1210 Brussels<br />info@namahn.com | +32 2 209 08 85<br />

×