Regional ITS Architecture Assessment Checklist - Version 3.0 (5/07)
Architecture Name:
Type of Architecture (e.g. Regional, Statewide, etc):
Date Architecture Developed or Last Updated (mm/yyyy):
Reviewer:
Review Date:
This checklist represents elements of a regional ITS architecture, and includes the requirements of the FHWA Rule and FTA Policy on ITS Architecture and Standards Conformity. The checklist is a tool for assessing the completeness of and identifying improvements to the regional ITS architecture. The questions are listed by main topic area with an area for a reviewer to make an assessment. The "Comments" column allows a reviewer to document any suggestions, notes, strengths, or shortcomings. The "Regional ITS Architecture Guidance" Document, version 2.0 contains information on all the elements shown below, and should be used as a reference document for this checklist. (FHWA-HOP-06-112; EDL #14317, https://ops.fhwa.dot.gov/publications/regitsarchguide/index.htm)
1. Architecture Scope and Region Description
Criteria/Question |
Yes/No/Partly |
Comments |
- Is the region defined geographically? Have boundaries been established such as counties, municipal boundaries, metropolitan areas, statewide, etc.?
|
|
|
- Has a timeframe for the architecture been defined? (For example, 5 or 10 years into the future, or the TIP/STIP or other Capital Plan planning period)?
|
|
|
- Has the range of services included in the regional architecture been defined? Does it seem appropriate given the circumstances?
|
|
|
- Are adjacent/overlapping ITS architectures identified?
|
|
|
2. Stakeholder Identification
Criteria/Question |
Yes/No/Partly |
Comments |
- Are the stakeholders identified in sufficient detail to understand who the players are including agency/department name and jurisdiction?
|
|
|
- Is the range of stakeholders commensurate with the defined scope of the regional architecture?
|
|
|
- Were the key stakeholders involved in the architecture development process?
|
|
|
- Was a champion established, either individual or group, to lead the development of the architecture?
|
|
|
3. System Inventory
Criteria/Question |
Yes/No/Partly |
Comments |
- Has a system inventory been defined that includes a list of applicable regional system elements along with descriptions and assigned stakeholders?
|
|
|
- Have the National ITS Architecture subsystems and terminators been correctly linked to regional elements?
|
|
|
- Does the inventory take into account adjacent regional ITS architectures such as neighboring districts or states.
|
|
|
- (Optional) Does the inventory appropriately map regionally unique elements to user-defined entities that are described in sufficient detail to understand their function?
|
|
|
4. Needs and Services
Criteria/Question |
Yes/No/Partly |
Comments |
- Are transportation needs for the region defined and described? (This could be by reference to another document, e.g. Strategic Plan.)
|
|
|
- Are transportation services, derived from the needs, defined and described?
|
|
|
- Are the services adequately represented in the regional architecture? (i.e. Are services(market packages) identified and linked to inventory elements?)
|
|
|
5. Operational Concept
Criteria/Question |
Yes/No/Partly |
Comments |
- Has an architecture operational concept been described in sufficient detail to understand the roles and responsibilities of the primary stakeholders in the region in the delivery of ITS services?
|
|
|
- Are the roles and responsibilities of the operational concept appropriately reflected in the architecture?
|
|
|
6. Functional Requirements
Criteria/Question |
Yes/No/Partly |
Comments |
- Have high-level functions been defined for each regionally significant element in the architecture?
|
|
|
- Are the requirements unambiguously stated in terms of shall statements or similar language such that the required functions of each system can be easily understood?
|
|
|
7. Interfaces/Information Flows
Criteria/Question |
Yes/No/Partly |
Comments |
- Are information flows defined between elements with descriptions of the information exchanged and their deployment status (existing, planned, etc.)?
|
|
|
- Does the architecture include appropriate linkages to elements outside the region or to elements from overlapping or adjacent regional architectures?
|
|
|
- Does the architecture address the significant integration opportunities implied by the inventory, needs/services, and the operational concept?
|
|
|
- (Optional) Does the architecture consider regionally unique interfaces (defined via user-defined flows) and are they described in sufficient detail to understand their purpose?
|
|
|
8. Project Sequencing
Criteria/Question |
Yes/No/Partly |
Comments |
- Have projects been defined to include the agencies involved, timeframe, and how each is tied to the regional architecture?
|
|
|
- Have the relationships to the regional architecture and the interdependencies between projects been defined?
|
|
|
- Has an initial sequencing of currently defined projects been established?
|
|
|
- (Optional) Have opportunities to coordinate implementation schedules with other transportation improvements been investigated?
|
|
|
9. Agreements
Criteria/Question |
Yes/No/Partly |
Comments |
- Have existing interagency agreements in the region been identified/considered by the regional architecture?
|
|
|
- Have future agreements been identified to implement the regional architecture and support project interoperability?
|
|
|
10. Standards Identification
Criteria/Question |
Yes/No/Partly |
Comments |
- Has a plan been documented for how ITS standards will be considered, selected, and/or applied across the region?
|
|
|
- Has a listing of ITS standards been generated and tailored that are applicable to the region and projects coming out of the regional ITS architecture?
|
|
|
- Are these standards associated with specific interfaces (information flows or interconnects)?
|
|
|
- Do the important/relevant ITS standards appear to be identified?
|
|
|
11. Using the Regional ITS Architecture
Criteria/Question |
Yes/No/Partly |
Comments |
- Is the architecture output presented in a way that is understandable to a variety of audiences, including the public and decision-makers?
|
|
|
- Is there a detailed description for incorporating and using the regional ITS architecture in the regional and/or statewide planning process?
|
|
|
- Has a regional stakeholder organization or committee been identified to monitor and manage the use of the architecture in the planning process?
|
|
|
- Is the relationship between the regional ITS architecture and the project implementation process well defined?
|
|
|
12. Maintenance Plan
Criteria/Question |
Yes/No/Partly |
Comments |
- Is there a specific documented plan for maintaining the architecture, including how changes are evaluated, who is involved, what configuration control processes are in place, and when/how often updates are made?
|
|
|
- Have the various reasons for updating the architecture been addressed (project updates, new requirements or initiatives, etc.)?
|
|
|
- Is there a plan for communicating changes in the architecture to stakeholders?
|
|
|
- Have the responsibilities of the various stakeholders or groups been well defined with respect to architecture maintenance?
|
|
|
- Is configuration control being used for the architecture outputs (e.g. version numbering schemes, naming conventions, date/time stamps, etc.)?
|
|
|
|