florida’s 511 sunguide data entry and style guide training

FLORIDA’S 511

SunGuide Data Entry and Style Guide Training

AGENDAAGENDA

» Introduction and Purpose of the Training» Flow of EM location data from TMC to 511» Data Entry Style Guide: The Need for consistency» How to Officially Add and Modify configuration» System Maintenance Activities» Operational Coordination Issues» Contact Information for Questions

Purpose of this TrainingPurpose of this Training

» Every change made in SunGuide has the potential to affect 511 users, especially My Florida 511 Personalized Services users

Purpose of this TrainingPurpose of this Training

» Review FDOT’s Data Entry Style Guide for SunGuide and FL-ATIS

Flow of EM Location Data Flow of EM Location Data from TMC to 511from TMC to 511

» Configuration Data within FL-ATIS

District X

IDS Database

FL-ATIS Website FL-ATIS

IVR Database

Config Data – Sent when C2C Publisher RestartsEM Locations, TSS and TvT Links, DMS, CCTV

Status/Command Data – Sent Periodically/AsynchronouslyEM Events, TSS and TvT Status DMS Messages, Floodgate Messages

All website status and configuration data comes from IDS Database

All IVR status and some IVR configuration data comes from IDS Database

Additional IVR configuration data comes from IVR Database

Manually-entered Config Data / Voice RecordingsEM Location Prompts, TvT Link Prompts, EM Extracts, Call Transfers

NOTE: Differences in these two configurations may lead to errors in IVR

Sources of FL-ATIS Data ErrorsSources of FL-ATIS Data Errors

» Administration inconsistencies among Districts– Naming Roadways– Cross Streets and Mile Markers– Travel Time reporting– Missing or different densities of EM Locations– DMS and CCTV location names

» Reporting inconsistencies among Districts– Incidents and congestion on roadways

» Cross-district congestion reporting– Inconsistency when duplicating other districts’

EM Locations

Sources of FL-ATIS Data ErrorsSources of FL-ATIS Data Errors

» C2C refresh for configuration data» Ramps» Latitude, Longitude and Midpoints

– CCTV camera locations– DMS locations– TSS and TvT links– EM Locations

Results of FL-ATIS Data ErrorsResults of FL-ATIS Data Errors

Data Entry Style GuideData Entry Style Guide

» Need for consistency– Twelve different systems entering data,

but public interacts with ONE 511 (One FDOT)– Web data is dynamic…it changes when SunGuide

data is changed or C2C Publisher is restarted– I-95, I95 and I 95 are different roads to FL-ATIS– How it looks to end user

• My Florida 511• 511 Traffic Map page

– Consequence of • Repeated EM locations • Gaps and missing locations

Negative Consequences of Adding Negative Consequences of Adding & Inconsistency of EM Locations& Inconsistency of EM Locations

» When a new EM location is added to SunGuide, there are consequences for FL-ATIS and 511– Impacts the Web site

• Changes My Florida 511 roadways and locations• Confuses users about where a crash or incident is located• Creates inconsistencies that reflect poorly on FDOT

– Impacts the IVR (phone) system• FL-ATIS team must record .wav files for all new locations in

English and Spanish• FL-ATIS team must program and test new grammars —

words 511 recognizes — in English and Spanish

Crucial Priorities in Crucial Priorities in Data ConsistencyData Consistency

» Roadway Description– Roadway Description is commonly referred to as

“Covered Roadways”– Affects how Highways appear in the filter drop-down

menus on the Web site

Roadway Description Roadway Description (Style Guide Page 3)(Style Guide Page 3)

» Interstate Highways: – I-XX (where XX is the number of the highway, whether it is 1, 2

or 3 digits in length)» U.S. Roads:

– US-XX (where XX is the number of the highway, whether it is 1, 2 or 3 digits in length)

» State Roads: – SR-XX (where XX is the number of the highway, whether it is 1,

2 or 3 digits in length)» County Roads:

– CR-XX (where XX is the number of the highway, whether it is 1, 2 or 3 digits in length)

» The Turnpike:– Florida’s Turnpike

» The roadway designator is in all capital letters» There is a hyphen (-) between the letters and the

roadway number» There are no spaces between the letters and the hyphen

or the hyphen and the numbers» There are no periods after the letters in the highway

designation» The direction of travel should not be included when not a

part of the roadway name

» Named Roadways: – Capitalize the first letter of each word in the roadway

name and designation, except where noted below– For example:

Davie Boulevard (not DAVIE BOULEVARD)» There should not be abbreviations in roadway names

(unless otherwise noted)» Roadway designations also should be spelled out fully:

Avenue, Boulevard, Causeway, Expressway, Road, Street

» For highway names that are abbreviations or acronyms, the name should be in all caps– For example:

