Intermodal Customer System --> Freight Distribution and Logistics Center:
freight transport payment information
Definitions
freight transport payment information (Information Flow): Acknowledgement that a payment has been made for freight transport. It includes fleet transaction ID, date of payment, and electronic signature.
Intermodal Customer System (Source Physical Object): The 'Intermodal Customer System' represents organizations that engage in the shipment of freight, either originator (consigner or shipper) or recipient of the cargo shipment. They enable the movement of goods on routes that require the use of other modes of transportation such as heavy rail, air, sea, etc. The Intermodal Customer System includes those personnel responsible for the movement of freight across international borders.
Freight Distribution and Logistics Center (Destination Physical Object): The 'Freight Distribution and Logistics Center' provides intermodal logistics support and support for the efficient distribution of freight across transport systems and modes. This can include consolidation arrangements, warehousing, and consignor-to-consignee intermodal shipping arrangements. These capabilities may be provided as part of intermodal fleet management activities or can be provided by an independent logistics specialist.
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) (32)
- (None-Data) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
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 | Moderate | Moderate | Low | |
Basis | Contains an identifier linked to a transaction and an electronic signature. Depending on what is being is being transported this could be LOW or MODERATE, but defaulting to the higher requirement. | Payment related information needs to be correct or the user may be inconvenienced or defrauded. | No time pressure likely on this flow. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |