1. ARC-IT Training
June 2017
ARC-IT Training
Session 1: Introduction to Architecture Reference for Cooperative and Intelligent Transportation (ARC-IT)
This training is designed for transportation professionals that want to understand how ARC-IT relates to the current National ITS Architecture and Connected Vehicle Reference Implementation Arch (CVRIA). The training discusses how to use ARC-IT and provides a basic overview of the tools that have been developed to support use.

2. Course Sessions Session 1 - Introduction to ARC-IT
ARC-IT Training
June 2017
Course Sessions
Session 1 - Introduction to ARC-IT
Session 2 – ARC-IT Website Tour
Session 3 – ARC-IT Website Navigation Example
Session 4 - Regional ITS Architectures
Session 5 - Using Regional ITS Architectures
Session 6 – Introduction to ARC-IT Tool Set
The ARC-IT training will be presented in six sessions:
Session 1 introduces ARC-IT,
Session 2 includes a tour the ARC-IT website,
Session 3 provides an example of how the ARC-IT website is navigated,
Session 4 presents an overview of what a Regional ITS Architecture is and how ARC-IT is used to support development of a RA
Session 5 discusses how to use a Regional ITS Architecture to support ITS Planning and project development
Session 6 introduces ARC-IT related tools and resources.
It will take approximately two hours to complete the entire course.

3. This session will take approximately 20 minutes to complete.
ARC-IT Training
June 2017
Session Outcomes
Describe ARC-IT
Identify key components of ARC-IT
Describe how ARC-IT is used
Describe tool set developed to support ARC-IT use
This session will take approximately 20 minutes to complete.
Describe the use of the ARC-IT tool set.

4. ARC-IT Training
June 2017
What is ITS?
Intelligent Transportation Systems (ITS) include the electronics, communications or information processing used singly or integrated to improve the efficiency or safety of surface transportation
One definition of ITS is that it includes the electronics, communications or information processing used singly or integrated to improve the efficiency or safety of surface transportation.

5. What is an ITS Architecture?
ARC-IT Training
June 2017
What is an ITS Architecture?
Framework for Developing Integrated Transportation Systems
Identifies:
Organizations
Systems operated
Functions performed
Information exchanged
Communications
What is an ITS Arch? A framework or Template.

6. ITS Architectures Provide a Framework for Integration
ARC-IT Training
June 2017
ITS Architectures Provide a Framework for Integration
Traffic
Traveler Info
I-93 Closed
at Decatur Blvd.
Traffic Information
Request for
Key is integration,
Transit
Emergency

7. National ITS Architecture CVRIA
ARC-IT Training
June 2017
ARC-IT Scope
ARC-IT
National ITS Architecture
CVRIA
ARC-IT takes the scope of the National ITS Architecture and combines it with the scope of CVRIA. The scope is defined through a set of ITS services. As shown, ARC-IT is slightly larger than either the existing National ITS Arch and CVRIA with the additional of several additional services.
ARC-IT combines services of National ITS Arch with connected vehicle content of CVRIA

8. ARC-IT Structure Defined around 4 views:
ARC-IT Training
June 2017
ARC-IT Structure
Defined around 4 views:
Enterprises to carry out services
Functions to implement services
Physical objects to implement that functionality
Communications protocols necessary
ARC-IT has been revised to have a structure like CVRIA which followed the ISO/IEC/IEEE standard for Systems and Software Engineering – Architecture Description. This led to the definition of four views for the architecture
The enterprise view of ARC-IT defines relationships between organizations and the roles those organizations play in providing services. This is similar to the Institutional Layer of the previous versions of the National ITS Architecture
The functional view of ARC-IT defines the set of Processes implement the functionality required to provide services. This view is similar to the Logical Architecture
The most familiar view of ARC-IT is the physical view which groups the functionality into physical objects that establish the interfaces between the objects.
Finally, the communications view identifies the communication protocols needed to send data along the interfaces defined by the Physical View..

