washington metropolitan area 511 feasibility study conceptual system design review meeting november...

52
Washington Washington Metropolitan Area Metropolitan Area 511 Feasibility Study 511 Feasibility Study Conceptual System Design Conceptual System Design Review Meeting Review Meeting November 1, 2004 November 1, 2004

Upload: bruce-antony-potter

Post on 28-Jan-2016

217 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

WashingtonWashingtonMetropolitan AreaMetropolitan Area

511 Feasibility Study 511 Feasibility Study

Conceptual System Design Conceptual System Design Review MeetingReview Meeting

November 1, 2004November 1, 2004

Page 2: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

22

AgendaAgenda

• Study Background / Next StepsStudy Background / Next Steps• Conceptual System Design Purpose / Conceptual System Design Purpose /

OverviewOverview• 511 Vision511 Vision• Information ContentInformation Content• Telephone SystemTelephone System• Call RoutingCall Routing• Business / N11 EnvironmentBusiness / N11 Environment• WebsiteWebsite• IssuesIssues

Page 3: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

33

Study Background /Study Background /Next StepsNext Steps

• 1.1 Study Overview 1.1 Study Overview – Feasibility Study for 511 in the Feasibility Study for 511 in the

Washington, DC Metropolitan Area part Washington, DC Metropolitan Area part of the Virginia 511 Statewide of the Virginia 511 Statewide ImplementationImplementation

– This Committee has direct oversight for This Committee has direct oversight for the Studythe Study

– Agreed at the project kickoff meeting Agreed at the project kickoff meeting on June 29, 2004, that the 511 on June 29, 2004, that the 511 Guidelines developed by the 511 Guidelines developed by the 511 Deployment Coalition would be a Deployment Coalition would be a baseline baseline

Page 4: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

44

Study Background /Study Background /Next StepsNext Steps

• 1.1 Study Overview 1.1 Study Overview – VDOT looks for compliance with the VDOT looks for compliance with the

Guidelines for the statewide 511 Guidelines for the statewide 511 serviceservice

– The 511 Guidelines:The 511 Guidelines:• Provide a “vision” for 511 Provide a “vision” for 511 • Have been reviewed by ATIS expertsHave been reviewed by ATIS experts• Are nationally acceptedAre nationally accepted

Page 5: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

55

Study Background /Study Background /Next StepsNext Steps

• 1.2 Study Activities to Date1.2 Study Activities to Date– Developed a Detailed Work PlanDeveloped a Detailed Work Plan

• Includes a schedule for the StudyIncludes a schedule for the Study• Reviewed and approved by VDOT and the Reviewed and approved by VDOT and the

CommitteeCommittee

– Discussed data sources and Discussed data sources and information availability for presentation information availability for presentation on 511 with the stakeholders in the on 511 with the stakeholders in the regionregion

Page 6: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

66

Study Background /Study Background /Next StepsNext Steps

• 1.2 Study Activities to Date 1.2 Study Activities to Date – Data sources / information:Data sources / information:

• Highway – congestion, incidents, Highway – congestion, incidents, construction, closures, etc. construction, closures, etc.

• Transit – service areas, schedules, fares, Transit – service areas, schedules, fares, service delays, parking status, etc. service delays, parking status, etc.

• Weather Weather • Tourism Tourism • Bike, pedestrian Bike, pedestrian • Special eventsSpecial events• Emergency situationsEmergency situations

Page 7: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

77

Study Background /Study Background /Next StepsNext Steps

• 1.2 Study Activities to Date1.2 Study Activities to Date– What of the above list of information content is What of the above list of information content is

currently available from your organization? currently available from your organization? • What is the source of this information content? What is the source of this information content? • What is the delivery mechanism for this What is the delivery mechanism for this

information content right now (for example – information content right now (for example – through the telephone? Which number? A through the telephone? Which number? A website? What URL)?website? What URL)?

– What specific information from your What specific information from your organization should be available directly organization should be available directly through a 511 service or be connected to 511? through a 511 service or be connected to 511?

– How often does this information change and How often does this information change and are you capable and willing to provide real-are you capable and willing to provide real-time or near real-time information to 511?time or near real-time information to 511?

– What format(s) is this information available in?What format(s) is this information available in?

Page 8: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

88

Study Background /Study Background /Next StepsNext Steps

