RAD-IT and SET-IT are the companion tools for ARC-IT. These tools enable regional and project architects to manipulate ARC-IT content and produce regional and project architectures to support 'left side' systems engineering activities.
Regional Architecture Development for Intelligent Transportation (RAD-IT) focuses in on regional planning and the development of Operations Concepts, the high level enterprise and physical views. It requires an understanding of the stakeholder community and the ITS services that are provided and planned for in the region. RAD-IT is a direct replacement for Turbo Architecture, and provides all of the functionality included in that tool with a more modern user interface, ARC-IT content and the linkages necessary to support future evolution of the toolset.
The Systems Engineering Tool for Intelligent Transportation (SET-IT) picks up where RAD-IT leaves off. 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.
So Which Tool is for Me?
Professionals focused on the transportation planning process, the development and maintenance of regional architectures, the high level specification of projects and satisfying Rule 940 requirements will be most interested in applying RAD-IT. As shown in the accompanying diagram, RAD-IT provides materials suitable for the earliest phases of the systems engineering process.
SET-IT produces artifacts the systems engineer will find useful in developing various pre-design documentation. SET-IT is ideally applied from ConOps through architecture definition phases of the SE process, providing the identification of functionality within subsystems and interfaces between subsystems that are the focus of subsequent design steps.