PGA or LPGA Boulevard (NOT Pga or Lpga)» When a direction is part of a roadway name,

spell out the direction– For example:

North Jones Road, Southwest Davis Boulevard

» A District wants to add this roadway to SunGuidefor coverage on 511. How should the roadwaydescription be correctly entered into SunGuide?

A. SR 434

B. Alafaya Trl

C. SR-434

D. N. Alafaya Trail

E. Alafaya Trail North

» A District wants to add this roadway to SunGuidefor coverage on 511. How should the roadwaydescription be correctly entered into SunGuide?

A. SR 434

B. Alafaya Trl

C. SR-434

D. N. Alafaya Trail

E. Alafaya Trail North

SR-434

» Cities and Metro Areas– It is required that each EM Location have an

associated City or Metro Area where applicable, except in rural parts of the state

• For example, I-10 between Tallahassee and Jacksonville

– This is important for the phone (IVR) system because it allows users to:

• Search for incidents by city at the main menu• Narrow down a highway search by city• If an event is at a location without a city or metro area,

selecting a city will not report that event

» Cities and Metro Areas– Multiple cities can be entered into SunGuide for an

location that is in or near multiple major cities. Multiple cities must be separated by a comma.

• For example: Hollywood, Pembroke Pines

– Leave the City and Metro Area fields blank on EM Locations with no city

• Anything other than a city name (for example: N/A, None) will cause errors in the IVR

– Exceptions to this rule should be discussed with Central Office

Cities and Metro AreasCities and Metro Areas(Style Guide Page 10)(Style Guide Page 10)

» Names should be entered with an initial cap only– For example: Orlando (NOT ORLANDO or orlando)

» Only use the word “City” when it is a part of the official name – For example: Dade City

» City names should be spelled out completely, even though certain parts of the name may ordinarily be abbreviated– For example:

Fort Myers, Saint Cloud, Port Saint Lucie

» Which of the following is an incorrect City or Metro Area entry in SunGuide?

A. Cooper City

B. Saint Augustine

C. South Daytona

D. City of Miami

E. Avon Park

» Which of the following is an incorrect City or Metro Area entry in SunGuide?

A. Cooper City

B. Saint Augustine

C. South Daytona

D. City of Miami

E. Avon Park

Altamonte Springs

Orlando

» EM Reference Point Long Name– Included in

• the Description column of an incident on the Web site

• My Florida 511 Segment Start and End Points

• SunGuide Response Plan Generator (RPG) to fill in the “Cross Street” variable on Dynamic Message Signs (DMSs)

» EM Reference Point Long Name– Needs to

• make clear to the user where an event is taking place• be configured to accommodate DMS message limitations• be consistent with MUTCD requirements, which do not allow

hyphens in roadway names

EM Reference Point Long NameEM Reference Point Long Name(Style Guide Page 13)(Style Guide Page 13)

» Include ONLY the most commonly-used name for the roadway – For example:

Floridas Tpke, I 595, US 441/ OBT SB, Sawgrass Expy

» Do not include:– The word “Exit”– The exit number– The name of the Covered Roadway

(Roadway Description) – The city or county name

» Capitalize the first letter of each word

Note: Excluding dashes and using abbreviations are due to DMS limitations

» When a directional location is part of a roadway name, the direction can be abbreviated, but should include a space between multiple letters (S E, S W, N E, N W)– For example:

N Jones Rd, S W Davis Blvd, E Branch Hwy» Use ordinal extensions for numbered streets

– For example: 1st Ave (NOT 1 Ave), 22nd St (NOT 22 St), 85th Blvd (NOT 85 Blvd)

» Special cases and exceptions should be discussed with Central Office

» Abbreviate when local residents commonly refer to the roadway by its abbreviated name (space between letters)– For example: J T B or O B T

» All abbreviated cross street names should be in all caps (space between letters)– For example:

P G A or L P G A Boulevard (NOT Pga or Lpga)» Abbreviations should follow the U.S. Postal Service

Guidelines: Hwy, Blvd, Rd, Trl, Expy, Pkwy, Cswy, Ave, Tpke, St

» MM XX – XX is the number of the mile marker– no space between the two Ms– a space between MM and the number– For example: MM 5, MM 37, MM 210

» For other locations or points of interest– unique and provide enough information– abbreviations may be used– For example: Fuller Warren Brg, St Johns River Brg

» How should this cross street on the Palmetto Expressway be correctly entered into SunGuide?

A. US-27/ Okeechobee Road

B. US 27/ Okeechobee Rd

C. Exit 17 Okeechobee Rd

D. US 17/ SR 25

E. US 27/ NW South River Dr

» How should this cross street on the Palmetto Expressway be correctly entered into SunGuide?

A. US-27/ Okeechobee Road

