Module 22 - A312a
A312a: Understanding User Needs for Transportation Sensor Systems (TSS) Based on NTCIP 1209 Standard
HTML of the Student Supplement
(Note: This document has been converted from the Student Supplement to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)
(Extended Text Description: Large graphic cover page with dark blue background with the title in white letters “A312a: Understanding User Needs for Transportation Sensor Systems (TSS) Based on NTCIP 1209 Standard” At the middle left is the “Standards ITS Training” logo with a white box and letters in blue and green. The words “Student Supplement” and “RITA Intelligent Transportation Systems Joint Program Office” in white lettering are directly underneath the logo. Three light blue lines move diagonally across the middle of the blue background.)
A312a: Understanding User Needs for Transportation Sensor Systems (TSS) Based on NTCIP 1209 Standard
Table of Contents
Introduction/Purpose - 2
Strengths and Weaknesses of Commercially Available Sensor Technologies - 2
Federal Highway Administration (FHWA) 13 Vehicle Classifications - 5
Glossary - 6
Reference to Other Standards - 9
References - 9
Study Questions - 10
1. Introduction/Purpose
A312a: Understanding User Needs for Transportation Sensor Systems (TSS) Based on NTCIP 1209 Standard is the first of two modules of the Professional Capacity Building (PCB) program on using NTCIP communications with transportation sensor systems and/or devices. A312a provides participants with an understanding of the structure of the NTCIP 1209 v02 Standard. It identifies specific TSS user needs (features), and introduces the protocol requirements list (PRL) table, which is used to specify implementations of the standard. A312a is a prerequisite for module A312b Specifying Requirements for Transportation Sensor Systems (TSS) Based on NTCIP 1209 Standard.
2. Strengths and Weaknesses of Commercially Available Sensor Technologies
(From the FHWA Detector Handbook)
Technology |
Strengths |
Weaknesses |
---|---|---|
Inductive loop |
|
|
Magnetometer (two-axis fluxgate magnetometer) |
|
|
Magnetic (induction or search coil magnetometer) |
|
|
Microwave radar |
|
|
Active infrared (laser radar) |
|
|
Passive infrared |
|
|
Ultrasonic |
|
|
Acoustic |
|
|
Video image processor |
|
|
3. Federal Highway Administration (FHWA) 13 Vehicle Classifications
Class 1 - Motorcycles: All two- or three-wheeled motorized vehicles. Typical vehicles in this category have saddle type seats and are steered by handle bars rather than wheels. This category includes motorcycles, motor scooters, mopeds, motor-powered bicycles, and three-wheeled motorcycles.
Class 2 - Passenger Cars: All sedans, coupes, and station wagons manufactured primarily for the purpose of carrying passengers and including those passenger cars pulling recreational or other light trailers.
Class 3 - Other Two-Axle, Four-Tire, Single Unit Vehicles: All two-axle, four-tire vehicles other than passenger cars. Included in this classification are pickups, panels, vans, and other vehicles such as campers, motor homes, ambulances, hearses, carryalls, and minibuses. Other two-axle, four-tire single unit vehicles pulling recreational or other light trailers are included in this classification.
Class 4 - Buses: All vehicles manufactured as traditional passenger-carrying buses with two axles and six tires or three or more axles. This category includes only traditional buses (including school buses) functioning as passenger-carrying vehicles. Modified buses should be considered to be trucks and be appropriately classified.
Note: In reporting information on trucks, the following criteria should be used:
Class 5 - Two-Axle, Six-Tire, Single Unit Trucks: All vehicles on a single frame including trucks, camping and recreational vehicles, motor homes, etc., having two axles and dual rear wheels.
Class 6 - Three-axle Single unit Trucks: All vehicles on a single frame including trucks, camping and recreational vehicles, motor homes, etc., having three axles.
Class 7 - Four or More Axle Single Unit Trucks: All trucks on a single frame with four or more axles.
Class 8 - Four or Less Axle Single Trailer Trucks: All vehicles with four or less axles consisting of two units, one of which is a tractor or straight truck power unit.
Class 9 - Five-Axle Single Trailer Trucks: All five-axle vehicles consisting of two units, one of which is a tractor or straight truck power unit.
Class 10 - Six or More Axle Single Trailer Trucks: All vehicles with six or more axles consisting of two units, one of which is a tractor or straight truck power unit.
Class 11 - Five or Less Axle Multi-Trailer Trucks: All vehicles with five or less axles consisting of three or more units, one of which is a tractor or straight truck power unit.
Class 12 - Six-Axle Multi-Trailer Trucks: All six-axle vehicles consisting of three or more units, one of which is a tractor or straight truck power unit.
Class 13 - Seven or More Axle Multi-Trailer Trucks: All vehicles with seven or more axles consisting of three or more units, one of which is a tractor or straight truck power unit.
4. Glossary
Term |
Definition |
---|---|
Agency Specification |
A document that has been prepared by an agency to define requirements for a subject item or process when procured by the agency. |
ASC |
Actuated Signal Control |
Arming Enable |
A selected state of an arming input bit or Arming Pin of the TSS that can be used to modify its operation. |
Arming Input Bit |
An external event that is reported to the TSS using this protocol and used to modify its operation. |
Arming Pin |
A physical input to the TSS that can be monitored and used to modify its operation. |
Class |
A subdivision of collected historical sample data. |
Compatibility |
Two or more systems or components perform their required functions while sharing the same environment. |
Compliance |
A condition that exists when an item meets all of the requirements of an agency specification. |
Conformance |
A condition that exists when an item meets all of the mandatory requirements as defined by the standard. It can be measured on the standard as a whole, which means that it meets all mandatory (and applicable conditional) requirements of the standard or on a feature level (i.e., it conforms to feature X as defined in section X.X.X), which means that it meets all mandatory (and applicable conditional) requirements of the feature. |
ConOps |
Concept of Operations |
Delay |
A feature that allows the detection output from a TSS detector to be deferred for a user set time period. |
Deprecated |
In the context of a MIB, "deprecated" is an object STATUS value that indicates the object is valid in limited circumstances and may have been replaced by another. |
DST |
Daylight Savings Time |
Extension |
A feature that allows the detection output from a TSS detector to be lengthened for a user set time period. |
Fail-Safe Mode |
Capable of compensating automatically and safely for a failure, as a mechanism or power source. |
Feature |
A service provided by or behavior of the TSS. |
Firmware Version |
A manufacturer specified description for identifying the software currently embedded in the TSS. |
Hardware Version |
A manufacturer specified description for identifying the electronic components that comprise the TSS. |
ICD |
Interface Control Document |
Interchangeability |
A condition that exists when two or more items possess such functional and physical characteristics as to be equivalent in performance and durability, and are capable of being exchanged one for the other without alteration of the items themselves, or adjoining items, except for adjustment, and without selection for fit and performance. (National Telecommunications and Information Administration, U.S. Department of Commerce) |
Interoperability |
The ability of two or more systems or components to exchange information and use the information that has been exchanged. |
Live Data |
A specific operational network configuration between the management station and the TSS where the information exchange can be performed without the need for initiating and terminating a physical network connection between the management station and TSS. From a network perspective, this configuration is an "always on" connection, where the management station has access to the "current" information available in the TSS. |
Management Information |
A structured collection or database of related managed objects |
Base (MIB) |
defined using Abstract Syntax Notation One (ASN.1). |
Management Station |
A remote computer (e.g., Traffic Management Center), local computer (e.g., Laptop), or local controller (e.g., Traffic Controller). |
MVI |
Multi-Version Interoperability (backward compatibility) |
Near Real-Time Data |
Data that depicts an event as it existed at the current time less the processing time. The data varies from real-time data because it is dependent on the type and speed of transmission. This data is useable for identifying changes in traffic flows. |
NTCIP |
National Transportation Communication for ITS Protocol |
Normalized |
Process of reducing sample data to a common denominator to accommodate comparison of the measured data. |
Occupancy |
A measurement of vehicle presence within a zone of detection, expressed in seconds of time a given point or area is occupied by a vehicle. |
Output |
The condition of an on/off status generated by a change of state. |
Output Mode |
There are two common modes, presence and pulse. In the presence output mode, a detection of a vehicle is output constantly while the vehicle is in the zone. In the pulse output mode, detection is output for 125 milliseconds (± 25 milliseconds) and then the zone is retuned. |
PRL |
Protocol Requirements List |
Protocol |
A specific set of rules, procedures, and conventions defining the format and timing of data transmissions between devices that are accepted and used to understand each other. |
Protocol Version |
A standardized description for identifying the version of the TSS standard to which the TSS is designed to conform. |
Requirement |
A condition or capability to which a system must conform, either derived directly from the user needs, or stated in a contract, standard, specification, or other formally imposed document. A desired feature, property, or behavior of a system. |
Requirements Traceability |
The ability to follow or study the logical progression among the needs, requirements, and design details in a step-by-step fashion. |
RTC |
Real Time Clock |
RTM |
Requirements Traceability Matrix |
Sample Period |
Duration of time in seconds when data for the zone is being collected. |
Sensitivity |
The ability of the TSS to react to incoming signals, expressed as the minimum input signal required to produce an output signal. |
Sensitivity Mode |
A characteristic of the loop detector being used. It is defined as either AL/L, AL/Vl, or AL. |
Sensor |
A physical device used for sensing traffic. |
SEP |
Systems Engineering Process |
SNMP |
Simple Network Management Protocol |
SRS |
Software Requirements Specification |
Transportation Sensor |
Any system capable of sensing and communicating near real-time |
System (TSS) |
traffic parameters using NTCIP. |
User |
A person who will utilize the system that is developed. |
User Need |
The business or operational problem (opportunity) that must be fulfilled in order to justify purchase or use. While this is termed a "user need" within the NTCIP community, it reflects needs of all stakeholders. |
Virtual Zone |
A logical combination of one or more zones to create a new zone with its own conditioning and arming enables. This is useful in combining zones to a single zone to provide one output from many zones. This can also be used to alias a zone so that the same zone can provide multiple outputs, each with different conditioning parameters, sample periods, and/or trigger usage. |
Volume |
The number of vehicles crossing a section of road per unit time at a selected period. |
Zone |
An area in which traffic parameters can be measured and/or traffic data can be generated. |
Zone Options |
Special settings for controlling the behavior of zones. |
5. Reference to Other Standards
6. References
7. Study Questions
Participant Questions Included in Presentation
1) A _____ is defined as any system or device capable of sensing and communicating _____ real-time traffic parameters using _____.
2) What is the role of the processing element of a TSS?
3) Which one of the following choices is NOT considered a capability for the TSS?
4) Which of the following Control features allows the TSS to be set to a known condition?
5) Which of the following Monitoring features lets a system or user know that there is a loss of contrast on a video detection camera?
6) Which of the following Collecting features identifies the user need to retrieve yearly average volume data from a TSS?
7) The PRL is a good tool to_.
8) Which item below is NOT good practice when writing a specification for a TSS?