FDOT District 7 Regional ITS Architecture (Final)

How to Use The Website


Roadmap for Stakeholders to Review the ITS Architecture

Stakeholders can find specific information relevant to their activities by following these general instructions:

Inventory by Entity or Inventory by Stakeholder
The inventory of physical elements in the region ("entities") is made up of each local stakeholders instance of any subsystems or terminators that they operate. The inventory is organized by Stakeholder (so that a stakeholder can easily see each of their assets in the architecture) or by Entity (so an analyst or other interested person can see all the stakeholder elements in a region of the same type).

Select Inventory by Stakeholder from the web site menu to view a list of elements in the ITS architecture identified for each stakeholder. The stakeholder should then be able to search the alphabetically organized list of stakeholders and find themselves (or their organization). Each of these ITS elements is a hot link, and can be clicked to view an ITS Element page that will allow the user to easily see all the other elements that their element is connected to, and with which architecture flows. Each ITS Element page also contains a link to a Context Diagram. This diagram illustrates all the information exchange opportunities in a region for a single inventory element.

If that element is going to be a project, then this diagram illustrates all the external information exchange opportunities for that element.

Customized Service Packages / ITS Services
Service Packages represent collections of subsystems and terminators that exchange information (illustrated with architecture flows in the service package diagrams) to do a specific service. The service packages are customized to represent the operational concept for service delivery specific to this region. Each subsystem or terminator in a service package diagram is labeled with both its generic National ITS Architecture name and the name of the local stakeholder instance that participates in the customized service package. In this way the service package identifies the information exchange (using architecture flows) between specific stakeholders elements in the region to affect a particular service or set of services.

The analysis of architecture flows into and out of stakeholders elements is of particular importance, as it defines at a high level the information exchange requirements with other stakeholders that a stakeholders element is involved. Stakeholders should appreciate the benefits of the information exchange. Alternatively, stakeholders may believe that additional information exchange relationships may be required to achieve some benefit. In either of these cases, the ITS architecture may require revision. The simplest way to provide your input is to click on the Feedback button on each of the pages on the web site.

Select Services from the menu to view service package diagrams grouped by ITS Functional Area (e.g., Traffic Management, Public Transportation, Emergency Management, etc.).

Select Services by Stakeholder from the menu to view service packages for a particular stakeholder, grouped to make it easy to review any service package diagram where a stakeholder's ITS element appears.

Roadmap for Stakeholders to Review the ITS Projects

Stakeholders can find specific ITS Projects relevant to their activities by following these general instructions:

Select Projects By stakeholder from the menu to view ITS Projects that have been identified to be relevant to the Stakeholder. Select the Stakeholder from the pull-down menu on top to "jump" to the ITS Projects for that Stakeholder.

Project information includes the name of the project, a project description, and the service package diagram that best represents the ITS Project in the regional ITS architecture. Click on the name of the project to view more detailed information about the project.