• 1.2 Study Activities to Date 1.2 Study Activities to Date – Reviewed the Data Source document October Reviewed the Data Source document October

7, 2004 developed by PB Farradyne for the 7, 2004 developed by PB Farradyne for the RITIS projectRITIS project

• 1.3 Study Next Steps1.3 Study Next Steps– Develop Implementation PlanDevelop Implementation Plan

• Organizational Roles and Responsibilities Organizational Roles and Responsibilities • Management Structure Management Structure • Estimated Implementation CostsEstimated Implementation Costs• Procurement Approach Procurement Approach • Implementation Schedule Implementation Schedule • Launch Launch • Enhancements Enhancements • Marketing Strategy Marketing Strategy

Page 9: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

99

Study Background /Study Background /Next StepsNext Steps

• 1.3 Study Next Steps1.3 Study Next Steps– Implementation PlanImplementation Plan

• Draft - January 6, 2005Draft - January 6, 2005• Review Meeting - January 14, 2005Review Meeting - January 14, 2005• Final - January 23, 2005Final - January 23, 2005

– Finalize Feasibility StudyFinalize Feasibility Study• Assess previous findingsAssess previous findings• Provide options and recommendationsProvide options and recommendations

– Draft - March 11, 2005Draft - March 11, 2005– Review Meeting - March 16, 2005 (conflict Review Meeting - March 16, 2005 (conflict

with National 511 Working Group meeting)with National 511 Working Group meeting)– Final - March 25, 2005Final - March 25, 2005

– Develop an Outreach PlanDevelop an Outreach Plan

Page 10: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1010

Conceptual System Design Conceptual System Design Purpose / OverviewPurpose / Overview

• 1.4 Conceptual System Design 1.4 Conceptual System Design PurposePurpose– Represents the structure of the system Represents the structure of the system

and its related content as perceived by and its related content as perceived by the ultimate user of the system – the the ultimate user of the system – the travelertraveler

– Allows stakeholders to review various Allows stakeholders to review various aspects of the proposed 511 system at aspects of the proposed 511 system at a high level a high level

– Ensures that the proposed direction for Ensures that the proposed direction for the 511 services best serves the the 511 services best serves the region’s interestsregion’s interests

Page 11: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1111

Conceptual System Design Conceptual System Design Purpose / OverviewPurpose / Overview

• 1.5 Conceptual System Design 1.5 Conceptual System Design OverviewOverview– Provides a vision for 511 servicesProvides a vision for 511 services– Examines the information content to be Examines the information content to be

providedprovided– Looks at the telephone system and call routingLooks at the telephone system and call routing– Notes the overall business environment that Notes the overall business environment that

the services operate in (including other N11 the services operate in (including other N11 services)services)

– Offers insight into 511 websitesOffers insight into 511 websites– Uncovers issues for the Committee to discuss Uncovers issues for the Committee to discuss

and resolveand resolve

Page 12: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1212

511 Vision511 Vision

• Based on the national vision:Based on the national vision:

The Washington metropolitan area The Washington metropolitan area 511 is a customer-focused, 511 is a customer-focused, multimodal traveler information multimodal traveler information service available across the region service available across the region via phones, the Internet and other via phones, the Internet and other personal communication devices. personal communication devices. The Washington metropolitan area The Washington metropolitan area 511 system will be interoperable 511 system will be interoperable with neighboring 511 systems with neighboring 511 systems resulting in a more satisfactory resulting in a more satisfactory travel experience.travel experience.

Page 13: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1313

Information ContentInformation Content

• 3.1 3.1 Coverage Coverage Area Area

Page 14: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1414

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Roadway Content Roadway Content

• Regional Overviews or Summaries Regional Overviews or Summaries • Content is Route / Corridor-based Content is Route / Corridor-based • Limited Access Roadways and the National Limited Access Roadways and the National

Highway System CoverageHighway System Coverage• More Detail Needed in Urban Areas More Detail Needed in Urban Areas • Content is Automated Content is Automated

Page 15: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1515

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Proposed Roadway Content Proposed Roadway Content

• Regional Reports Regional Reports – The DistrictThe District– Northern Virginia Northern Virginia – MarylandMaryland

• Draft Roadway Coverage (See Appendix A)Draft Roadway Coverage (See Appendix A)• Draft Segments (See Appendix B)Draft Segments (See Appendix B)

