TG CARS-Vox Winter Driving Concept of Operations, Detailed ...mndot.org/its/projects/2011-2015/511enhancements/carsvox.pdf · 1 du 10/20/2014 First draft of TG CARS-Vox Winter Driving,

TG CARS-Vox Winter Driving

Concept of Operations, Detailed System Requirements

and GUI Design

Prepared by:

Castle Rock Associates

Prepared for:

Minnesota Department of Transportation

Last updated:

June 18, 2015

Final TG CARS-Vox_SystemDesign_06m_du.doc

Confidential. Limited Circulation Document. Listed Agencies Only

2

Document Version History

Version Author Date Change Notes

1 du 10/20/2014 First draft of TG CARS-Vox Winter Driving, based on

first-gen CARS-Vox SDD

2 kv 10/20/2014 Update to draft

3 du 11/07/2014 Updated for MnDOT feedback

4 kv 12/1/2014 Reviewing MnDOT changes and preparing for

resubmission

5 du 12/2/2014 Updating per MnDOT comments. Updating per KV

comments.

6 du 6.16.15 Updated “Build” column

6m du 6/18/15 Preparing for MnDOT final submission



3

Table of Contents

1. CONCEPT OF OPERATIONS .............................................................................................................................. 4

2. SYSTEM REQUIREMENTS SPECIFICATION................................................................................................. 8

2.1 OVERVIEW ................................................................................................................................................................ 8 2.1.1 Sign Up Process .......................................................................................................................................... 8 2.1.2 Reporting Process ....................................................................................................................................... 8 2.1.3 Splitting Reports .......................................................................................................................................... 9 2.1.4 Training and Accreditation ......................................................................................................................... 9 2.1.5 Event Blog ................................................................................................................................................... 9 2.1.6 TG Vox Events ........................................................................................................................................... 10 2.1.7 Public Feedback on Existing Events (Future) ........................................................................................... 11

3. DETAILED DESIGN ............................................................................................................................................ 12

3.1 OVERVIEW .............................................................................................................................................................. 12 3.2 511 SIGN-UP .......................................................................................................................................................... 13

3.2.1 My account ................................................................................................................................................ 14 3.2.2 Account activation ..................................................................................................................................... 15 3.2.3 Screen name .............................................................................................................................................. 16 3.2.4 Submit an update ....................................................................................................................................... 17 3.2.5 Become an accredited reporter ................................................................................................................. 17 3.2.6 Training updates ....................................................................................................................................... 18

3.3 CREATING A WINTER UPDATE ............................................................................................................................... 19 3.3.1 Split up my drive ....................................................................................................................................... 21 3.3.2 Confirming a Report Submission .............................................................................................................. 22

3.4 DRIVER UPDATES IN TG WEB ................................................................................................................................ 23 3.4.1 Flagging a Blog Entry ............................................................................................................................... 25

3.5 DRIVER UPDATES IN LB-WEB................................................................................................................................ 26 3.6 PUBLIC FEEDBACK ON EXISTING EVENTS ............................................................................................................. 28

3.6.1 Submitting feedback .................................................................................................................................. 28

APPENDIX A: MY REPORTS HELP .................................................................................................................... 33



4

1. Concept of Operations

Public agencies—including the Minnesota Department of Transportation, the Idaho Transportation Department, and the Iowa Department of Transportation, among others—use CARS (Condition Acquisition and Reporting System) as their primary reporting tool for transportation-related event and condition reports that are displayed on 511. Examples of CARS event reports include road condition information, winter driving conditions, traffic and travel-related incidents, special events, evacuations, homeland security alerts, and natural disasters. The CARS software maintains a current event and highway conditions database, and allows the exchange of event information with the public via 511 phone systems, the Web, iPhone/Android apps, and email/pager/text message notifications. [1] The standard CARS operator interface allows authorized Mn/DOT and partner agency operators to enter roadway events as any single roadway point or any stretch of state highway. Many CARS agencies also need to enter winter driving condition reports for pre-defined roadway segments—typically fixed in relation to groups of snow plow routes used by maintenance operators, or stretches of roadway that are posted with chain restrictions or seasonal weight restrictions. Agency operators enter winter condition reports for predefined segments using a streamlined data entry module called CARS-Segment. [2] CARS-Vox is a module that builds upon that architecture to allows members of the public to sign up to report winter driving conditions for display on the 511 system, alongside DOT reports. CARS-Vox adds “crowd-sourced” updates into 511. CARS-Vox’s initial focus is to facilitate public input to Minnesota’s, Idaho’s, and Iowa’s winter condition reporting program. [3] In Phase 1, CARS-Vox will enable members of the public to submit winter driving condition “updates” for DOT operator review and approval. Crowd-sourced updates are not intended to change, replace or delete any official agency reports, but can help supplement or update information that the state has provided. Accredited reporters will get to post their updates direct to the state’s 511 web sites—initially, on the Full Feature and Streamlined 511 web sites, and in CARS 4/5. “Blogging” updates to public events will also be supported. [4]

The CARS-Vox design developed herein builds upon three of states’ already-operational 511 modules—specifically, Third-Gen CARS-Web (TG-Web), Third-Gen CARS-Routes (TG-Routes), and CARS-Web LB (LB-Web). Building CARS-Vox into these existing modules will enable the states to situate their crowd-sourced reporting capability within their existing 511 systems. The states may advertise and promote Vox functions to existing 511 end users, paving the way for the future expansion of crowd-sourced data. [5] Sign Up and Reporting Features Third-Gen CARS-Web includes add-on modules called Third-Gen CARS-Routes and Third-Gen CARS Alert D, which allow public users to create a personalized 511 accounts. TG Routes subscribers are asked to enter their first name, last name, email address, and—for mobile phone alerts—their cell phone number. The initial purpose of the subscriber sign-up function was to allow drivers to save their routes, in order to quickly review current traffic events along them. The second sign-up module, TG Alert D, allows users to receive emails and texts about their saved routes. A



