Safety Information Exchange Pairwise Tests by c7GYv3

VIEWS: 4 PAGES: 84

									ITS/CVO Interoperability Test Suite Package – Part 2




                                                                                                        Formatted: Bullets and Numbering
3.  SAFETY INFORMATION EXCHANGE PAIRWISE
INTERFACE TESTS
Throughout this section of this document (Part 2, Chapter 3, Safety Information Exchange
Pairwise Interface Tests) and in Part 2, Chapter 4 (End-to-End Interface Tests) there are
references to the use of the “State CVIEW” System. These references are referring to the
CVIEW System used by the State being tested. It may be the FMCSA developed CVIEW or
some other CVIEW equivalent developed by the state that performs the same functions. If
necessary,

TThe APL Test Facility can provide interfaces to either a test CVIEW (APL CVIEW) or a test
SAFER System (APL SAFER) for purposes of testing a roadside screening system or a state
CVIEW. References to the APL CVIEW or APL SAFERtest facility will use this terminology.
The ASPEN System utilizes an ASPEN-Unique, non-EDI file format, also called a Custom
Interface Agreement (CIA). As states migrate to 32-bit ASPEN units, the test procedures will be
updated to reflect a change to Application File Format (AFF) a precursor to EDI translation.

Note: There are references to TS 824 and TS 997 in these procedures; however, these
transaction sets will not be supported until the release of CVIEW 3.0. Test case data sets
referred to in the following procedures are provided in Part 4 of the Interoperability Test Suite
Package.                                                                                                Formatted


3.1 State Deskside – APL SAFER (i.e., CVIEW or equivalent –
SAFER) Snapshot Scenarios


3.1.1 SCENARIO ID PW-SAFE-01: CVIEW SENDS A VEHICLE SNAPSHOT
SEGMENT UPDATE TO APL SAFER (IRP SUPPLEMENTAL: ADD VEHICLE)

In order to initiate the subscription process and test the ability of the CVIEW to create a TS 285
snapshot segment update for the APL SAFER, CVIEW must first receive the snapshot segment
update from some source. Normally, this would be from the IRP legacy system for a change in
vehicle or carrier IRP registration status. For this test, a snapshot segment update that includes
the IRP supplemental test data for a vehicle will be inserted into the CVIEW via a test tool or via
email to the CVIEW inbox. This will trigger the subscription process and CVIEW will create
the TS 285 and send it to the APL SAFER data mailbox on the CVIEW system.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                 Page 3–1
ITS/CVO Interoperability Test Suite Package – Part 2




TEST MATRIX:

            Test                 Error Type                            Expected Results
            Case
                        No          EDI         Data
                        Errors      Syntax      Error
                                    Error
           3.01.01      X                               SAFER updates vehicle snapshot based on
                                                        snapshot segment input from CVIEW.CVIEW
                                                        receives a TS 824 from the APL SAFER.
           3.01.02                  X                   CVIEW receives a Functional
                                                        Acknowledgement TS 997 Negative message
                                                        from SAFER.
           3.01.03                              X       CVIEW receives an Application Advice TS 824
                                                        Error message from APL SAFER.



TEST CONFIGURATIONS:

        • APL Facility Requirements                                                                              Formatted: Bullets and Numbering
             Facility is equipped with software, hardware, and communications sufficient to
               manage the test execution. APL SAFER server is set up to conduct the test.
               Subscriptions for the APL SAFER have been established with the State CVIEW
               under test to include the vehicle in the test dataset. The APL SAFER System is
               configured to poll its mailbox on the State CVIEW System on a regular basis. For
               the purposes of this test, the polling interval should be set to every five minutes.
               The system is configured to save all incoming transactions to a directory.
        • User Facility Requirements                                                                             Formatted: Bullets and Numbering
             State CVIEW is set up to conduct the test. APL SAFER sSubscriptions hasve been
               established with SAFERon CVIEW. Communications are directed towards APL
               SAFER. Data from IRP activities, matching test cases,Test data are available in a
               format compatible with CVIEW..
        • Test Roles                                                                                             Formatted: Bullets and Numbering
             The three key test roles necessary to execute tests using this Test Configuration
               include: the CVIEW System Operator, the Master Test Conductor, and the Test
               Analyst. Make the necessary number of copies of the Test Procedures for each test
               participant.
                                                                                                                 Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         CVIEW and APL SAFER Systems. Out-of-date snapshot(s) corresponding to test case
         data already exist on both CVIEW and APL SAFER.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                      Baseline Version V1.0                   Page 3–2
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.01.01, CVIEW Sends a Vehicle Snapshot Segment Update to APL SAFER
(IRP Supplemental: Add Vehicle), No Errors


Test Summary
Testing the State CVIEW System: the State CVIEW System sends a vehicle snapshot segment
update to the APL SAFER System that includes IRP Supplemental information. The APL
SAFER System receives the vehicle snapshot segment update and updates its database with the
informationsends a TS 824 to the CVIEW system. The APL SAFER System is used.

Purpose
Verify that the State CVIEW sends a TS 285 snapshot segment update to APL SAFER when a
vehicle snapshot changes as a result of IRP data updates, and that APL SAFER acknowledges
receiving the information.

Test Case Initial Conditions
This test of the CVIEW System assumes that IRP Supplemental (Add Vehicle) processing has
already been completed. A snapshot for the vehicle being added to the fleet in one or more
jurisdictions should already exist in CVIEW and APL SAFER’s databases. The data for the IRP
Supplemental application that is to be included/updated in the vehicle snapshot will be input to
CVIEW according to whatever means the state is usingvia a test tool or via email to the CVIEW
inbox. The data will match that specified in test case data set 3.01.01. Test Case 3.01.01
represents a standard snapshot segment update with no errors.

Acceptance Criteria
1. 1. SAFER receives a valid TS 285 in one mail message for a vehicle snapshot segment                 Formatted: Bullets and Numbering
    update from CVIEW.CVIEW creates a TS 285 snapshot segment update and sends it to the
    APL SAFER data mailbox on the CVIEW system.
2. 2. CVIEW receives a TS 824 from APL SAFER.
3. 3. CVIEW sends a TS 997 to SAFER in response to TS 824.
4. 4. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                Page 3–3
ITS/CVO Interoperability Test Suite Package – Part 2




Test Procedures for Test 3.01.01
See Tables 3–1 , 3-2, 3-3 for the Master, CVIEW, and SAFER Test Procedures, respectively.
Note that some transaction sets are starred () in the Master Test Conductor Procedure Table
(under Master Test Criteria). The Test Analyst will examine these starred transaction sets for
conformance with the CVISN architecture in post-test evaluation. Operator Actions are
indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–1.
                                Test 3.01.01: Master Test Conductor Procedure

  Step               System or Operator Action                      Master Test Criteria     Pass/
                                                                                              Fail
     1       The Test Conductor inserts the IRP (add         None
             vehicle) data into CVIEW as a TS 285 in
             an email message or via a test tool.The
             MD IRP Operator properly configures
             and sends/transfers both the LSI kick-
             off message file and the IRP data file to
             the State CVIEW System.
             Note: Test Case Data Set 3.01.01
             contains the nominal parameters
     2       The State CVIEW System recognizes the           None
             files in the appropriate directoryinput data
             as an update and processes the MD IRP
             data file. The subscription process is
             triggered.
     3       The State CVIEW System sends the                None The State CVIEW
             TS 285 message to the APL SAFER data            System sends the TS 285 EDI
             mailbox on the CVIEW system.The APL             message and the APL SAFER
             SAFER System has a vehicle snapshot             System receives the TS 285
             subscription set up on the State CVIEW          EDI. This message is in the
             System. This vehicle snapshot                   form of a vehicle snapshot
             subscription must contain at least one          segment update (TS 285 EDI).
             vehicle in the MD IRP data file.                
             [note: The SAFER mailbox on CVIEW is
             SAFER and the password is SAFER.]
    54       The APL SAFER System polls its mailbox          The APL SAFER System
             on the State CVIEW System and                   retrieves (receives) its mail
             determines that it has new mail (the            from the State CVIEW System
             TS 285 EDI message) in its mailbox.             and processes the message(s)
                                                             (TS 285). The APL SAFER
                                                             System then retrieves
                                                             (receives) its mail from the
                                                             State CVIEW System and
                                                             processes the message(s) (TS
                                                             285 EDI). 
    58       The APL SAFER System completes                  The State CVIEW System
             processing the TS 285 sent by the State         receives the TS 824.
             CVIEW System and transmits a TS 824
             Accepted.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                    Baseline Version V1.0              Page 3–4
ITS/CVO Interoperability Test Suite Package – Part 2




  Step               System or Operator Action                    Master Test Criteria      Pass/
                                                                                             Fail
    69       The State CVIEW System processes the           SAFER receives TS 997
             TS 824 Accepted received from the APL          Positive from CVIEW,
             SAFER System and transmits a positive          acknowledging receipt of
             TS 997.                                        TS 824. 
   107       The Test Analyst should use a database         Updated vehicle snapshot
             utility to verify that the vehicle snapshot    records in database should be
             records were updated in both the State         verified. 
             CVIEW and APL SAFER databases.
Table 3 – 1.
Test 3.01.01 Procedures: State CVIEW Procedure
 Maste System or Operator Action                 CVIEW Test Criteria                         Pass/
 r Step                                                                                      Fail
 1        The MD IRP Operator properly
          configures and sends/transfers both
          the LSI kick-off message file and the
          IRP data file to the State CVIEW
          System.
          Note: Test Case Data Set 3.01.01
          contains the nominal parameters
 2        The State CVIEW System recognizes
          the files in the appropriate directory
          and processes the MD IRP data file.
 9        The State CVIEW System processes       SAFER receives TS 997 Positive
          the TS 997 Positive and the TS 824     from CVIEW, acknowledging
          Accepted received from the APL         receipt of TS 824. 
          SAFER System.
 10       The Test Analyst should use a          Updated vehicle snapshot records in
          database utility to verify that the    database should be verified. 
          vehicle snapshot records were
          updated in both the State CVIEW and
          APL SAFER databases.

Table 3 – 2.
Test 3.01.01 Procedures: APL SAFER Procedure
 Maste System or Operator Action                 SAFER Test Criteria                         Pass/
 r Step                                                                                      Fail
 3        The APL SAFER System has a             The State CVIEW System sends the
          vehicle snapshot subscription set up   TS 285 EDI message and the APL
          on the State CVIEW System. This        SAFER System receives the TS 285
          vehicle snapshot subscription must     EDI. This message is in the form of
          contain at least one vehicle in the MD a vehicle snapshot segment update
          IRP data file.                         (TS 285 EDI). 
          [Note: The SAFER mailbox on



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                   Baseline Version V1.0              Page 3–5
ITS/CVO Interoperability Test Suite Package – Part 2




 Maste       System or Operator Action                 SAFER Test Criteria                      Pass/
 r Step                                                                                         Fail
             CVIEW is SAFER and the password
             is SAFER.]
 4           The APL SAFER System is
             configured to poll its mailbox on the
             State CVIEW System on a regular
             basis. For the purposes of this test,
             the polling interval should be set to
             every five minutes. The actual
             polling interval is more likely to be
             approximately every day or twice a
             day.
 5           The APL SAFER System polls its            The APL SAFER System then
             mailbox on the State CVIEW System         retrieves (receives) its mail from the
             and determines that it has new mail       State CVIEW System and processes
             (the TS 285 EDI message) in its           the message(s) (TS 285 EDI). 
             mailbox.
 6           The APL SAFER System transmits a          The APL SAFER System transmits
             TS 997 Positive and a TS 824              the TS 997 and the State CVIEW
             Accepted to the State CVIEW               System receives the TS 997.
             System.
 7           The APL SAFER System then
             updates its local database with this
             new vehicle information (State IRP
             snapshot segment update).
 8           The APL SAFER System completes            The State CVIEW System receives
             processing the TS 285 sent by the         the TS 824.
             State CVIEW System and transmits a
             TS 824 Accepted.




Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                    Page 3–6
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.01.02, CVIEW Sends a Vehicle Snapshot Segment Update to APL SAFER
(IRP Supplemental: Add Vehicle), EDI Syntax Error in Snapshot


Test Summary
Testing the State CVIEW System: the State CVIEW System sends a vehicle snapshot segment
update to the APL SAFER System that includes IRP Supplemental information. The APL
SAFER System receives the vehicle snapshot segment update and detects an EDI syntax error in
the snapshot segment. APL SAFER responds to CVIEW with a negative message TS 997
acknowledgment indicating an EDI syntax error. The APL SAFER System is used.

Purpose
Verify that the State CVIEW sends a snapshot segment update to SAFER when a vehicle
snapshot changes as a result of IRP data updates and that SAFER can properly handle the
response to a syntactically incorrect EDI message.

Test Case Initial Conditions
This test of the CVIEW System assumes that IRP Supplemental (Add Vehicle) processing has
already been completed. A snapshot for the vehicle being added to the fleet in one or more
jurisdictions should already exist in CVIEW’s database. The data for the IRP Supplemental
application that is to be included/updated in the vehicle snapshot will be input to CVIEW via a
test tool or email.according to whatever means the state is using. The data will match that
specified in test case data set 3.01.02. Test Case 3.01.02 represents a standard snapshot segment
update with an EDI syntax error.

Acceptance Criteria
2. 1.    CVIEW receives a TS 997 EDI Invalid message from SAFER.                                       Formatted: Bullets and Numbering
3. 2.    All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedures for Test 3.01.02
See Tables 3–42 , 3-5, 3-6 for the Master Test Conductor Procedure s, respectively. Note that
some transaction sets are starred () in this table (under Master Test Criteria). The Test Analyst
will examine these starred transaction sets for conformance with the CVISN architecture in post-



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                Page 3–7
ITS/CVO Interoperability Test Suite Package – Part 2