9. ARC-IT Organization ARC-IT organized around Service Packages
Represent the portion of each view that provides a single ITS service
ARC-IT is organized around a set of Service Packages, which are the slice of the architecture needed to provide a single ITS service.

10. ARC-IT Service Package Areas
ARC-IT Training
June 2017
ARC-IT Service Package Areas
Public Transportation
Traffic Management
Traveler Information
Support
Commercial Vehicle Operations ☻◘
Public Safety
Maintenance and Construction
Sustainable Travel
Parking
Management
Key Message: Recall ARC-IT Service Packages – ITS services defined by the architecture.
Interactivity: None
Notes:
ARC-IT includes a list of ITS services. In ARC-IT, the services are referred to as service packages. You can review the list of service packages to identify those that can be used to meet your transportation goals and objectives.
Service packages have specific names, descriptions and even diagrams as given in ARC-IT. Service packages specify the specific architecture that will be used to implement a service. They do not include specific technologies but just identify the functions needed to deliver the service.
Weather
Data Management
Vehicle Safety

11. ARC-IT Physical View Depicts: Identifies options for…
ARC-IT Training
June 2017
ARC-IT Physical View
Depicts:
Physical objects that interact to deliver services
Interfaces and flows of information between those physical objects
Identifies options for…
What are the interfaces to support ITS services?
What functionality is allocated to physical objects?
What objects require information security safeguards and what are they?
The physical view is the most recognizable view of ARC-IT. It defines the physical objects that interact with each other to deliver services. It identifies interfaces between each object or device. This information is displayed on physical diagrams for each ITS Service. The physical objects are also used in the Enterprise view and appear on the enterprise diagrams.

12. Physical View - Physical Objects
ARC-IT Training
June 2017
Physical View - Physical Objects
Key “building blocks” of Physical View
The physical systems, devices, vehicles, or people that provide ITS services
Two Types
Subsystems
Functionality defined
Terminators
No Functionality
Three types
Terminators
Terminators
Subsystems
Physical Objects are the key pieces of the Physical View.
Like with National ITS Arch, the physical blocks come in two flavors- subsystems, which have functionality defined, and terminators, which do not have any functionality defined.
Three types of Terminators are defined: System (e.g. Media), Other System (e.g. Other TM), and human ( e.g. traffic operations personnel) .
Terminators
Terminators
Terminators

13. Physical View - Physical Objects
ARC-IT Training
June 2017
Physical View - Physical Objects
Organized into 5 Classes (and color-coded)
The organization of physical objects is similar to that in the National ITS Arch V7.1, with the addition of a 5th class of objects called Support Systems. Note the diagram above is similar to the Sausage Diagram of V7.1 in that it shows the type of communications used within or between classes.
Each Type of Physical object (Subsystems, Terminators) is organized by the 5 classes
The next 5 slides will review each object class.

14. Physical View - Physical Objects
ARC-IT Training
June 2017
Physical View - Physical Objects
Centers
Provide Key Operational functionality for ITS Services
Subsystem names use “Center” (vs “Subsystem” in earlier versions)
Includes generic Center to address how support functions interface with all centers.
Centers are the operational entities that send and receive information to provide ITS services. Note in ARC-IT the subsystem names use the word “center”, rather than subsystems in earlier versions of the National ITS Architecture. This represents an expression of the physical nature of these objects (rather than the abstract expression implied by the term subsystem). In fact the 13 objects shown in the diagram represent objects inside of ITS for which functionality will be defined. Each of the next 4 diagrams are defined the same way- physical objects that have functionality defined.
Most of the Centers in this diagram are duplicates of the equivalent center subsystem from the earlier versions of the National ITS Architecture. Note that the previous Information Service Provider has been renames Transportation Information Center in order to emphasize it traveler information focus. Two generic centers (Authorizing Center and Center) are now included in ARC-IT. The 'Authorizing Center' provides the functionality needed to enable data exchange between and among mobile and fixed transportation users. This “Center” physical object is used to model core capabilities that are common to any center.