– InterstatesInterstates– All Others – either inside or outside the All Others – either inside or outside the

BeltwayBeltway

Page 16: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1616

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Types of ContentTypes of Content

• Construction / Maintenance Projects Construction / Maintenance Projects • Road Closures and Delays Road Closures and Delays • Major Special Events Major Special Events • Weather and Road Surface Conditions Weather and Road Surface Conditions

Page 17: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1717

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Detailed InformationDetailed Information

• Location Location • Direction of Travel Direction of Travel • General Description and Impact General Description and Impact • Days / Hours and / or Duration Days / Hours and / or Duration • Travel Time or Delay Travel Time or Delay • Detours / Restrictions / Routing Advice Detours / Restrictions / Routing Advice • Forecasted Weather and Road Surface Forecasted Weather and Road Surface

Conditions Conditions • Current Observed Weather and Road Current Observed Weather and Road

Surface Conditions Surface Conditions

Page 18: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1818

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Sufficient data to provide actionable Sufficient data to provide actionable

information to travelers information to travelers – Implementation Issues to DiscussImplementation Issues to Discuss

• Travel time / speed / congestion dataTravel time / speed / congestion data• Observed weather conditions Observed weather conditions

Page 19: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

1919

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Public Transportation ContentPublic Transportation Content

• Information on All Transit Agencies in the Information on All Transit Agencies in the Area Should Be AvailableArea Should Be Available

• 511 Works in Conjunction with Transit 511 Works in Conjunction with Transit Customer Service Centers Customer Service Centers

• 511 Should Minimize Additional Customer 511 Should Minimize Additional Customer Service Center Overload Via Automated Service Center Overload Via Automated Messages Messages

• Each Agency Responsible for Their Each Agency Responsible for Their Information Information

Page 20: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2020

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Public Transportation Public Transportation

AgenciesAgencies• Alexandria DASHAlexandria DASH• Arlington Rapid Transit Arlington Rapid Transit • Fairfax ConnectorFairfax Connector• Fairfax CUEFairfax CUE• Loudoun County TransitLoudoun County Transit• MARCMARC• Metropolitan Washington Metropolitan Washington

Airports Authority Airports Authority • Montgomery County Transit Montgomery County Transit

– Ride On– Ride On• PRTC (serving Prince William PRTC (serving Prince William

Co.)Co.)• TheBus (Prince George's TheBus (Prince George's

County)County)• VREVRE

– Service disruptions / Service disruptions / exceptionsexceptions

– Brief agency Brief agency description with call description with call transfer optiontransfer option

Page 21: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2121

Information ContentInformation Content

• 3.2 Basic Content3.2 Basic Content– Weather ContentWeather Content

• If weather will impact a person’s trip, then If weather will impact a person’s trip, then they should be alerted to that actuality or they should be alerted to that actuality or possibilitypossibility

• Not be a “top level” menu optionNot be a “top level” menu option– Roadway content Roadway content – Public transportation “exception” messagesPublic transportation “exception” messages

• National Weather Service warnings and National Weather Service warnings and advisories available to travelers as advisories available to travelers as floodgate messages floodgate messages

Page 22: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2222

Information ContentInformation Content

• 3.3 Optional Content3.3 Optional Content– Include in Basic ContentInclude in Basic Content

• Roadway ContentRoadway Content– Security Measures and ClosuresSecurity Measures and Closures– Special Events Special Events

• Public Transportation Public Transportation – AirportsAirports– Carpool / Vanpool Carpool / Vanpool – Major Public Transportation Delays Major Public Transportation Delays – Security Measures and ClosuresSecurity Measures and Closures– Special Events Special Events

Page 23: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2323

Information ContentInformation Content

• 3.3 Optional Content3.3 Optional Content– Include in Basic ContentInclude in Basic Content

• Emergency Alerts Emergency Alerts – AMBER AlertsAMBER Alerts– Heightened Security AlertsHeightened Security Alerts– Security Measures and Closures Security Measures and Closures

• Tourist Information – handled through Tourist Information – handled through floodgates by the appropriate convention floodgates by the appropriate convention and visitors agency and visitors agency

Page 24: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2424

Information ContentInformation Content

• 3.4 Content Quality and 3.4 Content Quality and ConsistencyConsistency– Accuracy Accuracy – Timeliness Timeliness – Reliability Reliability – Consistency of Presentation Consistency of Presentation – Relevancy Relevancy

