Overview

The scope of the Regional ITS Architecture can be described in terms of: 1) the size of the region and jurisdictions covered (geographic scope), 2) the planning or time horizon, and 3) the variety of transportation services that are covered. This scope is defined in the context of adjacent and overlapping Regional ITS Architectures.

Description

The ITS Architecture is a roadmap for transportation systems integration in a defined region. The architecture was developed through a cooperative effort by the region's transportation agencies and represents a shared vision of how each agency's systems will work together in the future, sharing information and resources to provide a safer, more efficient, and more effective transportation system for travelers in the region.

The purpose of this Statewide Nevada ITS Architecture web site is to encourage the use of the ITS architecture and gather feedback to make sure that the architecture continues to be used and reflects the intelligent transportation system vision for the statewide area of Nevada outside of the Northwest and Southern regions which have their own dedicated ITS architectures.

This Statewide Nevada ITS Architecture represents the Carson area and Lake Tahoe area as well as the areas in all Districts outside of the Washoe RTC and the RTC of Southern Nevada. The Southern Nevada ITS Architecture represents the RTC of Southern Nevada and the County and local municipalities within the RTC boundary. The Northwest Nevada ITS Architecture represents the Washoe RTC, Washoe County, and local municipalities that are within the boundaries of the Washoe RTC.

Time Frame

10 Years through 2033

Geographic Scope

The Statewide ITS Architecture geographically encompasses the entire state and all NDOT Districts and local/county agencies outside of the two urbanized metropolitan areas of Reno/Sparks and Las Vegas.

Service Scope

Full services scope of traffic management, transit management, emergency management and other ITS related activities.

Project Support

Using the architecture, each project can be viewed as an element of the overall transportation system, providing visibility into the relationship between individual transportation projects and ways to cost–effectively build an integrated transportation system over time. This section will describe to the user the specific directions in order to find information contained within this ITS architecture to support project development.

IF YOU ARE LOOKING FOR REQUIREMENTS TO SUPPORT THE DEVELOPMENT OF AN RFP FOR AN ITS PROJECT:

Functional requirements are a description of WHAT the system has to do. The Systems Engineering Tool for Intelligent Transportation (SET–IT) picks up where RAD–IT leaves off in the systems engineering process. SET–IT is project–focused, and ideally applied to individual project deployments with scope constrained by project definitions specified in the regional architecture. SET–IT is a graphical tool, providing the user with visual feedback and tools necessary to manipulate service package physical and enterprise diagrams, develop communications stack templates, specify standards at all protocol layers, and export that information in a variety of forms and formats. SET–IT produces material that the systems engineer will find useful in developing various pre–design documentation for a specific project or application that is being designed/procured. Functional requirements are generic descriptions that are technology–neutral and are comprehensive in describing full capabilities of ITS elements for that particular function.

IF YOU NEED TO SHOW ITS ARCHITECTURE COMPLIANCE FOR YOUR PROJECT:

Nevada Department of Transportation (NDOT) has published a Systems Engineering and Architecture Compliance (Rule 940) checklist and a Simple Project Quick Checklist – both can be found on the NDOT website DOT.NV.GOV under PROJECTS/PROGRAMS. NDOT requires the completion of the appropriate checklist for all ITS related projects (large and small, statewide or local) established by Nevada DOT and all local metropolitan planning organizations (MPOs) such as the Washoe RTC, the RTC of Southern Nevada, CAMPO (Carson Area MPO), and Tahoe MPO.

The NDOT checklists for ITS Architecture compliance both point to using the appropriate ITS Architecture to determine project compliance with the developed ITS Architecture. The user should request the architecture web link from the NDOT Traffic Operations contact for the NDOT ITS & ATM Master Plan to identify the appropriate information required from the ITS architecture, including:Stakeholders: list the stakeholders that are involved in your project implementation, operation, or maintenance.

Inventory by Stakeholder: list the inventory elements that your project includes or impacts directly.

Services: identify the specific services that your project will provide (traffic management, traveler information, emergency management, archived data, etc.).

Interfaces: although not directly requested by the NDOT checklists, the user can address these questions by accessing this web page, finding the primary elements in the table that are involved in your project, and selecting the hyperlink of the associated interfacing element to reach the diagram that shows the specific interface description of how those two elements interface.

IF YOU ARE INTERESTED IN HOW YOUR PROJECT MAY IMPACT OTHERS IN THE REGION:

Each inventory element in the ITS architecture has additional detail included such as the associated stakeholder, the functionality that it serves in the region, and the list of other ITS elements that the main element selected interfaces with. The user can find relationships defined in the ITS architecture by:

What other ITS elements does my project impact?

By selecting the hyperlink of a specific ITS element of interest, other ITS elements will be shown at bottom of that page if the ITS element of interest has a relationship to another ITS element. Clicking on the hyperlink for that interface will take the user to a diagram that shows those interface descriptions. If the user is interested in information specific to that related ITS element (description, stakeholder, other related ITS elements, etc.), the user needs to go back to the Inventory web pages and find the ITS element to select.

Who else should I include in my project development?

Through the process defined in the question above, the user can find the stakeholder associated with the ITS element that is related to the users project. The agencies that "own" the ITS element in the ITS architecture are generally described in nature; however, NDOT can provide guidance to a good point person at each agency/stakeholder identified.

What other purpose does my project serve?

The Requirements menu option can provide an overview of how a specific ITS element is involved in a larger functional purpose in the region or state. The user can identify the subsystem on the left side of the table that associates most closely with the individual components of the project and under that subsystem, choose a functional area that most closely aligns with the functionality that the project will implement in the region. Specific ITS elements that are also associated with that functional area can help the user understand the broader context for that ITS function occurring in the region.

Contact Information

To request the ITS Architecture, contact:

• Juan Hernandez - Manager 1 ITS Planning & Operations

• Email: jchernandez@dot.nv.gov