15. Physical View - Physical Objects
ARC-IT Training
June 2017
Physical View - Physical Objects
Field Equipment
ITS Field Devices both
Long in use (e.g. CCTV, Traffic Signals, DMS) and
New (e.g. Connected Vehicle Roadside Equipment and Electric Charging Stations)

16. Physical View - Physical Objects
ARC-IT Training
June 2017
Physical View - Physical Objects
Vehicles
ITS OBE (On-Board Equipment) in vehicles
Includes Freight Equipment

17. Physical View- Physical Objects
ARC-IT Training
June 2017
Physical View- Physical Objects
Traveler Devices
Personal Devices (e.g. mobile smart phones, tablets, and computers)
Public Devices (e.g. fixed kiosks and transit stop signage)

18. Physical View - Physical Objects
ARC-IT Training
June 2017
Physical View - Physical Objects
Support Systems
Includes non operational use of data (e.g. Archived Data System)
Systems that support operations
for all ITS (e.g. Map Update System)
For connected vehicle specific services (e.g. cooperative ITS credentials management system)

19. Physical View - Interconnect Diagram
ARC-IT Training
June 2017
Physical View - Interconnect Diagram

20. Physical View - Terminators
Represent People or Systems “on the edge” or boundary of the scope of ARC-IT
Three primary types
System
Other Systems
Humans
Within each type organized by class
Center/ Field/ Vehicle/ etc.
Terminators are all the physical objects that sit on the “edge of the scope oval”, meaning that they interface with physical objects within ITS, but they have functions outside of ITS. For example Financial Institution- important for electronic payment systems, but is an “external” system as far as ITS is concerned.
Other Systems are the architecture’s way of describing interfaces between two of the same type of physical object- for example the interface between two TMCs.
The Human Terminators represent all the people who operate or maintain ITS systems.
There are a total of 90 Terminators defined
System- 46
Other System- 19
Human- 25

21. Physical View - Service Packages
ARC-IT Training
June 2017
Physical View - Service Packages
ITS Services
Transportation services provided by ITS
Defined by Service Packages
Portion of architecture that provides a specific service
Service Packages organized by “Area”
Commercial Vehicle Operations
Data Management
Maintenance and Construction
Parking Management
Public Safety
Public Transportation
Support
Sustainable Travel
Traffic Management
Traveler Information
Vehicle Safety
Weather
Discuss revised set of areas and how they have evolved since V7.1
The list of service packages for V8 includes all the service packages from V7.1 plus many of the Applications contained in CVRIA, which have been defined as SPs in V8.

22. Physical View- Service Packages
Service Packages in the Physical View are defined by a set of:
Physical Objects
Functional Objects
Information Flows
Plus a diagram showing all how all these are connected.
The Physical View representation of Service Packages is one of the key outputs of the architecture because it forms the basis for using the architecture to develop either regional or project architectures
Defined by
Physical Objects
Functional Objects (within the physical objects)
Information flows
And a diagram that shows how they are all connected to provide the service.

23. ARC-IT Physical View Example - Transit Signal Priority
ARC-IT Training
June 2017
ARC-IT Physical View Example - Transit Signal Priority
This is the physical view diagram of the Transit Signal Priority. The larger colored boxes are physical objects. The gray boxes inside the physical objects are functional objects. Functional objects are groupings of functional processes that provide specific capabilities such as Roadway Signal Control in the ITS Roadway Equipment object.
The information flows have characteristics that are denoted by their color and icons by the flow names.

24. Physical View- Functional Objects
ARC-IT Training
June 2017
Physical View- Functional Objects
Functional Objects are functional building blocks of Subsystems
Define the functions and interfaces required to support a “deployable” piece of the subsystem
Functional requirements are defined for each functional object
Functional objects (called Equipment Packages in previous versions) describe deployable subsets of a subsystem.
The functional objects are what actually originate or receive the information flows that are exchanged between the physical objects
Each FO maps to a single Subsystem (Terminators do not have FOs)
Detailed functional reqmts are assigned to each FO