B. US 27/ Okeechobee Rd

C. Exit 17 Okeechobee Rd

D. US 17/ SR 25

E. US 27/ NW South River Dr

US 27/ Okeechobee Rd

Break TimeBreak Time

Please be back here in 20 minutes.The workshop will resume promptly.

Other Priorities in Other Priorities in Data ConsistencyData Consistency

» TvT Link Description– TvT Link Description is used on the Web site to

designate unique Travel Time Links. It appears in the Estimated Travel Times pop-up and the Estimated Travel Times tab

TvT Link DescriptionTvT Link Description(Style Guide Page 21)(Style Guide Page 21)

» Each name must be unique» Consistency will help make the Web site list of Estimated

Travel Times easier to read» Use abbreviated roadway designations without periods

(Ave, St, Blvd, etc.)» Avoid other abbreviations unless necessary to make the

Description unique or clear to the user

» TVT Links should include the following information in this order:– Covered Roadway– Direction of travel

(abbreviated: NB, SB, EB, WB) – from – Starting Point

(Mile Marker XX, Exit XX or Cross Street) – to– Ending Point

(Mile Marker XX, Exit XX or Cross Street)

» For example: I-75 NB from Broward/ Miami-Dade County Line to I-595SR-826 SB from NW 67th Ave to I-75I-95 SB from I-10 to J Turner Butler BlvdI-275 SB from Exit 45: I-4 to Exit 39: SR-60/ West Tampa Airport

» County lines must refer to the two counties– For example:

I-95 NB from Broward/ Palm Beach County line to Mile Marker XX

» When a Cross Street is a numbered street, always use ordinal extensions.– For example:

1st Avenue (NOT 1 Avenue) 22nd Street (NOT 22 Street) 3rd Avenue (NOT 3 Avenue) 85th Boulevard (NOT 85 Boulevard)

» SR-826 in District Six travels in two different directions because of curves or other factors. In this case, include the direction of travel that local drivers will be most likely to recognize. Another option would be to include both directions of travel.– For example:

SR-826 WB/SB from NW 37th Ave to I-75

» Additional Note on TvT Links and FL-ATIS. There are other aspects of TvT Links that are published to FL-ATIS beyond the naming that affect FL-ATIS functionality:– TvT links that overlap can create confusion and

frustration among 511 users– Overlapping TvT links should to be kept to a

minimum, except where this might create gaps in reporting

– Make TvT links that make sense to end users and are most useful when setting up My Florida 511 routes

• End points at exits, but not necessarily every exit• Make lengths appropriate to local commuter and

traveler patterns• Use common sense

» What is missing from this TvT Link Description?– Covered Roadway– from– Starting Point

(Mile Marker XX, Exit XX or Cross Street)– To– Ending Point

» What is missing from this TvT Link Description?– Covered Roadway– Direction of travel

(abbreviated: NB, SB, EB, WB) – from– Starting Point

(Mile Marker XX, Exit XX or Cross Street)– To– Ending Point

» EM Location Long Name– Defines what shows on the Web site in the Location

column under the Incidents tab– Populates the Location field in an “event pop-up” on

the Map page– Can be exits, cross streets, mile markers, rest areas,

toll plazas and other points of interest – Wherever possible, the EM Location Long Name

should follow roadway signage with regard to the names of roadways included

– Should not include the Exit number, since this is added by FL-ATIS from another SunGuide field

EM Location Long NameEM Location Long Name(Style Guide Page 6)(Style Guide Page 6)

EM Location Long Name

EM Reference Point Long Name

» Use the following hierarchy to maintain common format:– I-XX (or Floridas Turnpike)/ US-XX/ SR-XX/ CR-XX/

Regional Name/ Local Name/ Attraction or Point of Interest

– NOTE: there should be a space after every forward slash to avoid unusual text wrapping on the Web site.

– Treat Florida’s Turnpike as an Interstate Highway in this hierarchy

– Always use “Floridas Turnpike”– Capitalize the first letter of each word in the roadway

name and designation

» Can include abbreviations – should follow the U.S. Postal Service Guidelines – should be in title case (only first letter is capitalized)

with no punctuation– For example:

Hwy, Blvd, Rd, Trl, Expy, Pkwy, Cswy, Ave, St

» EM Location Long Name examples:– Floridas Turnpike/ US-441/ SR-7– I-595/ SR-862– SR-84/ SW 24th St/ Marina Mile Blvd– US-441/ Orange Blossom Trl SB– I-95 NB– SR-858/ Hallandale Beach Blvd

» Roadway directions can be abbreviated– For example:

N Jones Road, SW Davis Boulevard, E Branch Highway

» Always use ordinal extensions for numbered streets – For example:

1st Avenue (NOT 1 Avenue), 85th Street (NOT 85 Street)

