CVRIA Glossary

• A
• B
• C
• D
• E
• F
• G
• H
• I
• J
• K
• L
• M
• N
• O
• P
• Q
• R
• S
• T
• U
• V
• W
• X
• Y
• Z

Cardinality

One of the Flow Characteristics. The characterization of the relationship between the number of sender(s) and receiver(s) of a data exchange, e.g., broadcast (one-to-many) unicast (one to one).

Center

An entity that provides application, management, administrative, and support functions from a fixed location not in proximity to the road network. The terms "back office" and "center" are used interchangeably. Center is a traditionally a transportation-focused term, evoking management centers to support transportation needs, while back office generally refers to commercial applications. From the perspective of CVVRIA these are considered the same.

Center Physical Objects

Physical Objects that provide management, administrative, and support functions for the transportation system. The centers each communicate with other centers to enable coordination between modes and across jurisdictions. Some examples of center objects are Traffic Management, Transit Management, Commercial Vehicle Administration, Archived Data Management, Emissions Management, Payment Administration, Emergency Management, Traveler Information, and Fleet and Freight Management. The Center class is one of four general physical object classes defined in the National ITS Architecture. The center class objects are typically shown as green boxes on the CVRIA application drawings.

Center to Center Communications

A communication link serving stationary entities, including center physical objects. It may be implemented using a variety of public or private communication networks and technologies. It can include, but is not limited to, twisted pair, coaxial cable, fiber optic, microwave relay networks, spread spectrum, etc. In center to center communication the important issue is that it serves stationary objects. Both dedicated and shared communication resources may be used. One of the types of architecture interconnects defined in the Connected Vehicle Reference Implementation Architecture.

Center to Field Communications

A communication link serving stationary entities, including center physical and field based objects. It may be implemented using a variety of public or private communication networks and technologies. It can include, but is not limited to, twisted pair, coaxial cable, fiber optic, microwave relay networks, cellular, spread spectrum, etc. In center to field communication the important issue is that it serves stationary objects. Both dedicated and shared communication resources may be used. One of the types of architecture interconnects defined in the Connected Vehicle Reference Implementation Architecture.

Clarus System

Integrated observation and data-management system that collects near-real-time information from state and
local government-owned Environmental Sensor Stations (ESSs) together with comprehensive metadata on these systems. The Clarus System conducts a variety of quality checks on the data and makes the data available to public and private-sector users and researchers. In 2013, 39 states, four local agencies, and five Canadian provinces provided data from more than 2,400 sensors to the Clarus System. It provides a one-stop, Internet-based portal for all surface transportation environmental observations. The Clarus Initiative is based on the premise that the
integration of a wide variety of weather observing, forecasting, and data management systems combined with robust and continuous data quality checking could serve as the basis for timely, accurate, and reliable weather and road condition information. The Clarus Initiative is based on the premise that the integration of a wide variety of weather observing, forecasting, and data management systems combined with robust and continuous data quality checking could serve as the basis for timely, accurate, and reliable weather and road condition information.

Clean Air Act (CAA)

The original Clean Air Act was passed in 1963, but the national air pollution control program is actually based on the 1970 revision of the law. The Clean Air Act as amended in 1990 made major changes and contains the most far-reaching revisions of the 1970 law.

Commercial Motor Vehicle

Commercial motor vehicle means any self-propelled or towed motor vehicle used on a
highway in interstate commerce to transport passengers or property when the vehicle:
1) Has a gross vehicle weight rating or gross combination weight rating, or gross vehicle weight or gross combination weight, of 4,536 kg (10,001 pounds) or more, whichever is greater; or
2) Is designed or used to transport more than 8 passengers (including the driver) for compensation; or
3) Is designed or used to transport more than 15 passengers, including the driver, and is not used to transport passengers for compensation; or
4) Is used in transporting material found by the Secretary of Transportation to be hazardous under 49 U.S.C. 5103 and transported in a quantity requiring placarding under regulations prescribed by the Secretary under 49 CFR, subtitle B, chapter I, subchapter C.
(Source: 49 U.S.C. 31132)