5

third, “Smart 511” plug-in module will also allow drivers to hear targeted phone reports along their saved routes. The same 511 sign-up process also serves TG Vox, as the drivers’ saved routes form the basis of TG Vox winter driving update submissions. [6] Any subscriber will be able to submit a TG Vox winter driving update after signing up and signing in. Any 511 web site user can submit updates to CARS 4/5 operators after creating a screen name to identify their submissions. If they also subscribe to 511 and check a box to indicate interest in posting updates directly to 511 web pages, an email will be sent to an agency trainer with the prospective reporter’s contact information. Before posting updates directly to 511 web sites, contributors will demonstrate their capabilities by being required to submit actual winter driving updates. Like all TG Vox updates sent in by unaccredited contributors, these “training updates” will appear in CARS 4/5 but not on public web sites—unless cleared by a CARS operator.1 A follow-up email will be sent to the agency trainer each time a prospective reporter’s training update expires from CARS 4, detailing the update itself plus CARS-Segment reports that overlapped the training submission in time and space. This will allow the agency trainer to assess the quality of the submissions, and to give emailed feedback to each trainee as necessary. [7] TG Vox Phase 1 will also include winter driving report training/advice pages that contributors can reference at any time—that is, during their initial training and thereafter. The training/advice pages will be reached from the TG Vox winter driving update data entry page, allowing contributors to check their information against the “recommended standard” before they send in each submission. In this way, it is proposed that a continuing quality control process will be initiated and maintained. Later, if crash reporting and public ‘blogging” on existing CARS events are instigated, similar advice screens will be linked off of those data entry pages, too, again with a training period of trial update submissions before a contributor is accredited to post updates to 511 without prior CARS operator review. [8] Two additional fields will be added to the 511 sign-up subscriber database: one indicating the subscriber’s status for posting TG Vox updates, and the other storing their screen name. A simple database management tool will allow CARS-Vox agencies to manually elevate each fully accredited CARS-Vox subscriber to direct 511-posting status, or to remove that privilege. [9] Optionally, Castle Rock will create web pages that 511 sign-up subscribers can use as a reference guide when creating winter driving updates. These simple web pages will include instructions on how to create updates, as well as pictorial illustrations of various winter driving conditions. Eventually, the site could include actual images of real roadways—perhaps taken from agency cameras—depicting different winter driving conditions to clarify what qualifies as good, fair, or difficult, etc. Making this information easily available to TG Vox participants within the data entry pages may help contributors to make their public winter driving updates more consistent and standardized. [10] All 511 Sign-Up subscribers will be able to post winter driving condition updates to CARS 4 for any route saved in their account. Accredited reporters will also see their updates displayed automatically on 511 web sites. To create an update, the contributor will click the menu button next to the route in his or her “Favorites” list and select “Post an update” to gain access to a simple interface for

1 All CARS events can be public domain or internal to the CARS system. A control in CARS 4 allows operators to move any event from one status to the other, or back.



6

entering their driving condition update. To facilitate reporting on days when conditions vary substantially, TG Vox will allow contributors to split saved routes into two or three segments. The default will however be to request that the contributor enter a single update for all the highways on his or her entire route. [11] For presentation to the public, TG Vox driver updates will be divided into at least one separate event report for each state highway on the route. That is, separate CARS-Event reports will be generated for each unique route designator. When a contributor subdivides his or her data entry, on days when conditions vary, the system will create a separate CARS-Event report for each designated route on each geographic section of the contributor’s submission. If any part of the contributor’s route includes only a very small portion of a particular state highway (e.g., <= half a mile), no report shall be created for that short extent of highway. [12] For each update, the contributor will initially be able to pick a winter driving descriptor. When conditions are adverse, further details of road and weather conditions may also be selected. Finally, contributors may complement their report with a short “blog” entry about when they drove the route and what was especially notable. CARS-Segment phrases that typically apply to a single point rather than a stretch of roadway (e.g., animals on roadway, avalanche, etc.) will be excluded. All updates submitted by TG Vox contributors will have a pre-determined extent time that cannot be changed by the contributor (e.g., 4 hours) and an event duration of “until further notice”. After the extent time has ended, the update will be automatically removed from public view. [13] As the primary domain of 511 is state roads, TG Vox contributors may submit winter driving condition updates only on state roads. In the future, TG Vox could potentially be expanded to allow end users to report conditions on non-state roads. Given the current absence of such reporting in most places, this might one day provide a major benefit for the 511 community, particularly in the more rural parts. [14] Displaying TG Vox Updates TG Vox updates on state roads will be displayed in CARS 4/5 and on TG Web and LB-Web maps as small, clickable icons—e.g., colored squares. They will be displayed on top of the statewide CARS-Segment reports generated by the CARS agency, which are displayed as painted roads. The TG Vox update icons will be color-coded according to the same color scheme used to display CARS-Segment “painted roads” for state roads today. This will help CARS operators and members of the public easily to see any differences between the state’s reports and volunteers’ updates. [15] For example, a “messy” update submitted by a TG Vox contributor in Idaho will appear as a dark purple clickable square on the map. When the 511 web site visitor mouses-over or clicks on a reporter’s update icon, the TG- and LB-Web sites will behave as for any other event. When the 511 web site user clicks the icon, the full details of the update will be displayed, including the time stamp indicating when the update was entered by the reporter. If there will be multiple, overlapping, and concurrent updates for the same stretch of road, TG Vox Phase 1 will keep all of the current updates visible, each as a separate, clickable square. [16] Attribution and Quality Control



7

In planning for the CARS-Vox project, Castle Rock explored different ways of achieving quality control, including both manual and automated methods. This design proposes that all 511 web site users be allowed to “blog about” (i.e., comment on) reporters’ updates. CARS agencies will be able to use the blog comments to help check out the validity of specific submissions, as well as each reporter’s overall performance. All “blog” contributions from members of the public will be filtered before posting using an on-line service such as WebPurify.2 511 web site users will also be able to flag inappropriate content. [17] For accredited reporters, TG Vox reports will flow directly to the applicable 511 web site without any agency vetting of individual updates. TG Vox driver updates will be attributed to “pen-named” individuals, using event attribution similar to that of today’s TG Web site. TG Vox contributors will be required to create a screen name when setting up their account. To participate in the program, they must agree to allow their screen name to appear on the 511 system alongside all updates they submit. This will be spelled out in the terms and conditions which contributors must accept before being allowed to post updates. [18] This initial deployment also includes the display of TG Vox winter driving updates on CARS-Web LB. At this time, TG Vox updates will not appear on the 511 phone system, in Alert D / Alert B, the App, or on any other CARS modules. In LB-Web, winter driving updates submitted by TG Vox reporters will be read-only. At this time, CARS-Web LB shall not include a mechanism for signing up to be a TG Vox contributor, nor a means of submitting TG Vox updates. [19]

2 http://www.webpurify.com/

http://www.webpurify.com/



8

2. System Requirements Specification

TG Vox shall be tested against the following system requirements. In accordance with Federal Highway Administration policies, TG Vox shall be required to satisfy 100% of critical requirements and at least 80% of other requirements. In the table below, critical requirements are marked with a star (“*”).

Below, Phase 1 cover initial developments funded by Idaho, Iowa, and Minnesota.

2.1 Overview

# Requirement Phase Build

1. In Phase 1, TG Vox shall allow volunteer members of the public to post winter driving updates to the public and to CARS agency staff.*

1 1.34.0

2. TG Vox shall be a plug-in module to Third-Gen CARS-Web. 1 1.34.0

3. TG Vox updates shall be mapped to standard CARS event reports. 1 1.34.0

4. Contributors whose updates are to be shown automatically on 511 web sites shall first be accredited by the CARS agency.*

1 1.34.0

5. Updates from other contributors shall be internal to CARS 4/5 only, but can be elevated to public domain after CARS operator review.

1 1.34.0

6. Winter update contributors shall pick from predefined conditions lists, and can also add a short text “blog” entry about observed conditions.

1 1.34.0

7. All blog posts shall be automatically vetted by a web service such as WebPurify. Posts that fail any checks shall be blocked automatically.

1 1.34.0

8. In Phase 1, only accredited reporters’ blog contributions that pass all web filtering tests shall be posted to 511 web pages.

1 1.34.0

9. In Phase 1, 511 web site visitors shall be able to comment on accredited reporters’ event reports through sequential “event-blog” posts.

1 1.34.0

10. In Phase 1, these web-site visitors’ event-blog posts shall be made available only to CARS operators.

1 1.34.0

11. TG Vox reporters shall never be able to edit any state event attributes or delete any state-entered CARS event.

1 1.34.0

2.1.1 Sign Up Process

12. Before submitting any updates, users shall sign up for and sign into their personal 511 account.

1 1.34.0

13. Each user shall have to verify his or her 511 account’s email address before they can submit updates or blog posts directly to 511.

1 1.34.0

14. Each TG Vox contributor shall be identified by a 511 screen name in all their updates and blog posts.

1 1.34.0

15. Contributors shall be allowed to select their own 511 screen name. 1 1.34.0

16. 511 screen names shall be subject to change by the CARS agency. 1 1.34.0

2.1.2 Reporting Process

17. In Idaho, contributors shall be allowed to submit winter driving updates year-round, for use in mountain pass condition reporting.

1 1.34.0



9

18. To begin submitting winter driving updates for any roadway sections, contributors shall save the roadways as personalized route(s).

1 1.34.0

19. TG Vox shall use standard condition reporting categories based on—and simplified from—those of CARS-Segment.

1 1.34.0

20. TG Vox deployments are expected to use different categories based on agency specific CARS-Segment deployments.

1 1.34.0

21. TG Vox shall aim to make user input simplest and quickest when conditions are good, with more detail requested as conditions worsen.

1 1.34.0

2.1.3 Splitting Reports

22. As a default, contributors shall be able to submit a single condition report for their entire route.

1 1.34.0

23. Contributors shall also be able to split their route into two or three parts and submit separate condition reports for each part.

1 1.34.0

24. Each contributor shall be able to choose where to split their saved route, each time they split it.

1 1.34.0

25. If a contributor has previously split a route, they shall first be offered their previous split, next time the need to split that route.

1 1.34.0

2.1.4 Training and Accreditation

26. Before contributors can post updates direct to 511, they shall first be accredited by the CARS agency.

1 1.34.0

27. The accreditation process shall include three training updates for CARS agency review.

1 1.34.0

28. These training update submissions shall map to events internal to CARS 4/5—appearing automatically in CARS 4/5, but not on public 511 web sites.

1 1.34.0

29. CARS agency trainer(s) shall be able to compare training update submissions with state winter driving reports for the corresponding highway segments.

1 1.34.0

30. The design shall assume that CARS agencies may give contributors feedback on their training updates before determining their accreditation status.

1 1.34.0