» EM Locations that are Mile Markers, use MM XX – For example: MM 5, MM 37, MM 210

» EM Locations that are Toll Plazas– Include an additional description to make it clear to

the user which toll plaza is being referencedFor example: Broward County Alligator Alley Toll Plaza

» EM Locations that are other locations or points of interest– Provide enough information that a tourist or visitor will

know the locationFor example: Fuller Warren Bridge, Mims Rest Area

» EM Location Long Name should not include – Covered Roadway (Roadway Description) name

A location on I-4 should not include “I-4” in its name– City or Metro Area Names which are in another

SunGuide field– Abbreviations in roadway names

» Abbreviated highway names should be in all caps– For example: PGA or LPGA Boulevard

(NOT Pga or Lpga)

» Which of these is a correct EM Location Long Name?

A. Fla Turnpike

B. SR-535/ Apopka-Vineland Rd

C. I-95 at US-98/ Southern Blvd

D. SR-780/ Fruitville Rd/ Sarasota

E. Main St/ SR-77

F. I-75 Rest Area

» Which of these is a correct EM Location Long Name?

A. Fla Turnpike

B. SR-535/ Apopka-Vineland Rd

C. I-95 at US-98/ Southern Blvd

D. SR-780/ Fruitville Rd/ Sarasota

E. Main St/ SR-77

F. I-75 Rest Area

SR-535/ Apopka-Vineland Rd

» DMS Location Description– Used on the Web site to designate unique DMSs– Naming these consistently and clearly will make sure

users can find the information they need quickly and accurately

DMS Location DescriptionDMS Location Description(Style Guide Page 24)(Style Guide Page 24)

» Use abbreviations for both Covered Roadways and Cross Streets

» Use the most commonly used Covered Roadway names – For example:

“US-441/ US-17/92/ Orange Blossom Trail” might read as “Orange Blossom Trl”

» Capitalize only the first letter of abbreviations, no punctuationHwy, Blvd, Rd, Trl, Expy, Pkwy, Cswy, Ave, Tpke and St

» Use ordinal extensions for numbered Cross Streets: 1st Ave (NOT 1 Ave), 22nd St (NOT 22 St)

» Follow this hierarchy:– Covered Roadway – Direction of Travel (abbreviated: NB, SB, EB, WB) – Directional Offset

(N of, S of, E of, W of — capitalize the direction, put “of” in lower case — or “at” in lower case)

– Cross Street (or Mile Marker)

» For example:– I-4 WB E of SR-436

I-95 SB at Fuller Warren BridgeI-95 NB at Saint Johns County Rest AreaSR-528 WB W of A1A/ Port CanaveralUS-1 NB at MM 7.5

» Which of these is a correct DMS Location Description?

A. 408-EB-JYP

B. I-295 SB S of Commonwealth Ave

C. 75 NB Before US 27

D. I-275 NB S of Bird St.

» Which of these is a correct DMS Location Description?

A. 408-EB-JYP

B. I-295 SB S of Commonwealth Ave

C. 75 NB Before US 27

D. I-275 NB S of Bird St.

I-295 SB S of Commonwe

Southbound

» DMS Messaging– Is not a part of FL-ATIS, except DMS messages

appear on • the Web site Maps page• the Message Boards tab under the Traffic section

– DMS messages on the roadways should match the information on the FL511.com Web site and IVR system. This will

• help users of both systems understand that they are connected

• increase the user trust of FDOT’s ITS systems

– Users should read a DMS message then call 511 and get more detail

DMS MessagingDMS Messaging(Style Guide Page 27)(Style Guide Page 27)

» Should follow these styles:– Covered Roadways: should follow the Roadway

Description style– Cross Streets: should follow the

EM Reference Point Long Name style

– MUTCD guidelines for changeable message signs

– Abbreviations should be used because of limited space on DMS panels

» CCTV Location Description– Used on the FL511.com to designate unique CCTV

camera locations. It appears in:• the Web site Maps page• the Cameras tab under the Traffic section

– Each name must be unique

CCTV Location DescriptionCCTV Location Description(Style Guide Page 28)(Style Guide Page 28)

» The CCTV camera location — which is hard-coded onto each camera image — should match the CCTV camera location description entered in to SunGuide for FL-ATIS

» Use abbreviations for both Covered Roadways and Cross Streets

» Use the most commonly used Covered Roadway names – For example:

“US-441/ US-17/92/ Orange Blossom Trail” might read as “Orange Blossom Trl”

» Capitalize only the first letter of abbreviations, no punctuationHwy, Blvd, Rd, Trl, Expy, Pkwy, Cswy, Ave, Tpke and St

» Use ordinal extensions for numbered Cross Streets: 1st Ave (NOT 1 Ave), 22nd St (NOT 22 St)