test evaluation. Operator Actions are indicated in bold print, whereas, System Actions are not in
bold print.
                                                  Table 3–2.
                                Test 3.01.02: Master Test Conductor Procedure

  Step              System or Operator Action                      Master Test Criteria            Pass/
                                                                                                    Fail
     1       The Test Conductor inserts the IRP           None
             (add vehicle) data into CVIEW as a
             TS 285 in an email message or via a
             test tool. APL SAFER operation has
             SAFER service turned off.The MD IRP
             Operator properly configures and
             sends/transfers both the LSI kick-off
             message file and the IRP data file to
             the State CVIEW System.
             Note: Test Case Data Set 3.01.02
             contains the nominal parameters
     2       The State CVIEW System recognizes the        None
             files in the appropriate directory and
             processes the MD IRP data file.
     3       The State CVIEW System sends the             The State CVIEW System sends the
             TS 285 message to the APL SAFER              TS 285 EDI message and the APL
             data mailbox on the CVIEW system.The         SAFER System receives the TS 285
             APL SAFER System has a vehicle               EDI. This message is in the form of a
             snapshot subscription set up on the          vehicle snapshot segment update (TS
             State CVIEW System. This vehicle             285 EDI).  None
             snapshot subscription must contain at
             least one vehicle in the MD IRP data file.
             [note: The SAFER mailbox on CVIEW is
             SAFER and the password is SAFER.]
     4       The Test Conductor uses an email             None
             tool such as Eudor Mail to open
             SAFER’s data mail box on CVIEW,
             retrieve the TS 285 (deleting it from the
             CVIEW server), edit the EDI to include a
             syntax error, and resend it to SAFER’s
             data mail box on CVIEW. Test
             Conductor turns SAFER system ON.
     5       The APL SAFER System polls its               None The APL SAFER System then
             mailbox on the State CVIEW System and        retrieves (receives) its mail from the
             determines that it has new mail (the         State CVIEW System and processes
             TS 285 EDI message) in its mailbox.          the message(s) (TS 285 EDI). 
     6       The APL SAFER System processes the           The APL SAFER System transmits the
             TS 285 with the syntax error and             TS 997 and the State CVIEW System
             transmits a TS 997 Negative to CVIEW.        receives the TS 997.
     7       The Test Analyst should use a                Updated vVehicle snapshot records in
             database utility to verify that the          the database should be reviewed to
             vehicle snapshot records were not            verifyi that they were not updated. 
             updated in either the State CVIEW or




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                  Baseline Version V1.0                    Page 3–8
ITS/CVO Interoperability Test Suite Package – Part 2




  Step              System or Operator Action                   Master Test Criteria   Pass/
                                                                                        Fail
             APL SAFER databases.
Table 3 – 3.
Test 3.01.02 Procedures: State CVIEW Procedure
 Maste System or Operator Action                 CVIEW Test Criteria                   Pass/
 r Step                                                                                Fail
 1        The MD IRP Operator properly
          configures and sends/transfers both
          the LSI kick-off message file and the
          IRP data file to the State CVIEW
          System.
          Note: Test Case Data Set 3.01.02
          contains the nominal parameters
 2        The State CVIEW System recognizes
          the files in the appropriate directory
          and processes the MD IRP data file.
          The State CVIEW System Operator
          should modify the TS 285 EDI
          message so as to include a syntactical
          error in the mail message.
          The way to do this is to delete the
          “BGN … ET” line in the message.
 7        The Test Analyst should use a          Updated vVehicle snapshot records
          database utility to verify that the    in the database should be reviewed
          vehicle snapshot records were not      to verifyi that they were not
          updated in both the State CVIEW and updated. 
          APL SAFER databases.


Table 3 – 4.
Test 3.01.02 Procedures: APL SAFER Procedure
 Maste System or Operator Action                 SAFER Test Criteria                   Pass/
 r Step                                                                                Fail
 3        The APL SAFER System has a             The State CVIEW System sends the
          vehicle snapshot subscription set up   TS 285 EDI message and the APL
          on the State CVIEW System. This        SAFER System receives the TS 285
          vehicle snapshot subscription must     EDI. This message is in the form of
          contain at least one vehicle in the MD a vehicle snapshot segment update
          IRP data file.                         (TS 285 EDI). 
          [note: The SAFER mailbox on
          CVIEW is SAFER and the password
          is SAFER.]
 4        The APL SAFER System is
          configured to poll its mailbox on the


4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0           Page 3–9
ITS/CVO Interoperability Test Suite Package – Part 2




 Maste       System or Operator Action                 SAFER Test Criteria                      Pass/
 r Step                                                                                         Fail
             State CVIEW System on a regular
             basis. For the purposes of this test,
             the polling interval should be set to
             every five minutes. The actual
             polling interval is more likely to be
             approximately every day or twice a
             day.
 5           The APL SAFER System polls its            The APL SAFER System then
             mailbox on the State CVIEW System         retrieves (receives) its mail from the
             and determines that it has new mail       State CVIEW System and processes
             (the TS 285 EDI message) in its           the message(s) (TS 285 EDI). 
             mailbox.
 6           The APL SAFER System transmits a          The APL SAFER System transmits
             TS 997 Negative.                          the TS 997 and the State CVIEW
                                                       System receives the TS 997.




Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                    Page 3–10
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.01.03, CVIEW Sends a Vehicle Snapshot Segment Update to APL SAFER
(IRP Supplemental: Add Vehicle), Data Contents Error in Snapshot


Test Summary
Testing the State CVIEW System: the State CVIEW System sends a vehicle snapshot segment
update to the APL SAFER System that includes IRP Supplemental information. The APL
SAFER System receives the vehicle snapshot segment update and detects a data contents error in
the snapshot segment. SAFER responds to CVIEW with a message TS 824 transaction
indicating that the snapshot segment was in error. The APL SAFER System is used.

Purpose
Verify that the State CVIEW sends a snapshot segment update to SAFER when a vehicle
snapshot changes as a result of IRP data updates and that SAFERcan properly handle a TS 824
data error message from the APL SAFER.in the EDI message.

Test Case Initial Conditions
This test of the CVIEW System assumes that IRP Supplemental (Add Vehicle) processing has
already been completed. A snapshot for the vehicle being added to the fleet in one or more
jurisdictions should already exist in CVIEW’s database. The data for the IRP Supplemental
application that is to be included/updated in the vehicle snapshot will be input according to
whatever means the state is usingvia a test tool or email. The data will match that specified in
test case data set 3.01.03. Test Case 3.01.03 represents a standard snapshot segment update with
a data contents error.

Acceptance Criteria
3. 1.    CVIEW receives a TS 824 from SAFER rejecting the update.                                      Formatted: Bullets and Numbering
4. 2.    All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedures for Test 3.01.03
See Tables 3–37, 3-8, 3-9 for the Master Test Conductor Procedure Table, respectively. Note
that some transaction sets are starred () in this table (under Master Test Criteria). The Test
Analyst will examine these starred transaction sets for conformance with the CVISN architecture



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–11
ITS/CVO Interoperability Test Suite Package – Part 2




in post-test evaluation. Operator Actions are indicated in bold print, whereas, System Actions
are not in bold print.
                                                  Table 3–3.
                                Test 3.01.03: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria          Pass/
                                                                                                 Fail
     1       The Test Conductor inserts the IRP          None
             add vehicle data into CVIEW as a
             TS 285 in an email message or via a
             test tool. APL SAFER service is OFF.
     2       The CVIEW System recognizes the input       None
             data as an update and processes the MD
             IRP data. The subscription process is
             triggered.
     3       The State CVIEW System sends the            None
             TS 285 message to the APL SAFER
             data mailbox on the CVIEW system.
     4       Note: Prior to turning the SAFER system     None
             ON and processing the TS 285, the APL
             SAFER Operator retrieves the
             transaction from its mailbox on
             CVIEW using an email tool such as
             Eudora Mail, and inserts a data error
             into the file. (For instance, by changing
             the view field from Q301 to Q501). The
             APL SAFER operator then re-sends
             the transaction to its mailbox on
             CVIEW and turns the SAFER system
             ON. The APL SAFER System polls its
             mailbox on the State CVIEW System and
             determines that it has new mail (the
             TS 285 message) in its mailbox. The
             APL SAFER System then retrieves
             (receives) its mail from the State CVIEW
             System and processes the message(s)
             (TS 285).
     5       The APL SAFER System completes              The State CVIEW System receives the
             processing the TS 285 sent by the State     TS 824.
             CVIEW System and transmits a TS 824
             Rejected.
     6       The State CVIEW System processes the        SAFER receives TS 997 Positive from
             TS 824 Rejected received from the APL       CVIEW, acknowledging receipt of
             SAFER System and transmits a positive       TS 824. 
             TS 997.
     7       The Test Analyst should use a               Vehicle snapshot records in database
             database utility to verify that the         should be verified as NOT updated.
             vehicle snapshot records were NOT
             updated in either the State CVIEW and
             APL SAFER databases.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                  Page 3–12
ITS/CVO Interoperability Test Suite Package – Part 2




Table 3 – 5.
Test 3.01.03 Procedures: State CVIEW Procedure



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–13
ITS/CVO Interoperability Test Suite Package – Part 2




3.1.2 SCENARIO ID PW-SAFE-08: CVIEW PROCESSES RECEIVES
SUBSCRIPTION UPDATE FOR VEHICLE SNAPSHOTS VIA SAFER FOR AN OUT-
OF-SERVICE (OOS) VEHICLE

For these tests, CVIEW has a subscription on the APL SAFER to receive snapshot updates for
the vehicle in the test data set. In order to initiate the subscription process and test the ability of
the CVIEW to receive a TS 285 snapshot segment update from the APL SAFER, APL SAFER
must first receive a snapshot segment update from some source. Normally this would be from
another CVIEW or the state roadside system for a change in vehicle OOS status. For this test, a
snapshot segment update that includes OOS status for a vehicle will be inserted into the APL
SAFER via a test tool or via email to the APL SAFER inbox. This will trigger the subscription
process and APL SAFER will create the TS 285 and send it to the CVIEW data mailbox on the
APL SAFER system.


TEST MATRIX:

         Test                Error Type                                 Expected Results
         Case
                    No         EDI         Data
                    Errors     Syntax      Error
                               Error
       3.08.01      X                                  SAFER sends CVIEW retrieves and processes a
                                                       Vehicle Snapshot from its APL SAFER data mailbox
                                                       for a recently placed Out-of-Service (OOS) vehicle
                                                       in its subscription list on APL SAFER.
       3.08.02                 X                       CVIEW transmits a Functional Acknowledgement
                                                       TS 997 Negative message to SAFER.
       3.08.03                             X           CVIEW transmits an Application Advice TS 824
                                                       Error message to SAFER.



TEST CONFIGURATIONS:3.08.A STATE CVIEW; APL SAFER

       • APL Facility Requirements                                                                                 Formatted: Bullets and Numbering
           Facility is equipped with software, hardware, and communications sufficient to
              manage the test execution. APL SAFER servers are set up to conduct the test.
              Subscriptions have been established with State CVIEW under test.
       • User Facility Requirements                                                                                Formatted: Bullets and Numbering
           State CVIEW is set up to conduct the test. Subscriptions have been established with
              APL SAFER to include the test vehicle. Communications are directed towards APL
              SAFER.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                        Baseline Version V1.0                  Page 3–14
ITS/CVO Interoperability Test Suite Package – Part 2




        • Test Roles                                                                                 Formatted: Bullets and Numbering
             The three key test roles necessary to execute tests using this Test Configuration
               include: the CVIEW System Operator, the Master Test Conductor, and the Test
               Analyst. Make the necessary number of copies of the Test Procedures for each test
               participant.
                                                                                                     Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         CVIEW and APL SAFER Systems.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–15
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.08.01, CVIEW Receives Subscription Update for Vehicle Snapshots via
SAFER for an Out-of-Service (OOS) VehicleCVIEW Processes Subscription for Vehicle
Snapshots via SAFER for an Out-of-Service (OOS) Vehicle, No Errors


Test Summary
Testing the State CVIEW System: the APL SAFER System sends provides a vehicle snapshot
(for a recently placed OOS vehicle) to the State CVIEW System via the SAFER data mailbox.
The State CVIEW System receives retrieves the vehicle snapshot, responds appropriately to the
APL SAFER system, and updates its database accordingly.

Purpose
Verify that SAFER sends a snapshot to CVIEW when a vehicle snapshot changes as a result of
an Out-of-Service (OOS) Inspection and that CVIEW can receive, process, and respond
appropriately to a snapshot segment update TS 285 transaction for a vehicle placed
OOS.acknowledges receiving the information.

Test Case Initial Conditions
This test of the CVIEW System assumes that an OOS Inspection Report has been prepared and is
already to been sent to the APL SAFER SystemThis test requires that APL SAFER has
processed information about an OOS vehicle that already exists in the APL SAFER (and
CVIEW) database. The OOS Inspection will change a vehicle from being in-service to OOS, so
that the test can verify the proper functioning of the code. The data will match that specified in
test case data set 3.08.01.

Acceptance Criteria
1. 1. CVIEW receives a valid TS 285 in one mail message for a vehicle snapshot from                    Formatted: Bullets and Numbering
    SAFER.
3. 2. CVIEW sends and APL SAFER receives a TS 997 and TS 824 from CVIEW.
4. 3. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–16
ITS/CVO Interoperability Test Suite Package – Part 2




Test Procedures for Test 3.08.01
See Tables 3–410, 3-11, 3-12 for the Master Test Conductor Procedure Tables, respectively.
Note that some transaction sets are starred () in this table (under Master Test Criteria). The
Test Analyst will examine these starred transaction sets for conformance with the CVISN
architecture in post-test evaluation. Operator Actions are indicated in bold print, whereas,
System Actions are not in bold print.
                                                  Table 3–4.
                                Test 3.08.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria            Pass/
                                                                                                   Fail
    51       The Test Conductor inserts an email        None Verify that the e-mail message in
             message containing a TS 285                the State CVIEW’s subscription
             snapshot update for a vehicle placed       mailbox includes the vehicle snapshot
             OOS into the APL SAFER inbox,              for the OOS and that the snapshot
             which triggers the subscription            contains the OOS information. 
             process. APL SAFER sends the
             TS 285 to CVIEW data mailbox on the
             APL SAFER system. The APL SAFER
             System sends a TS 285, vehicle
             snapshot e-mail message to the State
             CVIEW’s mailbox (on APL SAFER).
    62       The State CVIEW System retrieves its       APL SAFER receives the TS 997 and
             mail message from the APL SAFER            TS 824.The State CVIEW System
             System and sends a TS 997 valid and        updates its database with the newly
             TS 824 Accepted to APL SAFER..             obtained vehicle snapshot information
                                                        that includes the OOS information 
    38       The State CVIEW Operator should            One way to verify this update is to use
             then verify that it received the vehicle   SQL and verify that the database has
             snapshot and updated its local             been properly updated. 
             database.