31. The design shall assume that accreditation decisions may be based in part on CARS agency review of applicants’ training update submissions.

1 1.34.0

32. TG Vox shall send a training support email to CARS agency trainer(s) each time an applicants’ training update expires in CARS 4.

1 1.34.0

33. Each training support email shall include the trainee’s update submission, as well as state segment reports that overlapped it in time and space.

1 1.34.0

34. Each training support email shall include the applicant’s first and last names and their screen name as part of its email heading.

1 1.34.0

2.1.5 Event Blog

35. Winter driving contributors shall be able to add a short comment or “blog entry” to their winter condition update.

1 1.34.0



10

36. 511 web site users who are signed in to their accounts shall also be able to blog about the TG Vox event reports created by reporters’ winter condition updates.

1 1.34.0

37. Successive blog entries shall form a sequential “updates blog” for each TG Vox event report.

1 1.34.0

38. Individual blog entries shall not exceed 160 characters. 1 1.34.0

39. Blog entries shall be attributed to the screen name of the blogger. 1 1.34.0

40. Accredited reporters’ blog updates shall be shown as public comments on 511 web sites and in CARS 4/5.

1 1.34.0

41. Other contributors’ blog entries shall appear in CARS 4 only, for use by CARS agency staff.

1 1.34.0

42. In Phase 1, CARS 4/5 operators shall be able add their own blog responses to public contributors’ blogs, by editing the CARS 4/5 comments.

1 1.34.0

43. All TG Vox blog entries shall be automatically checked for the presence of specific words that will automatically flag the entry.

1 1.34.0

44. Blog entries that are flagged shall not be added to any CARS-Event report (whether in CARS 4/5 or on 511 web sites).

1 1.34.0

45. TG Web users shall have the ability to manually flag blog entries as inappropriate.

2 (new) 1.34.0

46. A notification email shall be sent to the CARS agency program manager with details about the flagged blog entry, including a link to the event in TG Web.

2 (new) 1.34.0

47. CARS operators shall be able to delete any blog entry from CARS 4/5. 2 (new) 1.34.0

2.1.6 TG Vox Events

48. Each TG Vox update shall be mapped to a separate CARS event for each state highway extent of 0.5 miles or more traversed by the route.

1 1.34.0

49. TG Web and CARS 4/5 shall display TG Vox updates as “icon events” with extents.

1 1.34.0

50. TG Vox shall not change the existing CARS-Event database in any way. 1 1.34.0

51. Whenever a reporter saves a TG Vox update for any saved route, any existing TG Vox event reports for that user’s route shall be deleted.

1 1.34.0

52. TG Vox events shall not appear on CARS-Web 3G, or on NG-511, or in Alert B or D.

1 1.34.0

53. Although users’ routes in CARS-Routes are one-way, TG Vox events shall be non-directional in CARS-Event.

1 1.34.0

54. In Phase 1, no TG Vox events shall be created on local roads or state highway sections of less than one half-mile.

1 1.34.0

55. All TG Vox event reports shall be fully editable in CARS 4/5. 1 1.34.0

56. The TG Vox events of accredited reporters shall have an accessibility status of public domain.

1 1.34.0

57. The TG Vox events of other contributors shall have an accessibility status of “internal” in CARS 4/5.

1 1.34.0

58. The accessibility status of any TG Vox event (public domain or internal) can be changed by CARS 4/5 operators.

1 1.34.0

59. All TG Vox events shall have a duration of “until further notice.” 1 1.34.0



11

60. Updates submitted by TG Vox contributors shall have an extent expiry time set to a fixed time after their initial creation (default 4 hours).

1 1.34.0

61. After the fixed period has passed, the update submitted by the TG Vox contributor shall be automatically deleted from CARS-Event.

1 1.34.0

62. Blogging about an event report shall not change its expiry time. 1 1.34.0

63. CARS 4/5 operators can edit the duration and expiry time of any event, including TG Vox events.

1 1.34.0

64. CARS 4/5 operators shall be able to delete any TG Vox event report, whether or not it is public.

1 1.34.0

2.1.7 Public Feedback on Existing Events

65. TG Vox shall allow public users to submit structured feedback on existing events that are visible in TG Web and CARS App, except events that are due to start in the future.

2 (new) 1.34.0

66. Only App end users who have confirmed that they are not drivers will be able to submit feedback on events via the App.

2 (new) N/A

67. End users who have not confirmed that they are not driving shall only be able to see aggregated end user content.

2 (new) N/A

68. Structured feedback on existing events shall initially be focused on event verification or confirmation (i.e., does this event really exist?)

2 (new) 1.34.0

69. Structured feedback on existing events shall immediately be made available on the 511 system for other end users to see.

2 (new) 1.34.0

70. End users shall be able to submit only one piece of feedback per event. 2 (new) 1.34.0



12

3. Detailed Design

In accordance with FHWA’s Systems Engineering Process, this GUI design section is illustrative, rather than definitive. The concepts described below may not all be supported in the final system. The final system may satisfy the detailed system requirements (Section 2 of this document) in other ways. Module testing and acceptance are based on meeting the detailed system requirements, rather than deploying the particular concepts and initial ideas of this section.

3.1 Overview

Figure 1 illustrates the architecture of the information flow from TG Vox to TG- and LB-Web—and potentially to other 511 dissemination modules, too. TG Vox user reports shall be Full Event Update (FEU) events, like those created in CARS 4/5, CARS-Imports or CARS-Segment. They shall be able to include all the event fields carried in other CARS events, including those defined in FEU and those used only in CARS. Only a subset of the current event data fields is expected to be used in this initial TG Vox deployment.

Figure 1: CARS-Vox Architecture (TG-Web—Phase 1)