» When naming CCTVs, use the following hierarchy:– Covered Roadway

(following the Roadway Description naming style, with abbreviations)

– Direction of the highway the camera is monitoring (NB, SB, EB, WB) — optional when two cameras are at the same location

– Directional Offset (N of, S of, E of, W of — capitalize the direction, put “of” in lower case — or “at” in lower case)

– Cross Street (or Mile Marker)

» For example:– I-4 E of SR-436– I-275 W of HowardFrank Br Hump– I-95 at SW 18th Rd

» Other exceptions to these naming protocols should be discussed with FDOT Central Office on an as-needed basis

I-95 at SW 18th Rd

» Latitude/Longitude (Lat/Long)– Used by the website to determine device and

EM locations on the maps• My Florida 511 Personalized Services routes • CCTV cameras • DMSs• Incident locations• Travel Time mapping

– Used by IVR to determine radius of incident reporting• +/- 5 miles from a given location

Latitude/Longitude (Lat/Long)Latitude/Longitude (Lat/Long)(Style Guide Page 33)(Style Guide Page 33)

» Inaccurate Lat/Long values result in:– CCTV and DMS appearing off the covered roadway– Travel Time and Personalized Services routes

appearing incorrect or impossible

» Lat/Long values should place EM and device locations accurately on the map– EM Locations at the

actual intersection, exit or mile marker

– Device icons on or adjacent to the roadway

» Interstates and other multi-lane highways should have different values for different directions (NB/SB or EB/WB) since FL-ATIS shows different Travel Time paths for the different sides

» There are many Internet tools available to assist in determining the accurate Lat/Long values – http://www.findlatitudeandlongitude.com/– http://itouchmap.com/latlong.html

» Lat/Long values are saved within SunGuide in microdegrees (degrees x 106)

» Invalid values will not be displayed properly from FL-ATIS– Entered in degrees– Lie outside the approximate range

» Florida lat/long values should fall approximately within:– Latitude: 24543532 to 30998800 microdegrees– Longitude: -80030937 to -87636566 microdegrees

» Microdegree values without at least six points of precision must be padded with zeros — values should always have 8 digitsFor example,

26.58 = 26580000 microdegrees

» Primary & Secondary Alternate Roads– The Primary and Secondary Alternate Roads are

presented by the 511 system when a roadway is closed

– It is important that these be consistent so users will be able to easily and accurately identify their detour or alternate route

Primary & Secondary Primary & Secondary Alternate RoadsAlternate Roads(Style Guide Page 31)(Style Guide Page 31)

» Use the same style as EM Long Name– Alternate Roads may include direction of travel,

which should be spelled out– Include only the name of one roadway

(not complete directions or detour)– For example:

SR-XX Northbound Not: Take SR-XX Northbound to CR-YY

Primary & Secondary Primary & Secondary Alternate RoadsAlternate Roads(Style Guide Page 31)(Style Guide Page 31)

» EM Extract Spreadsheets: Extended IVR Portion– Contains information used by the IVR (phone)

system to• Alias = recognize what users request• Spoken Name = deliver (speak) information to users

– Does not come from SunGuide, but is entered into the spreadsheet after the data is extracted from SunGuide

• Roadway Alias• Roadway Spoken Name• Cross Street Alias• Cross Street Spoken Name• Travel Time Links Spoken Name

EM Extract Spreadsheets: EM Extract Spreadsheets: Roadway Alias Roadway Alias (Style Guide Page 37)(Style Guide Page 37)

» Should include ALL variations of frequently used names for the Covered Roadway

» These aliases are used for recognition only and are not spoken out to the user

» This is a 511 user satisfaction issue:– Overloading the system with too many aliases could

slow down 511 for users– 511 needs to include as many aliases as callers might

use, so they get the information they want on their first request

» The IVR (phone) system already understands abbreviations such as: I, SR, CR, US and others

» All words should be spelled out completely to avoid confusion– For example:

Avoid confusion between St. (Saint) and St. (Street):Spell out “Old Saint Augustine Road” and “Port Saint Johns Parkway”

» Entries into this field MUST be separated by a comma– For example:

US-41 is also called US-41 Tamiami Trail, Tamiami Trail, 9th Street (in Collier County), or Cleveland Avenue (in Lee County)

Enter: US-41 Tamiami Trail, US-41, Tamiami Trail, 9th Street, Cleveland Avenue, Highway 41, Route 41

» Which of the following is a correct Alias list for SR-202/ J. Turner Butler Boulevard?A. SR-202 J. Turner Butler Boulevard, SR-202, J.

Turner Butler Boulevard, J. Turner, JTB, Butler Boulevard

