data provision (Information Flow): Data provision provides the source material for a publish-subscribe or query-retrieval data distribution scheme. This is the 1 of the 1:N data distribution architecture. This flow is a super-flow; it does not define data elements but is inclusive of any flow implemented using publish-subscribe or query-retrieval methods.
ITS Object (Source Physical Object): The general 'ITS Object' includes core capabilities common to any class of object.
Data Distribution System (Destination Physical Object): The 'Data Distribution System' collects, processes, and distributes ITS data, connecting data producers with data consumers and facilitating data exchange.
This Triple is in the following Service Packages:
This Triple is described by the following Functional View Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Communication SolutionsNo communications solutions identified.
|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).|
|Information Flow Security|
|Basis||This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE or LOW confidentiality requirement, then this could be MODERATE or LOW, as appropriate.||This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE integrity requirement, then this could be MODERATE.||This value is derived from the specific flows are satisfied by this super-flow. MODERATE is set because some flows may require it. If the implementation includes flows with only a LOW availability requirement, then this could be LOW. HIGH is not considered; any flow requiring HIGH availability will not use DDS.|