13

3.2 511 Sign-Up

TG Web sites including the TG Routes plug-in module sign-in functions are illustrated below. The TG Routes module allows TG Web site users to enter and save their own personalized routes so they can easily view current traffic events along them. The Routes module also forms the basis of TG Alert D messaging, and Smart 511 (where deployed), which personalize information directed toward individual subscribers. TG Vox will build upon the current 511 sign-up/sign-in process so that it can meet the needs of all these software modules.

Figure 2: 511 Sign-Up / Sign In

The single hyperlink Your 511 (sign in) shall link to a modal dialogue box that can handle both new and returning users. The dialogue box to which it links shall promote saving routes, getting alerts, and

Your 511 (sign in)



14

the new Vox crowd-sourcing options. Returning users who have opted to stay signed-in on their computers shall see: <First name>’s 511 and (sign out). Clicking (sign out) shall immediately log the user out, displaying the view that would have been by new users instead (e.g., the initial view seen by users who are not logged in automatically).

Figure 3: 511 Sign-up / Sign-in Modal Dialogue

Mousing over Save your routes on the dialogue-box shown above shall cause tooltip text to be displayed that says: Save the routes you often drive, so you’ll see them when you next return to 511. Mousing over Get alerts shall similarly indicate: You can schedule email or text message alerts when new reports come up for your saved routes. Mousing over Hear your routes first shall be explained by: Go straight to your routes when you call 511. (This option is available only where the Smart 511 module is deployed.) The next two items relate specifically to CARS-Vox functionality and will appear where CARS-Vox is deployed. Mousing over Send us driving reports shall bring up tool tip text that says: You can choose to send us winter condition reports for any route you’ve saved. Mousing over Post your reports on 511 shall bring up tooltip text that says: Help other drivers! Post your own winter condition updates on 511.

3.2.1 My account

When a user clicks on the “Get Started” button of the two-column box above, they shall arrive at the My Account sign-up modal dialogue box below.



15

Figure 4: Account Sign-Up Box

3.2.2 Account activation

When a subscriber clicks Create my account, the subscriber shall be prompted with a box advising that they have been sent an email, and that they need to activate their account by clicking Accept link in the email. As at present, subscribers will have up to 24 hours to click Accept, after which their account is automatically deleted from 511.

Figure 5: 511 Sign-up: Account Activation Email Notification



16

3.2.3 Screen name

With TG Vox, the only additional sign-up need is for the 511 subscriber to pick a Screen Name, which TG Vox will request and explain at the moment when he or she first submits an update or blog contribution. Subscribers will also be able to pick a screen name if they edit their account details (below). TG Vox contributors can add, review, or change their Screen Name for sending in or (after having been accredited by the state) posting updates and blog comments to 511, which they may have initially chosen when posting their first TG Vox update or blog entry. In states that have not deployed TG Vox, the Screen Name lines shall be omitted.

Figure 6: Subscriber’s Account—Changing My Info (No Screen Name Selected)



17

3.2.4 Submit an update

All 511 subscribers with saved routes shall be able to submit winter updates by clicking “Send us an update” in <User>’s Favorites. For the unaccredited and trainee contributors, only CARS agency staff will be able to see the updates, using the CARS 4/5 GUI. Updates and blog entries from non-accredited 511 users will be mapped to CARS events that are Internal only—not Public Domain. All public comments are of potential benefit to 511 operators, as well as providing a means for the public to give constructive feedback on 511 reports. Any user’s update can be easily made public by a CARS 4/5 operator, using the existing CARS 4/5 control to switch events from being “internal” to being in the public domain. The first time a subscriber submits an update, they shall be required to enter a screen name, with a modal dialogue box that explains how the screen name will be used to publicly identify their posts.

Figure 7: CARS-Vox: Create a Screen Name

3.2.5 Become an accredited reporter

511 subscribers can express initial interest in signing up for TG Vox by checking a box on the 511 sign-up pages. Subscribers who do not check this box will not be contacted as potential accredited reporters, though they may choose to send in occasional or regular contributions into the system. Specific contributors’ TG Vox reports shall only be posted automatically to 511 web sites after that reporter has been accredited by the state. It is up to each state agency to decide policy on this. In some states (e.g., Idaho) initial “training” submissions are required of prospective reporters as a means of checking on the quality of their reports, as well as on each contributor’s continued enthusiasm for making regular submissions. CARS agencies may require that the contributor has shown a certain level of performance in his or her reporting, in terms of the user’s number of reports submitted, their frequency and their consistency with other data sources. Training reports also provide for CARS agencies to be able to offer feedback on actual reports (i.e., “on the job” training), before contributors become accredited to post updates directly to 511. An initial email shall be sent to the CARS agency trainer when a user expresses interest in becoming accredited as a regular reporter via the sign-up page. Each of the prospective reporter’s training



18

submissions are also emailed to the CARS agency trainer, as described in the next section.

Figure 8: TG Vox: Reporter Accreditation Request Page

3.2.6 Training updates

511 subscribers who do check the box will initially create updates that are Internal Only—not Public Domain. This design provides for an initial expression of interest to be followed by an explanatory email, after which the user (in Idaho) will be required to submit at least three training updates before being considered for accreditation. TG Vox will automatically count how many updates each prospective reporter has submitted, as well as emailing details of each report they submit to the CARS agency trainer. Each current event on their route (including current CARS-Segment reports) shall also be noted in the emails to the CARS agency. An example of the email that the system sends in these circumstances is given below:



19

From: <[email protected]>

Date: Wed, Oct 2, 2013 at 6:39 PM

Subject: CARS-Vox Training Update for Boreas

To: [email protected]

