Project Support

Using the architecture, each transportation 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 NEVADADOT.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, and CAMPO (Carson Area MPO).


The NDOT checklists for ITS Architecture compliance both point to using this web site to determine project compliance with the developed ITS Architecture. Specific information requested in the checklists can be found under the following menu links at the left:


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 once opened 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.