Fleet and Freight Management Center --> Commercial Vehicle Administration Center:
credential application
Definitions
credential application (Information Flow): Application for commercial vehicle credentials. Authorization for payment is included. It contains details about the administrative request for a Freight Vehicle registration. It also carries the acknowledgement that a payment has been placed in the bank account of the administration by the Fleet Operator. This information flow includes fleet operator request ID, vehicle characteristics, transport need (origin and destination), electronic signature and date of payment.
Fleet and Freight Management Center (Source Physical Object): The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.
Commercial Vehicle Administration Center (Destination Physical Object): The 'Commercial Vehicle Administration Center' performs administrative functions supporting credentials, tax, and safety regulations associated with commercial vehicles. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It communicates with motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with cognizant authorities. It coordinates with other Commercial Vehicle Administration Centers (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. It communicates with field equipment to enable credential checking and safety information collection at the roadside. It makes safety information available to qualified stakeholders to identify carriers and drivers that operate unsafely.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (43)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | High | Moderate | Low | |
Basis | Includes personal and payment information that if compromised would have severe impact on the individual that is the subject of the application. | Personal ID and payment data needs to be correct or the individual will not be approved or properly pay. However the impact is limited to the application and individual in question, which is why it is MODERATE. | This information does not need real time access and can safely be assigned LOW. There should be alternative mechanisms as well. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |