Scope Page 7 - 1

1
S1 Welcome and Introduction S2 Deployment State
CVISN System Design S3 System Design Guidelines/
Pre-Work Review S4 Panel Discussion S5 Safety
Information Exchange S6 Credentials
Administration S7 Conformance Assurance
Process/Questions S8 Electronic
Screening S9 Scope Workshop Recap S10 Work
Session Consultation S11 State
Presentations S12 Feedback and Next Steps
Session 7 Conformance Assurance Process/ Questions
2
Session Plan

• What is architecture conformance (15)
• What documents and tools are available to help
  you (5)
• What process should you follow to assure
  conformance (5)
• Interoperability testing (10)
• Questions (20)
• Total Time 60 min (1 hr)

3
Session Objectives

• Understand what you need to do to conform with
  the architecture
• Understand interoperability testing

4
Conformance with the architecture and standards
is necessary to achieve interoperability. All of
us want to maximize the benefits realized from
ITS deployments.
An example Without architecture consistency,
this is what might happen in two separate
deployments for Vehicle Safety Information
Exchange. One deployment cant use the others
data, because the information is indexed on a
different identifier.
Vehicle ID in the National Safety Database
Manufacturers VIN only
Oops!
Vehicle ID in My States Roadside Electronic
Screening Process License Plate Number only
Following the architecture and standards assures
that different deployments match up!
Architecture Conformance
5
Legislative mandate and Final Rule

• TEA-21 (section 5206(e)) requires that ITS
  projects using Highway Trust Funds conform with
  the architecture.
• A Final Rule was published in the Federal
  Register on January 8, 2001
• Intelligent Transportation System Architecture
  and Standards (docket ID 5899)

Architecture Conformance
6
Architecture Conformance Final Rule Highlights

• Regions must develop Regional ITS Architectures.
• The policy statement final rule reemphasizes that
  ITS Projects are included in the federal planning
  requirements, under 23 CFR part 450, thus they
  must be part of the planning process.
• Require that recipients of Highway Trust Funds
  use US DOT-adopted standards and interoperability
  tests.
• Adopt specific standards and interoperability
  tests through rulemaking after they have matured.
  

Architecture Conformance
7
Architecture Conformance Integrate CVISN with
Other Transportation Activities

• It is important that you integrate your CVISN
  plans with other transportation plans in the
  state/region.
• Ensure that CVISN architecture is consistent with
  statewide/regional ITS architecture
• Some states are developing regional architectures
  using the Turbo Architecture tool.
• The tool is a planning and integration aid
  intended to facilitate usage of the National ITS
  Architecture.
• More on the integration process on subsequent
  slides. . .

Architecture Conformance
8
Architecture Conformance What You Need To Do

• Related to ensuring consistency with the National
  ITS Architecture, on an annual basis states
  should
• Contact State and local transportation officials
  to explore potential joint-uses of transponders
  and ensure integration among multiple
  applications (i.e., CVO, toll, traffic probes,
  etc.)
• Evaluate the data that is being collected for
  CVISN initiatives to determine if other State and
  local transportation entities (e.g., TMC) outside
  the CVO community could use the data which is
  collected under CVISN deployment, consistent with
  data privacy agreements (Archived Data User
  Service).
• Conduct outreach to its motor carrier partners
  about metropolitan and rural ITS initiatives
  within the State that could provide benefits to
  its motor carrier operations. Examples of these
  initiatives include web sites on roadway weather
  information systems, incident management systems,
  etc.
• As part of post-work for Scope Workshop, submit
  to FMCSA a letter documenting these efforts.

Architecture Conformance
9
Architecture Conformance What You Need To Do

• Prior to the formal adoption of standards and
  interoperability tests, you should use the
  available recommended standards and
  interoperability tests.
• You should require adherence to the CVISN Level 1
  standards in all requests for proposal that are
  issued.
• In all requests for proposal that are issued, you
  should require demonstration of technical
  interoperability through the execution of the
  standard interoperability tests.

Architecture Conformance
10
Architecture Conformance What You Need To Do

• Use the COACH (all parts) to track your own
  compliance with the CVISN architecture and
  standards recommendations.
• Maintain a Business Plan that encompasses all
  ITS/CVO activities in the state or region.
• Complete and maintain a Program Plan that
  encompasses all CVISN projects or efforts in the
  state or region.
• Complete and maintain a State Top-Level Design
  that describes the top-level design for all
  planned changes or additions to CVISN-related
  systems or products.