Communications View

One of four views (along with the physical, functional, and enterprise views) defined by the Connected Vehicle Reference Implementation Architecture. The communications view includes all of the communications equipment (e.g., wired and wireless transmitters and receivers) and the information management and transport capabilities necessary to transfer information among objects in the physical view in an interoperable manner. Each triple (source, destination, flow) from the Physical View has been mapped to one or more data dictionary standards, referred to by the CVRIA as an information layer standard. In addition, the Comm View relates each flow triple to one or more of 16 standards profiles, defined to identify the communications protocols necessary to transport data described by an information flow.

Concept of Operations (ConOps)

For a specific project, the document in which the project stakeholders document their shared understanding of the system to be developed and how it will be operated and maintained. A user-oriented document that describes a system's operational characteristics from the end user's viewpoint.

Concern

Concerns are concepts that are of interest or importance to one or more stakeholders. Concerns may apply to any phase of the system life cycle. However, some concerns may apply more during system design, implementation, operations, or maintenance and not during other phases of the system's life. A concern could be manifest in many forms, such as in relation to one or more stakeholder needs, goals, expectations, responsibilities, requirements, design constraints, assumptions, dependencies, quality attributes, architecture decisions, risks or other issues pertaining to the system.

Confidentiality

One of the Flow Characteristics. The property of being unable to read Protocol Data Unit (PDU) contents by any listener that is not the intended receiver.

Configurable Parameter

Non-static data that can be adjustable and updated when needed.

Configuration

Data that is used to customize the operational environment for a System Element or System User, or the System as a whole.

Configure

The process of selecting from a set of option(s) or alternative values in order to create a specific operational environment.

Connected Device

Any device used to transmit to or receive messages from another device. A connected device can be sub-categorized as an OBU, ASD, or RSU. In many cases the connected device will be a DSRC device, but other types of communications could be
supported.

Connected Vehicle

A vehicle containing an OBU or ASD.

Constraint

An externally imposed limitation on system requirements, design, or implementation or on the process used to develop or modify a system. A constraint is a factor that lies outside – but has a direct impact on – a system design effort. Constraints may relate to laws and regulations or technological, socio-political, financial, or operational factors.

Contract

In project management, a legally binding document agreed upon by the customer and the hardware or software developer or supplier; includes the technical, organizational, cost, and/or scheduling requirements of a project.

Control

To exercise influence over.

Control Channel

A single radio channel, not a service channel, intended for the exchange of management frames, including Wireless Access in Vehicular Environments (WAVE) Service Advertisements, and WAVE Short Messages.
(Source: IEEE 1609.3)

Controller Area Network

A Controller Area Network (CAN) bus is a message-based protocol, designed specifically for automotive applications. The CAN bus is one of five protocols used in the OBD-II vehicle diagnostics standard. The OBD-II standard has been mandatory
for all cars and light trucks sold in the United States since 1996.

Coordinated Universal Time (UTC)

The primary time standard by which the world regulates clocks and time. UTC serves to accommodate the timekeeping differences that arise between atomic time (which is derived from atomic clocks) and solar time (which is derived from astronomical measurements of the Earth's rotation on its axis relative to the Sun). Since Jan. 1, 1972, UTC has been modified by adding "leap seconds" when necessary.

Correspondence

Rules that guide the relationships between viewpoints. Generally speaking, elements in one view may be referenced in some fashion in at least one other view.

Coverage Area

A geographic jurisdiction within which the System provides services.

Cross Support

An agreement between two or more organizations to exploit the technical capability of interoperability for mutual advantage, such as one organization offering support services to another in order to enhance or enable some aspect of a mission.

Current (C)

One of the values for the Time Context Flow Characteristic. Data that is current (relevant at the time of reporting for applications that do not require sub-second response). May also be described as "Recent" in CVRIA.