Table 3 – 6.
Test 3.08.01 Procedures: State CVIEW Procedure
 Maste System or Operator Action                   CVIEW Test Criteria                            Pass/
 r Step                                                                                           Fail
 6        The State CVIEW System retrieves         The State CVIEW System updates
          its mail message from the APL            its database with the newly obtained
          SAFER System.                            vehicle snapshot information that
                                                   includes the OOS information
 7        The State CVIEW sends a TS 997
          valid and TS 824 accepted.
 8        The State CVIEW Operator should          One way to verify this update is to
          then verify that it received the vehicle use SQL and verify that the
          snapshot and updated its local           database has been properly updated.
          database.                                




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                    Page 3–17
ITS/CVO Interoperability Test Suite Package – Part 2




Table 3 – 7.
Test 3.08.01 Procedures: APL SAFER Procedure
 Maste System or Operator Action                   SAFER Test Criteria                     Pass/
 r Step                                                                                    Fail
 1        The APL SAFER System has a
          vehicle snapshot subscription set up
          on it that includes the vehicle
          inspected as part of this test scenario.
          Test Case Data Set 3.08.01 contains
          the nominal parameters.
 2        The APL SAFER Operator sends the
          Vehicle Inspection to the APL
          SAFER System that includes the
          information to place the vehicle Out-
          of-Service (OOS).
          The Operator should not use the
          ASPEN unit, instead the Operator
          should transfer the mail message (that
          contains the Inspection Report) to the
          proper directory on the APL SAFER
          System.
 3        The APL SAFER Operator should
          record the Vehicle Identification
          Number and Inspection Report
          Number here:

             VIN:
             ____________________________

             IR:
             _____________________________

 4           The APL SAFER System processes
             the Inspection Report and this
             triggers the subscription for the State
             CVIEW System that includes this
             vehicle.
 5           The APL SAFER System sends the            Verify that the e-mail message in
             vehicle snapshot e-mail message to        the State CVIEW’s subscription
             the State CVIEW’s mailbox (on APL         mailbox includes the vehicle
             SAFER).                                   snapshot for the OOS and that the
                                                       snapshot contains the OOS
                                                       information. 




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–18
ITS/CVO Interoperability Test Suite Package – Part 2




Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
State CVIEW Mailbox and the APL SAFER Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–19
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.08.02, CVIEW Receives Subscription Update for Vehicle Snapshots via
SAFER for an Out-of-Service (OOS) VehicleCVIEW Processes Subscription for Vehicle
Snapshots via SAFER for an Out-of-Service (OOS) Vehicle, EDI Syntax Error in
Snapshot


Test Summary
Testing the State CVIEW System: the APL SAFER System sends a vehicle snapshot update (for
a recently placed OOS vehicle) to the State CVIEW System, however, the snapshot contains an
EDI syntax error. The State CVIEW System receives the vehicle snapshot, identifies that it is an
invalid message and replies to SAFER with a TS 997 Negative.

Purpose
Verify that when if a vehicle snapshot is received at CVIEW from SAFER as a result of an Out-
of-Service (OOS) Inspection and this snapshot contains with an EDI syntax error, CVIEW
identifies the error and responds properly.

Test Case Initial Conditions
This test of the CVIEW System assumes that an OOS Inspection Report has already been sent to
the APL SAFER System. The OOS Inspection will change a vehicle from being in-service to
OOS, so that the test can verify the proper functioning of the code. The data will match that
specified in test case data set 3.08.02.

Acceptance Criteria
2. 1. CVIEW receives an invalid (syntax error) TS 285 in one mail message for a vehicle                Formatted: Bullets and Numbering
    snapshot from SAFERsends a TS 997 Negative to the APL SAFER.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedures for Test 3.08.02
See Tables 3–5 13, 3-14, 3-15 for the Master, CVIEW, and SAFER Test Conductor Procedure,
respectively. Note that some transaction sets are starred () in this table (under Master Test
Criteria). The Test Analyst will examine these starred transaction sets for conformance with the
CVISN architecture in post-test evaluation. Operator Actions are indicated in bold print,
whereas, System Actions are not in bold print.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–20
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–5.
                                Test 3.08.02: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
     1       The Test Conductor inserts an email        None
             message containing a TS 285
             snapshot update for a vehicle placed
             OOS into the CVIEW data mailbox on
             the APL SAFER system. The
             snapshot must be for a vehicle that
             exists in the SAFER and CVIEW
             systems. The TS 285 contains a
             syntax error, such as missing
             delimiters.
     2       The State CVIEW System retrieves its       APL SAFER receives the Negative
             mail message from the APL SAFER            TS 997.  Test operator verifies.
             System and sends a negative TS 997 to
             APL SAFER
     3       The State CVIEW Operator should            One way to verify this is to use SQL
             then verify that it did not receive the    and verify that the database has not
             vehicle snapshot and has not updated       been updated.
             its local database.



Table 3 – 8.
Test 3.08.02 Procedures: State CVIEW Procedure
 Maste System or Operator Action                   CVIEW Test Criteria                         Pass/
 r Step                                                                                        Fail
 6        The State CVIEW System retrieves
          its mail message from the APL
          SAFER System.
 7        The State CVIEW System sends a TS The APL SAFER System receives
          997 Negative EDI message.                the TS 997 EDI messages from the
                                                   State CVIEW.
 8        The State CVIEW Operator should
          see an error message on the computer
          screen.
Table 3 – 9.
Test 3.08.02 Procedures: APL SAFER Procedure
 Maste System or Operator Action                   SAFER Test Criteria                         Pass/
 r Step                                                                                        Fail
 1        The APL SAFER System has a
          vehicle snapshot subscription set up
          on it that includes the vehicle
          inspected as part of this test scenario.
          Test Case Data Set 3.08.02 contains



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–21
ITS/CVO Interoperability Test Suite Package – Part 2




 Maste       System or Operator Action                  SAFER Test Criteria                 Pass/
 r Step                                                                                     Fail
             the nominal parameters.
 2           The APL SAFER Operator should
             modify the TS 285 EDI message so
             as to include a syntactical error in the
             mail message. The way to do this is
             to delete the “BGN … ET” line in the
             message.
 3           The APL SAFER Operator sends the
             Vehicle Inspection to the APL
             SAFER System that includes the
             information to place the vehicle Out-
             of-Service (OOS).
             The Operator should not use the
             ASPEN unit, instead the Operator
             should transfer the mail message (that
             contains the Inspection Report) to the
             proper directory on the APL SAFER
             System.
 4           The APL SAFER System processes
             the Inspection Report and this
             triggers the subscription for the State
             CVIEW System that includes this
             vehicle.
 5           The APL SAFER System sends the             Verify that the e-mail message in
             vehicle snapshot e-mail message to         the State CVIEW’s subscription
             the State CVIEW’s mailbox (on APL          mailbox includes the vehicle
             SAFER).                                    snapshot for the OOS and that the
             Note: This TS 285 EDI message              snapshot contains the OOS
             indicated that there is a syntax error     information. 
             in the original mail message.


Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
State CVIEW Mailbox and the APL SAFER Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                Baseline Version V1.0               Page 3–22
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.08.03, CVIEW Receives Subscription Update for Vehicle Snapshots via
SAFER for an Out-of-Service (OOS) VehicleCVIEW Processes Subscription for Vehicle
Snapshots via SAFER for an Out-of-Service (OOS) Vehicle, Data Error in Snapshot


Test Summary
Testing the State CVIEW System: the APL SAFER System sends a vehicle snapshot (for a
recently placed OOS vehicle) to the State CVIEW System, however, the snapshot contains a data
error. The State CVIEW System receives the vehicle snapshot, identifies that it is an error and
replies to SAFER with a TS 824 Application Advice indicating an error.

Purpose
Verify that when if a vehicle snapshot is received at CVIEW from SAFER as a result of an Out-
of-Service (OOS) Inspection and this snapshot containswith a data error, CVIEW identifies the
error and responds properly.

Test Case Initial Conditions
This test of the CVIEW System assumes that an OOS Inspection Report has already been sent to
the APL SAFER System. The OOS Inspection will change a vehicle from being in-service to
OOS, so that the test can verify the proper functioning of the code. The data will match that
specified in test case data set 3.08.03.

Acceptance Criteria
1. 1. CVIEW receives an invalid (data error) TS 285 in one mail message for a vehicle                  Formatted: Bullets and Numbering
    snapshot from SAFER. The snapshot contains a data error.
3. 2. CVIEW sends a TS 997 Valid and TS 824 Error Message to SAFER.
4. 3. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedures for Test 3.08.03
See Tables 3–16 , 3-17, 3-18 for for the Master, CVIEW, and SAFER Test Conductor
Procedures, respectively. Note that some transaction sets are starred () in the table (under
Master Test Criteria). The Test Analyst will examine these starred transaction sets for




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–23
ITS/CVO Interoperability Test Suite Package – Part 2




conformance with the CVISN architecture in post-test evaluation. Operator Actions are
indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–6.
                                Test 3.08.03: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
     1       The Test Conductor inserts an email        None
             message containing a TS 285
             snapshot update for a vehicle placed
             OOS into the CVIEW data mailbox on
             the APL SAFER system. The
             snapshot must be for a vehicle that
             exists on the SAFER/CVIEW systems.
             The file contains a data error such as
             an incorrect view field of Q999.
     2       The State CVIEW System retrieves its       APL SAFER receives the TS 997 and
             mail message from the APL SAFER            TS 824.
             System and sends a TS 997 Valid and
             TS 824 Rejected to APL SAFER
     3       The State CVIEW Operator should            One way to verify this is to use SQL
             then verify that it received the vehicle   and verify that the database has NOT
             snapshot but did not update its local      been updated.
             database.



Table 3 – 10.
Test 3.08.03 Procedures: State CVIEW Procedure
 Maste System or Operator Action                   CVIEW Test Criteria                         Pass/
 r Step                                                                                        Fail
 6        The State CVIEW System retrieves
          its mail message from the APL
          SAFER System.
 7        The State CVIEW System sends a TS The APL SAFER System receives
          997 Positive and TS 824 Rejected         the TS 997 and TS 824 EDI
          EDI messages.                            messages from the State CVIEW.
 8        The State CVIEW Operator should
          see an error message on the computer
          screen.
Table 3 – 11.
Test 3.08.03 Procedures: APL SAFER Procedure
 Maste System or Operator Action                   SAFER Test Criteria                         Pass/
 r Step                                                                                        Fail
 1        The APL SAFER System has a
          vehicle snapshot subscription set up
          on it that includes the vehicle
          inspected as part of this test scenario.


4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–24
ITS/CVO Interoperability Test Suite Package – Part 2




 Maste       System or Operator Action                 SAFER Test Criteria                 Pass/
 r Step                                                                                    Fail
             Test Case Data Set 3.08.03 contains
             the nominal parameters.
 2           The APL SAFER Operator should
             modify the TS 285 EDI message so
             as to include a data error in the mail
             message. The way to do this is to
             modify the Data View/View Version
             field. To do this, change the Q301 to
             a Q501.
 3           The APL SAFER Operator sends the
             Vehicle Inspection to the APL
             SAFER System that includes the
             information to place the vehicle Out-
             of-Service (OOS).
             The Operator should not use the
             ASPEN unit, instead the Operator
             should transfer the mail message (that
             contains the Inspection Report) to the
             proper directory on the APL SAFER
             System.
 4           The APL SAFER System processes
             the Inspection Report and this
             triggers the subscription for the State
             CVIEW System that includes this
             vehicle.
 5           The APL SAFER System sends the            Verify that the e-mail message in
             vehicle snapshot e-mail message to        the State CVIEW’s subscription
             the State CVIEW’s mailbox (on APL         mailbox includes the vehicle
             SAFER).                                   snapshot for the OOS and that the
             Note: This TS 285 EDI message             snapshot contains the OOS
             indicated that there is a data error in   information. 
             the original mail message.


Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
State CVIEW Mailbox and the APL SAFER Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–25
ITS/CVO Interoperability Test Suite Package – Part 2




                                                                                                                Formatted: Bullets and Numbering


3.1.3 SCENARIO ID PW-SAFE-04: CVIEW RECEIVES SUBSCRIPTION UPDATE
FOR CARRIER SNAPSHOTS VIA APL SAFER



3.1.4 SAFER PROCESSES SUBSCRIPTION FOR CARRIER SNAPSHOT TO
CVIEW

For these tests, CVIEW has a subscription on the APL SAFER to receive snapshot updates for
the carrier specified in the test data set. In order to initiate the subscription process and test the
ability of the CVIEW to receive a TS 285 snapshot segment update from the APL SAFER, APL
SAFER must first receive a snapshot segment update from some source. Normally this would be
from another CVIEW or a state legacy system for a change in carrier status or information. For
this test, a snapshot segment update that includes a change in carrier information will be inserted
into the APL SAFER via a test tool or via email to the APL SAFER inbox. This will trigger the
subscription process and APL SAFER will create the TS 285 and send it to the CVIEW data
mailbox on the APL SAFER system.

This scenario covers the non-error case only, as the error cases are covered in the previous
scenario for CVIEW receiving (vehicle) snapshot updates. The type of update does not alter the
error case test.


TEST MATRIX:

         Test                Error Type                                Expected Results
         Case
                    No         EDI         Data
                    Errors     Syntax      Error
                               Error
        3.04.01     X                                  CVIEW receives a Carrier Snapshot update from
                                                       SAFER and responds with a TS 997 and TS 824 to
                                                       SAFER.



TEST CONFIGURATIONS:

    •     3.04.A State CVIEW; APL SAFER APL Facility Requirements
             Facility is equipped with software, hardware, and communications sufficient to
               manage the test execution. APL SAFER servers are set up to conduct the test.
               Subscriptions have been established with the State CVIEW under test.
        • User Facility Requirements                                                                            Formatted: Bullets and Numbering
             State CVIEW is set up to conduct the test. Subscriptions have been established with
               APL SAFER. Communications are directed towards APL SAFER.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                       Baseline Version V1.0                Page 3–26
ITS/CVO Interoperability Test Suite Package – Part 2




        • Test Roles                                                                                 Formatted: Bullets and Numbering
             The three key test roles necessary to execute tests using this Test Configuration
               include: the CVIEW System Operator, the Master Test Conductor, and the Test
               Analyst. Make the necessary number of copies of the Test Procedures for each test
               participant.
                                                                                                     Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         CVIEW and APL SAFER Systems.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–27
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.04.01, CVIEW Receives Subscription Update for Carrier Snapshots via
APL SAFERSAFER Processes Subscription for Carrier Snapshot to CVIEW, No Errors


Test Summary
Testing the State CVIEW System: the APL SAFER System sends a carrier snapshot to the State
CVIEW System. The State CVIEW System receives the carrier snapshot, and updates its
database with the information, and responds appropriately to the APL SAFER.

Purpose
Verify that SAFER fulfills its carrier subscriptions for CVIEW systems when carrier information
changes in the carrier snapshot, and that CVIEW receives and acknowledges receiving the
informationcarrier snapshot update from APL SAFER..

Test Case Initial Conditions
For this test of the CVIEW System, assumes that a MCMIS update file has been sent to the
SAFER system. Aa snapshot for the carrier being changed already exists in the APL SAFER
and State CVIEW’ databases. The data will match that specified in test case data set 3.04.01.
The change to the snapshot can be an IFTA check flag change or some other similar action. Test
Case 3.04.01 represents a standard carrier subscription fulfillment with no data errors.

Acceptance Criteria
1. 1. CVIEW receives a valid TS 285 in one mail message for a carrier snapshot from APL                Formatted: Bullets and Numbering
    SAFER.
3. 2. CVIEW sends a TS 997 and TS 824 to SAFER.
4. 3. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedures for Test 3.04.01
See Tables 3–197, 3-20, and 3-21 for the Master, CVIEW, and SAFER Test Conductor
Procedures, respectively. Note that some transaction sets are starred () in the table (under
Master Test Criteria). The Test Analyst will examine these starred transaction sets for
conformance with the CVISN architecture in post-test evaluation. Operator Actions are
indicated in bold print, whereas, System Actions are not in bold print.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–28
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–7.
                                Test 3.04.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria            Pass/
                                                                                                   Fail
     1       The Test Conductor inserts an email        None
             message containing a TS 285
             snapshot update for a carrier with a
             changed IFTA flag into the APL
             SAFER system inbox. APL SAFER
             sends TS 285 to CVIEW data mailbox
             on the APL SAFER system.
     2       The State CVIEW System retrieves its       APL SAFER receives the TS 997 and
             mail message from the APL SAFER            TS 824. 
             System and sends a TS 997 valid and
             TS 824 Accepted to APL SAFER
     3     The State CVIEW Operator should              One way to verify this update is to use
           then verify that it received the carrier     SQL and verify that the database has
           snapshot and updated its local               been properly updated.
           database.
Table 3 – 12.
Test 3.04.01 Procedure: State CVIEW Procedure
 Maste       System or Operator Action                  CVIEW Test Criteria                       Pass/
 r Step                                                                                           Fail
 6           The State CVIEW System retrieves           The State CVIEW System updates
             its mail message from the APL              its database with the newly obtained
             SAFER System.                              carrier snapshot information that
                                                        includes the changed information.
 7           The State CVIEW sends a TS 997
             valid and TS 824 accepted.
 8           The State CVIEW Operator should            One way to verify this update is to
             then verify that it received the carrier   use SQL and verify that the
             snapshot and updated its local             database has been properly updated.
             database.                                  

 Maste       System or Operator Action                  SAFER Test Criteria                       Pass/
 r Step                                                                                           Fail
 1           The APL SAFER System has a
             carrier snapshot subscription set up
             on it that includes the carrier snapshot
             changed as part of this test scenario.
             Test Case Data Set 3.04.01 contains
             the nominal parameters.
 2           The APL SAFER Operator sends the
             changed Carrier Snapshot to the APL
             SAFER System that includes the
             changed information.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                    Page 3–29
ITS/CVO Interoperability Test Suite Package – Part 2




 Maste       System or Operator Action                 SAFER Test Criteria                 Pass/
 r Step                                                                                    Fail
             The Operator should transfer the mail
             message (that contains the changed
             Snapshot) to the proper directory on
             the APL SAFER System.
 3           The APL SAFER Operator should
             record the Carrier Identification
             Number and OOS status here:

             Carrier ID:
             _______________________

             Carrier OOS:
             _____________________

 4           The APL SAFER System processes
             the snapshot and this triggers the
             subscription for the State CVIEW
             System that includes this carrier.
 5           The APL SAFER System sends a TS           Verify that the e-mail message in
             285 EDI message, carrier snapshot         the State CVIEW’s subscription
             segment update, to the State              mailbox includes the carrier
             CVIEW’s mailbox (on APL SAFER).           snapshot for the changed item and
                                                       that the snapshot contains the
                                                       changed information. 


Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
State CVIEW Mailbox and the APL SAFER Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–30
ITS/CVO Interoperability Test Suite Package – Part 2




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0   Page 3–31
ITS/CVO Interoperability Test Suite Package – Part 2




                                                    Table 3 – 13.
                               Test 3.04.02 Procedure: State CVIEW Procedure




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                Baseline Version V1.0   Page 3–32
ITS/CVO Interoperability Test Suite Package – Part 2




                                                    Table 3 – 14.
                               Test 3.04.03 Procedures: State CVIEW Procedure



                                                    Table 3 – 15.
                               Test 3.04.03 Procedures: APL SAFER Procedure




         Data Recording/Reduction/Evaluation Procedures:


3.1.53.1.4 SCENARIO ID PW-SAFE-05: SCENARIO ID PW-SAFE-05: CVIEW
SENDS SUBSCRIPTION UPDATE FOR SAFER PROCESSES SUBSCRIPTION FOR
VEHICLE SNAPSHOT TO CVIEW CARRIER SNAPSHOTS TO APL SAFER

In order to initiate the subscription process and test the ability of the CVIEW to create a TS 285
snapshot segment update for the APL SAFER, CVIEW must first receive the snapshot segment
update from some source. Normally this would be from a legacy system for a change in vehicle
or carrier status. For this test, a snapshot segment update that includes the carrier test data will
be inserted into the CVIEW via a test tool or via email to the CVIEW inbox. This will trigger
the subscription process and CVIEW will create the TS 285 carrier snapshot and send it to the
APL SAFER data mailbox on the CVIEW system.

This scenario covers the non-error case only, as the error cases are covered in the previous
scenario for CVIEW receiving (vehicle) snapshot updates. The type of update does not alter the
error case test.


TEST MATRIX:

         Test                Error Type                                Expected Results
         Case
                    No         EDI         Data
                    Errors     Syntax      Error
                               Error
       3.05.01      X                                  CVIEW sends a Carrier Snapshot to SAFER in
                                                       response to a subscription.



TEST CONFIGURATION:3.05.A STATE CVIEW; APL SAFER

       • APL Facility Requirements                                                                              Formatted: Bullets and Numbering
           Facility is equipped with software, hardware, and communications sufficient to
             manage the test execution. APL SAFER servers are set up to conduct the test.
             Subscriptions have been established with the State CVIEW under test.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                       Baseline Version V1.0                Page 3–33
ITS/CVO Interoperability Test Suite Package – Part 2




        • User Facility Requirements                                                                 Formatted: Bullets and Numbering
             State CVIEW is set up to conduct the test. Subscriptions have been established with
               SAFER. Communications are directed towards APL SAFER.
        • Test Roles                                                                                 Formatted: Bullets and Numbering
             The three key test roles necessary to execute tests using this Test Configuration
               include: the CVIEW System Operator, the Master Test Conductor, and the Test
               Analyst. Make the necessary number of copies of the Test Procedures for each test
               participant.
                                                                                                     Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         CVIEW and APL SAFER Systems.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–34
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.05.01, SAFER Processes Subscription for Vehicle Snapshot to CVIEW
CVIEW Sends Subscription Update for Carrier Snapshots to APL SAFER, No Errors


Test Summary
Testing the State CVIEW System: the CVIEW system successfully sends a carrier snapshot to
the APL SAFER System via the subscription process. The CVIEW receives a TS 997 and
TS 824 in response and sends a final TS 997 to APL SAFER.

Purpose
Verify that CVIEW can send a carrier snapshot update successfully to the APL SAFER, and
receive acknowledgement from the APL SAFER.

Test Case Initial Conditions
This test of the CVIEW system assumes that a carrier update file has been input to the CVIEW
system. A snapshot for the carrier being changed already exists in the CVIEW and APL SAFER
databases. The data will match that specified in test case data set 3.05.01. The change to the
snapshot can be an IFTA flag or some other similar action. Test Case 3.05.01 represents a
standard carrier subscription fulfillment with no errors.

Acceptance Criteria
1. 1. CVIEW sends a valid TS 285 in one mail message for a vehicle snapshot to APL                     Formatted: Bullets and Numbering
    SAFER.
2. 2. CVIEW receives a TS 824 from SAFER.
3. 3. CVIEW sends a TS 997 to SAFER in response to TS 824.
4. 4. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.05.01
See Table 3–8 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–35
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–8.
                                Test 3.05.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
     1       The Test Conductor inserts carrier         None
             data into CVIEW as a TS 285 in an
             email message or via a test tool.
     2       The CVIEW System recognizes the input      None
             data as an update and processes it. The
             subscription process is triggered.
     3       The State CVIEW System sends the           The APL SAFER System polls its
             TS 285 message to the APL SAFER            mailbox on the State CVIEW System
             data mailbox on the CVIEW system.          and determines that it has new mail
                                                        (the TS 285 message) in its mailbox.
                                                        The APL SAFER System then retrieves
                                                        (receives) its mail from the CVIEW
                                                        System and processes the message
                                                        (TS 285). 
     4       The APL SAFER System completes             The State CVIEW System receives the
             processing the TS 285 sent by the          TS 824.
             CVIEW System and transmits a TS 824
             Accepted.
     5       The CVIEW System processes the             SAFER receives TS 997 Positive from
             TS 824 Accepted received from the APL      CVIEW, acknowledging receipt of
             SAFER System and transmits a positive      TS 824. 
             TS 997 in response to the TS 824.
     6       The Test Analyst should use a              Updated carrier snapshot records in
             database utility to verify that the        database should be verified.
             carrier snapshot records were
             updated in both the State CVIEW and
             APL SAFER databases.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
State CVIEW Mailbox and the APL SAFER Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–36
ITS/CVO Interoperability Test Suite Package – Part 2




3.1.63.1.5 SCENARIO ID PW-SAFE-06: CVIEW SENDS A TS 285 QUERY FOR A
CARRIER SNAPSHOT TO APL SAFER

This scenario utilizes the CVIEW OPCON (operator console) or similar tool to submit a query to
the APL SAFER system. It covers the non-error case only, as the error cases are covered in
scenario Safe-01 for CVIEW sending snapshot updates. The type of TS 285 sent does not alter
the error case tests.
SAFER Processes Query for Carrier Snapshot from CVIEW


TEST MATRIX:

          Test                         Error Type                              Expected Results
          Case
                       No Data       Error in          Error in
                       or Syntax     CVIEW EDI         response
                       Errors,       file being        from APL
                       snapshot      sent to APL       SAFER
                       not found     SAFER             being sent
                       in                              to
                       CVIEW                           CVIEWDat
                       but found                       a error
                       in APL
                       SAFER
       3.06.01         X                                            CVIEW sends a query and receives
                                                                    the requested carrier snapshot from
                                                                    SAFER.



TEST CONFIGURATION:

       • APL Facility Requirements                                                                                    Formatted: Bullets and Numbering
            Facility is equipped with software, hardware, and communications sufficient to
              manage the test execution. APL SAFER servers are set up to conduct the test.
              Subscriptions have been established with the State CVIEW under test.
       • User Facility Requirements                                                                                   Formatted: Bullets and Numbering
            State CVIEW is set up to conduct the test. Subscriptions have been established with
              SAFER. Communications are directed towards APL SAFER.
       • Test Roles                                                                                                   Formatted: Bullets and Numbering
            The three key test roles necessary to execute tests using this Test Configuration
              include: the State CVIEW System Operator, the APL SAFER System Operator and
              the Test Analyst. Make the necessary number of copies of the Test Procedures for
              each test participant.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                       Baseline Version V1.0                      Page 3–37
ITS/CVO Interoperability Test Suite Package – Part 2

                                                                                                      Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         CVIEW and APL SAFER Systems. APL SAFER System has the required carrier
         snapshots in its database. State CVIEW System does not have the carrier snapshot in its
         local database.




Test Case 3.06.01, CVIEW Sends a TS 285 Query for a Carrier Snapshot to APL
SAFER SAFER Processes Query for Carrier Snapshot from CVIEW, No Errors,
snapshot not found in CVIEW but found in APL SAFER


Test Summary
Testing the State CVIEW System: the State CVIEW System sends a request (query) for a carrier
snapshot to the APL SAFER System and receives a carrier snapshot in response from the APL
SAFER System. CVIEW responds with a TS 997 acknowledgement.

Purpose
Verify the ability of the State CVIEW System to send a carrier snapshot request (query) to the
APL SAFER System and receive the response message from SAFER.

Test Case Initial Conditions
This test of the SAFER and CVIEW Systems assumes that the SAFER System’s database has the
snapshot for the carrier being requested (queried) and that the CVIEW System’s database does
not have the carrier snapshot. The State CVIEW System must be able to capture EDI messages.
Test case data set 3.06.01 defines nominal parameters.

Acceptance Criteria
1. 1. CVIEW sends a TS 285 query EDI message to SAFER.                                                Formatted: Bullets and Numbering
2. 2. CVIEW receives one valid TS 285 EDI message in one mail message for a carrier
    snapshot request from SAFER.
3. 3. CVIEW sends a TS 997 to SAFER.
4. 4. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0              Page 3–38
ITS/CVO Interoperability Test Suite Package – Part 2




reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.06.01
See Table 3–9 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas System Actions are not in bold print.
                                                  Table 3–9.
                                Test 3.06.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
     1       The CVIEW System Operator verifies          None
             that the Carrier Snapshot being
             requested (queried) does NOT reside
             in the local CVIEW database.
             Test Case Data Set 3.06.01 contains
             the nominal parameters.
     2       The CVIEW System Operator requests          None
             (queries) the SAFER System for a
             Carrier Snapshot.
     3       The CVIEW System Operator records           None
             the Carrier Snapshot that is being
             requested (queried) in Step 2 above:

             Carrier US DOT #: ________________
     4       The CVIEW System sends a TS 285 EDI         The SAFER System receives the
             message containing the request (query)      TS 285 EDI query from the State
             for the Carrier Snapshot to the SAFER       CVIEW system. 
             System.
     5       The SAFER System processes the              The CVIEW System receives the
             request (query) for the Carrier Snapshot    TS 285 EDI message containing the
             and transmits the Carrier Snapshot to the   Carrier Snapshot that was requested
             CVIEW System.                               from SAFER.
     6       The CVIEW System replies to the             The SAFER System receives the
             SAFER System’s TS 285 EDI message           TS 997 EDI message from CVIEW. 
             with a TS 997 Positive EDI message.
     7       The CVIEW System Operator brings            The CVIEW System Operator verifies
             up the Carrier Snapshot on the CVIEW        the information received from the
             display.                                    SAFER System.

                                                         Carrier US DOT #: _______________




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–39
ITS/CVO Interoperability Test Suite Package – Part 2




Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the captured EDI messages using a mail tool (e.g., Eudora Light Mail Client) to
examine the State CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–40
ITS/CVO Interoperability Test Suite Package – Part 2




3.1.73.1.6 SCENARIO ID PW-SAFE-07: CVIEW SENDS A TS 285 QUERY FOR A
VEHICLE SNAPSHOT TO APL SAFER

This scenario utilizes the CVIEW OPCON (operator console) or similar tool to submit a query to
the APL SAFER system. It covers the non-error case only, as the error cases are covered in
scenario Safe-01 for CVIEW sending snapshot updates. The type of TS 285 sent does not alter
the error case tests.
SAFER Processes Query for Vehicle Snapshot from CVIEW


TEST MATRIX:

         Test                         Error Type                               Expected Results
         Case
                    No Data or       Error in          Data Error
                    Syntax           CVIEW EDI         in response
                    Errorssnap       file being        from APL
                    shot not         sent to APL       SAFER
                    found in         SAFER             being sent
                    CVIEW but                          to CVIEW
                    found in
                    APL
                    SAFER
        3.07.01     X                                                CVIEW queries SAFER and receives
                                                                     the requested vehicle snapshot



TEST CONFIGURATIONS:

    •     3.07.A State CVIEW; APL SAFER APL Facility Requirements
             Facility is equipped with software, hardware, and communications sufficient to
               manage the test execution. APL SAFER servers are set up to conduct the test.
               Subscriptions have been established with the State CVIEW under test.
        • User Facility Requirements                                                                            Formatted: Bullets and Numbering
             State CVIEW is set up to conduct the test. Subscriptions have been established with
               APL SAFER. Communications are directed towards APL SAFER.
        • Test Roles                                                                                            Formatted: Bullets and Numbering
             The four key test roles necessary to execute tests using this Test Configuration
               include: the State CVIEW System Operator; the APL SAFER System Operator, the
               Master Test Conductor; and the Test Analyst. Make the necessary number of copies
               of the Test Procedures for each test participant.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                       Baseline Version V1.0                Page 3–41
ITS/CVO Interoperability Test Suite Package – Part 2

                                                                                                       Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         CVIEW and APL SAFER Systems. APL SAFER System has the required carrier
         snapshots in its database. State CVIEW System does not have the carrier snapshot in its
         local database.




Test Case 3.07.01, CVIEW Sends a TS 285 Query for a Vehicle Snapshot to APL
SAFER, No Errors


Test Summary
Testing the State CVIEW System: the State CVIEW System sends a request (query) for a vehicle
snapshot to the APL SAFER System and receives a vehicle snapshot in response from the APL
SAFER System. CVIEW responds with a TS 997 acknowledgement.

Purpose
Verify the ability of the State CVIEW System to send a vehicle snapshot request (query) to the
APL SAFER System and receive the TS 285 snapshot from SAFER.

Test Case Initial Conditions
This test of the SAFER and CVIEW Systems assumes that the SAFER System’s database has the
snapshot for the vehicle being requested (queried) and that the CVIEW System’s database does
not have the vehicle snapshot. The State CVIEW System must be able to capture EDI messages.
Test case data set 3.07.01 defines nominal parameters.

Acceptance Criteria
1. 1. CVIEW sends a TS 285 EDI query to SAFER.                                                         Formatted: Bullets and Numbering
2. 2. CVIEW receives one valid TS 285 EDI message for a vehicle snapshot request from
    SAFER.
3. 3. CVIEW sends a TS 997 to SAFER.
4. 4. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–42
ITS/CVO Interoperability Test Suite Package – Part 2




Test Procedure for Test 3.07.01
See Table 3–10 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–10.
                                Test 3.07.01: Master Test Conductor Procedure

Step              System or Operator Action                       Master Test Criteria             Pass/
                                                                                                    Fail
  1       The CVIEW System Operator verifies           None
          that the Vehicle Snapshot being
          requested (queried) does NOT reside
          in the local CVIEW database; but does
          reside in the SAFER database.
          Test Case Data Set 3.07.01 contains
          the nominal parameters.
  2       The CVIEW System Operator requests           None
          (queries) the SAFER System for a
          Vehicle Snapshot using the
          Vehicle Identification Number (VIN).
  3       The CVIEW System Operator records            None
          the Vehicle Snapshot that is being
          requested (queried) in Step 2 above:

          Vehicle Identification Number (VIN):
          ____________________________
  4       The CVIEW System sends a TS 285 EDI          The SAFER System receives the TS 285
          message containing the request (query)       EDI message from the State CVIEW
          for the Vehicle Snapshot to the SAFER        system. 
          System.
  5       The SAFER System processes the               The CVIEW System receives the TS 285
          request (query) for the Vehicle Snapshot     EDI message containing the Vehicle
          and transmits the Vehicle Snapshot to        Snapshot that was requested from SAFER.
          the CVIEW System.
  6       The CVIEW System replies to the              APL SAFER receives the TS 997. 
          SAFER System’s TS 285 EDI message
          with a TS 997 acknowledgement.
  7       The CVIEW Operator displays the              CVIEW Operator verifies the information
          Vehicle Snapshot that was requested          received from the SAFER System. 
          (queried).
                                                       VIN: ___________________________
                                                       Carrier Name: ___________________
                                                       State: __________________________
                                                       Plate: __________________________




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                   Page 3–43
ITS/CVO Interoperability Test Suite Package – Part 2




Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the captured EDI messages using a mail tool (e.g., Eudora Light Mail Client) to
examine the State CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–44
ITS/CVO Interoperability Test Suite Package – Part 2




 Maste       System or Operator Action                 SAFER Test Criteria                Pass/
 r Step                                                                                   Fail
 4        The SAFER System Operator verifies
          that the SAFER Service is not
          running.
 6        The SAFER System Operator saves a
          copy of the file into a different folder.
 7        The SAFER System Operator
          corrupts the file by compressing or
          zipping the file.
 8        The SAFER System Operator starts
          the SAFER Service.
 9        The SAFER System begins to process The SAFER System provides the
          the request (query) for the Vehicle       Vehicle Snapshot that was
          Snapshot but can not process the file     requested. 
          since it is
          compressed/zippedcorrupted.
Table 3 – 16.
Test 3.07.02 Procedures: State CVIEW Procedure
 Maste System or Operator Action                    CVIEW Test Criteria                   Pass/
 r Step                                                                                   Fail
 1        The CVIEW System Operator
          verifies that the Vehicle Snapshot
          being requested (queried) does NOT
          reside in the local CVIEW database.
          Test Case Data Set 3.07.02 contains
          the nominal parameters.
 2        The CVIEW System Operator
          requests (queries) the SAFER System
          for a Vehicle Snapshot.
 3        The CVIEW System Operator records
          the Vehicle Snapshot that is being
          requested (queried) in step 2 above,
          here:

             Vehicle Identification Number (VIN):
             ______________________________

 5           The CVIEW System sends a TS 285           The SAFER System receives the TS
             EDI message containing the request        285 EDI message from the State
             (query) for the Vehicle Snapshot to       CVIEW system. 
             the SAFER System.
 Step        System or Operator Action                 Master Test Criteria               Pass/
                                                                                          Fail




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0              Page 3–45
ITS/CVO Interoperability Test Suite Package – Part 2




 Maste       System or Operator Action                 CVIEW Test Criteria                  Pass/
 r Step                                                                                     Fail
 1           The CVIEW System Operator
             verifies that the Vehicle Snapshot
             being requested (queried) does NOT
             reside in the local CVIEW database.
             Test Case Data Set 3.07.03 contains
             the nominal parameters.
 2           The CVIEW System Operator
             requests (queries) the SAFER System
             for a Vehicle Snapshot.
 3           The CVIEW System Operator records
             the Vehicle Snapshot that is being
             requested (queried) in step 2 above,
             here:

             Vehicle Identification Number (VIN):
             ______________________________

 4           The CVIEW System sends the                The SAFER System receives the
             request (query) for the Vehicle           Vehicle Snapshot request. 
             Snapshot to the SAFER System.
 5           The SAFER System processes the            The SAFER System provides the
             request (query) for the Vehicle           Vehicle Snapshot that was
             Snapshot and transmits the requested      requested; however, the response
             (queried) Vehicle Snapshot back to        message is in AFF vice EDI format.
             the CVIEW System; however, the            
             response is in AFF format and not the
             expected EDI format.
 6           The CVIEW System displays a
             message indicating that the response
             message is in the incorrect file
             format.

Table 3 – 17.
Test 3.07.03 Procedures: APL SAFER Procedure
 Step     System or Operator Action          Master Test Criteria                           Pass/
                                                                                            Fail
 5           The SAFER System processes the            The SAFER System provides the
             request (query) for the Vehicle           Vehicle Snapshot that was
             Snapshot and transmits the requested      requested; the response message is
             (queried) Vehicle Snapshot back to        in AFF format. 
             the CVIEW System; however, the
             response is in AFF format and not the
             expected EDI format.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                Page 3–46
ITS/CVO Interoperability Test Suite Package – Part 2




Table 3 – 18.
Test 3.07.03 Procedures: State CVIEW Procedure
 Step     System or Operator Action           Master Test Criteria                        Pass/
                                                                                          Fail
 1           The CVIEW System Operator
             verifies that the Vehicle Snapshot
             being requested (queried) does NOT
             reside in the local CVIEW database.
             Test Case Data Set 3.07.03 contains
             the nominal parameters.
 2           The CVIEW System Operator
             requests (queries) the SAFER System
             for a Vehicle Snapshot.
 3           The CVIEW System Operator records
             the Vehicle Snapshot that is being
             requested (queried) in step 2 above,
             here:

             Vehicle Identification Number (VIN):
             ______________________________

 4           The CVIEW System sends the                The SAFER System receives the
             request (query) for the Vehicle           Vehicle Snapshot request. 
             Snapshot to the SAFER System.
 6           The CVIEW System displays a
             message indicating that the response
             message is in the incorrect file
             format.


Data Recording/Reduction/Evaluation Procedures:
There will be a manual log of events and electronic log of events, post test comparison of receipt
of appropriate messages with appropriate steps in procedures. Should a failure occur, a summary
list of successful steps prior to such failure will be prepared. The Test Analyst will examine the
captured EDI messages using a mail tool (i.e., Eudora Light Mail Client) to examine the State
CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0              Page 3–47
ITS/CVO Interoperability Test Suite Package – Part 2




3.2 State Roadside – CVIEW (i.e., Roadside Operations –
 CVIEW) Snapshot Scenarios


3.2.1 SCENARIO ID PW-SAFE-02: ROADSIDE OPERATIONS SYSTEM SENDS A
REQUEST FOR A VEHICLE SNAPSHOT TO CVIEW USING A VEHICLE
IDENTIFICATION NUMBER (VIN)

For these tests, the State roadside system is under test. It is tested with the APL CVIEW for
those states that have chosen to use this CVIEW. For those who have developed their own
system that performs the same functions, the tests will be carried out with the state CVIEW-
equivalent system, with no involvement of the APL test facility. In this case it is assumed that
before the roadside to CVIEW tests are conducted, the State CVIEW has passed the
interoperability tests for CVIEW to SAFER interchanges to verify basic EDI capability. The test
procedures are the same regardless of whether the APL CVIEW or the state CVIEW equivalent
is used by the state. The only difference is in the communications configuration, which point the
roadside system to the correct CVIEW system.


TEST MATRIX:

        Test                         Error Type                                 Expected Results
        Case
                      No       EDI Syntax Error        CVIEW
                      Error    from CVIEW              Data
                      s                                Error
       3.02.01        X                                            Roadside Operations System receives
                                                                   the requested vehicle snapshot from
                                                                   CVIEW.
       3.02.02                 X                                   Roadside Operations System sends a
                                                                   Functional Acknowledgement TS 997
                                                                   Negative message to CVIEW.
       3.02.03                                         X           Roadside Operations System sends an
                                                                   Application Advice TS 824 Error message
                                                                   to CVIEW.



TEST CONFIGURATION:

       • APL Facility Requirements                                                                                Formatted: Bullets and Numbering
           Facility is equipped with software, hardware, and communications sufficient to
              manage the test execution. APL CVIEW server is set up to conduct the test.
       • User Facility Requirements                                                                               Formatted: Bullets and Numbering
           State Roadside Operations System is set up to conduct the test. Communications
              are directed towards APL CVIEW or State CVIEW equivalent as appropriate.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                       Baseline Version V1.0                  Page 3–48
ITS/CVO Interoperability Test Suite Package – Part 2




        • Test Roles                                                                                Formatted: Bullets and Numbering
             The three key test roles necessary to execute tests using this Test Configuration
               include: the Roadside Operations System Operator, the Master Test Conductor, and
               the Test Analyst. Make the necessary number of copies of the Test Procedures for
               each test participant.
                                                                                                    Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         Roadside Operations System and APL CVIEW Systems.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0            Page 3–49
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.02.01, Roadside Operations System Sends a Request for a Vehicle
Snapshot to CVIEW using a Vehicle Identification Number (VIN), No Errors


Test Summary
Testing the Roadside Operations System; the Roadside Operations System sends a request
(query) for a vehicle snapshot to the CVIEW System and receives the vehicle snapshot as a result
of that request (query).

Purpose
Verify the ability of the Roadside Operations System to send a vehicle snapshot request (query)
to the CVIEW System and receive the proper vehicle snapshot in return.

Test Case Initial Conditions
This test of the CVIEW System and Roadside Operations System assumes that the CVIEW
System’s database has the snapshot for the vehicle being requested (queried) and that the
Roadside Operations System’s database does not have the vehicle snapshot. The vehicle being
requested (queried) must be for an Interstate, vice Intrastate, vehicle. The CVIEW system must
be able to capture EDI messages. Test case data set 3.02.01 defines nominal parameters.

The Roadside Operations System should have an email client (e.g., Eudora Light Mail Client)
that will be used to view the mail messages.

The Test Case Account Information for the APL Systems should be obtained prior to executing
this test and must be obtained from the APL Interoperability Test Team.

Acceptance Criteria
1. 1. Roadside System sends and CVIEW receives a TS 285 EDI message from Roadside                      Formatted: Bullets and Numbering
    Operations System.
2. 2. Roadside Operations System receives one valid TS 285 EDI message in one mail
    message for a vehicle snapshot request from CVIEW.
3. Roadside Operations System sends a TS 997 to CVIEW.
4. 4. All EDI transactions are in conformance with the CVISN architecture.                             Formatted: Bullets and Numbering



Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–50
ITS/CVO Interoperability Test Suite Package – Part 2




Test Procedures for Test 3.02.01
See Tables 3-11 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–11.
                                Test 3.02.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
    21       The Roadside Operations System             None
             Operator should use the Vehicle
             Identification Number (VIN) shown
             here to submit a request (query) for a
             vehicle snapshot from the CVIEW
             System:

             VIN: 1GTFG35K3RF517952
             State: VA
             Plate: 17297S

             [Note: The vehicle snapshot being
             requested (queried) must not be in the
             local database on the Roadside
             Operations System, but must be in the
             CVIEW System.
             Test Case Data Set 3.02.01 contains the
             nominal parameters.]
     2       The Roadside Operations System             None
             Operator submits a query for a vehicle
             snapshot to CVIEW using the VIN in
             Step 2 above.The Roadside Operations
             System Operator should submit a
             request (query) for the vehicle snapshot
             to the APL CVIEW System using the VIN
             in Step 2 above.
     3       The Roadside Operations System sends       The CVIEW System receives the
             a TS 285 EDI message (encapsulated in      TS 285 EDI message from the
             a mail message) to the CVIEW Systems       Roadside Operations System. 
             email IN box.
     4       The CVIEW System sends a TS 285 EDI        The Roadside Operations System
             message (encapsulated in a mail            receives the TS 285 EDI message from
             message) to the Roadside Operations        the APL CVIEW System.
             System.
     5       The Roadside Operations System replies     The CVIEW System receives the
             to the CVIEW System’s TS 285 EDI           TS 997 EDI message from the
             message with a TS 997 Positive EDI         Roadside Operations System. 
             message.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–51
ITS/CVO Interoperability Test Suite Package – Part 2




  Step              System or Operator Action                   Master Test Criteria       Pass/
                                                                                            Fail
     6       The Roadside Operations System            The Roadside Operations System
             Operator should see the vehicle           Operator should verify and record
             snapshot that was requested (queried)     the information shown on the
             on the computer screen.                   computer screen.

                                                       VIN: __________________________

                                                       Carrier Name: __________________

                                                       State: _________________________

                                                       Plate: _________________________



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–52
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.02.02, Roadside Operations System Sends a Request for a Vehicle
Snapshot to CVIEW using a Vehicle Identification Number (VIN), EDI Syntax Error in
Response from CVIEW


Test Summary
Testing the Roadside Operations System: the Roadside Operations System sends a request
(query) for a vehicle snapshot to the CVIEW System and receives a syntactically incorrect EDI
message in response from the CVIEW System.

Purpose
Verify the ability of the Roadside Operations System to send a vehicle snapshot request (query)
to the CVIEW System and properly handle a syntactically incorrect EDI message in response
from CVIEW.

Test Case Initial Conditions
This test of the CVIEW System and Roadside Operations System assumes that the CVIEW
System’s database has the snapshot for the vehicle being requested (queried) and that the
Roadside Operations System’s database does not have the vehicle snapshot. The vehicle being
requested (queried) must be for an Interstate, vice Intrastate, vehicle. Test case data set 3.02.02
defines nominal parameters.

The Roadside Operations System should have an email client (i.e., Eudora Light Mail Client)
that will be used to view the mail messages.

The Test Case Account Information for the APL Systems should be obtained prior to executing
this test and must be obtained from the APL Interoperability Test Team.

Acceptance Criteria
1. Roadside Operations System sends and CVIEW receives a valid TS 285 EDI message query
    (request) for a vehicle snapshot.
2. Roadside Operations System receives one invalid (syntax error) TS 285 EDI message in one
    mail message from CVIEW in response to forthe vehicle snapshot request.
3. 3. Roadside Operations System sends and CVIEW receives a negative TS 997.                            Formatted: Bullets and Numbering
4. 4. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                Page 3–53
ITS/CVO Interoperability Test Suite Package – Part 2




reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedures for Test 3.02.02
See Tables 3–1222, 3-23, 3-24 for the Master, CVIEW, and Roadside Operations System Test
Conductor Procedures, respectively. Note that some transaction sets are starred () in the table
(under Master Test Criteria). The Test Analyst will examine these starred transaction sets for
conformance with the CVISN architecture in post-test evaluation. Operator Actions are
indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–12.
                                Test 3.02.02: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria     Pass/
                                                                                            Fail
     1       The Roadside Operations System             None
             Operator should use the Vehicle
             Identification Number (VIN) shown
             here to submit a request (query) for a
             vehicle snapshot from the APL CVIEW
             System:

             VIN: 1GTFG35K3RF517952
             State: VA
             Plate: 17297S

             [Note: The vehicle snapshot being
             requested (queried) must not be in the
             local database on the Roadside
             Operations System, but must be in the
             CVIEW System.
             Test Case Data Set 3.02.02 contains the
             nominal parameters.]
     2       The Roadside Operations System             None
             Operator submits a query for a vehicle
             snapshot to CVIEW using the VIN in
             Step 2 above.The Roadside
             Operations System Operator should
             submit a request (query) for the
             vehicle snapshot to the APL CVIEW
             System using the VIN in Step 2 above.
     3       The Roadside Operations System sends       The CVIEW System receives the
             a TS 285 message (encapsulated in a        TS 285 message from the Roadside
             mail message) to the CVIEW System.         Operations System. 
             Note: The Roadside Operator then turns
             off the roadside system.
     4       The CVIEW System sends a TS 285            None
             message (encapsulated in a mail
             message) to the Roadside Operations
             System.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0             Page 3–54
ITS/CVO Interoperability Test Suite Package – Part 2




  Step              System or Operator Action                   Master Test Criteria           Pass/
                                                                                                Fail
     5       Before the Roadside system is             None
             started, the test conductor should
             retrieve and modify the TS 285
             message from the roadside’s CVIEW
             data mailbox so as to include a
             syntactical error in the mail message.
             One way to do this is to delete
             element delimiters.
     6       Test Conductor signals the Roadside       None
             System Operator to turn on the
             Roadside system. The snapshot with
             the syntax error is retrieved and
             processed.
     7       The Roadside Operations System replies    The CVIEW System receives the
             to the CVIEW System’s TS 285 EDI          TS 997 EDI message from the
             message with a TS 997 Negative EDI        Roadside Operations System. 
             message.
     8       The Roadside Operations System            The Roadside Operations System
             Operator should see an error              Operator should retrieve and read the
             message on the computer screen.           “SAFER Error Response” mail
                                                       message.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the captured EDI messages using a mail tool (e.g., Eudora Light Mail Client) to
examine the APL CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                   Page 3–55
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.02.03, Roadside Operations System Sends a Request for a Vehicle
Snapshot to CVIEW using a Vehicle Identification Number (VIN), Data Error in
Response from CVIEW


Test Summary
Testing the Roadside Operations System; the Roadside Operations System sends a request
(query) for a vehicle snapshot to the APL CVIEW System and receives a vehicle snapshot that
contains a data error as a result of that request (query).

Purpose
Verify the ability of the Roadside Operations System to send a vehicle snapshot request (query)
to the CVIEW System and properly handle a vehicle snapshot that contains a data error in return.

Test Case Initial Conditions
This test of the CVIEW System and Roadside Operations System assumes that the CVIEW
System’s database has the snapshot for the vehicle being requested (queried) and that the
Roadside Operations System’s database does not have the vehicle snapshot. The vehicle being
requested (queried) must be for an Interstate, vice Intrastate, vehicle. Test case data set 3.02.03
defines nominal parameters.

The Roadside Operations System should have an email client (i.e., Eudora Light Mail Client)
that will be used to view the mail messages.

The Test Case Account Information for the APL Systems should be obtained prior to executing
this test and must be obtained from the APL Interoperability Test Team.

Acceptance Criteria
1. 1. Roadside Operations System sends and CVIEW receives a TS 285 EDI query for vehicle                Formatted: Bullets and Numbering
    snapshot.
2. Roadside Operations System receives one valid TS 285 EDI message with a data error in one
    mail message in response to the vehicle snapshot request.
3. 3. Roadside Operations System sends a positive TS 997 and negative TS 824 (error                     Formatted: Bullets and Numbering
    message) to CVIEW.
4. 4. All EDI transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria that apply for safety-related data flows are based on ANSI ASC X12 EDI
standards. These criteria are a subset of those found in COACH Part 5, Section 5, and reflect
those requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                Page 3–56
ITS/CVO Interoperability Test Suite Package – Part 2




reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.02.03
See Table 3–13 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–13.
                                Test 3.02.03: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria     Pass/
                                                                                            Fail
     1       The CVIEW System Operator must             None
             ensure that the CVIEW Service is NOT
             running.The Roadside Operations            ROC Account info is:
             System Operator determines which
             Vehicle Identification Number (VIN)        User ID: tstsafe
             that will be used to request (query) a     Password: safety
             vehicle snapshot from the APL CVIEW        Domain: CVISNnet
             System.
             [Note: The vehicle snapshot being
             requested (queried) must not be in the
             local database on the Roadside
             Operations System, but must be in the
             APL CVIEW System.
             Test Case Data Set 3.02.03 contains
             the nominal parameters.]
     2       The Roadside Operations System             None
             Operator should use the Vehicle
             Identification Number (VIN) shown
             here to submit a request (query) for a
             vehicle snapshot from the CVIEW
             System:

             VIN: 1GTFG35K3RF517952
             State: VA
             Plate: 17297S

             [Note: The vehicle snapshot being
             requested (queried) must not be in the
             local database on the Roadside
             Operations System, but must be in the
             CVIEW System.
             Test Case Data Set 3.02.03 contains the
             nominal parameters.]




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0             Page 3–57
ITS/CVO Interoperability Test Suite Package – Part 2




  Step              System or Operator Action                   Master Test Criteria          Pass/
                                                                                               Fail
     3       The Roadside Operations System            The Roadside Operations System
             Operator submits a query for a vehicle    sends a TS 285 EDI message
             snapshot to CVIEW using the VIN in        (encapsulated in a mail message) to
             Step 2 above.The Roadside                 the CVIEW System.
             Operations System Operator should
             submit a request (query) for the
             vehicle snapshot to the APL CVIEW
             System using the VIN in Step 2 above.
     4       The Roadside Operations System            None
             Operator turns off the roadside
             system.
     5       The CVIEW System Operator must            Startup Parameter: CVIEW
             start the CVIEW Service.
     6       The CVIEW System receives the query       None
             and sends aa TS 997 valid and TS 285
             824 Error response to the Roadside
             Operations System data mail box on the
             CVIEW System.
     7       Before turning the Roadside system        None
             on, the Test Conductor retrieves the
             snapshot from the CVIEW data
             mailbox and inserts a data error. The
             Roadside system is then turned on
             and the snapshot is processed.
     8       The Roadside Operations System            The Roadside Operations System
             Operator should see an error              Operator should retrieve and read
             message on the computer screen            the “SAFER Error Response” mail
             after receiving the TS 285 message.       message.
     9       Roadside Operations System sends a        CVIEW receives a Positive TS 997 and
             TS 997 and a TS 824 error message to      Negative TS 824 (error message). 
             CVIEW.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL CVIEW Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0                  Page 3–58
ITS/CVO Interoperability Test Suite Package – Part 2




3.3 State Roadside – SAFER (i.e., ASPEN – SAFER) Snapshot
Scenarios


3.3.1 SCENARIO ID PW-SAFE-15: ASPEN SENDS A REQUEST FOR A CARRIER
SNAPSHOT TO SAFER

For these tests, the state roadside system (ASPEN) is under test. It is tested with the APL
SAFER. The interface being tested is the Custom Interface Agreement (CIA) data format that is
transmitted between ASPEN and SAFER. These are non-EDI exchanges.


TEST MATRIX:

         Test                         Error Type                              Expected Results
         Case
                                     Error in          Error in
                    No Data or       ASPEN             response
                    Syntax           CIA file          from APL
                    Errors           being sent        SAFER to
                                     to APL            ASPEN
                                     SAFER
       3.15.01      X                                              ASPEN receives snapshot
       3.15.02                       X                             ASPEN receives error message from
                                                                   SAFER
       3.15.03                                         X           ASPEN sends error message to
                                                                   display



TEST CONFIGURATION:

       • APL Facility Requirements                                                                             Formatted: Bullets and Numbering
            Facility is equipped with software, hardware, and communications sufficient to
              manage the test execution. APL SAFER server is set up to conduct the test.
       • User Facility Requirements                                                                            Formatted: Bullets and Numbering
            User’s ASPEN is set up to conduct the test. Communications are directed towards
              APL SAFER in lieu of Production SAFER.
       • Test Roles                                                                                            Formatted: Bullets and Numbering
            The four key test roles necessary to execute tests using this Test Configuration
              include: the State ASPEN System Operator, the APL SAFER System Operator, the
              Master Test Conductor, and the Test Analyst. Make the necessary number of copies
              of the Test Procedures for each test participant.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                      Baseline Version V1.0                Page 3–59
ITS/CVO Interoperability Test Suite Package – Part 2

                                                                                                      Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on APL
         SAFER and User’s ASPEN Systems. APL SAFER System has the required carrier
         snapshots in its database. State ASPEN System does not have the carrier snapshot in its
         local database.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0              Page 3–60
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.15.01, ASPEN Sends a Request for a Carrier Snapshot to SAFER, No
Data or Syntax Errors, snapshot found in APL SAFER


Test Summary
Testing the State ASPEN System; the State ASPEN System sends a request (query) for a carrier
snapshot to the APL SAFER System and receives a carrier snapshot in response from the APL
SAFER System.

Purpose
Verify the ability of the State ASPEN System to send a carrier snapshot request (query) to the
APL SAFER System and receive the response message from SAFER.

Test Case Initial Conditions
This test of the SAFER and ASPEN Systems assumes that the SAFER System’s database has the
snapshot for the carrier being requested (queried) and that the ASPEN System’s database does
not have the carrier snapshot.