B. SR-202 J. Turner Butler Blvd, SR-202, J. Turner Butler Blvd, J. Turner, JTB, Butler Blvd

C. SR-202 J. Turner Butler Boulevard - SR-202 - J. Turner Butler Boulevard - J. Turner - JTB - Butler Boulevard

D. SR-202/ J. Turner Butler Boulevard, SR-202, J. Turner Butler Boulevard, J. Turner, JTB, Butler Boulevard

» Which of the following is a correct Alias list for SR-202/ J. Turner Butler Boulevard?A. SR-202 J. Turner Butler Boulevard, SR-202, J.

Turner Butler Boulevard, J. Turner, JTB, Butler Boulevard

B. SR-202 J. Turner Butler Blvd, SR-202, J. Turner Butler Blvd, J. Turner, JTB, Butler Blvd

C. SR-202 J. Turner Butler Boulevard - SR-202 - J. Turner Butler Boulevard - J. Turner - JTB - Butler Boulevard

D. SR-202/ J. Turner Butler Boulevard, SR-202, J. Turner Butler Boulevard, J. Turner, JTB, Butler Boulevard

EM Extract Spreadsheets: EM Extract Spreadsheets: Roadway Spoken Name Roadway Spoken Name (Style Guide Page 39)(Style Guide Page 39)

» What the IVR (phone system) says to the user» Not a SunGuide field, exists only in the Covered

Roadways and EM Extract spreadsheets» Should duplicate what is in the SunGuide Roadway

Description field for consistency» Should include the top one or two names for a roadway

that a user will expect to hear– For example:

SR-826 should be SR-826 Palmetto Expressway

» Which of the following is a correct IVR Roadway Spoken Name for the Turnpike?

A. Florida’s Turnpike SR-91

B. Florida’s Turnpike, The Turnpike

C. Florida’s Turnpike

D. Florida Turnpike

» Which of the following is a correct IVR Roadway Spoken Name for the Turnpike?

A. Florida’s Turnpike SR-91

B. Florida’s Turnpike, The Turnpike

C. Florida’s Turnpike

D. Florida Turnpike

» Are there other examples around the state that are equally tricky or have multiple possible right answers?

EM Extract Spreadsheets: EM Extract Spreadsheets: Cross Street Alias Cross Street Alias (Style Guide Page 40)(Style Guide Page 40)

» Used by the IVR (phone) system to recognize the location along a Covered Roadway for which a user wants information

» Relates to EM Location Long Name and EM Reference Point Long Name

» Should include ALL variations of frequently used names for the Cross-Street or Exit

» MUST include either the exit number or Mile Marker number (but NOT both) and the Cross Street or Location Name

» Should NOT include the offset (before, at, beyond, ramp to, ramp from) or any information contained in another field

» Should be as generic as possible to avoid confusion within the system

» Any differences in a Cross Street Name will cause the system to believe they are two different locations, and request the user to clarify their request– For example:

An entry of “Southwest 8th Street” in one row and “Southwest 8th Street East” in another will cause the IVR (phone) system to believe they are different locations. These entries should reflect a more generic version of the intersection name, “Southwest 8th Street,” to avoid this confusion.

» Roadway names in this field should also be spelled out completely and entered consistently each time– For example:

The IVR (phone) system does not know that • Martin Luther King Boulevard, • Martin Luther King Blvd and • MLK Boulevard are the same roadway. It believes they are different, and will ask a user to clarify their request and say, “Did you mean Martin Luther King Boulevard, Martin Luther King Boulevard or MLK Boulevard?”

» Entries MUST be separated by a comma » For example:

– Exit 80 B: US-17 92 US-441 Orange Blossom Trail, Exit 80 B: OBT, Exit 80 B: US-17 92, Exit 80 B: US-441, Exit 80 B: 17 92, Exit 80 B: 441, US-17 92 US-441 Orange Blossom Trail, OBT, US-17 92, US-441, 17 92, 441, Exit 80 B

– MM 229: Canoe Creek Road, Canoe Creek Road, Canoe Creek, MM 229

» What’s wrong with the following Cross Street, Exit #, Location of Interest entry?

A. Exit #68: SR-535 Apopka-Vineland Road Lake Buena Vista Walt Disney World, Exit #68: SR-535 Apopka-Vineland Road, Exit #68: SR-535, Exit #68: Apopka-Vineland Road, Exit #68: Lake Buena Vista Walt Disney World, Exit #68: Lake Buena Vista, SR-535, Apopka-Vineland Road, Lake Buena Vista, Walt Disney World, Disney

» What’s wrong with the following Cross Street, Exit #, Location of Interest entry?