Architecture Conformance
11
Architecture Conformance What You Need To Do

• Follow the ITS/CVO Architecture Conformance
  Assurance Process.
• Use the available documents and tools.
• Participate in the FMCSAs configuration
  management process for the CVISN Architecture.
• Take advantage of available technical resources
  and lessons learned (e. g., ITS/CVO Deployment
  Forums, Peer-to-Peer Program, CVISN State
  experts, etc.).

Architecture Conformance
12
Architecture Conformance What You Need To
DoSummary

• Work with stakeholders to
• Ensure ITS/CVO systems are interoperable at the
  operational level.
• Ensure ITS/CVO systems are interoperable at the
  program administration level.
• Developers/operators of these systems
• Toll Administration
• Toll Collection
• Parking Management
• Roadway
• Archived Data Management
• Information Service Provider
• Emergency Management

Architecture Conformance
13
States are encouraged to use these documents and
tools with their ITS/CVO Projects

• CVISN Operational and Architectural Compatibility
  Handbook (COACH)
• Part 1 - Operational Concept and Top-Level Design
  Checklists
• Part 2 - Project Management Checklists
• Part 3 - Detailed System Checklists
• Part 4 - Interface Specification Checklists
• Part 5 - Interoperability Test Criteria
• CVISN System Design Description
• Sample technical and management documents

Recently updated or not out of date
Useful version available Update in progress
Draft in development
Documents and Tools
14
States are encouraged to use these documents and
tools with their ITS/CVO Projects

• Guide to Developing a State ITS/CVO Business Plan
• Conformance Assurance Process (CAP) Description
• Interoperability Test Suite Package
• Part 1 Test Specifications
• Part 2 Test Cases Procedures
• Part 3 Test Tool Description
• Part 4 Test Data

Recently updated or not out of date
Useful version available Update in progress
Draft in development
Documents and Tools
15
States are encouraged to use these documents and
tools with their ITS/CVO Projects

• CVISN Guides
• Management Guides
• Introductory Guide to CVISN
• CVISN Guide to Program Project Planning
• CVISN Guide to Phase Planning Tracking
• Technical Process Guides
• CVISN Guide to Top-Level Design
• CVISN Guide to Integration Test
• Technical Application Guides
• CVISN Guide to Safety Information Exchange
• CVISN Guide to Credentials Administration
• CVISN Guide to Electronic Screening

Recently updated or not out of date
Useful version available Update in progress
Draft in development
Documents and Tools
16
Each part of the COACH supports the CVISN
workshop series and implementation of a states
CVISN project
(ITS/CVO Training Courses)
Scope Workshop
Design Workshop
Planning Workshop
(Implementation)
COACH Part 2 Project Management Checklists
COACH Part 1 Operational Concept and
Top-Level Design Checklists
COACH Part 5 Interoperability Test Criteria
COACH Part 3 Detailed System Checklists
COACH Part 4 Interface Specification Checklists
Documents and Tools
17
How The Tools Workshops Relate
Workshops Implementation
Guides
CVISN Tool Kit

• State Lessons Learned
• ID White Paper
• Snapshot White Paper
• Glossary

COACH Part 1

• Introductory Guide to CVISN
• CVISN Guide to Top-Level Design

Scope
Product Preliminary Top-Level Design
COACH Part 2

• CVISN Guide to Program Project Planning
• CVISN Guide to Phase Planning Tracking

Planning

• Sample Project Plans
• Vendor Lists

Product Preliminary Program Plan

• EDI Stds IGs
• DSRC Stds IGs
• CARS
• SAFER/CVIEW Reqts Design Docs
• Sample Design Docs

• CVISN Guide to Safety Information Exchange
• CVISN Guide to Credentials Administration
• CVISN Guide to Electronic Screening

COACH Parts 3 4
Design
Product Updated Top-Level Design
COACH Part 5

• Sample Test Plans
• Interoperability Test Suite Package
• Sample OM Plans

• CVISN Guide to Integration Test

Implementation
Documents and Tools
18
The Conformance Assurance Process
checkpointsITS/CVO deployment throughout the
lifecycle
Deployment Cycle
Checkpoints
MOA Requirements Definition
Start Verify commitment to principles
Project Planning, Review Top-Level Design
Definition Verify plan is sound and top-level
design is consistent
Top-Level Design
Detailed design for Phase n - Verify detailed
design is consistent
Detailed Design
Interoperability Testing at end of Phase n
- Test that systems meet standards and are
interoperable
Implementation
Test
Conformance Assurance Process
19
The Conformance Assurance Process (CAP)
Description will provide details