Acceptance Criteria
1. 1. ASPEN sends and SAFER receives CIA message.                                                      Formatted: Bullets and Numbering
2. 2. ASPEN receives one valid CIA message in one mail message for a carrier snapshot
    request from SAFER.
3. 3. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
These criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.15.01
See Table 3–14 for the Master Test Conductor Procedures. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–61
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–14.
                                Test 3.15.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
     1       The ASPEN System Operator verifies          None
             that the Carrier Snapshot being
             requested (queried) does NOT reside
             in the local ASPEN database but does
             reside in the SAFER database.
             Test Case Data Set 3.15.01 contains
             the nominal parameters.
     2       The ASPEN System Operator, using            None
             ASPEN and the ISS option in ASPEN,
             requests (queries) the SAFER System
             for a Carrier Snapshot.
     3       The ASPEN System Operator records           None
             the Carrier Snapshot that is being
             requested (queried) in Step 2 above:

             Carrier US DOT #: _________________
     4       The ASPEN System sends the request          The SAFER System receives the
             (query) for the Carrier Snapshot to the     Carrier Snapshot request. 
             SAFER System.
     5       The SAFER System processes the              The ASPEN System displays the
             request (query) for the Carrier Snapshot    Carrier Snapshot that was requested
             and transmits the Carrier Snapshot to the   (queried).
             ASPEN System.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–62
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.15.02, ASPEN Sends a Request for a Carrier Snapshot to SAFER, Error in
ASPEN CIA file being sent to APL SAFER


Test Summary
Testing the State ASPEN System: the State ASPEN System sends a request (query) for a carrier
snapshot to the APL SAFER System. The request being sent to the APL SAFER System
contains an error in the ASPEN CIA file. SAFER receives this erroneous CIA file and
determines it to be in error and properly handles the file and its response.

Purpose
Verify the ability of the State ASPEN System to properly handle the response from the APL
SAFER System to an erroneous CIA file.

Test Case Initial Conditions
This test of the SAFER and ASPEN Systems assumes that the SAFER System’s database has the
snapshot for the carrier being requested (queried) and that the ASPEN System’s database does
not have the carrier snapshot.

Acceptance Criteria
2. 1. ASPEN receives a mail message regarding the erroneous CIA file sent to the APL                   Formatted: Bullets and Numbering
    SAFER System.
3. 2. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
These criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.15.02
See Table 3–15 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–63
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–15.
                                Test 3.15.02: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria        Pass/
                                                                                               Fail
     1       The ASPEN System Operator verifies          None
             that the Carrier Snapshot being
             requested (queried) does NOT reside
             in the local ASPEN database but does
             reside in the SAFER database.
             Test Case Data Set 3.15.02 contains
             the nominal parameters.
     2       The ASPEN System Operator, using            None
             ASPEN and the ISS option in ASPEN,
             requests (queries) the SAFER System
             for a Carrier Snapshot.
     3       The ASPEN System Operator records           None
             the Carrier Snapshot that is being
             requested (queried) in Step 2 above:

             Carrier US DOT #: _________________
     4       The SAFER System Operator verifies          None
             that the SAFER Service is not
             running.
     5       The ASPEN System sends the request          The SAFER System receives the
             (query) for the Carrier Snapshot to the     Carrier Snapshot request. 
             SAFER System.
     6       The SAFER System Operator saves a           None
             copy of the file into a different folder.
     7       The SAFER System Operator corrupts          None
             the file by compressing or zipping the
             file.
     8       The SAFER System Operator starts            None
             the SAFER Service.
     9       The SAFER System begins to process          The ASPEN System displays an
             the request (query) for the Carrier         AFFsome error message concerning
             Snapshot but cannot process the file        the request for the Carrier
             since it is compressed/zippedcorrupted.     Snapshot.The SAFER System provides
                                                         the Carrier Snapshot that was
                                                         requested. 



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                Page 3–64
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.15.03, ASPEN Sends a Request for a Carrier Snapshot to SAFER, Error in
response from APL SAFER being sent to ASPEN


Test Summary
Testing the State ASPEN System: the State ASPEN System sends a request (query) for a carrier
snapshot to the APL SAFER System and receives a carrier snapshot that contains an error as a
result of that request (query). ASPEN responds appropriately to the erroneous data.

Purpose
Verify the ability of the State ASPEN System to send a carrier snapshot request (query) to the
APL SAFER System and respond appropriately to a carrier snapshot that is returned with a data
error.

Test Case Initial Conditions
This test of the SAFER and ASPEN Systems assumes that the SAFER System’s database has the
snapshot for the carrier being requested (queried) and that the ASPEN System’s database does
not have the carrier snapshot.

Acceptance Criteria
2. 1. ASPEN receives an invalid CIA message from SAFER for a carrier snapshot in response              Formatted: Bullets and Numbering
    to a query and responds appropriately.
3. 2. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.15.03
See Table 3–16 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the Master Test Conductor Procedure Table (under Master Test Criteria). The
Test Analyst will examine these starred transaction sets for conformance with the CVISN
architecture in post-test evaluation. Operator Actions are indicated in bold print, whereas,
System Actions are not in bold print.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–65
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–16.
                                Test 3.15.03: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria             Pass/
                                                                                                    Fail
     1       The ASPEN System Operator verifies         None
             that the Carrier Snapshot being
             requested (queried) does NOT reside
             in the local ASPEN database but does
             reside in the SAFER database.
             Test Case Data Set 3.15.03 contains
             the nominal parameters.
     2       The ASPEN System Operator, using           None
             ASPEN and the ISS option in ASPEN,
             requests (queries) the SAFER System
             for a Carrier Snapshot.
     3       The ASPEN System Operator records          None
             the Carrier Snapshot that is being
             requested (queried) in Step 2 above:

             Carrier US DOT #: _________________
     4       The ASPEN System sends the request         The SAFER System receives the
             (query) for the Carrier Snapshot to the    Carrier Snapshot request. 
             SAFER System.
     5       The SAFER System processes the             None
             request (query) for the Carrier Snapshot
             and transmits the requested (queried)
             Carrier Snapshot back to the ASPEN
             System; however, the Test Conductor
             insures that the response is in EDI
             format and not the expected CIA format,
             causing an error.
     6       The ASPEN system receives and              The ASPEN System displays a
             processes the response from the SAFER      message indicating that the response
             system.                                    message is in the incorrect file format.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                     Page 3–66
ITS/CVO Interoperability Test Suite Package – Part 2




3.4 State Roadside – SAFER (i.e., ASPEN – SAFER)
Inspection Scenarios
3.4.1 SCENARIO ID PW-SAFE-09: ASPEN SENDS INSPECTION REPORTS TO
SAFER (CIA)

For these tests, the state roadside system (ASPEN) is under test. It is tested with the APL
SAFER. The interface being tested is the Custom Interface Agreement (CIA) data format that is
transmitted between ASPEN and SAFER. These are non-EDI exchanges.


TEST MATRIX:

         Test           Error Type                               Expected Results
         Case
                    No         CIA
                    Errors     Syntax
                               Error
        3.09.01     X                      APL SAFER stores the inspection report.
        3.09.02                X           Inspection report is forwarded to “bad IR” directory on APL
                                           SAFER.

         Note: If the user intends to run both the Scenario ID PW-Safe-08 and the Scenario ID PW-Safe-
         09, PW-Safe-08 should be run after PW-Safe-09.


TEST CONFIGURATION:

        • APL Facility Requirements                                                                                  Formatted: Bullets and Numbering
             Facility is equipped with software, hardware, and communications sufficient to
               manage the test execution. APL SAFER server is set up to conduct the test.
        • User Facility Requirements                                                                                 Formatted: Bullets and Numbering
             State ASPEN System is set up to conduct the test. Communications are directed
               towards APL SAFER.
        • Test Roles                                                                                                 Formatted: Bullets and Numbering
             The three key test roles necessary to execute tests using this Test Configuration
               include: the ASPEN System Operator, the APL SAFER Operator, and the Master
               Test Conductor/Test Analyst. Make the necessary number of copies of the Test
               Procedures for each test participant.
                                                                                                                     Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         ASPEN and APL SAFER Systems.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                      Baseline Version V1.0                      Page 3–67
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.09.01, ASPEN Sends Inspection Reports to SAFER (CIA), No Errors


Test Summary
Testing the ASPEN System: the State ASPEN sends an Inspection Report to the APL SAFER
System, and the APL SAFER System updates its database properly with the newly obtained
information from the State ASPEN System.

Purpose
Verify the ability of the State ASPEN System to send an Inspection Report to the APL SAFER
System and have the SAFER System update its database.

Test Case Initial Conditions
Test case data set 3.09.01 defines nominal parameters.

The ASPEN System should have an email client (e.g. Eudora Light Mail Client) that will be used
to view the mail messages.

The Test Case Account Information for the APL Systems should be obtained prior to executing
this test and must be obtained from the APL Interoperability Test Team.

Acceptance Criteria
2. 1.    ASPEN sends an Inspection Report, using the CIA file format, to SAFER.                        Formatted: Bullets and Numbering
3. 2.    All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
These criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.09.01
See Table 3–17 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–68
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–17.
                                Test 3.09.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria        Pass/
                                                                                               Fail
     1       The ASPEN System Operator                  None
             determines which Inspection Report
             will be sent to the APL SAFER
             System.

             [Note: The Inspection Report being sent
             must not be in the local database on the
             APL SAFER System.
             Test Case Data Set 3.09.01 contains the
             nominal parameters.]
     2       The ASPEN System Operator should           None
             complete an Inspection Report using
             the ASPEN System.
     3       The ASPEN System Operator should           None
             record the Inspection Report
             Information here:

             Carrier DOT #: 357362
             VIN: 1GTFG35K3RF517952
             State: VA
             Plate: 17297S
             Inspection Report Number: _________
     4       The ASPEN System Operator should           None
             submit the Inspection Report using
             the ASPEN Manager to the APL
             SAFER System using the Inspection
             Report Number identified in Step 2
             above.
     5       The ASPEN System sends the                 The APL SAFER System received the
             completed Inspection Report to the APL     Inspection Report CIA file from the
             SAFER System.                              ASPEN System. 
     6       The ASPEN System Operator should           The ASPEN System Operator should
             then perform a Past Inspection Query       see the Inspection Report that was
             (PIQ) to validate that the APL SAFER       just sent to the APL SAFER System.
             System received the Inspection
             Report and updated the APL SAFER
             database.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                Page 3–69
ITS/CVO Interoperability Test Suite Package – Part 2




examine the CIA messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL SAFER Mailbox.


Test Case 3.09.02, ASPEN Sends Inspection Reports to SAFER (CIA), CIA Syntax
Error


Test Summary
Testing the ASPEN System: using the APL SAFER System as the mechanism, the State ASPEN
sends an Inspection Report to the APL SAFER System. However, the Inspection Report that
was sent contains a syntax error. This syntax error takes the form of a corrupted zip file. The
APL SAFER System realizes that it is an Inspection Report file but cannot properly update its
database, since the zip file is corrupted.

Purpose
Verify the ability of the State ASPEN System to properly handle the response from the APL
SAFER system to an Inspection Report that contains a syntax error.

Test Case Initial Conditions
Test case data set 3.09.02 defines nominal parameters.

The ASPEN System should have an email client (e.g. Eudora Light Mail Client) that will be used
to view the mail messages.

The Test Case Account Information for the APL Systems should be obtained prior to executing
this test and must be obtained from the APL Interoperability Test Team.

Acceptance Criteria
2. 1. ASPEN sends an Inspection Report (containing a CIA syntax error), using the CIA file             Formatted: Bullets and Numbering
    format, to SAFER.
3. 2. ASPEN receives error response from SAFER.
4. 3. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
These criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–70
ITS/CVO Interoperability Test Suite Package – Part 2