Boreas has submitted a training update for review:

Training update #2

I-84: Snow patches.

between The Oregon State Line (near Fruitland) and Exit 141: I-84B; US 26 (1 mile west of

the Bliss area). A driver reported snow patches on the roadway.

Posted by Boreas at 3:30 PM MDT

Boreas: Test 3:30 PM

I-84: Ice.

between Exit 137 (1 mile west of the Bliss area) and The Utah State Line (64 miles east of

the Heyburn area). A driver reported ice on the roadway. It was snowing.

Posted by Boreas at 3:30 PM MDT

Boreas: Test 3:30 PM

Other current events on this route:

I-84 in both directions: Icy patches.

between The Oregon State Line (near Fruitland) and Exit 121 (near Glenns Ferry). Look out

for icy patches. Be prepared for heavy rain.

I-84 in both directions: Left lane closed.

between Exit 64: Black's Creek Road and The Boise Port of Entry (4 miles east of the Boise

area). The left lane is closed.

I-84 in both directions: Icy patches.

between Exit 121 (near Glenns Ferry) and The Utah State Line (65 miles east of the

Heyburn area). Look out for icy patches. Be prepared for snow.

I-84: Accident.

between Exit 188: Valley Road and Exit 194: ID 25; Ridgeway Road (2 miles east of the

Hazelton area). Look out for an accident.

The concept is that users who wish to be considered for accredited reporter status will be evaluated once they confirm their capabilities and their continued enthusiasm by filing a configurable number of training reports (initially, at least three).

3.3 Creating a Winter Update

Where TG Vox is deployed, a new link will appear in the menu options for each saved route that is in a user’s Favorites list in the Your 511 account screens. For accredited reports, this link will read “Post an update.” For unaccredited reporters, this link will read “Send an update”.

mailto:[email protected]



20

Figure 9: Saved Routes List

When an accredited reporter clicks “Post an update” in <User>’s Favorites, or an unaccredited subscriber or trainee reporter clicks “Send us an update”, the following screen shall appear. The specific phrases / colors to appear may vary per state deployment.

Figure 10: Post an Update (select Clear, Patchy or Completely Covered)

On the left panel, the subscriber is required to pick Clear, Patchy or Completely Covered (driving



21

condition options are configurable per agency deployment). If Clear is picked, the update is complete—unless the subscriber wants to add a “Tell us more” blog entry. No further details (e.g., wet or dry; sky conditions) are required in this simplest use-case. However, if the subscriber picks Patchy or Completely Covered, further details shall be requested. If the user picks Patchy, they shall be required to indicate whether the patches are mainly snow, ice, or slush. If the weather is bad (rain and/or snow), an optional weather report can also be given. If the user picks Completely Covered, he or she shall be required to say if the road is snowy, icy or slushy. If the weather is bad (rain and/or snow), an optional weather report can also be given.

Figure 11: Driving Conditions are Patchy (select Road is … Weather is)

3.3.1 Split up my drive

The default is that a single report is submitted for the whole route. If the subscriber considers it necessary to split up his or her drive today, he or she will click on the Split up my drive hyperlink. A black and white circle shall appear in the place last used to subdivide the user’s route. It can be dragged along the route to a new position if desired.



22

Figure 12: Split Up My Drive – 1 Patchy, 1 Clear

If it is the first time that the route has been split, the default is to place the circle at the nearest highway designator change to the half-way point of the route. However, if there is only one state highway on the route, or the nearest designator change to the route’s mid-point would cause one part to be more than three times the length of the other, the default is to locate the circle half way along the route. The subscriber can now enter data and make blog comments for each part of the route. When a conditions color has been picked, the pink markers are replaced by numbered squares of the selected color. Further details can now be entered for each part of the route, or a third part added.

If the reporter decides to add a third part to the update, Part 2 is subdivided using the same rules as above (applied to Part 2 alone, rather than to the whole route). In more detail, if it is the first time that Part 2 has been split, the default is to place the circle at the nearest highway designator change to the half-way point of Part 2. However, if there is only one state highway on Part 2, or the nearest designator change to Part 2’s mid-point would cause one sub-part to be more than three times the length of the other, the default is to locate the circle half way along Part 2. Both black and white circles can be dragged and data entered or changed until the subscriber presses Done or Cancel.

3.3.2 Confirming a Report Submission (New)

Each time a subscriber submits a new report, TG Vox will confirm that the submission was received. Accredited reporters will receive a simple “Thank you!” confirmation dialog that briefly



23

displays on the screen and then disappears on its own.

Figure 13: Confirming an Accredited User’s Report Submission

For unaccredited subscribers, the report submission confirmation will include a link to send an email to the CARS agency trainer and express interest in becoming accredited as a regular reporter.

Figure 14: Confirming an Unaccredited User’s Report Submission

The DOT will follow up with the end user upon receiving the email.

3.4 Driver Updates in TG Web

The TG Vox map legend and driver update event icon display for TG Web shall appear as follows. Vox icons always appear on top of any painted roads.



24

Figure 15: TG Vox Legend and Icon Display in TG Web

Driver update events shall always be labeled Driver Update, right justified in the event’s heading. Special phrases shall also be used for these events that make the source of the information clear (e.g., A driver reported ice on the roadway. It was snowing).

Figure 16: TG Vox Album View Display in TG Web



25

Where present, the reporter’s blog comment goes at the end, after the event’s attribution and its time stamp. The event attribution says Posted by … instead of Last updated by … Web site users are invited to “Tell us more”. Any comment that generates any Web PurifyTM * symbols shall not be written into the event report at all and a message will be displayed upon comment submission explaining that the comment did not pass the Web PurifyTM screening.

