Integration of Transportation Models and Transportation Concurrency

ProcessAgenda:

Concurrency Background

Rationale for Better Integration

Core Data Sets

Key Points for Integration

Brief Bio My Backgrounds

– I am not a transportation modeler– I write software for data systems and GIS

systems and work frequently in the transportation planning field

– I have written a number of applications which attempt to scour data from various models: FSUTMS, Synchro, ArtPlan/Highplan, various spreadsheets.

– I have been involved with Level of Service and Concurrency Management with FDOT and a number of Florida Counties.

– DTS has written and GIS based Concurrency Management System.

Concurrency Background

What is traffic concurrency?– Concurrency is the basic tool of growth

management. It means that public services and facilities will be planned and built such that they will be available in sufficient quantity to meet growth demands.

– Traffic Concurrency: Roads and highways must be built in time and with sufficient capacity to handle the traffic created by new growth as it comes on line.

Why is it important?– Florida Senate Bill 360 (SB 360)– Fair Share

Concurrency Background Florida Senate Bill 360 (SB 360)

– Effective July 1, 2005– Requires Local Governments Update

Capital Improvements Element (CIE)– Transportation Concurrency

Requirements Become Effective December 1, 2006

– SB 360 Addresses Other Concurrency• Sanitary Sewer, Solid Waste, Drainage,

Potable Water, Parks & Recreation, Schools, Transportation Facilities

Concurrency Background SB 360 Non Compliance Penalties

– If CIE Not Received by Dept of Community Affairs by Dec. 1 of Each Year• Local government prohibited from adopting

Future Land Use Map changes, except for amendments to meet new statutory requirements and emergency amendments.• Dept of Community Affairs will notify

Administration Commission (AC)• The AC may impose sanctions on the local

government

Concurrency Background Generally two types of Transportation

Concurrency Strategies– Growth Based

• Use existing trends and long range planning to determine concurrency compliance

– Reservation Based (Checkbook)• Determine trips generated by

development and track reservations of trips.

• Reservation based seems to be the most common implementation.

Relationship with Modeling Data– My organization markets GIS Based

checkbook style concurrency solutions.

– We partner with Land Management System Vendors.

– We have seen multiple projects, in implementation and in consideration that will involve Concurrency Management, Land Management, and Transportation Models.

For Example– A consulting firm was hired to take a

regional FSUTMS model and adapt it to better reflect the specific characteristics of a single county within the region.

– Another consulting firm was being hired to develop a Synchro model for a significant part of the same county.

– A concurrency management system is planned for implementation, and the intent is to seamlessly incorporate model data and model output.

A Second Example– My organization implemented a

concurrency management system in Southwest Florida.

– To deploy quickly, we initially imported existing concurrency information which was derived from models (Synchro).

– County is now migrating to new Land Management System, and we will then connect concurrency to this process. Concurrency will be fully integrated into the Land Management System workflow.

Rationale For Better Integration Initially transportation concurrency

was simply part of the Engineering/Planning Community

It is now becoming a core component of “Enterprise” Land Management Systems.

Rationale For Better Integration Life Cycle…

Rationale Contd. In the “Enterprise” world, automation

and consistency are king.

To support automation, data must be readily accessible and available for use in any of the participating applications.

Concurrency Management and Transportation Models share many similar datasets, and might even be dependant on each other.

Key Concurrency Datasets Projects

Segmentation

Traffic Counts

Assignments

Build Out Status

Data – Key Datasets Projects

– Associated with permit application submittal

– Geographically, projects are most often based on Parcels

Data – Key Datasets Segmentation

– Generally based on roadway basemap

– Both concurrency and models tend to share Node/Link organization

Concurrency Segmentation Sample Attributes

Column Name DescriptionRoad Name of the RoadwayFrom Desc The description of the beginning point of the segment.To Desc The description of the ending point of the segment.Length Length of the segment in MilesFunctional Class The functional classification of the segment.Arterial Group Segment Arterial Grouping (ArtPlan, HighPlan, Synchro,etc)Number of Lanes The number of lane designation (e.g. 4 Div = 4 lane divided)Posted Speed Limit Posted Speed limit or range of speed limits along the segment.Daily Volume Measured current daily volume.K% Peak to Daily RatioD% Peak Hour Distribution PM PK DIR PM Peak Hour direction.LOS A through E Standards Level of Service Standards (Peak Hour) for each segment.PM Peak Hour Directional Volumes Calculated PM Peak Hour Directional VolumesDeMinimus Trips Reserved Sum of reserved trips for a segment.LOS The segments Level of Service Value

Traffic Counts

Assignments

Build Out Status Build Out (i.e. Percentage Complete)

– Extremely important dataset– Allows for the “release” of trips back

onto the network– Highly subjective and might require

field investigation.– Can be objectified by utilizing

Certificate of Occupancy data that exists within Land Management Systems.

Core Data We can break these down

– Data Shared by both processes• Roadway Characteristics• Count Stations/and Associated Counts

– Data derived through one process and used by another• Link Assignments• Reserved Trips

The Bigger Picture

– There is significant overlap between the Transportation Modeling data needs/output and concurrency management needs/output

Key Points for Integration Segmentation:

– This is possibly #1 consideration.– Consideration must be make to

ensure that data derived or collected for one segmentation is compatible with the other.• Synchronize node locations.• Work off of a common basemap.• Utilize common unique identifiers (i.e.

key values)

Key Points for Synchronization Data Standards

– As professionals, create standards bodies and develop standards.

– Push vendors to implement these standards.

UTDF is example of existing standard. Move beyond flat file storage. Transportation modeling incorporates

and generates a tremendous amount of data, much of which is useful to others.

Key Points for Synchronization Aggregation of Results:

– When networks to not precisely match, is there a strategy/understanding for the migration of data from one network structure to the other.

In Summary There is a trend towards formalization of

concurrency processes and incorporation of these in Enterprise Municipal Workflows.– Many administrators believe– Many practitioners see the issues…

Transportation Models are a critical component in management of concurrency.

Begin thinking now about implementing standards such as node/link identifications and their ability to relate data between other networks.