A. Exit #68: SR-535 Apopka-Vineland Road Lake Buena Vista Walt Disney World, Exit #68: SR-535 Apopka-Vineland Road, Exit #68: SR-535, Exit #68: Apopka-Vineland Road, Exit #68: Lake Buena Vista Walt Disney World, Exit #68: Lake Buena Vista, SR-535, Apopka-Vineland Road, Lake Buena Vista, Walt Disney World, Disney

EM Extract Spreadsheets: EM Extract Spreadsheets: Cross Street Spoken Name Cross Street Spoken Name (Style Guide Page 42)(Style Guide Page 42)

» What the user hears when an incident or event is located at (or near) that exit or intersection

» Not a SunGuide field, but should closely follow the EM Location Long Name field for consistency

» Include enough information, but keep the name brief:– When the location is an Exit, always include “Exit XX”– When the location is a Mile Marker, even if the

location also has a cross-street name, the term “Mile Marker XX” should always be included

– Always list “Exit XX” or “Mile Marker XX” first, followed by the name for consistency

» The IVR Intersection Spoken Name should follow this format: – Exit XX: Name of Exit

For example:Exit 8: Florida's Turnpike US-441 SR-7Exit 19: I-595 SR-862Exit 25: SR-84 SW 24th Street Marina Mile BoulevardExit 10A: I-95 NB

» IVR Intersection Spoken Name should NOT include: – Covered Roadway (Roadway Description) name

• For example:A location on I-4 should not include “I-4” in its name

– The offset: “before, at, after, ramp to or ramp from”– City, Metro Area or County name– Abbreviations — always use the full name of

the roadway

» Toll Plazas, Rest Areas and Bridges should include an additional description to make it clear to the user which toll plaza is being referenced.– For example:

Broward County Alligator Alley Toll PlazaCollier County Toll Plaza

» Which of the following is a correct IVR Intersection Spoken Name entry?

A. I-75 at SR-846 Immokalee Rd 11th Ave

B. Exit 111: Immokalee Road 11th Avenue SR-846

C. Exit 111: SR-846 Immokalee Road Naples

D. Exit 111: SR-846 Immokalee Road 11th Avenue

E. I-75 Exit 111: SR-846 Immokalee Road 11th Avenue

» Which of the following is a correct IVR Intersection Spoken Name entry?

A. I-75 at SR-846 Immokalee Rd 11th Ave

B. Exit 111: Immokalee Road 11th Avenue SR-846

C. Exit 111: SR-846 Immokalee Road Naples

D. Exit 111: SR-846 Immokalee Road 11th Avenue

E. I-75 Exit 111: SR-846 Immokalee Road 11th Avenue

EM Extract Spreadsheets: EM Extract Spreadsheets: Travel Time Links Spoken NameTravel Time Links Spoken Name(Style Guide Page 44)(Style Guide Page 44)

» The spoken name of the Travel Times Links is not derived from SunGuide data

» Even though the names of the end points may be EM Locations, they are not directly linked in SunGuide

» The names of the Travel Time Link Segments are based on the end points and direction of travel, and should follow this format:– Starting Point

(MM XX, Exit XX or Cross Street) – to– Ending Point

(MM XX, Exit XX or Cross Street)» The IVR automatically adds “from” at the beginning of all

Travel Time Links Spoken Names

» Travel Time Link Segments– For example:

Broward Miami-Dade County Line to I-595NW 67th Ave to I-75I-10 to J Turner Butler BlvdExit 45: I-4 to Exit 39: SR-60 West Tampa Airport

» County lines must refer to the two counties– For example:

Broward Palm Beach County line to MM XX

» Additional Note on TVT Links and FL-ATIS:– TVT links that overlap can create confusion and

frustration among 511 users– Overlapping TVT links (where a single point on a

highway is included in multiple TVT links) should be kept to a minimum, except where this might create gaps in reporting

» Which of the following does not belong in a Travel Time Links Spoken Name entry?

A. Covered Roadway

B. From

C. Starting Point

E. Ending Point

» Which of the following does not belong in a Travel Time Links Spoken Name entry?

A. Covered Roadway

B. From

C. Starting Point

E. Ending Point

Special FL-ATIS AdditionsSpecial FL-ATIS Additions

» E-mail Central Office to make these changes:– New Call Transfer phone numbers

• Transit Agencies• Airports/Seaports• Carpool/Commuter Services

– Construction project public information offices– Web site links– New Floodgate slots within the IVR Call Flow

structure, for example new roadways or roadway segments

How to Officially Add and How to Officially Add and Modify ConfigurationModify Configuration

» EM Locations– Contact Central Office to discuss proposed changes– Once changes are approved:

• Make changes in SunGuide• Extract data from your database• Combine data with the EM Extract Spreadsheet• Send spreadsheet to JohnHope@pbsj.com• Follow-up from John may be necessary for additional

information or corrections• Changes take effect on Quarterly Updates

