Regional Architecture Logo
 

Send Your Comments

E-Mail

Basic Information Broadcast Equipment Package

Architecture Geographic Scope

Description:

This Equipment package provides the capabilities to collect, process, store, bill, and disseminate traveler information including traveler, transit, ridematching, traffic, and parking information. The traveler information shall include maintaining a database of local area services available to travelers with up-to-the-minute information and providing an interactive connectivity between, sponsors, and providers of services. The transit information shall include the latest available information on transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence. The traffic information shall include latest available information on traffic and highway conditions, and current situation information in real-time including incidents, road construction, recommended routes, current speeds on specific routes, current parking conditions in key areas, schedules for any current or soon to start events, and current weather situations. This Equipment package shall also provide users with real-time travel related information while they are traveling, and disseminate to assist the travelers in making decisions about transfers and modification of trips. These capabilities shall be provided using equipment such as a fixed facility with a communications system such as a data Subcarrier multiplexing device.

 

Included in:

TxDOT 511 System
TxDOT Highway Conditions Reporting System
TxDOT Lubbock District TMC
TxDOT Lubbock District Website

Processes:

1.1.4.5Provide Media System Traffic Data Interface
1.1.4.6Provide Traffic Data Retrieval Interface
4.1.8Provide Transit Operations Data Distribution Interface
6.1.1Provide Trip Planning Information to Traveler
6.2.1.1Collect Traffic Data for Advisory Messages
6.2.1.3Collect Transit Data for Advisory Messages
6.2.1.4Provide Traffic and Transit Broadcast Messages
6.2.1.5Provide ISP Operator Broadcast Parameters Interface
6.2.4Collect Yellow Pages Data
6.5.1Collect and Update Traveler Information
7.4.2Collect Price Data for ITS Use
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.1PRE-TRIP TRAVEL INFORMATION
1.1.0ITS shall include a Pre-Trip Travel Information (PTTI) capability to assist travelers in making mode choices, travel time estimates, and route decisions prior to trip departure. It consists of four major functions, which are, (1) Available Services Information, (2) Current Situation Information, (3) Trip Planning Service, and (4) User Access. Information is integrated from various transportation modes and presented to the user for decision making.
1.1.1PTTI shall provide travelers with Available Services Information on travel, for their use.
1.1.1.1PTTI shall provide users with available services information that is timely.
1.1.1.1.1PTTI shall provide users the latest available information on transit routes.
1.1.1.1.2PTTI shall provide users the latest available information on transit schedules.
1.1.1.1.3PTTI shall provide users with the latest available schedule adherence information.
1.1.1.1.4PTTI shall provide users the latest available information on transit transfer options.
1.1.1.1.5PTTI shall provide users the latest available information on transit fares.
1.1.1.1.6PTTI shall provide users information on accessing ridematching services.
1.1.2PTTI shall provide the capability for users to access the Current Situation Information on transportation systems.
1.1.2.1PTTI shall provide the latest available information on the current status of transportation services.
1.1.2.1.1Real-time information provided by PTTI shall include the current condition of any incidents, including rural incidents such as high winds, extreme temperature, and falling rocks.
1.1.2.1.2Real-time information provided by PTTI shall include the current status of any accidents or incidents.
1.1.2.1.3Real-time information provided by PTTI shall include the current condition of any road construction.
1.1.2.1.4Real-time information provided by PTTI shall include any currently recommended alternate routes.
1.1.2.1.5Real-time information provided by PTTI shall include the current speeds on specific routes.
1.1.2.1.6Real-time information provided by PTTI shall include current parking conditions in key areas.
1.1.2.1.7Real-time information provided by PTTI shall include the schedules for any current or soon to start events.
1.1.2.1.8Real-time information provided by PTTI shall include the current weather situation.
1.1.3PTTI shall include a Trip Planning Service.
1.1.3.1PTTI trip planning service shall provide the users with information needed for planning an upcoming trip.
1.1.3.1.1Based on user specified parameters PTTI shall provide users with a calculated itinerary.
1.1.3.1.2Based on user specified parameters PTTI shall provide users with transportation mode choices.
1.1.3.1.3Based on user specified parameters PTTI shall provide users with real-time travel conditions for time of inquiry and estimated conditions for estimated time of travel.
1.1.3.1.4Based on user specified parameters PTTI shall provide users with one or more alternate itineraries in addition to the primary calculated itinerary.
1.1.3.2PTTI shall provide the capability for users to specify transportation parameters that are unique to their individual needs.
1.1.3.3In addition to the user specified parameters PTTI shall use additional factors when planning trips.
1.1.3.3.1PTTI shall consider current travel conditions when calculating a trip itinerary.
1.1.3.3.2PTTI shall consider predicted travel conditions when calculating a trip itinerary.
1.1.4PTTI shall provide the capability for User Access.
1.1.4.1PTTI shall provide the capability for users to access the system from multiple distributed locations.
1.1.4.1.1PTTI shall provide the capability for users to access the system from their homes.
1.1.4.1.2PTTI shall provide the capability for users to access the system from their place of work.
1.1.4.1.3PTTI shall provide the capability for users to access the system from major trip generation sites.
1.1.4.1.4PTTI shall provide the capability for users to access the system from personal portable devices.
1.2EN-ROUTE DRIVER INFORMATION
1.2.0ITS shall include an En-Route Driver Information (DI) function. Driver Information provides vehicle drivers with information, while en-route, which will allow alternative routes to be chosen for their destination. Driver Information consists of two major functions, which are, (1) Driver Advisory and (2) In-vehicle Signing. The potential decrease in traffic may also provide benefits in highway safety, reduced air pollution, and decreased congestion.
1.2.2DI shall include a Driver Advisory function, which shall be implemented in two phases with first a short term capability and later a long term capability.
1.2.2.1The short term DI driver information capability shall include the ability to provide information to travelers within the limited area of deployment.
1.2.2.1.1DI shall include the capability to provide travelers with accurate information concerning available travel options and their state of operational availability.
1.2.2.1.2DI shall provide information to travelers required for them to avoid areas of congestion.
1.2.2.1.2.1DI shall provide information needed for travelers to select transportation modes that allow them to avoid congestion.
1.2.2.1.3DI shall provide the capability for users to receive travel information in their vehicles.
1.3ROUTE GUIDANCE
1.3.0ITS shall include a Route Guidance (RG) function. Route Guidance will provide travelers with directions to selected destinations. Four functions are provided, which are, (1) Provide Directions, (2) Static Mode, (3) Real-Time Mode, and (4) User Interface.
1.3.1RG shall include the capability to Provide Directions to travelers.
1.3.1.2The Provide Directions function shall issue directions to travelers based on information about current conditions of transportation systems.
1.3.1.2.1Current transportation system conditions upon which directions to travelers is based shall include, but not be limited to, the following:
1.3.1.2.1(d)Events taking place that influence travel routes.
1.3.1.2.1(d).1Street closures.
1.3.1.2.1(d).2Pedestrian events.
1.3.1.2.1(d).3No pedestrian zones.
1.4RIDE MATCHING AND RESERVATION
1.4.0ITS shall include a Ride Matching and Reservation (RMR) function. Ride Matching and Reservation will provide travel users with information on rideshare providers. Three major functions are provided, which are, (1) Rider Request, (2) Transportation Provider Services, and (3) Information Processing. This will also include a billing service to the providers.
1.4.1RMR shall include a Rider Request capability.
1.4.1.3Rider Request shall provide the traveler with the available ridesharing options, based on the traveler's request and specified itinerary.
1.4.2RMR shall include a Transportation Provider Service function.
1.4.2.3Transportation Provider Services shall automatically generate needed reports and financial documentation.
1.4.3RMR shall include an Information Processing function.
1.4.3.1Information Processing shall quickly match preferences and demands of requesting travelers with the services available from providers.
1.4.3.3Information Processing shall link together the services available from all travel modes including, but not limited to, the following:
1.4.3.3(a)Bus.
1.4.3.3(b)Rail.
1.4.3.3(c)Vanpools.
1.4.3.3(d)Express bus.
1.4.3.3(e)Commercial providers.
1.4.3.3(f)Specialized service.
1.4.3.5Information Processing shall provide the capability to gather market information to assist in the planning of service improvements.
1.4.3.6Information Processing shall provide the capability to gather market information to assist in operations.
1.5TRAVELER SERVICES INFORMATION
1.5.0ITS shall include a Traveler Services Information (TSI) function. Traveler Services Information provides travelers with service and facility data for the purpose of assisting prior to embarking on a trip or after the traveler is underway. The functions which are included in this capability are Information Receipt and Information Access. This will provide the traveler with a "yellow pages" type of capability.
1.5.1TSI shall include an Information Receipt function for the collection of information to be provided to travelers.
1.5.1.1Information Receipt shall provide and maintain a database of local area services available to travelers.
1.5.1.2Information Receipt provides the capability to acquire current information relating to traveler services available in the local area.
1.5.1.2.1Information Receipt shall acquire information on the condition of local traveler services.
1.5.1.2.2Information Receipt shall acquire information on the status of local traveler services.
1.5.1.2.3Information Receipt shall acquire information on the availability of local traveler services.
1.5.1.2.4Information Receipt shall acquire information on the availability of local motorist services.
1.5.1.2.5Information Receipt shall acquire information on the availability of local tourist services.
1.5.1.3Information Receipt shall be capable of being integrated with Pre-Trip Planning information.
1.5.1.4Information Receipt shall provide the capability to support the financial transactions required for travelers to be billed for the purchase of activity tickets and room reservations.
1.5.1.5Information Receipt shall include the capability to have interactive connectivity between users, sponsors and providers of services.
1.5.2TSI shall include an Information Access function that allows travelers to access the available information.
1.5.2.1Information Access shall provide the capability for travelers to request and receive general information about the local area.
1.5.2.2Information Access shall provide the capability for travelers and centers to request and receive information about the location of facilities and the quality of specific services provided in an area to include but, not be limited to, the following:
1.5.2.2(b)Food information.
1.5.2.2(d)Hours of operation information.
1.5.2.2(e)Tourist activities information.
1.5.2.2(f)Daily or special events information.
1.5.2.2(g)Local shelter/medical facility availability information including level of service provided.
1.5.2.2(h)Nearest gas station information.
1.5.2.3Information Access shall provide the capability for travelers to request specific actions of area service providers to include, but not be limited to:
1.5.2.5Information Access shall provide the capability for travelers to access the TSI information via any of, but not limited to, the following methods:
1.5.2.5(d)Computers in the office.
1.5.2.5(g)Personal portable devices.
1.6TRAFFIC CONTROL
1.6.0ITS shall include a Traffic Control (TC) function. Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions are provided, which are, (1) Traffic Flow Optimization, (2) Traffic Surveillance, (3) Control, and (4) Provide Information. This will also include control of network signal systems with eventual integration of freeway control.
1.6.3TC shall include a Device Control function.
1.6.3.4Device Control shall communicate control data to the following devices.
1.6.3.4.1Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.4Device Control shall provide traffic control information to other elements of the ITS, including but not limited to the following:
1.6.4(b)Trip planning.
1.6.4(c)Routing systems.
1.7INCIDENT MANAGEMENT
1.7.0ITS shall include an Incident Management (IM) function. Incident Management will identify incidents, formulate response actions, and support initiation and ongoing coordination of those response actions. Four major functions are provided, which are, (1) Incidents Identification, (2) Response Formulation, (3) Response Implementation, and (4) Predict Hazardous Conditions.
1.7.1Incident Management shall provide an Incident Identification function to identify incidents.
1.7.1.1The Incident Identification function shall include the capability to identify predicted incidents.
1.7.1.1.1The Incident Identification function shall use information from the following types of sources, where available, to identify predicted incidents:
1.7.1.1.1(e)Weather information sources.
1.7.1.1.1(f)Transportation providers.
1.7.1.1.1(g)Sponsors of special events.
1.8TRAVEL DEMAND MANAGEMENT
1.8.1TDM shall include a communications function.
1.8.1.2The communications function shall include the capability to send information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action:
1.8.1.2(d)Employment sites.
1.8.1.2(e)Toll facilities.
1.8.1.3TDM shall provide the capability to receive information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action:
1.8.1.3(a)Parking facilities.
1.8.1.3(e)Toll facilities.
1.8.1.3(f)Travel (and traveler) information facilities.
1.8.1.6The communications function shall include the capability for two-way communications with other ITS user services including, but not limited to, the following:
1.8.1.6(a)Pre-Trip Planning.
1.8.2TDM shall include a processing function.
1.8.2.3Strategies developed by the processing function shall include the guidance for the operation of physical systems that:
1.8.2.3(c)Collect fees.
1.8.2.4The processing function shall provide the capability generate guidance for the pricing and control for locations of action that include, but are not limited to, the following:
1.8.2.4(a)Parking facilities.
1.8.2.4(f)Travel information facilities.
2.0PUBLIC TRANSPORTATION MANAGEMENT
2.1.0ITS shall include a Public Transportation Management (PTM) function.
2.1.1PTM shall include an Operation of Vehicles and Facilities (OVF) function that provides computer assisted control of the operation of vehicles and their associated facilities.
2.1.2PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations.
2.1.2.2The PSS shall include a Schedule Generation capability.
2.1.2.2.1The PSS Schedule Generation function shall collect data for schedule generation including, but not limited to, the following:
2.1.2.2.5The PSS Schedule Generation function shall provide the capability to automatically update the customer service operator system with the most current schedule and schedule adherence information.
2.2.0ITS shall include an En-Route Transit Information (TI) function. En-Route Transit Information provides travelers with real-time transit and high-occupancy vehicle information allowing travel alternatives to be chosen once the traveler is en-route. It consists of three major functions, which are, (1) Information Distribution, (2) Information Receipt, and (3) Information Processing. This capability integrates information from different transit modes and presents it to travelers for decision making.
2.2.1TI shall include an Information Distribution function that disseminates information to travelers.
2.2.1.1Information Distribution shall include an Information Network capability.
2.2.1.1.1The Information Network shall provide the capability to furnish users with real-time travel related information while they are traveling.
2.2.2TI shall include an Information Receipt function for acquiring that data that are used for generation of the En-Route Transit Information.
2.2.2.1Information Receipt shall provide the capability to be continuously updated with real-time information from each transit system within the local area of jurisdiction.
2.2.2.2Information Receipt shall provide the capability to be updated with information that is inclusive of all possible transportation modes within the local area of jurisdiction.
2.2.2.3Information Receipt shall provide the capability to be updated with information from all providers of transportation services in the local area of jurisdiction to include:
2.2.3TI shall include an Information Processing function for processing that data used for generation of the En-Route Transit Information.
2.2.3.1Information Processing shall include an information collection feature.
2.2.3.1.1Information collection shall acquire transit operations information to include, but not be limited to, the following type:
2.2.3.1.2Information collection shall acquire transit situation conditions to include, but not be limited to, the following type:
2.2.3.1.2(a)Actual road data.
2.2.3.1.2(b)Traffic data.
2.2.3.2Information Processing shall include an information integration feature.
2.2.3.2.1Information integration shall collect data, store it and maintain it on-line.
2.2.3.2.2Information integration shall collect data from traffic and transit systems including, but not limited to, the following:
2.2.3.2.2(a)Transit systems.
2.2.3.2.2(b)Traffic management services.
2.2.3.2.2(c)Rideshare programs.
2.3.0ITS shall include a Personalized Public Transit (PPT) function.
2.3.1The PPT shall include a Rider Request function.
2.3.1.2Rider Request shall provide the capability for an individual to specify a rider's special equipment or handling requirements.
2.4.0ITS shall include a Public Travel Security (PTS) function to create an environment of safety in public transportation.
2.4.3PTS shall include a Personal Sensors Items (PSI) function.
2.4.3.1PSI for ridematching shall include the capability for participants to be identified.
2.4.3.2PSI shall provide the capability for riders to use electronic payment to eliminate the need for passengers to carry cash and to reduce cash handling.
3.0ELECTRONIC PAYMENT
3.1ELECTRONIC PAYMENT SERVICES
3.1.2Electronic Payment shall include an Electronic Fare Collection (EFC) capability.
3.1.2.7EFC shall include the capability to collect the data required to determine accurate ridership levels.
3.1.4ITS shall include an Electronic Payment Services Integration (EPSI) feature.
3.1.4.3EPSI shall collect and provide usage data to develop pricing strategies that favor certain transportation modes or routes.
3.1.5ITS shall provide a Roadway Pricing (RP) capability.
3.1.5.1RP shall provide the capability to implement various road pricing policies.
3.1.5.1.1Road pricing policies capable of being implemented by RP shall include variable pricing.
3.1.5.2RP shall provide the capability to implement roadway pricing strategies, developed by other services, that alleviate congestion.
3.1.5.3RP shall provide the capability to implement roadway pricing, developed by other services, that can be used to influence mode selection.
7.0INFORMATION MANAGEMENT
7.1ARCHIVED DATA FUNCTION
7.1.0ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas.
7.1.3The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function.
7.1.3.1DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.8DIV shall be capable of importing ITS Vehicle and Traveler data to include:
7.1.3.1.8(e)Parking and roadway pricing change data.
7.1.3.1.8(g)Service requests
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 02-24-2005 using Ronald C. Ice and Associates Web Spinner Technology.