IntelliDriveSM, 47888-47891 [2010-19534]
Download as PDF
sroberts on DSKD5P82C1PROD with NOTICES
47888
Federal Register / Vol. 75, No. 152 / Monday, August 9, 2010 / Notices
interstate system and on other roads
built to interstate standards. Moreover,
driving in congested urban areas
exposes the driver to more pedestrian
and vehicular traffic than exists on
interstate highways. Faster reaction to
traffic and traffic signals is generally
required because distances between
them are more compact. These
conditions tax visual capacity and
driver response just as intensely as
interstate driving conditions. The
veteran drivers in this proceeding have
operated CMVs safely under those
conditions for at least 3 years, most for
much longer. Their experience and
driving records lead us to believe that
each applicant is capable of operating in
interstate commerce as safely as he/she
has been performing in intrastate
commerce. Consequently, FMCSA finds
that exempting these applicants from
the vision standard in 49 CFR
391.41(b)(10) is likely to achieve a level
of safety equal to that existing without
the exemption. For this reason, the
Agency is granting the exemptions for
the 2-year period allowed by 49 U.S.C.
31136(e) and 31315 to the 30 applicants
listed in the notice of June 16, 2010 (75
FR 34209).
We recognize that the vision of an
applicant may change and affect his/her
ability to operate a CMV as safely as in
the past. As a condition of the
exemption, therefore, FMCSA will
impose requirements on the 30
individuals consistent with the
grandfathering provisions applied to
drivers who participated in the
Agency’s vision waiver program.
Those requirements are found at 49
CFR 391.64(b) and include the
following: (1) That each individual be
physically examined every year (a) by
an ophthalmologist or optometrist who
attests that the vision in the better eye
continues to meet the standard in 49
CFR 391.41(b)(10), and (b) by a medical
examiner who attests that the individual
is otherwise physically qualified under
49 CFR 391.41; (2) that each individual
provide a copy of the ophthalmologist’s
or optometrist’s report to the medical
examiner at the time of the annual
medical examination; and (3) that each
individual provide a copy of the annual
medical certification to the employer for
retention in the driver’s qualification
file, or keep a copy in his/her driver’s
qualification file if he/she is selfemployed. The driver must also have a
copy of the certification when driving,
for presentation to a duly authorized
Federal, State, or local enforcement
official.
VerDate Mar<15>2010
17:01 Aug 06, 2010
Jkt 220001
Discussion of Comments
DEPARTMENT OF TRANSPORTATION
FMCSA received one comment in this
proceeding. The comment was
considered and discussed below.
The Pennsylvania Department of
Transportation stated that it had
reviewed the driving record for Chris A.
Miller and was in favor of granting a
Federal vision exemption to this
individual.
Federal Highway Administration
Conclusion
SUMMARY:
Based upon its evaluation of the 30
exemption applications, FMCSA
exempts, David E. Balboni, Mark S.
Berkheimer, Rodney H. Bridges, James
D. Broadway, Wesley M. Creamer,
Charles M. Dunn, Tony K. Ellis, Leonard
J. Ferrin, Paul A. Giarrusso, Jerry L.
Gibson, Rici W. Giesseman, George R.
House, Michael A. Jabro, Thomas L.
Jashurek, Jr., Michael M. Martinez,
Robert L. McClain, Daniel E. Miller,
Buddy W. Myrick, James L. Okonek,
Aaron L. Paustian, Alan J. Reynaldos,
Kenneth R. Riener, Charles L. Rill, Sr.,
Jules M. Sancho, Jr., Robert Smiley,
Rogers L. Sulfridge, Christopher M.
Vincent, Derik T. Winebrenner, Curtis L.
Wolff and Robert L. Zebrowski, from the
vision requirement in 49 CFR
391.41(b)(10), subject to the
requirements cited above (49 CFR
391.64(b)).
In accordance with 49 U.S.C. 31136(e)
and 31315, each exemption will be valid
for 2 years unless revoked earlier by
FMCSA. The exemption will be revoked
if: (1) The person fails to comply with
the terms and conditions of the
exemption; (2) the exemption has
resulted in a lower level of safety than
was maintained before it was granted; or
(3) continuation of the exemption would
not be consistent with the goals and
objectives of 49 U.S.C. 31136 and 31315.
If the exemption is still effective at the
end of the 2-year period, the person may
apply to FMCSA for a renewal under
procedures in effect at that time.
Issued on: July 29, 2010.
Larry W. Minor,
Associate Administrator for Policy and
Program Development.
[FR Doc. 2010–19592 Filed 8–6–10; 8:45 am]
BILLING CODE 4910–EX–P
PO 00000
IntelliDriveSM 1 Performance
Measurement and Performance-Based
Management Demonstrations; Request
for Information
Federal Highway
Administration (FHWA), DOT.
ACTION: Notice.
AGENCY:
This notice is a Request for
Information (RFI) and comments that
will be used to help refine the plans for
one or more demonstrations focused on
the use of IntelliDriveSM data sources
for performance measurement and
performance-based management. The
FHWA is issuing this RFI in
collaboration with and on behalf of
other agencies within the DOT,
specifically the Federal Transit
Administration, the Federal Motor
Carrier Safety Administration, and the
Research and Innovative Technology
Administration. Feedback and
comments on any aspect of the RFI are
welcomed from all interested public,
private, and academic entities. While all
feedback is welcomed, DOT is
particularly interested in feedback on
the questions provided in the last
section of this RFI.
RFI Guidelines: Responses to this RFI
should be submitted by 11:59 p.m.
Eastern Time on September 8, 2010.
Responses to this RFI should be
delivered electronically as an e-mail or
as an attachment to an e-mail sent to
DMAdemo@dot.gov.
Responses to this notice are not offers
and cannot be accepted by the
Government to form a binding contract
or issue a grant. Information obtained as
a result of this RFI may be used by the
government for program planning on a
non-attribution basis. If you wish to
submit any information under a claim of
confidentiality, you should submit via
e-mail to the address given below under
FOR FURTHER INFORMATION CONTACT, your
complete submission, including the
information you claim to be confidential
commercial information. When you
submit information containing
information identified as confidential
commercial information, you should
include a cover letter setting forth the
reasons you believe the information
qualifies as ‘‘confidential commercial
information.’’ (49 CFR 7.13(c)(4) and
7.17) If we receive a request to examine
or copy this information, we treat it as
any other request under the Freedom of
Information Act (5 U.S.C. 552), but we
1 IntelliDrive is a service mark of the U.S.
Department of Transportation.
Frm 00134
Fmt 4703
Sfmt 4703
E:\FR\FM\09AUN1.SGM
09AUN1
sroberts on DSKD5P82C1PROD with NOTICES
Federal Register / Vol. 75, No. 152 / Monday, August 9, 2010 / Notices
will process the request in accordance
with the procedures found in 49 CFR
7.17.
FOR FURTHER INFORMATION CONTACT: For
questions about the program discussed
herein, contact Mr. Robert Rupert,
Transportation Information
Management Team, FHWA Office of
Operations, (202) 366–2194,
robert.rupert@dot.gov. For legal
questions, interpretations and counsel,
please contact Sheryl Williams, Office
of the Chief Counsel, (202) 366–0618,
sheryl.williams@dot.gov, 1200 New
Jersey Avenue, SE., Washington, DC
20590. Office hours for the FHWA are
from 7:45 a.m. to 4:15 p.m., e.t., Monday
through Friday, except Federal holidays.
Additional information about the
IntelliDriveSM initiative is at https://
www.its.dot.gov/intellidrive/.
SUPPLEMENTARY INFORMATION: The DOT
IntelliDriveSM program is a multimodal
initiative that aims to enable safe,
interoperable networked wireless
communications among vehicles, the
infrastructure, and travelers’ personal
communications devices. IntelliDriveSM
research is being sponsored by the DOT
and others to leverage the potentially
transformative capabilities of wireless
technology to make surface
transportation safer, smarter, and
greener. One component of this
initiative is the Dynamic Mobility
Applications program. This program
seeks to identify, develop, and deploy
applications that leverage the full
potential of connected vehicles,
travelers, and infrastructure in order to
enhance current operational practices
and transform future surface
transportation systems management.
The Dynamic Mobility Applications
program will include one or more field
demonstrations of applications that
integrate IntelliDriveSM data to support
multi-modal performance measurement
and performance-based management.
The applications are envisioned to
include support for both real-time and
non real-time decisionmaking and
operations. The intent is to conduct one
or more demonstrations that include
mobility and productivity performance
measurement as a cornerstone element
of the demonstration plan.
Demonstrations selected in this effort
will focus on the data collection and
processing to produce performance
metrics in one, or preferably more, of
the following areas:
• Productivity.
• Mobility, including impact on
freight movements.
• Livability/Accessibility
(accessibility is defined as the ability to
reach goods, services and activities).
VerDate Mar<15>2010
17:01 Aug 06, 2010
Jkt 220001
• Environment/fuel use.
• Pavement conditions (e.g., snow or
ice cover, surface roughness, pothole
detection).
The DOT seeks comments and
innovative ideas from the public sector,
private sector, and academic
communities concerning the
demonstration program described in
this RFI. While comments are welcomed
on any area of the RFI, the DOT is
particularly interested in responses to
the questions listed at the end of this
RFI.
Dynamic Mobility Applications
Demonstration Program Description
This program envisions one or more
demonstrations beginning in 2011. The
intent of these near-term demonstrations
is to begin work with private
companies, States, transit agencies, and
commercial vehicle operators or freight
shippers to develop applications
utilizing data captured from multiple
sources (e.g., vehicles, travelers,
infrastructure) across all elements of the
surface transportation system (i.e.,
transit, freeway, arterial, parking
facilities and tollways) to support
performance measurement and
performance-based management. This
demonstration effort aims to leverage
existing operational capabilities or to
spur innovation among early adopters of
innovative performance measurement
and mobility applications. The limited
number of resources and the short lead
time for this effort precludes the largescale deployment of new in-vehicle or
roadside technologies. Therefore, unless
a site already has a deployed Dedicated
Short Range Communications (DSRC)
infrastructure, it is anticipated that any
required mobile communications will
use existing commercial wireless
services.
The performance measurement
demonstration(s) should address the
following research questions:
• Can system productivity and
traveler mobility be characterized in
innovative and meaningful new ways by
integrating emerging data sources (i.e.,
vehicles and mobile devices as data
sources)?
• To what extent can IntelliDriveSM
be used to support real-time
performance-based management of
roadways, transit systems, and freight
carriers?
• What are the institutional, legal,
and technical issues that may help or
hinder the use of IntelliDriveSM to
improve performance-based
management?
• What wireless and other
communications media can be
combined to make large-scale data
PO 00000
Frm 00135
Fmt 4703
Sfmt 4703
47889
capture and mobility applications cost
effective?
• How can diverse data sources be
efficiently integrated and utilized?
• Can customer satisfaction with
demonstrated applications be
identified?
Proposed Performance Measurement
Demonstration Program Requirements
All candidate sites and prospective
partners will be required to address the
following fundamental aspects of the
Performance Measurement
Demonstration vision, including:
• Performance measurement. Welldefined, quantitative performance
measures and a clear strategy for
evaluating these impacts must be a part
of any candidate demonstration.
Preliminary thinking on possible
measures of interest is provided later in
this RFI. More specific guidance will be
included in the solicitation. System
productivity measures will quantify the
efficient movement of travelers and
goods under periods of peak demand.
Traveler mobility measures will
quantify travel delay and improved
travel reliability. This specifically
includes mobility or accessibility
assessments for travelers who utilize
transit as a component of end-to-end
trip-making. Other measures will
characterize the reliability of freight/
goods movement within the system.
Additional performance areas such as
accessibility, environment/fuel use, and
pavement conditions should also be
considered.
• Multi-source data capture.
Demonstrations should feature frequent
capture and systematic integration of
data from a broad range of sources.
Desired sources should include multiple
types of infrastructure-based sensors,
transit vehicle systems (bus and rail), a
full range of vehicle types acting as
mobile probes (including freight carriers
and transit vehicles), and travelers
moving between modes as they
complete trips.
• Innovative decision support
applications. These applications should
exploit the value of integrated
multisource performance data.
Applications selected for demonstration
should fully and cost effectively
leverage captured data to provide
innovative services to multiple users.
The primary focus is on providing
decision support tools (both real-time
and non real-time) to traffic managers
and transit operators. As a secondary
objective, demonstrations may also
provide mobility applications targeted
at system users, including freight
carriers and multimodal travelers. To
the greatest extent possible, it is the
E:\FR\FM\09AUN1.SGM
09AUN1
sroberts on DSKD5P82C1PROD with NOTICES
47890
Federal Register / Vol. 75, No. 152 / Monday, August 9, 2010 / Notices
intent of the Dynamic Mobility
Applications Program to make
algorithms and source code associated
with new applications or application
enhancements funded as a part of these
demonstrations to be made freely
available under open source agreements.
• Critical mass demonstration.
Demonstrations should be scoped to be
conducted in operational multifacility,
multimodal transportation networks
spanning urban areas or in interurban
corridors. Demonstrations set in
laboratory or closed facility test
environments are precluded from
consideration. Preference will be shown
to demonstration proposals combining
data drawn from large contemporaneous
populations of vehicles or travelers with
mobile devices participating as mobile
probes concurrently with fixed
infrastructure-based sensor systems.
• Complex Environment. System
performance in each demonstration will
be characterized in complex networks
containing multiple facility types (e.g.,
freeway, arterial, parking, transit bus,
and rail), considering both the quantity
and quality of travelers and goods
movement supported by the system in
end-to-end trip-making across multiple
facilities and modes.
• No driver distraction effects.
Demonstrated applications will involve
collection of information from moving
vehicles. The information collection
must be conducted in a manner that will
not distract drivers or compromise
safety. This demonstration will not
include applications that require driver
interaction while a vehicle is in motion.
See https://www.distraction.gov for
additional information on distracted
driving.
• Data sharing. A required element of
the demonstration(s) is the systematic
collection of data (from both mobile and
fixed sources). It is the intent to provide
open access to these data through the
IntelliDriveSM Data Capture and
Management program. These data may
be made available as the demonstration
is conducted, or made available shortly
after the conclusion of the
demonstration. These data are intended
to support research activity and
mobility application development in
later phases of the Dynamic Mobility
Applications program. If necessary, data
may be transformed or aggregated to
protect privacy, and the Government
will consider allowing transformation or
aggregation to protect intellectual
property rights.
• Independent Evaluation.
Demonstrations must contain an
impacts evaluation and target user
satisfaction assessment for each tested
application. An independent evaluation
VerDate Mar<15>2010
17:01 Aug 06, 2010
Jkt 220001
contractor will assist in planning and
executing an evaluation plan and will
author a national evaluation report.
• Use of Standards. Demonstration
projects shall make appropriate use of
ITS standards for information exchange.
The demonstration(s) should collect
the data and implement applications
that can calculate the following types of
performance metrics and, where
appropriate, include applications for
acting on the real-time measurement
information.
Mode-Independent Overall System
Measures. A key element of the
demonstration will be the
characterization and quantitative
measurement of the performance of the
overall surface transportation system.
This includes the assessment of system
performance based on the collective
experience of travelers within the
system and the ability of the system to
efficiently transport people and goods.
Measures of interest at the system level
include:
• System Delay is travel time in
excess of some subjective minimum
travel time, or the trip-weighted average
delay for corridor, region, or system.
• System Travel Time Reliability
represented by the Planning Time Index
which is the ratio of the 95th percentile
travel time to the travel time under zerodelay conditions, by origin/destination
pair, by time period, weighted by trip
volume.
• System Throughput is intended to
quantify the total number of people and
goods transported reliably through the
system over a period of peak
transportation demand. While there are
well established point measures, there is
no consensus on a system-wide
measure; therefore, innovative ideas for
system-wide measures are sought.
Trip-based travel time will likely be a
key data element required for all of
these measures of interest.
Traffic Measures. Traffic measures of
interest characterize performance in a
range of conditions, from key
bottlenecks, to specific facilities, in
freeway/arterial corridors, and in
subnetworks (e.g., an arterial grid or
freeway network). Both real-time and
non real-time measures are sought,
including:
• Congested Hours.
• Delay.
• Travel Time Reliability, including
the Travel Time Index and the Planning
Time Index
• Throughput.
• Speed.
While measures based on road
segment are of interest, trip-based
measures are of particular interest since
PO 00000
Frm 00136
Fmt 4703
Sfmt 4703
such information cannot be easily
collected today.
Transit Measures. Real-time and non
real-time measures are sought for
transit, including measures that apply to
fixed-route bus, paratransit, and rail
systems:
• Ridership.
• Mode share.
• Passenger throughput.
• Travel time/speed.
• Travel time variability.
• Schedule/headway adherence.
• Delay.
• Station/stop dwell time.
• Miles between transit vehicle
failures.
• Revenue miles per vehicle.
• Revenue hours per vehicle.
• Passengers per revenue vehiclemile.
• Passenger wait time for pickup.
• Passenger and driver no shows.
• Cost per passenger trip.
• Cost per passenger mile.
Freight Measures. Freight and goods
movement measures include:
• Planning time index and travel time
variance, as described under Traffic
Measures, but measured specifically for
freight trips.
• Point to point travel times on
selected freight-significant routes.
• Hours of delay per 1,000 vehicle
miles on selected freight-significant
routes.
• Number of bobtail truck trips (i.e.,
empty truck without a load).
• Truck travel time between origin
and destination.
• Truck emissions.
• Idle time at terminals.
Other Measures. Other measures of
interest include:
• Accessibility or livability measures
on a region-wide basis that may include
metrics such as the percentage of
population with total commute times
less than a set parameter, both by travel
mode and overall. Comments and input
are sought for appropriate measures.
• Environmental measures, such as
fuel use per passenger mile or ton-mile
of freight and greenhouse gas emissions
per passenger mile or ton-mile of
freight.
• Pavement conditions such as snow
or ice cover, slippery conditions, surface
roughness, or pothole detection.
• Weather-related transportation
management such as time to restore to
bare pavement, or time to return to preevent travel speeds after a weather
event.
Summary of Questions
A summary of the specific questions
posed in this notice follows. Responders
are reminded that feedback or
E:\FR\FM\09AUN1.SGM
09AUN1
sroberts on DSKD5P82C1PROD with NOTICES
Federal Register / Vol. 75, No. 152 / Monday, August 9, 2010 / Notices
comments on any aspect of this notice
is welcomed from all interested public,
private, and academic entities. While all
feedback is welcomed, the DOT is
particularly interested in feedback on
the following questions. Respondents
may respond, to some, all, or none of
these specific questions.
1. Based on the nature of the
performance measurement
demonstration(s), DOT believes that a
multimodal cooperative effort involving
both private sector and public sector
organizations will be required. The DOT
currently envisions awarding one or
more contracts to private sector
organization(s) as the lead
organization(s) in partnership with
public transportation agencies and other
entities appropriate to develop and
conduct the demonstration(s). An
alternative would be to conduct a
competitive grant program and award
one or more grants to public sector
organization(s) as the lead(s)
organization, engaging and involving
other entities as appropriate. Academic
institutions are welcomed as team
members; however, DOT does not
envision an academic institution serving
as the lead. Feedback is requested on
these procurement options and issues
including the challenges in forming the
teams as either a lead organization or as
a partner or other participant. What
forms or demonstrations of commitment
by the participants are reasonable and
appropriate requirements of
respondents to a solicitation for the
performance measurement
demonstration program?
2. The DOT envisions the
demonstration(s) awarded and
commencing in early 2011, with the
demonstration’s(s’) applications
beginning operations approximately 6
months of preparation and
development. The operational period,
results analysis, and publication of final
results are anticipated to occur over a
period that does not exceed 18 months.
Is this schedule too cautious, too
ambitious, or about right?
3. Are the identified performance
metrics the right ones to focus on? Are
there metrics or applications that you
would add or delete?
4. The goals of this near-term dynamic
mobility demonstration program are to
demonstrate the use of IntelliDriveSM to
improve the collection of performance
measurement information, and to
demonstrate the use of this information
to support performance-based
management, e.g., through the use of
decision support tools. To what extent
can the real-time or near real-time
collection of performance measures be
demonstrated, and to what extent can
VerDate Mar<15>2010
17:01 Aug 06, 2010
Jkt 220001
real-time or near real-time performancebased management applications or tools
be demonstrated?
5. There are important advantages to
conducting a single demonstration,
including concentration of resources
and funding, ease of management, and
demonstration of integrated applications
running in a common environment. At
the same time, the breadth of envisioned
applications and the desire for a diverse
operating environment argue for
conducting a small number of smaller
demonstrations. Is it feasible to address
a majority (if not all) of the goals and
environments in a single demonstration
project? Can multiple meaningful,
smaller demonstrations be conducted if
the funding per demonstration is
$1,000,000 or less?
6. It is the intent to provide open
access to the data collected as part of
this demonstration through the
IntelliDriveSM Data Capture and
Management program.
a. Do you see value in broadly sharing
these data with other researchers?
b. Will such data sharing inhibit
participation in the demonstration? If
so, what mitigation actions do you
recommend to encourage participation?
7. To the greatest extent possible, it is
the intent of the Dynamic Mobility
Applications Program to make
algorithms and source code associated
with new applications or applications
enhancements funded as a part of these
demonstrations to be made freely
available under open source agreements.
a. Do you see value in making
algorithms and application source code
funded by this demonstration program
broadly available?
b. Will an open source focus inhibit
participation in the demonstration? If
so, what mitigation actions do you
recommend to encourage participation?
Issued on: August 2, 2010.
Victor M. Mendez,
Administrator.
[FR Doc. 2010–19534 Filed 8–6–10; 8:45 am]
BILLING CODE 4910–22–P
DEPARTMENT OF TRANSPORTATION
Federal Aviation Administration
Notice of Intent to Rule on Request to
Release Airport Property at the Dubois
Regional Airport, Reynoldsville,
Pennsylvania
Federal Aviation
Administration (FAA), DOT.
ACTION: Notice of request to release
airport property.
AGENCY:
PO 00000
Frm 00137
Fmt 4703
Sfmt 4703
47891
The FAA proposes to rule and
invite public comment on the release of
land at the Dubois Regional Airport,
Reynoldsville, Pennsylvania under the
provisions of Section 47125(a) of Title
49 United States Code (U.S.C.).
DATES: Comments must be received on
or before September 8, 2010.
ADDRESSES: Comments on this
application may be mailed or delivered
to the following address:
Robert W. Shaffer, Manager, Dubois
Regional Airport, 377 Aviation Way,
Reynoldsville, PA 15851.
and at the FAA Harrisburg Airports
District Office:
Lori K. Pagnanelli, Manager, Harrisburg
Airports District Office, 3905
Hartzdale Dr., Suite 508, Camp Hill,
PA 17011.
FOR FURTHER INFORMATION CONTACT: Lori
Ledebohm, Community Planner,
Harrisburg Airports District Office
location listed above.
The request to release property may
be reviewed in person at this same
location.
SUMMARY:
The FAA
invites public comment on the request
to release property at the Dubois
Regional Airport under the provisions of
Section 47125(a) of Title 49 U.S.C. On
July 30, 2010, the FAA determined that
the request to release property at the
Dubois Regional Airport submitted by
the Clearfield-Jefferson Counties
Regional Airport Authority (Authority)
met the procedural requirements.
The following is a brief overview of
the request:
The Authority requests the release of
real property totaling 0.22 acre, of nonaeronautical airport property to Joseph
and Rosemary Barber. Also, Joseph and
Rosemary Barber desire to transfer real
property totaling 0.02 acre to the
Authority. The land was originally
purchased with Federal funds in 1958,
C.A.A Project 9–36–037–5801. The
purpose for the change is to transfer
land that was airport property but was
used as Right-Of-Way (ROW) for State
Route (SR) 830. SR 830 was relocated
and one half of the ROW width was
turned back to the Authority and the
other half was turned back to Joseph
and Rosemary Barber. The ROW
continues to be needed by Joseph and
Rosemary Barber to access SR 830 from
their property. Therefore, the Authority
desires to convey their half of the former
ROW to Joseph and Rosemary Barber.
Additionally, Joseph and Rosemary
Barber wish to convey the small portion
of land they obtained when SR 830 was
relocated, back to the Authority. The
property is located on the north-west
SUPPLEMENTARY INFORMATION:
E:\FR\FM\09AUN1.SGM
09AUN1
Agencies
[Federal Register Volume 75, Number 152 (Monday, August 9, 2010)]
[Notices]
[Pages 47888-47891]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: 2010-19534]
-----------------------------------------------------------------------
DEPARTMENT OF TRANSPORTATION
Federal Highway Administration
IntelliDrive\SM\ \1\ Performance Measurement and Performance-
Based Management Demonstrations; Request for Information
---------------------------------------------------------------------------
\1\ IntelliDrive is a service mark of the U.S. Department of
Transportation.
---------------------------------------------------------------------------
AGENCY: Federal Highway Administration (FHWA), DOT.
ACTION: Notice.
-----------------------------------------------------------------------
SUMMARY: This notice is a Request for Information (RFI) and comments
that will be used to help refine the plans for one or more
demonstrations focused on the use of IntelliDrive\SM\ data sources for
performance measurement and performance-based management. The FHWA is
issuing this RFI in collaboration with and on behalf of other agencies
within the DOT, specifically the Federal Transit Administration, the
Federal Motor Carrier Safety Administration, and the Research and
Innovative Technology Administration. Feedback and comments on any
aspect of the RFI are welcomed from all interested public, private, and
academic entities. While all feedback is welcomed, DOT is particularly
interested in feedback on the questions provided in the last section of
this RFI.
RFI Guidelines: Responses to this RFI should be submitted by 11:59
p.m. Eastern Time on September 8, 2010. Responses to this RFI should be
delivered electronically as an e-mail or as an attachment to an e-mail
sent to DMAdemo@dot.gov.
Responses to this notice are not offers and cannot be accepted by
the Government to form a binding contract or issue a grant. Information
obtained as a result of this RFI may be used by the government for
program planning on a non-attribution basis. If you wish to submit any
information under a claim of confidentiality, you should submit via e-
mail to the address given below under FOR FURTHER INFORMATION CONTACT,
your complete submission, including the information you claim to be
confidential commercial information. When you submit information
containing information identified as confidential commercial
information, you should include a cover letter setting forth the
reasons you believe the information qualifies as ``confidential
commercial information.'' (49 CFR 7.13(c)(4) and 7.17) If we receive a
request to examine or copy this information, we treat it as any other
request under the Freedom of Information Act (5 U.S.C. 552), but we
[[Page 47889]]
will process the request in accordance with the procedures found in 49
CFR 7.17.
FOR FURTHER INFORMATION CONTACT: For questions about the program
discussed herein, contact Mr. Robert Rupert, Transportation Information
Management Team, FHWA Office of Operations, (202) 366-2194,
robert.rupert@dot.gov. For legal questions, interpretations and
counsel, please contact Sheryl Williams, Office of the Chief Counsel,
(202) 366-0618, sheryl.williams@dot.gov, 1200 New Jersey Avenue, SE.,
Washington, DC 20590. Office hours for the FHWA are from 7:45 a.m. to
4:15 p.m., e.t., Monday through Friday, except Federal holidays.
Additional information about the IntelliDrive\SM\ initiative is at
https://www.its.dot.gov/intellidrive/.
SUPPLEMENTARY INFORMATION: The DOT IntelliDrive\SM\ program is a
multimodal initiative that aims to enable safe, interoperable networked
wireless communications among vehicles, the infrastructure, and
travelers' personal communications devices. IntelliDrive\SM\ research
is being sponsored by the DOT and others to leverage the potentially
transformative capabilities of wireless technology to make surface
transportation safer, smarter, and greener. One component of this
initiative is the Dynamic Mobility Applications program. This program
seeks to identify, develop, and deploy applications that leverage the
full potential of connected vehicles, travelers, and infrastructure in
order to enhance current operational practices and transform future
surface transportation systems management.
The Dynamic Mobility Applications program will include one or more
field demonstrations of applications that integrate IntelliDrive\SM\
data to support multi-modal performance measurement and performance-
based management. The applications are envisioned to include support
for both real-time and non real-time decisionmaking and operations. The
intent is to conduct one or more demonstrations that include mobility
and productivity performance measurement as a cornerstone element of
the demonstration plan. Demonstrations selected in this effort will
focus on the data collection and processing to produce performance
metrics in one, or preferably more, of the following areas:
Productivity.
Mobility, including impact on freight movements.
Livability/Accessibility (accessibility is defined as the
ability to reach goods, services and activities).
Environment/fuel use.
Pavement conditions (e.g., snow or ice cover, surface
roughness, pothole detection).
The DOT seeks comments and innovative ideas from the public sector,
private sector, and academic communities concerning the demonstration
program described in this RFI. While comments are welcomed on any area
of the RFI, the DOT is particularly interested in responses to the
questions listed at the end of this RFI.
Dynamic Mobility Applications Demonstration Program Description
This program envisions one or more demonstrations beginning in
2011. The intent of these near-term demonstrations is to begin work
with private companies, States, transit agencies, and commercial
vehicle operators or freight shippers to develop applications utilizing
data captured from multiple sources (e.g., vehicles, travelers,
infrastructure) across all elements of the surface transportation
system (i.e., transit, freeway, arterial, parking facilities and
tollways) to support performance measurement and performance-based
management. This demonstration effort aims to leverage existing
operational capabilities or to spur innovation among early adopters of
innovative performance measurement and mobility applications. The
limited number of resources and the short lead time for this effort
precludes the large-scale deployment of new in-vehicle or roadside
technologies. Therefore, unless a site already has a deployed Dedicated
Short Range Communications (DSRC) infrastructure, it is anticipated
that any required mobile communications will use existing commercial
wireless services.
The performance measurement demonstration(s) should address the
following research questions:
Can system productivity and traveler mobility be
characterized in innovative and meaningful new ways by integrating
emerging data sources (i.e., vehicles and mobile devices as data
sources)?
To what extent can IntelliDrive\SM\ be used to support
real-time performance-based management of roadways, transit systems,
and freight carriers?
What are the institutional, legal, and technical issues
that may help or hinder the use of IntelliDrive\SM\ to improve
performance-based management?
What wireless and other communications media can be
combined to make large-scale data capture and mobility applications
cost effective?
How can diverse data sources be efficiently integrated and
utilized?
Can customer satisfaction with demonstrated applications
be identified?
Proposed Performance Measurement Demonstration Program Requirements
All candidate sites and prospective partners will be required to
address the following fundamental aspects of the Performance
Measurement Demonstration vision, including:
Performance measurement. Well-defined, quantitative
performance measures and a clear strategy for evaluating these impacts
must be a part of any candidate demonstration. Preliminary thinking on
possible measures of interest is provided later in this RFI. More
specific guidance will be included in the solicitation. System
productivity measures will quantify the efficient movement of travelers
and goods under periods of peak demand. Traveler mobility measures will
quantify travel delay and improved travel reliability. This
specifically includes mobility or accessibility assessments for
travelers who utilize transit as a component of end-to-end trip-making.
Other measures will characterize the reliability of freight/goods
movement within the system. Additional performance areas such as
accessibility, environment/fuel use, and pavement conditions should
also be considered.
Multi-source data capture. Demonstrations should feature
frequent capture and systematic integration of data from a broad range
of sources. Desired sources should include multiple types of
infrastructure-based sensors, transit vehicle systems (bus and rail), a
full range of vehicle types acting as mobile probes (including freight
carriers and transit vehicles), and travelers moving between modes as
they complete trips.
Innovative decision support applications. These
applications should exploit the value of integrated multisource
performance data. Applications selected for demonstration should fully
and cost effectively leverage captured data to provide innovative
services to multiple users. The primary focus is on providing decision
support tools (both real-time and non real-time) to traffic managers
and transit operators. As a secondary objective, demonstrations may
also provide mobility applications targeted at system users, including
freight carriers and multimodal travelers. To the greatest extent
possible, it is the
[[Page 47890]]
intent of the Dynamic Mobility Applications Program to make algorithms
and source code associated with new applications or application
enhancements funded as a part of these demonstrations to be made freely
available under open source agreements.
Critical mass demonstration. Demonstrations should be
scoped to be conducted in operational multifacility, multimodal
transportation networks spanning urban areas or in interurban
corridors. Demonstrations set in laboratory or closed facility test
environments are precluded from consideration. Preference will be shown
to demonstration proposals combining data drawn from large
contemporaneous populations of vehicles or travelers with mobile
devices participating as mobile probes concurrently with fixed
infrastructure-based sensor systems.
Complex Environment. System performance in each
demonstration will be characterized in complex networks containing
multiple facility types (e.g., freeway, arterial, parking, transit bus,
and rail), considering both the quantity and quality of travelers and
goods movement supported by the system in end-to-end trip-making across
multiple facilities and modes.
No driver distraction effects. Demonstrated applications
will involve collection of information from moving vehicles. The
information collection must be conducted in a manner that will not
distract drivers or compromise safety. This demonstration will not
include applications that require driver interaction while a vehicle is
in motion. See https://www.distraction.gov for additional information on
distracted driving.
Data sharing. A required element of the demonstration(s)
is the systematic collection of data (from both mobile and fixed
sources). It is the intent to provide open access to these data through
the IntelliDrive\SM\ Data Capture and Management program. These data
may be made available as the demonstration is conducted, or made
available shortly after the conclusion of the demonstration. These data
are intended to support research activity and mobility application
development in later phases of the Dynamic Mobility Applications
program. If necessary, data may be transformed or aggregated to protect
privacy, and the Government will consider allowing transformation or
aggregation to protect intellectual property rights.
Independent Evaluation. Demonstrations must contain an
impacts evaluation and target user satisfaction assessment for each
tested application. An independent evaluation contractor will assist in
planning and executing an evaluation plan and will author a national
evaluation report.
Use of Standards. Demonstration projects shall make
appropriate use of ITS standards for information exchange.
The demonstration(s) should collect the data and implement
applications that can calculate the following types of performance
metrics and, where appropriate, include applications for acting on the
real-time measurement information.
Mode-Independent Overall System Measures. A key element of the
demonstration will be the characterization and quantitative measurement
of the performance of the overall surface transportation system. This
includes the assessment of system performance based on the collective
experience of travelers within the system and the ability of the system
to efficiently transport people and goods. Measures of interest at the
system level include:
System Delay is travel time in excess of some subjective
minimum travel time, or the trip-weighted average delay for corridor,
region, or system.
System Travel Time Reliability represented by the Planning
Time Index which is the ratio of the 95th percentile travel time to the
travel time under zero-delay conditions, by origin/destination pair, by
time period, weighted by trip volume.
System Throughput is intended to quantify the total number
of people and goods transported reliably through the system over a
period of peak transportation demand. While there are well established
point measures, there is no consensus on a system-wide measure;
therefore, innovative ideas for system-wide measures are sought.
Trip-based travel time will likely be a key data element required
for all of these measures of interest.
Traffic Measures. Traffic measures of interest characterize
performance in a range of conditions, from key bottlenecks, to specific
facilities, in freeway/arterial corridors, and in subnetworks (e.g., an
arterial grid or freeway network). Both real-time and non real-time
measures are sought, including:
Congested Hours.
Delay.
Travel Time Reliability, including the Travel Time Index
and the Planning Time Index
Throughput.
Speed.
While measures based on road segment are of interest, trip-based
measures are of particular interest since such information cannot be
easily collected today.
Transit Measures. Real-time and non real-time measures are sought
for transit, including measures that apply to fixed-route bus,
paratransit, and rail systems:
Ridership.
Mode share.
Passenger throughput.
Travel time/speed.
Travel time variability.
Schedule/headway adherence.
Delay.
Station/stop dwell time.
Miles between transit vehicle failures.
Revenue miles per vehicle.
Revenue hours per vehicle.
Passengers per revenue vehicle-mile.
Passenger wait time for pickup.
Passenger and driver no shows.
Cost per passenger trip.
Cost per passenger mile.
Freight Measures. Freight and goods movement measures include:
Planning time index and travel time variance, as described
under Traffic Measures, but measured specifically for freight trips.
Point to point travel times on selected freight-
significant routes.
Hours of delay per 1,000 vehicle miles on selected
freight-significant routes.
Number of bobtail truck trips (i.e., empty truck without a
load).
Truck travel time between origin and destination.
Truck emissions.
Idle time at terminals.
Other Measures. Other measures of interest include:
Accessibility or livability measures on a region-wide
basis that may include metrics such as the percentage of population
with total commute times less than a set parameter, both by travel mode
and overall. Comments and input are sought for appropriate measures.
Environmental measures, such as fuel use per passenger
mile or ton-mile of freight and greenhouse gas emissions per passenger
mile or ton-mile of freight.
Pavement conditions such as snow or ice cover, slippery
conditions, surface roughness, or pothole detection.
Weather-related transportation management such as time to
restore to bare pavement, or time to return to pre-event travel speeds
after a weather event.
Summary of Questions
A summary of the specific questions posed in this notice follows.
Responders are reminded that feedback or
[[Page 47891]]
comments on any aspect of this notice is welcomed from all interested
public, private, and academic entities. While all feedback is welcomed,
the DOT is particularly interested in feedback on the following
questions. Respondents may respond, to some, all, or none of these
specific questions.
1. Based on the nature of the performance measurement
demonstration(s), DOT believes that a multimodal cooperative effort
involving both private sector and public sector organizations will be
required. The DOT currently envisions awarding one or more contracts to
private sector organization(s) as the lead organization(s) in
partnership with public transportation agencies and other entities
appropriate to develop and conduct the demonstration(s). An alternative
would be to conduct a competitive grant program and award one or more
grants to public sector organization(s) as the lead(s) organization,
engaging and involving other entities as appropriate. Academic
institutions are welcomed as team members; however, DOT does not
envision an academic institution serving as the lead. Feedback is
requested on these procurement options and issues including the
challenges in forming the teams as either a lead organization or as a
partner or other participant. What forms or demonstrations of
commitment by the participants are reasonable and appropriate
requirements of respondents to a solicitation for the performance
measurement demonstration program?
2. The DOT envisions the demonstration(s) awarded and commencing in
early 2011, with the demonstration's(s') applications beginning
operations approximately 6 months of preparation and development. The
operational period, results analysis, and publication of final results
are anticipated to occur over a period that does not exceed 18 months.
Is this schedule too cautious, too ambitious, or about right?
3. Are the identified performance metrics the right ones to focus
on? Are there metrics or applications that you would add or delete?
4. The goals of this near-term dynamic mobility demonstration
program are to demonstrate the use of IntelliDrive\SM\ to improve the
collection of performance measurement information, and to demonstrate
the use of this information to support performance-based management,
e.g., through the use of decision support tools. To what extent can the
real-time or near real-time collection of performance measures be
demonstrated, and to what extent can real-time or near real-time
performance-based management applications or tools be demonstrated?
5. There are important advantages to conducting a single
demonstration, including concentration of resources and funding, ease
of management, and demonstration of integrated applications running in
a common environment. At the same time, the breadth of envisioned
applications and the desire for a diverse operating environment argue
for conducting a small number of smaller demonstrations. Is it feasible
to address a majority (if not all) of the goals and environments in a
single demonstration project? Can multiple meaningful, smaller
demonstrations be conducted if the funding per demonstration is
$1,000,000 or less?
6. It is the intent to provide open access to the data collected as
part of this demonstration through the IntelliDrive\SM\ Data Capture
and Management program.
a. Do you see value in broadly sharing these data with other
researchers?
b. Will such data sharing inhibit participation in the
demonstration? If so, what mitigation actions do you recommend to
encourage participation?
7. To the greatest extent possible, it is the intent of the Dynamic
Mobility Applications Program to make algorithms and source code
associated with new applications or applications enhancements funded as
a part of these demonstrations to be made freely available under open
source agreements.
a. Do you see value in making algorithms and application source
code funded by this demonstration program broadly available?
b. Will an open source focus inhibit participation in the
demonstration? If so, what mitigation actions do you recommend to
encourage participation?
Issued on: August 2, 2010.
Victor M. Mendez,
Administrator.
[FR Doc. 2010-19534 Filed 8-6-10; 8:45 am]
BILLING CODE 4910-22-P