Figure 17: TG Vox Album View Display in TG Web (New)

3.4.1 Flagging a Blog Entry (New)

TG Web users shall have the ability to flag a Vox user’s blog entry as offensive or spam. Mousing over a blog entry will cause a red flag icon to appear next to the comment. When the flag icon is moused over, tool tip text shall appear displaying the message “Flag this comment as offensive or spam.” Clicking on the flag icon shall cause the red flag to display permanently next to the flagged comment and a notification email will be sent to the CARS agency program manager.

Figure 18: Flagging a Blog Entry



26

CARS agency operators shall have the ability to delete any Vox report blog entry when viewing the Vox report details on the CARS 4/5 main map or event list. A trashcan icon shall appear next to each blog entry in CARS 4/5. Clicking the trashcan shall permanently delete the blog entry from the Vox report. Blog entries that have been flagged as inappropriate shall appear in CARS 4/5 with a red flag icon.

Figure 19: Deleting a Blog Comment

3.5 Driver Updates in LB-Web

In LB Web, driver updates will be displayed in a very similar fashion as in TG Web, though users will not be able to submit blog comments.



27

Figure 20: TG Vox Display in LB Web List



28

Figure 21: TG Vox Display in LB Web Individual Event

3.6 Public Feedback on Existing Events (New)

TG Vox and CARS-App shall include controls that enable members of the public to submit basic feedback on existing events that are visible in TG Web and CARS App.

Users may submit feedback on any current event in the system, whether it was created by a CARS agency operator, imported through CARS-Import, or created by another member of the public via TG Vox or CARS-App. Events that are scheduled to start in the future shall not be eligible for end user feedback.

3.6.1 Submitting feedback through TG Web

To submit feedback on an existing event via TG Web, the user must first open the event report in an album view. A link and icon reading, “I have something to say about this report” will be visible in the event album view.



29

Figure 22: Initiating Event Feedback

Once the user has initiated the existing event feedback function by clicking on the link or icon, they will be able to either verify that they saw the event, or respond that they did not see the event. Event validation and confirmation is a major topic of concern in all traveler information systems. Often, reports are entered incorrectly or, more commonly, never deleted even after they have gone away.

Figure 23: Submitting Event Feedback

Once the user makes a selection, the user is thanked for the feedback and the feedback is captured



30

and immediately added to what other travelers have said about the event.

Figure 24: Confirming Feedback Submission

3.6.2 Submitting feedback through TG App

End users shall be able to submit the same types of feedback on both public and agency events using similar controls in the CARS-App user interface.

Touch-screen feedback on events shall be limited to app users who have indicated that they are Passengers in the App “Mode” dialogs and/or settings.

To submit feedback on an existing event via the CARS-App touch screen inputs, the user must first open the event report in CARS-App. If the user is a Passenger, a link and icon reading, “I have something to say about this report” will be visible. If the user has indicated that they are a driver, this link and icon will not be visible.



31

Figure 25: Control to initiate touch-screen input on an existing

report

Figure 26: Event screen when touch screen control has been

disabled

3.6.3 End User Feedback

End users shall be able to submit only one piece of feedback for each individual event in the system. Once, for example, an end user submits confirmation of an event, the “I have something to say” control shall no longer appear in that event’s album view for that end user—either in App or in TG Web. The end user will still be able to see the aggregated feedback for that event, however.

No Vox feedback controls shall appear for events whose start time is in the future.



32

Figure 27: Submitting Vox feedback on App Figure 28: Viewing Vox feedback on App

The consolidated end user feedback shall be aggregated regardless of whether the end user submitted feedback on TG Web or CARS-App. For example, if 2 end users confirmed the event on App and 5 on TG Web, both App and TG Web shall indicate “7 users confirmed it.”



33

Appendix A: My Reports Help

The following text shall appear on a separate web page whenever a user clicks the “Need help?” hyperlink at any point within My Reports, where CARS-Routes and Alert D is deployed.. An index at the top of the Help page will allow users to jump directly to the topic they are interested in.

<State> My Reports Help

Help Topics

Route Reports:

General information

Creating a route

Viewing route reports

Getting driving directions

Saving a route

Managing your routes

Printing route information

Send Us Driving Reports:

Sending an update

Publish to 511

My Reports Accounts:

Creating an account

Logging into your account

Changing account settings

Password recovery

Deleting your account

Route Reports

General information

My Reports personalizes your experience by letting you see traffic reports that are

relevant to the highways you travel most often. You don’t need an account to get

started—just create a route by clicking at your origin and destination on the map, or by

entering addresses or city names in the “Pick a route” A and B boxes by the map. Then,

click "Search". If you want to save a particular route for future use, then you will have to

sign up for an account. It’s quick and easy.

Creating a route

Start creating your personalized route by entering an origin and destination into the



34

“Pick a route” boxes labeled A and B. These can be street addresses, cities, or

landmark names. Or, you can right-click the map at your starting and ending locations.

The quickest route between your two points will be calculated automatically and drawn

with a pink line on the map. Colored pins labeled A and B will mark the origin and

destination points. To adjust the origin or destination, type a new address, city, or

landmark name into the A or B box, or click and drag the colored pins on the map. The

route will change accordingly.

If you do not like the route that appears, you can change it by adding an intermediate

point. Hover your mouse over the pink route highlighting and then click and drag the

black and white circle that appears to a new location. You can delete the point by right-

clicking it a second time.

Viewing route reports

After you have created a route, click the "Search" button next to the A and B boxes.

This will bring up a list of road reports that are currently affecting state highways along

your route according to the latest information we have in our systems. Click on any

report in the list to view it in greater detail.

