Stakeholders can find specific information relevant to their activities by following these general instructions:
Inventory by Architecture Entity or Inventory by
Stakeholders
The inventory of physical elements in the Statewide Services ITS Architecture ("entities") is made
up of each local stakeholders instance of any subsystems or terminators that they operate. The inventory is organized by Stakeholders (so that a stakeholder can easily see each of their assets in the architecture) or by Architecture Entity (so an analyst or other interested person can see all the stakeholder elements in a state 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 the state 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 Market Packages
Market Packages represent collections of subsystems and terminators that exchange information (illustrated with architecture flows in the market package diagrams) to do a specific service. The market packages are customized to represent the operational concept for service delivery specific to the state. Each subsystem or terminator in a market 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 market package. In this way the market package identifies the information exchange (using architecture flows) between specific stakeholders elements in the state 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 Send Your Comments button on each of the pages on the web site.
Select Market Packages by Functional Area from the menu to view market package diagrams grouped by ITS Functional Area (e.g., Traffic Management, Public Transportation, Emergency Management, etc.).
Select Market Packages by Stakeholder from the menu to view market packages for a particular stakeholder, grouped to make it easy to review any market package diagram where a stakeholder's ITS element appears.
Stakeholders can find specific ITS Projects relevant to their activities by following these general instructions:
Select Projects List from the menu to view ITS Projects that have been identified to be relevant to the State. Select the ITS Project from the pull-down menu on top to "jump" to that ITS Project.
Project information includes the name of the project, a project description, and the market package diagram that best represents the ITS Project in the Statewide Services ITS architecture. Click on the name of the project to view more detailed information about the project, and click on the market package diagram to view the customized market package diagram.