25. ARC-IT Communications View
ARC-IT Training
June 2017
ARC-IT Communications View
Depicts:
Layered communications protocols that support communications between physical objects
Identifies options for…
Identity and appropriateness of protocols at all layers
How these protocols ensure or support:
Security
Privacy
Status of protocols as standards or privately provided protocols and the implications of their use from an evolve-ability perspective
The communications view of ARC-IT identifies the communications protocols that support information exchange between physical objects. It illustrates protocols at all layers, appropriate security considerations, and applicable standards for each interface, known as a triple. A triple is a source-information flow-destination combination that represents an information exchange between physical objects or application objects.

26. ARC-IT Communications View Example
ARC-IT Training
June 2017
ARC-IT Communications View Example
This example of the local signal priority request flow between the transit vehicle OBE object and the roadside equipment object, altogether defining the triple, shows the protocols identified for each layer of the interface. Included on the diagram is the security plane that identifies the security considerations, in this case in IEEE

27. ARC-IT Enterprise View
ARC-IT Training
June 2017
ARC-IT Enterprise View
Depicts:
Relationships between organizations
Roles organizations play in delivery of ITS services
Organized around Enterprise Objects
Interact to exchange information
Manage or operate systems
Enterprise View will be added in a future version of ARC-IT
The Enterprise View is not included in V It will be included in version For additional information on the Enterprise View, you can view it on the CVRIA website.
When included the enterprise view identifies will consider the following:
Who is responsible for delivering services?
Who uses, operates, owns and manages the systems that deliver services?
Who is responsible for securing data?
Who is responsible for detecting malfunction and misbehavior?
Who is responsible for physical device protection?
Who has to deal with personnel security?
Who contributes to development, testing, maintenance and transition?, and
How do support application providers interact with and support end-application providers?
The enterprise view addresses the relationships and roles throughout system life cycle across installation, operations, maintenance and certification phases. The relationships and roles are depicted on enterprise diagrams.

28. ARC-IT Functional View
ARC-IT Training
June 2017
ARC-IT Functional View
Depicts:
Abstract functional objects (processes)
Flows of data between those processes
Identifies options for…
What functionality is in physical objects?
What are the interfaces between logical objects?
What data flows between those functional objects?
Information Security
Functional View will be added in a future version of ARC-IT
The functional view of ARC-IT defines the functional objects or processes and the data flows between the processes that define the functionality in the architecture. It also identifies the information security that is needed for data exchange.

29. ARC-IT Website http://www.arc-it.net ARC-IT Training June 2017
ARC-IT is available at In the next session of this training, we will take a tour of the website to see how you access information of the four views of ARC-IT.

30. Quiz Match each ARC-IT view with its description.
ARC-IT Training
June 2017
Quiz
Match each ARC-IT view with its description.
Describes the layered sets of protocols that are required to allow physical objects to exchange information
Describes the relationships between organizations and the roles those organizations play within the connected vehicle environment
Describes systems and devices and their application objects as well as the high-level interfaces between the objects
Describes processes and their logical interactions that satisfy the system requirements
Enterprise
Functional
Physical
Communications
Before we conclude this session, let's take a quick quiz. This one addresses the ARC-IT views. Please match the view on the left with its description on the right.

31. Quiz Review Match each ARC-IT view with its description.
ARC-IT Training
June 2017
Quiz Review
Match each ARC-IT view with its description.
Describes the layered sets of protocols that are required to allow physical objects to exchange information
Describes the relationships between organizations and the roles those organizations play within the connected vehicle environment
Describes systems and devices and their application objects as well as the high-level interfaces between the objects
Describes processes and their logical interactions that satisfy the system requirements B
Enterprise
Functional
Physical
Communications D C A
A for Communications view that describes the layered sets of protocols that are required to allow physical objects to exchange information.

32. Review Session Outcomes
ARC-IT Training
June 2017
Review Session Outcomes
Scope of ARC-IT
ARC-IT Views
Key components of Views
ARC-IT consists of four views: the physical, enterprise, functional and communications views.
The key view that most people will use is the Physical View which is made up of physical objects, functional objects, and information flows which are organized to provide ITS services (through Service Packages).