Page 25: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2525

Information ContentInformation Content

• 3.5 Other Content Issues3.5 Other Content Issues– Amber Alerts / Security – Concept of Operations Amber Alerts / Security – Concept of Operations

neededneeded• When activatedWhen activated• Message structureMessage structure• What authorizations are required to activateWhat authorizations are required to activate• Etc.Etc.

– Timestamping – should be utilized to give travelers a Timestamping – should be utilized to give travelers a reference as to the latency of the informationreference as to the latency of the information

– Other Optional Services DiscussionOther Optional Services Discussion• Travel Time or Other Enhanced Traffic Information (e.g. Travel Time or Other Enhanced Traffic Information (e.g.

Alternate Routes) Alternate Routes) • Parking Parking • Personalized / Customizable ServicesPersonalized / Customizable Services• Points of InterestPoints of Interest• Highway Advisory Radio (HAR) contentHighway Advisory Radio (HAR) content• VMS / DMS contentVMS / DMS content

Page 26: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2626

4. Telephone System4. Telephone System

• Accept wireless and wireline callsAccept wireless and wireline calls• Fully voice-activated Fully voice-activated • Touchtone backup Touchtone backup • Voice shortcutsVoice shortcuts• Privately hosted network-based Privately hosted network-based

system system • Available 24 / 7 / 365Available 24 / 7 / 365• Call transfers Call transfers • Floodgate messages Floodgate messages

Page 27: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2727

4. Telephone System4. Telephone System

• 511 Conceptual Menu511 Conceptual MenuWashington Metropolitan

Area 511

TourismTips/Help/Comments

PublicTransportation

Other TravelerInformation

Roadways

FloodgateFloodgate

Roads (regionalreports, incident/events, including

weather)

Floodgate Floodgate Floodgate

Maryland

West Virginia

Virginia (to 511)

Carpool / Vanpool

Transit Agencyservice

disruptions /exceptions/ brief

agencydescription, call

transfer

AirportsGeneralizedDelays andBroadcastMessages

Convention andVisitor Bureaus

Baltimore

Page 28: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2828

5. Call Routing5. Call Routing

• The call goes through and the The call goes through and the call gets answeredcall gets answered

• Call routing and carrier Call routing and carrier coordination is not a trivial coordination is not a trivial matter, for both wireline and matter, for both wireline and wireless carriers with cost wireless carriers with cost implicationsimplications

• Calling areas do not neatly Calling areas do not neatly follow political boundaries and follow political boundaries and jurisdictionsjurisdictions

Page 29: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

2929

5. Call Routing5. Call Routing

• Cingular / AT&T WirelessCingular / AT&T Wireless

Page 30: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3030

5. Call Routing5. Call Routing

• Verizon WirelessVerizon Wireless

Page 31: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3131

5. Call Routing5. Call Routing

• NextelNextel

Page 32: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3232

5. Call Routing5. Call Routing

• Sprint PCSSprint PCS

Page 33: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3333

5. Call Routing5. Call Routing

• T-MobileT-Mobile

Page 34: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3434

Call RoutingCall Routing

• 5.2 Wireline5.2 Wireline– ILECsILECs– CLECsCLECs

• 5.3 Access for the Hearing 5.3 Access for the Hearing ImpairedImpaired

• 5.4 Payphone and Private 5.4 Payphone and Private Branch Exchange (PBX) AccessBranch Exchange (PBX) Access– Payphone access has cost implications Payphone access has cost implications

Page 35: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3535

6. Business /6. Business /N11 EnvironmentN11 Environment

• Basic services should be no more Basic services should be no more than the cost of a local callthan the cost of a local call

• Deploying agencies should expect Deploying agencies should expect to fully fund the 511 service to fully fund the 511 service

• Advertising and sponsorship are Advertising and sponsorship are acceptableacceptable

• Fee-generating premium or Fee-generating premium or enhanced services are acceptableenhanced services are acceptable

Page 36: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3636

Business /Business /N11 EnvironmentN11 Environment

• 6.1 Operations and 6.1 Operations and Maintenance CostsMaintenance Costs– 511 deployers do not all account for their costs 511 deployers do not all account for their costs

in a similar mannerin a similar manner– Cost examplesCost examples

• San Francisco Bay Area - $6 million per year San Francisco Bay Area - $6 million per year • Orlando - additional $500,000 for system planning and Orlando - additional $500,000 for system planning and

design and application development and testing and design and application development and testing and $265,000 per year for operations personnel and $265,000 per year for operations personnel and telephone service minutestelephone service minutes

• Southeast Florida - $1 million per year Southeast Florida - $1 million per year • Tampa - $8.2 million over 5 years (includes ITIP)Tampa - $8.2 million over 5 years (includes ITIP)• Cincinnati - system development costs of $400,000 and Cincinnati - system development costs of $400,000 and

expected O&M costs of $60,000 per yearexpected O&M costs of $60,000 per year

Page 37: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3737

Business /Business /N11 EnvironmentN11 Environment

• 6.2 Identification of a Business 6.2 Identification of a Business ModelModel– Public sector funding is likely required Public sector funding is likely required

for near-term implementation and for near-term implementation and continued operations continued operations

– Watch VDOT’s advertising / travel Watch VDOT’s advertising / travel services offering services offering

– Experience with Partners in MotionExperience with Partners in Motion– SANDAG RFP met with skepticism SANDAG RFP met with skepticism

Page 38: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3838

Business /Business /N11 EnvironmentN11 Environment

• 6.3 Funding Strategy and 6.3 Funding Strategy and SourcesSources– ITS earmark funding ITS earmark funding – STPSTP– NHSNHS– CMAQ CMAQ – Agency fundingAgency funding– Opportunity to fund the 511 services in Opportunity to fund the 511 services in

a unique multi-agency manner across a unique multi-agency manner across state lines and modesstate lines and modes• CincinnatiCincinnati• Southeast FloridaSoutheast Florida

Page 39: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

3939

Business /Business /N11 EnvironmentN11 Environment

• 6.4 N11 “Lessons Learned”6.4 N11 “Lessons Learned”– 311 in Washington and Baltimore311 in Washington and Baltimore

• Millions of callsMillions of calls• Public educationPublic education

– Partners in MotionPartners in Motion• Failed business modelFailed business model

Page 40: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4040

Business /Business /N11 EnvironmentN11 Environment

• 6.5 Applicability to 5116.5 Applicability to 511– With 311 and 211 available in the With 311 and 211 available in the

District, educating consumers on the District, educating consumers on the types of information available through types of information available through 511 is paramount511 is paramount

Page 41: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4141

7. Website7. Website

• Co-branded as 511Co-branded as 511• Easy to navigate Easy to navigate • Accessible using a standard Internet Accessible using a standard Internet

browser browser • Consistent with information available Consistent with information available

on the 511 telephone service on the 511 telephone service • More detailed information possiblyMore detailed information possibly• Minimize load times and the number Minimize load times and the number

of “mouse clicks” of “mouse clicks” • Available helpAvailable help• Section 508 compliantSection 508 compliant

Page 42: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4242

7. Website7. Website

• TampaTampa

Page 43: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4343

7. Website7. Website

• TampaTampa

Page 44: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4444

7. Website7. Website

• Southeast FloridaSoutheast Florida

Page 45: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4545

7. Website7. Website

• Southeast Florida Southeast Florida

Page 46: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4646

7. Website7. Website

• KentuckyKentucky

Page 47: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4747

7. Website7. Website

• KentuckyKentucky

Page 48: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4848

7. Website7. Website

• San Francisco Bay Area San Francisco Bay Area

Page 49: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

4949

7. Website7. Website

• San Francisco Bay AreaSan Francisco Bay Area

Page 50: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

5050

8. Issues8. Issues

• Extension of the 511 Virginia Extension of the 511 Virginia service or a separate, entirely service or a separate, entirely independent system?independent system?

• Other issues? Other issues?

Page 51: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

5151

DiscussionDiscussion

Page 52: Washington Metropolitan Area 511 Feasibility Study Conceptual System Design Review Meeting November 1, 2004

5252

Contact InfoContact Info

Todd Kell Todd Kell

PBS&J Project ManagerPBS&J Project Manager

Ph. (804) 560-7600 or (804) 512-6601Ph. (804) 560-7600 or (804) [email protected]

Pete Costello Pete Costello

PBS&J Task ManagerPBS&J Task Manager

Ph. (407) 806-4440 or (202) 550-5795Ph. (407) 806-4440 or (202) [email protected]