# Presentation: 157138

## ITS/CVO Architecture Conformance:Interoperability Testing StrategyTable of Contents

- ITS/CVO Architecture Conformance:Interoperability Testing StrategyTable of Contents

- 1	Introduction
- 2	Terminology
- 3	Scope
- 4	Roles and Responsibilities
- 5	Test Environment & Tools
- 6	Test Process
- 7	Key Criteria
- Appendix A  Level 1 Interoperability Test Matrix
- Appendix B  Example of Interoperability Testing Status

- 3.1  Guidelines
- 3.2  Requirements Subject to Interoperability Testing

*Table of Contents *

## The Scope of Interoperability Testing Is Based on Requirements from COACH Part 1

- COACH Chapter 5 - State Systems
- COACH Chapter 6 - CVISN Core Infrastructure Systems
- COACH Chapter 7 - Carrier Systems
- Requirements selected from these chapters address
- Use of standard interfaces between pairs of products or systems
- Functions where dataflow and data usage among several selected products/ systems are essential

*Guidelines*

## Guidelines for Selecting PairwiseInterface Standards Requirements

- Focus on
- Interfaces unique to ITS/CVO
- Newly-developed standards (EDI, DSRC)
- Verify pairs of interfaces between
- Public and private entities
- State and multi-state or national systems

*Guidelines*

## Guidelines for Selecting  End-to-End Interface Requirements

- Focus on
- Geographic interoperability issues
- Domestic electronic screening
- International border crossing
- Functional interoperability issues
- Data meaning and interpretation
- Multi-purpose transponder
- Using interface specifications as a guide, verify end-to-end interfaces in
- Snapshot usage
- Electronic screening systems
- Credentials application
- Inspection reporting

*Guidelines*

## Pairwise Interface Interoperability Test Requirements are Based on Interface Standards

- Verify CVO systems generate transactions that comply with EDI ANSI ASC X12 standards
- TS 150 Tax Rates
- TS 151 IFTA Tax Return Receipt
- TS 285 CV Safety & Credentials Information
- 	 Exchange
- TS 286 CV Credentials
- TS 284 CV Safety Reports
- Verify roadside systems communicate with Commercial Vehicles using DSRC standards
- IEEE P1455, Standard for Message Sets for Vehicle/Roadside Communications
- ASTM ver 7
- ASTM 17.51 Draft, Standard Specification for DSRC Data Link Layer: Medium Access and Logical Link Control
- ASTM PS 111-98, Standard Specification for Dedicated Short Range Communications (DSRC) Physical Layer using Microwave in the 902 to 928 MHz band
- ASTM ver 6
- ASTM Standard for Dedicated, Shortrange, Two-Way Vehicle to Roadside Communications Equipment, Draft 6

*Requirements Subject to Interoperability Testing*

-   TS 813 Electronic Filing of Tax Return Data
-   TS 820 Payment Order/Remittance Advice
-   TS 826 Tax Information Exchange
-   TS 864 Text Message
-   TS 997 Acknowledgment

## End-to-End Tests Demonstrate Conformance to Key Operational Concepts Across Multiple Systems

- Verify that standard identifiers can be recognized, and snapshots accessed successfully
- Verify that selected fields in snapshots are interpreted uniformly
- Verify that required fields in credentials applications are interpreted uniformly
- Verify that inspection reporting is uniform

*Requirements Subject to Interoperability Testing*

- End-to-End Tests provide implicit verification of standards by looking at the overall results from multiple systems working together.
- This contrasts with Pairwise Tests that explicitly test transactions flowing across interfaces.

## The COACH Part 1 Establishes the Basis for Interoperability Testing Criteria

- 	The COACH summarizes key concepts and architectural guidelines for CVISN in a series of checklist tables.  COACH Part 1 defines the CVISN Level 1 Criteria.  Each state assigns a ***commitment level*** and a ***requirements level*** to the conformance criteria items listed in the COACH.
- _Commit Level_ (F/P/N) - the state’s commitment level to the item:
- (F)		This rating indicates a *full* commitment.  At least 80% of the state’s systems involved in the process implied by 	the checklist item are or are intended to be compatible with the checklist item statement.
- (P)		This rating indicates a *partial* commitment.  Between 50% and 80% of the state’s systems involved in the 			process implied by the checklist item are or are intended to be compatible with the checklist item statement.
- (N)		This rating indicates *no* commitment.  Less than 50% of the state’s systems involved in the process implied by 	the checklist are or are intended to be compatible with the checklist statement.

*Requirements Subject to Interoperability Testing*

- _Requirements Level_ (L1/E/C) - the compatibility requirement level assigned to this compatibility criterion by the FHWA CVISN project team
- (L1)	 This rating identifies a CVISN *Level 1* compatibility requirement.
- (E)		 This rating indicates an *enhanced* level of CVISN compatibility.  These items may require a little longer to complete (3-4 years).
- (C)	   This rating indicates a *complete* level of CVISN compatibility.  Satisfying all these provides complete CVISN compatibility.  These items are expected to require a longer-range (5 or more years) time frame.
- States are expected to focus initially on checklist items with an L1 compatibility requirement level rating.

**These requirements form the basis of interoperability testing for Level 1.**

## Interoperability Tests Are Conducted Throughout the Testing Phase

- Pairwise interoperability tests can be conducted early as part of the external interface tests that occur during Product Integration & Test and later to verify operational interfaces.
- End-to-end interoperability tests can be conducted as soon as multiple products or systems pass the relevant pairwise tests.

*Requirements Subject to Interoperability Testing*