 Welcome to the CTS Learning Series Chapter 4, Data Model Conformance Verification. Video 3, Verification of the USM Using the CTS GUI. In this video, we will understand the Data Model Conformance Testing Workflow, use the CTS GUI to successfully test a USM, use the CTS GUI to unsuccessfully test a USM, and understand how to read and recover from Data Model Conformance Testing Errors. Testing a USM consists of configuring the Data Model tab in the Project Configuration Builder. To learn more about the Project Configuration Builder and the possible options to configure a Project Configuration File, please refer to Chapter 3. In the Data Model tab, we have the option to enter the location of a shared Data Model and the UOP Supplied Model. The shared Data Model may be downloaded at the shown location. The Data Model that we want to download is SDM version 3.1.4. I have already downloaded the SDM onto my machine. In the CTS, let's select the location of the SDM that I downloaded. Next, let's select the location of the USM. After the USM is selected, the USM's path will be shown in the CTS. Additionally, the CTS will automatically populate the UOP drop-down menu, where a UOP may be selected. Depending on the UOP selected, the associated views for that UOP will be listed in the bottom of the interface. To test for Data Model Conformance, select the Top Rate button. The Run Segment Conformance Test Interface opens. We are able to see the progress of the Conformance Test Report being shown in the Progress Bar. The Conformance Test Report's output location will be shown. The report is generated as a PDF file. Let's open it now. The Conformance Test Report lists a title page, immediately showing the name of the project and the Conformance Test Results. In our case, we passed Conformance Testing. Under the Conformance Test Result, we see the version of the face tactical standard we tested against, followed by a timestamp of when the Conformance Test Report was created. Next, a table of contents has been created. The table of contents list entries are clickable and lead to the corresponding page in the report. Then, the project configuration is listed. This is how the project configuration is generated as the PCFG. The TCFG would then be listed, but since we have only tested for data model conformance, we do not have a tool gene configuration file. Finally, the Conformance Test Report lists the Conformance Test Results in detail. Each test is listed with a passing or failing result noted. The data model conformance tests do not list a test log as they were passed successfully, according to the DMVT. Let's create a failing result by using a non-conformant USM. As you can see, this USM has major syntactical errors. Let's replace the successful USM with the USM containing the syntactical errors. The data model will be loaded into the CTS and allow for us to test the data model for conformance once again. When the test completes, we can see we have a failing result for our Conformance Test. For more information about the requirements to make data models conformant, please refer to the FACE technical standard. This error in particular refers to the fact that the official SDM must be the same SDM contained in the USM. To fix this error, it is important to make sure the provided SDM is the same as the official SDM. Thank you for watching. In the next video, entitled Verification of the USM Using the Command Line, we will explore how to invoke a data model conformance test from the command line, understand where the DMVT and DIG are located, and demonstrate a successful and failing data model conformance test.