This is background material for a subsequent post.
The [US] National ITS Architecture provides a common framework for planning, defining, and integrating intelligent transportation systems. It is a mature product that reflects the contributions of a broad cross-section of the ITS community (transportation practitioners, systems engineers, system developers, technology specialists, consultants, etc.).
The architecture defines:
- The functions (e.g., gather traffic information or request a route) that are required for ITS
- The physical entities or subsystems where these functions reside (e.g., the field or the vehicle).
- The information flows and data flows that connect these functions and physical subsystems together into an integrated system.
Basically, the National ITS architecture brings taxonomy to Intelligent Transportation Systems, all through the confusing lens of the typical American engineer (c.f. the usage of the ackronym ISP). It looks like this:
The ne-plus ultra of the National ITS Architecture is the connected vehicle. Below the fold, a shiny video.
Personally, I remain cynical of the next big thing.
For more on the National ITS Architecture (and a reminder that slides make bad documents), see here. If you need bedtime material, there is a ~300 page theory of operation from USDOT.