Development of an Enterprise Transportation Data Model for Fairfax County, Virginia Presented by:

1. Development of an Enterprise Transportation Data Model for Fairfax County, VirginiaPresented by: Jim Fries PlanGraphics, Inc Brendan Ford Fairfax County GIS

2. Presentation Topics • Background/Existing Situation • Model Requirements • Model Development Process • Existing Model Review • Transportation Network Applications • 911 CAD and Non-emergency Routing Needs • Logical Model • Issues and Next Steps

3. Where is Fairfax County? • 1990 Population: 818,584 • 2000 Population: 969,749 (+18.5%) • Total Land Area:400 square miles • Roadway Miles: Over 4,000 miles

4. Regional Area City of Fairfax City of Falls Church Loudoun County Arlington County City of Alexandria Prince William County Fairfax County Stafford County

5. Existing Situation • Multiple centerlines currently in use • Enterprise, School, E911 • Implementing a new CAD system • Go live target of Q4 2008 • Strong data sharing ties with State and other local governments • Lots of users and agencies with desire to perform AVRR applications • Existing CAD system does not support routing

6. Enterprise Centerline • Relatively simple data model • One of the most detailed in Virginia • Over 40 attributes • Maintained in Oracle/ArcSDE • Regional (multi-jurisdiction) coverage • Updated regularly based on (a) plat recordation, (b) site plan approval, (c) error reports from users, and (d) annual orthoimagery updates • Contains few attributes that support routing

7. Centerline Model Requirements • Provide a single centerline model that can be used by all Fairfax County agencies irrespective of purpose • Support advanced automated routing for Fairfax County’s public safety agencies (Police, Fire & Rescue, Sheriff, Emergency Management) using new CAD software • Support routing by non public safety agencies • Allow use by Virginia State Police and Virginia Department of Transportation to be co-located in new joint Public Safety and Transportation Operations Center (PSTOC) • Contribute to the maintenance of the new VITA road centerline (RCL) dataset for the entire Commonwealth of Virginia

8. Participating Agencies Public Safety • Police • Fire & Rescue • Sheriff • OEM • DPSC • VSP Non-Public Safety • Public Works and Environmental Services • Transportation • Human Services • Public Schools • GIS • Others (Parks, TA, etc.) • VDOT • VITA

9. Model Development Process • Three Step Process: Centerline, AVRR, and Model • Step One: Centerline • Ascertain existing County street centerline and addressing components, processes, and procedures • Analyze CAD products for centerline and routing capabilities • Evaluate available models, standards, and protocols • Establish comprehensive street centerline requirements • Assess external state and local data sources (9 entities) • Step Two: AVRR • Establish automated vehicle routing recommendation (AVRR) requirements • Evaluate non-commercial sources for routing data (26 entities)

10. Model Development Process – con’t • Step Three: Transportation Network Model • Document enterprise transportation network and AVRR requirements • Prepare and Review Conceptual Strawman Model • Develop Logical Data Model • Prepare Physical Data Model

11. Existing Model Review

12. King County, Washington

13. Cobb County, Georgia

14. DHS Geospatial Model

15. DHS Geospatial Model

16. Transportation Network Applications • Address Location(e.g. geocoding, address assignment) • General Analysis/Modeling(e.g., incident and network analysis) • General Reference(e.g., base map layer, reporting, visual reference) • Permitting(e.g., coordination, inspection scheduling) • Planning(e.g., employment and housing forecasts, new facility site selection, route selection, traffic zone analysis, highway planning) • Road Attribute Determination(e.g., cross street determination, legal speed limit confirmation) • Public Health and Safety(e.g., 911 dispatching, alert notification) • Emergency Routing(e.g., network incident response, criminal escape route determination, evacuation route selection) • Routine Routing(e.g., school buses, solid waste, legal service) • Asset/Infrastructure Management(e.g., equipment tracking, project operation and maintenance)

17. Automated Routing Needs • Automated routing routines must account for multiple factors: • direction of travel • speed (legal and free flow) • grade/inclination • traffic flow • impedances (intersections, turn restrictions, vehicle restrictions, blockages, obstacles) • other risk factors • Nearly all agencies recognize the value of performing automated routing across an integrated network that consists of all roadways, pathways, railways, and waterways • Only four County agencies (public schools, transit,para-transit, solid waste) currently do limited computerized routing using different proprietary COTS software packages

18. Fairfax County Logical Model

19. Fairfax County Logical Model

20. Fairfax County Logical Model

21. Logical Model Characteristics • Contains point, polyline, polygon, boundary, and other features • Includes 53 primary tables • Incorporates raster imagery • Provides a non-asset management focus • Introduces a “connector” polyline feature for use in routing • Meets nearly all needs of Fairfax County agencies and VDOT • Allows incremental adoption by other regional jurisdictions • Supports point addressing and integration with County’s Master Address Repository (MAR) for CAD

22. Issues and Next Steps • 911 Dispatch requires a complete network of both planned and actual roads for public safety incident response, and this requirement will necessitate a change in current County street centerline updating procedures (three stage approach) • A variety of relatively minor anomalies with the current enterprise centerline will need to be resolved • No single source of data exists to populate the new model • Multiple existing sources and techniques will need to be utilized to build and maintain some portions of the new transportation network database; new sources and procedures will also be required to populate other data elements

23. Issues and Next Steps – con’t • Some County agencies have unique centerline requirements because of their current COTS software, and some software/procedural modifications may be required • CAD AVRR routines emphasize roadway routing and may not be sophisticated enough to effectively use all modes and data included in the transportation network model • Regional data will be considerably less detailed than Fairfax County data

24. Next Steps • Produce physical data model • Determine data gaps • Prepare data migration plan for existing data sources • Craft development plan for missing data • Generate statement of work to produce data required for transportationnetwork database and AVRR factors • Prepare data procurement RFP • Evaluate current 911 CAD layers for migration • Prepare CAD conversion statement of work and RFP

25. Presented by: Jim Fries Executive Consultant PlanGraphics, Inc. jfries@plangraphics.com and in absentia Brendan Ford Application Development Manager Fairfax County Department of Information Technology Geographic Information Services Brendan.Ford@fairfaxcounty.gov