Right click on the map to add a destination, or click on the “Add destination” link that

appears below the origin and destination boxes, labeled A and B. Your route will be re-

calculated each time the origin, destination, or intermediate location is changed. You

can reverse your origin and destination by clicking the 3 bar button next to your route

description and selecting “Go the other way.”

Reports are available only for Minnesota’s State Highway System.

Getting driving directions

After you have created a route, 3 bar button next to your route description and select

“Show directions” to view step-by-step driving directions for that route. Driving directions

can be hidden at any time by clicking the 3 bar button again and selecting “Hide

directions

Saving a route

To save a route, you will need to create an account and log in. After you’re logged in to

your account, a link that says "Save this route" will appear beneath each new route you

create. Follow this link to give the route a name (e.g. "Home to Airport") and save it for

future reference. Up to 20 different routes can be saved to your account.

Managing your routes



35

To view and modify saved routes, you will need to create an account and log in. When

you log in to My Reports, a new “Favorites” main menu option will appear. Clicking on

this will take you to your saved routes list. You can also go to your saved routes list at

any point by clicking the button with the yellow star.

When you move your mouse over a route name, the origin and destination points will

appear on the map using blue dots connected by a blue arrow. Click on any route name

to view traffic reports and driving directions for that route. To edit a route, click the 3 bar

button next to the route name and select “Edit this route.” To delete a route, click

"Delete this route.”

To return to your list of routes at any time, click the button with the yellow star.

Printing route information

You can print the current list of reports and/or driving directions for any route by clicking

the 3 bar button and then selecting “Print this list.” A printer-friendly window will open up

containing a list of current traffic reports affecting that route. If you have opened the

driving directions for that route, they will also be included in the print view.

Route Alerts

Minnesota's direct messaging feature allows users with a My Reports account to sign up

to receive text messages and/or emails alerting them to incidents and delays along their

saved routes.

Signing up for alerts

To sign up for alerts, log in to your My Reports account. An account settings “Cog” will

appear next to your name in the upper right corner of the screen. Click on this cog and

select “My account settings” and then select the “My alerts” tab.

If you want to set up email alerts, just select the types of alerts you'd like to receive,

accept the Terms Of Use and click "Save" - your email address is already on file from

your My Reports account. If you'd like to receive text alerts, select the "Yes" button, and

then enter your cell phone number and service carrier. To verify your cell phone number

and start receiving alerts, click the blue "Verify Now" text. You'll immediately get a text

message with a 4 digit code, which you should enter as directed in the verification box.

As soon as your phone number is verified, you're all set to start receiving alerts - just

select the types of alerts you'd like to receive, as above, accept the Terms Of Use and

hit "Save."

Scheduling alerts



36

To schedule an alert, click the 3 bar button next to the name of the route you'd like to

set an alert for. Select the days of the week and time of day you'd like to get alerts for,

then select either: email alerts, text alerts, or both, and hit "Save." Once alerts are active

for your saved route, a bell next to the route name will appear, and you'll begin receiving

your reports automatically. You can disable alerts for a route at any time by clicking the

3 bar button and selecting “Turn alerts off.”

My Reports Accounts

You can create a personal My Reports account to save routes for easy future access.

Creating an account

If you do not have a My Reports account, click the "(sign in)" link next to the "Your 511"

logo in the upper right corner of the screen. Click the "Get Started" button. The sign-up

page will ask for your first name, last name, email address, and password. The email

address you enter will be used to confirm your account, and to log into your account in

the future. Check the box next to "Sign me in automatically on this computer" if you

want My Reports remember your account information the next time you visit the site.

Press the "Create My Reports account" button to submit your information. We will send

a message to the email address you provided, asking you to read and accept the My

Reports Terms of use. Click the "Accept" link to activate your account. You must

activate your account within 24 hours or it will be deleted.

Logging into your account

If you already have an account with My Reports and are not signed in to the web site

automatically, click the "(sign in)" link in the upper right corner of the screen or click the

button with the yellow star. Enter your email address and password into the boxes

provided.

Changing account settings

You can change your account settings at any time. To open the Account Settings page,

click the "Cog" button in the upper right corner of the screen and select “My account

settings.” The Account Settings page will let you change your first and last name, email

address, or password. You can change your name and/or email address by typing into

the appropriate text boxes, then entering your current password and clicking the "Save"

button. To change your password, click the "Change my password" link. A new window

will open, asking you to enter your current and new passwords. Click "Save" to finalize

your changes.



37

Password recovery

If you forget your password, click the "Forgot your password?" link on the Sign In

window or Account Settings window. We will email you with directions for resetting your

password.

Deleting your account

You can delete your account from the Account Settings window by clicking the "Delete

my account" link. Enter your password in the confirmation window, select “Confirm”, and

your account will be deleted. Sending us driving reports

You can submit driving reports to the 511 system.

Sending an update

To send an update, you will need to create an account [link to Accounts section], log in

[link to Logging in section] and save a route [link to Saving a route section]. A route

menu option that says “Send us an update” appears next to each route you create.

Follow this link to describe the driving conditions you experienced along your route, and

press “Done.”

Publish to 511

Driving reports that you send may be posted on the public 511 web pages. To request

that your reports be posted automatically, go to your account settings and select the

“Share your driving reports on 511” tab. Check the box labeled “I’d like my updates to

be posted automatically to 511,” and click “Save Changes.” A 511 representative will

then contact you with further details.

Documents

TG CARS-Vox Winter Driving Concept of Operations, Detailed ...mndot.org/its/projects/2011-2015/511enhancements/carsvox.pdf · 1 du 10/20/2014 First draft of TG CARS-Vox Winter Driving,