Test Procedure for Test 3.09.02
See Table 3–18 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.
Operator Actions are indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–18.
                                Test 3.09.02: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
     1       The ASPEN System Operator                  None
             determines which Inspection Report
             will be sent to the APL SAFER
             System. This Inspection Report file
             should consist of a corrupted zip file.

             [Note: Test Case Data Set 3.09.02
             contains the nominal parameters.]
     2       The ASPEN System Operator should           None
             record the Inspection Report
             Information here:

             Inspection Report Number: _________
             Other info: _______________________
     3       The ASPEN System Operator should           None
             submit the corrupted Inspection
             Report to the APL SAFER System
             using the Inspection Report Number
             identified in Step 2 above.
     4       The ASPEN System sends the corrupted       The APL SAFER System received
             Inspection Report to the APL SAFER         the corrupted Inspection Report CIA
             System.                                    file from the ASPEN System. If the
                                                        attachment is unzippable, an error
                                                        occurs and the APL SAFER System
                                                        does not continue any processing
                                                        on the message.

                                                        The zip file is then written to a
                                                        directory on the APL SAFER System
                                                        (bad Inspection Report directory
                                                        (e.g., d:/cview/inspections) and an
                                                        entry is made in the Application
                                                        Event Log.

                                                        Test Conductor verifies that the bad
                                                        IR is in the “Bad IR” directory.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–71
ITS/CVO Interoperability Test Suite Package – Part 2




Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL SAFER Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–72
ITS/CVO Interoperability Test Suite Package – Part 2




                                                                                                                Formatted: Bullets and Numbering


3.1.23.4.2 SCENARIO ID PW-SAFE-14: ASPEN SENDS A REQUEST FOR AN
INSPECTION REPORT TO SAFER (CIA)

For these tests, the state roadside system (ASPEN) is under test. It is tested with the APL
SAFER. The interface being tested is the Custom Interface Agreement (CIA) data format that is
transmitted between ASPEN and SAFER. These are non-EDI exchanges.


TEST MATRIX:

         Test           Error Type                             Expected Results
         Case
                    No         Data
                    Errors     Error
        3.14.01     X                      ASPEN receives an Inspection Report from the APL SAFER
                                           System.
        3.14.02                X           ASPEN does not receive an Inspection Report. An error
                                           message is displayed.



TEST CONFIGURATION:

        • APL Facility Requirements                                                                             Formatted: Bullets and Numbering
             Facility is equipped with software, hardware, and communications sufficient to
               manage the test execution. APL SAFER server is set up to conduct the test.
        • User Facility Requirements                                                                            Formatted: Bullets and Numbering
             State ASPEN System is set up to conduct the test. Communications are directed
               towards APL SAFER.
        • Test Roles                                                                                            Formatted: Bullets and Numbering
             The three key test roles necessary to execute tests using this Test Configuration
               include: the ASPEN System Operator, the APL SAFER Operator, the Master Test
               Conductor/Analyst. Make the necessary number of copies of the Test Procedures
               for each test participant.
                                                                                                                Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly on State
         ASPEN and APL SAFER Systems.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                     Baseline Version V1.0                  Page 3–73
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.14.01, ASPEN Sends a Request for an Inspection Report to SAFER (CIA),
No Errors


Test Summary
Testing the ASPEN System: the State ASPEN sends a request for an Inspection Report to the
APL SAFER System and the APL SAFER System sends the Inspection Report to the State
ASPEN System.

Purpose
Verify the ability of the State ASPEN System to send a request for an Inspection Report to the
APL SAFER System and receive the report that is returned from the SAFER System.

Test Case Initial Conditions
This test of the State ASPEN and APL SAFER Systems assumes that the APL SAFER System’s
database has the Inspection Report for the vehicle being requested (queried) and that the
Roadside Operations System’s database does not have the vehicle Inspection Report. The
vehicle being requested (queried) must be for an Interstate, vice Intrastate, vehicle. Test case
data set 3.14.01 defines nominal parameters.

The ASPEN System should have an email client (i.e., Eudora Light Mail Client) that will be used
to view the mail messages.

The Test Case Account Information for the APL Systems should be obtained prior to executing
this test and must be obtained from the APL Interoperability Test Team.

Acceptance Criteria
1. ASPEN sends and SAFER receives a request (query) for an Inspection Report, using the CIA
    file format.
4. 2. ASPEN receives the Inspection Report that was requested from SAFER.                              Formatted: Bullets and Numbering
5. 3. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
The test criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–74
ITS/CVO Interoperability Test Suite Package – Part 2




Test Procedure for Test 3.14.01
See Table 3–19 for the Master Test Conductor Procedure, respectively. Note that some
transaction sets are starred () in the table (under Master Test Criteria). The Test Analyst will
examine these starred transaction sets for conformance with the CVISN architecture in post-test
evaluation. Operator Actions are indicated in bold print, whereas, System Actions are not in
bold print.
                                                  Table 3–19.
                                Test 3.14.01: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria          Pass/
                                                                                                 Fail
     1       The ASPEN System Operator                  None
             determines which Inspection Report
             will be requested from the APL
             SAFER System.

             [Note: The Inspection Report being
             requested must not be in the local
             database on the ASPEN System.
             Test Case Data Set 3.14.01 contains the
             nominal parameters.]
     2       The ASPEN System Operator should           None
             record the Inspection Report
             Information here:

             Inspection Report Number: ________
             Other info: _______________________
     3       The ASPEN System Operator should           None
             submit the request for the Inspection
             Report to the APL SAFER System
             using the Inspection Report Number
             identified in Step 2 above.
     4       The ASPEN System sends the request         The APL SAFER System receives the
             for the Inspection Report to the APL       request for the Inspection Report CIA
             SAFER System.                              file from the ASPEN System. 
     5       The ASPEN System receives the              The ASPEN System Operator should
             requested Inspection Report from the       see the Inspection Report that was
             APL SAFER System.                          just requested from the APL SAFER
                                                        System.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, post-test comparison of receipt
of appropriate messages with appropriate steps in procedures. Should a failure occur, a summary
list of successful steps prior to such failure will be prepared. The Test Analyst will examine the
EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the APL SAFER
Mailbox.



4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                  Page 3–75
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.14.02, ASPEN Sends a Request for an Inspection Report to SAFER (CIA),
Data Error in Request


Test Summary
Testing the ASPEN System: the State ASPEN sends a request for an Inspection Report to the
APL SAFER System. The request contains a CIA Syntax Error in the form of a corrupted file.
The APL SAFER System cannot process the file. ASPEN displays an error message when it
does not receive the expected report.

Purpose
Verify the ability of the State ASPEN System to respond appropriately in the case of sending a
request to SAFER that contains an error such that the request cannot be filled. ASPEN should
display an error message.

Test Case Initial Conditions
This test of the State ASPEN and APL SAFER Systems assumes that the APL SAFER System’s
database has the Inspection Report for the vehicle being requested (queried) and that the
Roadside Operations System’s database does not have the vehicle Inspection Report. The
vehicle being requested (queried) must be for an Interstate, vice Intrastate, vehicle. Test case
data set 3.14.02 defines nominal parameters.

The ASPEN System should have an email client (e.g. Eudora Light Mail Client) that will be used
to view the mail messages.

The Test Case Account Information for the APL Systems should be obtained prior to executing
this test and must be obtained from the APL Interoperability Test Team.

Acceptance Criteria
1. 1. ASPEN sends an Inspection Report (containing a data error), using the CIA file format,           Formatted: Bullets and Numbering
    to SAFER.
2. 2. ASPENSAFER receives and displays an error message from SAFER.
3. 3. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
These criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–76
ITS/CVO Interoperability Test Suite Package – Part 2




Test Procedure for Test 3.14.02
See Table 3–20 for the Master Test Conductor Procedure, respectively. Operator Actions are
indicated in bold print, whereas, System Actions are not in bold print.
                                                  Table 3–20.
                                Test 3.14.02: Master Test Conductor Procedure

  Step              System or Operator Action                      Master Test Criteria           Pass/
                                                                                                   Fail
     1       The ASPEN System Operator                    None
             determines which Inspection Report
             that will be requested from the APL
             SAFER System.

             [Note: The Inspection Report being
             requested must not be in the local
             database on the APL SAFER System.
             Test Case Data Set 3.14.02 contains the
             nominal parameters.]
     2       The ASPEN System Operator should             None
             record the Inspection Report
             Information here:

             Inspection Report Number: _________
             Other info: _______________________
     3       The ASPEN System Operator should             None
             submit the request for the Inspection
             Report to the APL SAFER System
             using the Inspection Report Number
             identified in Step 2 above.
     4       The ASPEN System sends the request           The APL SAFER System receives the
             for the Inspection Report to the APL         request for the Inspection Report CIA
             SAFER System.                                file from the ASPEN System. 
     5       The APL SAFER Operator should                None
             modify the request to include a
             semicolon (;) in the Inspection Report
             field.
     6       The APL SAFER System then processes          None
             the request for the Inspection Report that
             includes the error.
     7       The APL SAFER System sends the               None
             response to the Inspection Report
             request to the ASPEN System.                                                                     Formatted
    78       The ASPEN System receives error              The ASPEN System Operator should
             code/condition/warning from SAFER.           see some error
                                                          code/condition/warning.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                  Baseline Version V1.0                   Page 3–77
ITS/CVO Interoperability Test Suite Package – Part 2




Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared. The Test Analyst will
examine the EDI messages using a mail tool (e.g., Eudora Light Mail Client) to examine the
APL SAFER Mailbox.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0             Page 3–78
ITS/CVO Interoperability Test Suite Package – Part 2




                                                                                                                  Formatted: Bullets and Numbering
3.33.5   State Roadside – CVIEW (i.e., ASPEN – CVIEW)
Snapshot Scenarios


3.3.13.5.1 SCENARIO ID PW-SAFE-03: CVIEW RECEIVES REQUEST FOR A
CARRIER SNAPSHOT FROM ASPEN (CIA)

For these tests, the State CVIEW or CVIEW equivalent is under test. It is tested with the APL
installation of ASPEN. The interface being tested is the Custom Interface Agreement (CIA) data
format that is transmitted between ASPEN and CVIEW. These are non-EDI exchanges.


TEST MATRIX:

            Test                       Error Type                             Expected Results
            Case
                       No Data or             Error in ASPEN
                       Syntax Errors          CIA file being sent
                                              to CVIEW
          3.03.01      X                                             ASPEN receives snapshot from
                                                                     CVIEW
          3.03.02                             X                      ASPEN receives error message
                                                                     from CVIEW (requested data not
                                                                     found)



TEST CONFIGURATION:

        • APL Facility Requirements                                                                               Formatted: Bullets and Numbering
             Facility is equipped with software, hardware, and communications sufficient to
               manage the test execution. APL installation of ASPEN is set up to conduct the test.
        • User Facility Requirements                                                                              Formatted: Bullets and Numbering
             User’s CVIEW is set up to conduct the test.
        • Test Roles                                                                                              Formatted: Bullets and Numbering
             The four key test roles necessary to execute tests using this Test Configuration
               include: the APL ASPEN System Operator, the State CVIEW System Operator, the
               Master Test Conductor, and the Test Analyst. Make the necessary number of copies
               of the Test Procedures for each test participant.
                                                                                                                  Formatted: Bullets and Numbering


  CONFIGURATION INITIAL CONDITIONS:

    •    Required services, timers, modems, networks active and functioning properly at APL test
         lab and User’s CVIEW Systems. State ASPEN System does not have the carrier
         snapshot in its local database.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                       Baseline Version V1.0                  Page 3–79
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.03.01, CVIEW Receives a Request for a Carrier Snapshot from ASPEN:
No Data or Syntax Errors, Snapshot Found in State CVIEW


Test Summary
Testing the State CVIEW System: the State CVIEW System receives a request (query) for a
carrier snapshot from the APL ASPEN System and sends a carrier snapshot in response to the
APL ASPEN System.

Purpose
Verify the ability of the State CVIEW System to send a carrier snapshot in response to a request
(query) from the APL ASPEN System.

Test Case Initial Conditions
This test of the CVIEW and ASPEN Systems assumes that the CVIEW System’s database has
the snapshot for the carrier being requested (queried) and that the ASPEN System’s database
does not have the carrier snapshot.

Acceptance Criteria
1. 1. CVIEW receives CIA message from ASPEN requesting a carrier snapshot.                             Formatted: Bullets and Numbering
2. CVIEW sends one valid CIA message in one mail message for a carrier snapshot request to
    ASPEN.
3. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
These criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.03.01
See Table 3–21 for the Master Test Conductor Procedure. Note that some transaction sets are
starred () in the table (under Master Test Criteria). The Test Analyst will examine these
starred transaction sets for conformance with the CVISN architecture in post-test evaluation.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–80
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–21.
                                Test 3.03.01: Master Test Conductor Procedure

  Step             System or Operator Action                     Master Test Criteria         Pass/
                                                                                               Fail
     1      The ASPEN System Operator verifies          None
            that the Carrier Snapshot being
            requested (queried) does NOT reside
            in the local ASPEN database but does
            reside in the CVIEW database.

            [Note: Test Case Data Set 3.03.01
            contains the nominal parameters.]
     2      The ASPEN System Operator, using            None
            ASPEN and the ISS option in ASPEN,
            requests (queries) the CVIEW System
            for a Carrier Snapshot.
     3      The ASPEN System Operator records           None
            the Carrier Snapshot that is being
            requested (queried) in Step 2 above:

            Carrier US DOT #: _________________
     4      The ASPEN System sends the request          None
            (query) for the Carrier Snapshot to the
            CVIEW System.
     5      The CVIEW System processes the              The ASPEN System displays the
            request (query) for the Carrier Snapshot    Carrier Snapshot that was requested
            and transmits the Carrier Snapshot to the   (queried). 
            ASPEN System.



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, post-test comparison of receipt
of appropriate messages with appropriate steps in procedures. Should a failure occur, a summary
list of successful steps prior to such failure will be prepared.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                Page 3–81
ITS/CVO Interoperability Test Suite Package – Part 2




Test Case 3.03.02, CVIEW Receives a Request for a Carrier Snapshot from ASPEN:
Data not Found on CVIEW


Test Summary
Testing the State CVIEW System: the State CVIEW System receives a request (query) for a
carrier snapshot from the APL ASPEN System. The request being sent to the State CVIEW
System is for a snapshot that does not exist on CVIEW. CVIEW returns an error message to
ASPEN indicating that the requested data was not found on CVIEW.

Purpose
Verify the ability of the State CVIEW System to return an error message in response to a request
for unknown data.

Test Case Initial Conditions
This test of the CVIEW and ASPEN Systems assumes that the CVIEW System’s database does
not have the snapshot for the carrier being requested (queried), and that the ASPEN System’s
database does not have the carrier snapshot.

Acceptance Criteria
2. 1. CVIEW sends an error message to ASPEN indicating data not found.                                 Formatted: Bullets and Numbering
2. All CIA transactions are in conformance with the CVISN architecture.

Requirements Tested
These criteria are a subset of those found in COACH Part 5, Section 5, and reflect those
requirements that are pertinent to this test case. See COACH Part 5 for a detailed cross-
reference of test cases to requirements tested. This is supporting material to understand what is
being tested but is not required to execute this test.

Test Procedure for Test 3.03.02
See Tables 3-22 for the Master Test Conductor Procedure.




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc               Baseline Version V1.0               Page 3–82
ITS/CVO Interoperability Test Suite Package – Part 2



                                                  Table 3–22.
                                Test 3.03.02: Master Test Conductor Procedure

  Step              System or Operator Action                     Master Test Criteria         Pass/
                                                                                                Fail
     1       The ASPEN System Operator verifies         None
             that the Carrier Snapshot being
             requested (queried) does NOT reside
             in the local ASPEN database and does
             not reside in the CVIEW database.

             [Note: Test Case Data Set 3.03.02
             contains the nominal parameters.]
     2       The ASPEN System Operator, using           None
             ASPEN and the ISS option in ASPEN,
             requests (queries) the CVIEW System
             for a Carrier Snapshot.
     3       The ASPEN System Operator records          None
             the Carrier Snapshot that is being
             requested (queried) in Step 2 above:

             Carrier US DOT #: _________________
     5       The ASPEN System sends the request         The CVIEW System receives the
             (query) for the Carrier Snapshot to the    Carrier Snapshot request. 
             CVIEW System.
     9       The CVIEW System begins to process         The ASPEN System displays an error
             the request (query) for the Carrier        message concerning the request for
             Snapshot but cannot find the requested     the Carrier Snapshot.The SAFER
             snapshot; CVIEW sends an error             System provides the Carrier Snapshot
             message to ASPEN                           that was requested. 



Data Recording/Reduction/Evaluation Procedures
There will be a manual log of events and electronic log of events, and post-test comparison of
receipt of appropriate messages with appropriate steps in procedures. Should a failure occur, a
summary list of successful steps prior to such failure will be prepared




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                 Baseline Version V1.0                 Page 3–83
ITS/CVO Interoperability Test Suite Package – Part 2




                                           This Page Intentionally Blank




4b249529-f1f2-43e9-9fde-bf3685d86e33.doc                    Baseline Version V1.0   Page 3–84

								
To top