EM Flag is being discussed as a SunGuide upgrade

» EM Locations– Do not add locations or a new roadway without

notifying Central Office– There are larger implications of adding a new

roadway to FL-ATIS• Marketing materials need to be updated• Districts must be notified• New Grammars, Aliases and Spoken Names need to be

added to the IVR, and .wav files need to be recorded (English and Spanish)

• Additions need to be tested and tuned before release

» Device configuration: (Traffic Sensors, DMS or CCTV)– Make changes in SunGuide– Restart the C2C components– Changes made upon restart– CCTV modifications may take additional coordination

» TvT Link configuration– Once TSS detectors are added, Map Detectors with

TSS Links (Admin Editor: TSS / Map Detectors)– Create Travel Time Links from selecting one or more

TSS Links (Admin Editor: TVT / Travel Time Links)– From the Link and Shield Editor, create TSS links,

adding midpoints to closely follow path of road• Make sure to save often when using editor• Assign TSS links with a roadway and direction

» TvT Link configuration– Update the Travel Time Links Spreadsheet with

added / modified Travel Time links• Submit updated spreadsheet to JohnHope@pbsj.com

– Do not check the “Publish to FL-ATIS” flag until you have coordinated the addition or modification with Central Office

» Floodgate Slots– Contact John Hope at PBS&J to make changes

or additions (JohnHope@pbsj.com)– You will receive an updated SunGuide configuration

file that will update your system– Changes go into effect when local SunGuide

configuration is updated

» Website hyperlinks– E-mail Global-5 with the following

information:• Organization name• URL of English and Spanish

home pages• Appropriate Page on FL511.com:

Links or Transit• Appropriate Category on the page• Changes are made in real-time

Floodgate/Banner MessagesFloodgate/Banner Messages

» There are times when data entry into SunGuide, and thus messages on the 511 systems, cannot provide the level of information or sense of urgency required for certain messages

» Floodgate/banner messages are designed to fill this need

» Floodgates/banner messages impact a large area such as:– an entire roadway– county– region or – the whole state

System Maintenance ActivitiesSystem Maintenance Activities

» Please refer to Floodgate guidelines on Teamsite for details of configuration, composition, and coordination.

» A few key details are:– Floodgate and banner messages are special messages that are

played on the 511 interactive voice response (IVR) system and shown as alerts on FL511.com.

– These messages are meant to be sent in tandem — for every floodgate message there should be a Web site banner message and vice versa.

– Floodgates/banner messages should be posted in English and Spanish. The District 2 Regional Transportation Management Center (RTMC) will provide assistance with Spanish floodgates and banner messages in the event that a fluent Spanish speaker is not available in a District.

Operational Coordination IssuesOperational Coordination Issues

» Standardized congestion reporting» Coordinating AMBER, Silver and LEO alerts» Coordinating Floodgates and Banner Messages,

especially in Spanish» Reporting events near district boundaries» Caller feedback: reporting events

Questions and DiscussionQuestions and Discussion

For More Information…

Mike WachtAsst. Project Manager, 511 Educational Outreach (407) 571-6782 (office)(407) 312-3481 (cell)MikeWacht@global-5.com

John HopeITS GEC Specialist407.806.4147 (office)JohnHope@pbsj.com

Gene Glotzbach, PEFDOT ITS Engineer Administrator (850) 410-5616 (office)Gene.Glotzbach@dot.state.fl.us

florida’s 511 sunguide data entry and style guide training

flatis slide

ivr slide

sunguide data entry

districts em locations

fdot web data

cctv statuscommand data

inconsistency of em

spanish slide

Documents

sop for cctvs in sunguide - cflsmartroads.com

smart sunguide bc v7 · the fort lauderdale smart sunguide...

chapter 25 florida’s design criteria for resurfacing...

sunguide sm software development project status meeting ...

sunguide-ip-d1fm-1.0sunguidesoftware.com/.../deployments/sunguide-ip-d1fm-1.0.2.pdf ·...

training progress report - sunguide®...

florida’s snakes

windows server 2008 r2 x64 sunguide compatibility...

sunguide tm 4.0 fl-atis scenarios / use cases june 24, 2008

smart sunguide tmc -

sunguide and lonestar review - sunguide®...

sop for cctvs in sunguide - florida department of ... ›...

general interface control document - sunguide®...

sunguide sm software development project ad hoc training

sunguide tm software development project test readiness...

sunguide sm software development project status meeting...

sunguide-utvt-2.0sunguidesoftware.com/sunguidesoftware/.../etc/sunguide-utvt-2.0.1.pdftvt...

sop for cctvs in sunguide - cflsmartroads.com for cohuhd...

sailmaker’s guide · 2018. 12. 10. · rcb 30 511-595-11...

statewide transportation management center software library...