# Presentation: 134987

## Turbo Architecture A National ITS Architecture Tool

- Lee Simmons
- ITS Joint Program Office
- Federal Highway Administration
- May 3, 2000

***USDOT***
***Iteris, Inc.***
***Lockheed Martin***

## Topics

- Tool Purpose and Functionality
- What You Need to Start Using Turbo
- User Interface and Outputs

## Turbo Architecture is...

- An interactive software program
- for the development of regional and project architecture using National ITS Architecture as a reference
- for Transportation planners, System integrators, Public and Private sectors

## Turbo Architecture is Not...

- A complete end-to-end solution to fully develop ITS Architectures
- Stakeholder Outreach/Involvement
- Gather inventory
- A design tool

**Notes:**
Turbo Architecture is one step in the development of an ITS Architecture.  It is not an end to end solution.  There are many other activities that must occur to fully develop an ITS Architecture such as stakeholder outreach and involvement, and gathering an inventory of systems and services.
Turbo Architecture applies to pre-design activities.  It aids in the planning process of a region or project.  It is not a design tool for ITS systems.

## Turbo Architecture Benefits

- Leverages National ITS Architecture for structured local planning
- Maximizes ITS integration opportunities
- Facilitates efficient expansion of ITS
- Saves time and money in development of ITS Architectures

## Primary Turbo Architecture Functions

- Create a Regional Architecture
- Create a Project Architecture when no Regional Architecture exists
- Create a Project Architecture from existing Regional Architecture
- Add a Project Architecture to existing Regional Architecture

## Turbo Architecture Process

- Identify and Map System Inventory

- Map systems to the National ITS Architecture

- Interview Dialog
- Forms-Driven

- Identify and Map Transportation Services/Needs

- Map services to the National ITS Architecture

- Tailor Subsystem/ Terminator Interconnections

- Tailor Interconnections to reflect local environment

- Tailor Architecture Flows

- Tailor Architecture Flows to reflect local environment

- Interview Dialog
- Forms-Driven

- Tables

- Tables

**Notes:**
The first step in the process is to Map systems to the National ITS Architecture subsystems and terminators.  This can be done through an interview or through a forms-driven approach.
The second step is to Map services to the National ITS Architecture market packages.  This, also, can be done through an interview or through a forms-driven approach.
At this point, Turbo Architecture has linked the regional or project systems to the National ITS Architecture.
The next 2 steps will provide the tailoring that is necessary to reflect the local environment.  The tailoring will first address the interconnections between subsystems and terminators.  The second tailoring step will address architecture flows between subsystems and terminators.  Both of these steps are table-driven.

## What You Need to Start Using Turbo Architecture

- Recognition of need for ITS Architecture
- Integration
- Structured planning
- Stakeholder commitment and participation
- Assessment of present and future needs
- Inventory of transportation systems and services

## What You Need to Start Using Turbo Architecture

- Understanding of the National ITS Architecture
- Relationships
- Definitions
- Terminology

## What You Need to Start Using Turbo Architecture

- Minimum System Configurations
- PC with Pentium Processor (100 MHz or better)
- Operating Systems: Windows 95, 98 Second Edition, NT4
- 80MB Free on Hard Drive
- 800X600 or Higher Monitor Resolution
- 32MB RAM
- A CD-ROM drive

## Getting Started

**Notes:**
Turbo Architecture follows Microsoft Windows standards for user interfaces and steps the user through the process of developing an ITS Architecture.

## Interview Questions

**Notes:**
Through the interview process, the user is presented with questions to answer about their ITS.  The answers provided will be used by Turbo Architecture to map to subsystems, terminators, and market packages.

## Sausage Diagram

**Notes:**
One of the diagrams that can be created by Turbo Architecture is the Sausage Diagram representing the subsystems that have been selected for the ITS Architecture.

## Interconnect Diagram

**Notes:**
Another diagram that is even more useful than the Sausage diagram is the interconnect diagram.  This diagram illustrates the interconnections between each subsystem.

## Architecture Flow Diagram

**Notes:**
The next level of detail below the interconnect diagram is the Architecture Flow diagram.  The Architecture Flow diagram illustrates the information that is exchanged between subsystems.

## Standards Report

**Notes:**
Several reports can be produced by Turbo Architecture.  One of those reports is a Standards report that identifies applicable standards that address the Architecture Flows in the ITS Architecture. 

Note to presenter:  This screen shot is of the 4th page of the subject report.  It was taken to illustrate a more applicable standard (Message Set for External TMC communications).  It is not necessary to highlight this fact but if asked you will have an answer.

## Turbo Architecture Summary

- Tool for developing ITS Architectures
- Uses National ITS Architecture to create Regional or Project Architectures
- Leverages National ITS Architecture for structured local planning
- Maximizes ITS integration opportunities
- Facilitates orderly, efficient expansion of ITS

**Notes:**
Through our training courses and deployment support activities, it has become apparent that there is a need for a tool to assist stakeholders in extracting the elements of the National ITS Architecture for their use.  We are currently developing a tool called TurboArchitecture to meet this need.
TurboArchitecture will help stakeholders develop regional and project architectures using the National ITS Architecture as a reference.  It uses 2 methods for user inputs, an interview process to gather information from the user or information can be directly input by the user.  The outputs of the tool include 
- subsystem and terminator definitions that are mapped to the appropriate stakeholders
- interface definitions consisting of architecture flows between subsystems and terminators
- references to standards that address the architecture flows defined for particular interfaces giving the user a source of information to further define that interface
- and various report and diagram outputs that illustrate the ITS architecture for presentation and stakeholder outreach purposes.
TurboArchitecture will be available in early 2000.

## How to order your copy

- Mc*Trans*
*Phone number: *(352) 392-0378 x242
*Email address: *_*[mctrans](mailto:mctrans@ce.ufl.edu)*__*[@](mailto:mctrans@ce.ufl.edu)*__*[ce](mailto:mctrans@ce.ufl.edu)*__*[.](mailto:mctrans@ce.ufl.edu)*__*[ufl](mailto:mctrans@ce.ufl.edu)*__*[.](mailto:mctrans@ce.ufl.edu)*__*[edu](mailto:mctrans@ce.ufl.edu)*_
*Price:  $190*
*Site licenses available*