Home Contact Us Search

Terminator Interfaces Diagram

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Inputs/Outputs: Architecture Flows* and Data Flows*

Commercial Vehicle Administration Enforcement Agency

• accident report (Architecture Flow*) - Report of commercial vehicle safety accident. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
  Data Flows*:
  • tea-accident_data

• carrier participation report (Architecture Flow*) - Report that summarizes motor carrier participation in CVO programs. Used to identify the level of active participation and to report which enrolled carriers are not participating as expected.
  Data Flows*:
  • tea-cv_carrier_participation_report

• citation (Architecture Flow*) - Report of commercial vehicle citation. The citation includes references to the statute(s) that was (were) violated. It includes information on the violator and the officer issuing the citation. A citation differs from a violation because it is adjudicated by the courts. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
  Data Flows*:
  • tea-cv_citation_data

• safety inspection report (Architecture Flow*) - Report containing results of commercial vehicle safety inspection. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
  Data Flows*:
  • tea-cv_safety_inspection

• violation notification (Architecture Flow*) - Notification to enforcement agency of a violation. The violation notification flow describes the statute or regulation that was violated and how it was violated (e. g., overweight on specific axle by xxx pounds or which brake was out of adjustment and how far out of adjustment it was). A violation differs from a citation because it is not adjudicated by the courts.
  Data Flows*:
  • tea-cv_violation_data

Commercial Vehicle Check Enforcement Agency

• violation notification (Architecture Flow*) - Notification to enforcement agency of a violation. The violation notification flow describes the statute or regulation that was violated and how it was violated (e. g., overweight on specific axle by xxx pounds or which brake was out of adjustment and how far out of adjustment it was). A violation differs from a citation because it is not adjudicated by the courts.
  Data Flows*:
  • tea-cvo_violation

Emissions Management Enforcement Agency

• emissions violation notification (Architecture Flow*) - Notification to enforcement agency of a detected vehicle emissions violation.
  Data Flows*:
  • tea-emissions_violation_data

Enforcement Agency Commercial Vehicle Administration

• information on violators (Architecture Flow*) - Information on violators provided by a law enforcement agency. May include information about commercial vehicle violations or other kinds of violations associated with the particular entity. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
  Data Flows*:
  • fea-cv_enforcement_agency_response

• targeted list (Architecture Flow*) - List of carriers, drivers, and/or vehicles of interest for enforcement purposes.
  Data Flows*:
  • fea-cv_enforcement_targets

• trigger area definition (Architecture Flow*) - Information that defines the desired trigger area for wireless roadside inspection safety data message submission.
  Data Flows*:
  • fea-cv_enforcement_configuration

• trigger control (Architecture Flow*) - Controls to enable or disable a particular trigger.
  Data Flows*:
  • fea-cv_enforcement_control

Enforcement Agency Commercial Vehicle Check

• information on violators (Architecture Flow*) - Information on violators provided by a law enforcement agency. May include information about commercial vehicle violations or other kinds of violations associated with the particular entity. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
  Data Flows*:
  • fea-violator_information

Enforcement Agency Roadway

• speed monitoring control (Architecture Flow*) - Information used to configure and control automated speed monitoring, speed warning, and speed enforcement systems.
  Data Flows*:
  • fea-enforcement_parameters
  • fea-speed_sensor_control

Maintenance and Construction Management Enforcement Agency

• request for enforcement (Architecture Flow*) - Request for traffic enforcement of speed limits, lane controls, etc. on a roadway including in a work zone or other special situations.
  Data Flows*:
  • tea-enforcement_request_from_m_and_c

Parking Management Enforcement Agency

• payment violation notification (Architecture Flow*) - Notification to enforcement agency of a toll, parking, or transit fare payment violation.
  Data Flows*:
  • tea-parking_violation_data

Payment Administration Enforcement Agency

• payment violation notification (Architecture Flow*) - Notification to enforcement agency of a toll, parking, or transit fare payment violation.
  Data Flows*:
  • tea-toll_violation_data
  • tea-vmt_equipment_failure

Roadway Enforcement Agency

• speed monitoring information (Architecture Flow*) - System status including current operational state and logged information including measured speeds, warning messages displayed, and violation records.
  Data Flows*:
  • tea-speed_sensor_status

• traffic violation notification (Architecture Flow*) - Notification to enforcement agency of a detected traffic violation including speed violations, HOV violations, and dynamic lane violations.
  Data Flows*:
  • tea-lane_violation_notification_from_roadway
  • tea-shoulder_violation_notification_from_roadway
  • tea-speed_violation_notification

Traffic Management Enforcement Agency

• request for enforcement (Architecture Flow*) - Request for traffic enforcement of speed limits, lane controls, etc. on a roadway including in a work zone or other special situations.
  Data Flows*:
  • tea-enforcement_request_from_traffic
  • tea-request_lane_enforcement
  • tea-request_shoulder_enforcement

• traffic violation notification (Architecture Flow*) - Notification to enforcement agency of a detected traffic violation including speed violations, HOV violations, and dynamic lane violations.
  Data Flows*:
  • tea-lane_violation_notification
  • tea-shoulder_violation_notification
  • tea-traffic_violation_data

Transit Management Enforcement Agency

• payment violation notification (Architecture Flow*) - Notification to enforcement agency of a toll, parking, or transit fare payment violation.
  Data Flows*:
  • tea-fare_collection_roadside_violation_data
  • tea-fare_collection_vehicle_violation_data
  • tea-fare_payment_violation_data