• Will identify conformance criteria for each
  checkpoint
• Defines conformance measurement and evaluation
  tools, based on the COACH

Conformance Assurance Process
20
A Conformance Assessment Team (COAT) supports the
Conformance Assurance Process for each project
The COAT makes sure the project conforms with the
architecture and standards.

• The COAT Includes
• State CVISN System Architect
• FMCSA Division Office ITS/CVO Specialist
• FMCSA Service Center ITS/CVO Specialist
• Architecture Standards Expert

State CVISN System Architect has dual role as
part of the development team and leader of the
COAT.
Conformance Assurance Process
21
The COAT checks for conformanceat each checkpoint
COAT Task
Deployment Cycle
Checkpoints
MOA Requirements Definition
Start Verify commitment to principles
Review completed COACH Part 1
Project Planning, Review Top-Level Design
Definition Verify plan is sound and top-level
design is consistent
Review Program Plan Top-Level Design
Top-Level Design
Detailed design for Phasen -Verify detailed
design is consistent
Detailed Design
Review Detailed Design
Interoperability Testing at end of Phase n
- Test that systems meet standards and are
interoperable
Help Tailor Tests Analyze Interoperability
Test Results
Implementation
Test
Conformance Assurance Process
22
What we mean by interoperability/acceptance
testing

• These tests are standardized in the sense that
  they are
• Developed once, used by many
• Used for initial and regression testing
• Tests establish criteria for what it means to
  meet specific standards
• The tests can be used to support both
  Interoperability and Acceptance Testing
• End-to-End tests demonstrate functional
  capability and data integrity across systems
• Improve quality of systems being delivered

Interoperability Testing
23
FMCSA supports the development and maintenance of
the interoperability tests. States execute the
tests.
Interoperability Test Suite Package
Develop CVISN Test Facility
Define Interoperability Test Scenarios
Define Test Cases and Procedures
Develop Test Tools
Develop Test Data
JHU/ APL
Validate Tests in CVISN Test Facility
Schedule Interoperability Tests
Tailor Test Procedures and Data
Execute Tests
Evaluate Tests
States Carriers
AS Expert
AS Expert
AS Expert An Architecture Standards Expert
provides support to help assess whether the
system is in conformance.
Schedule CVISN Test Facility
Support Test Execution
JHU/ APL
Interoperability Testing
24
When? Conduct interoperability tests 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
  have passed the relevant pairwise tests, and you
  are ready to demonstrate that they work together.

Interoperability Testing
25
Interoperability Testing What FMCSA Provides

• FMCSA intends to support interoperability testing
  through 2003
• FMCSA plans to provide
• Limited technical assistance
• CVISN Test Facility
• Test documentation (criteria, scenarios,
  procedures, data) is available from the CVISN Web
  site http//www.jhuapl.edu/cvisn/

Interoperability Testing
26
Interoperability Testing What You Should Do

• Plan to conduct interoperability tests as part of
  the acceptance testing process.
• To get a handle on the planning aspects, you
  might want to consider consulting with other
  states about their experiences.

Interoperability Testing
27
Many interoperability tests are available now

• Accept process electronic IRP IFTA credential
  applications (EP)
• Accept process web-based IRP IFTA credential
  applications (E)
• Accept electronic filing of and payment for IFTA
  quarterly tax returns (EP)
• Screen vehicles electronically at a
  weigh/inspection site, using snapshot data and
  different kinds of transponders (EP)
• Update snapshot segment via CVIEW (P)
• Query for snapshot (P)
• Receive snapshot subscription from SAFER (P)
• Report inspection (EP)
• Query for inspection report (P)
• E end-to-end test involving multiple systems
• P pairwise test focusing on use of standard
  interchanges between two systems.

Interoperability Testing
28
Additional tests are planned for future
development

• As many tests as needed for XML interfaces that
  are developed in the safety realm (potential
  examples SAFER-CVIEW snapshots, ASPEN-SAFER
  snapshots or inspections, etc.)
• As many tests as needed for XML interfaces that
  are developed in the credentials realm (potential
  examples carrier-state IRP application
  response, carrier-state permit application
  response)

Interoperability Testing
29
Questions?
Questions
30
This Page Intentionally Blank