Database Overview

The Master Database is the structure that houses all of our IOP device testing globally.  The Admin site is the tool we use to add/edit the data contained in our Master Database.  We often use these terms interchangably.  The IOP testers will enter new devices and track where those are within our testing process.  They will also enter IOP testing results and pairing instructions by device into the module test plans.  The Customer Service team will publish those devices to the front facing websites, along with pairing instructions, public comments, features comments (Japan only), and OEM requested testing results overrides.  Everyone will have access to reporting, with more advanced reporting coming in the future.  The Admin Site was designed with permissions in mind so the user has access to what they need and aren't overwhelmed with items they don't.  The MDB houses all of our pre-2015 testing data in a limited format, due to the limited information housed in the previous database.  Full test plans were not available in the old DB.  We also did not track the results of every iteration of device and HFT software - only the latest.  The new database allows for many test plans to be completed for various device SW versione and HFT software versions, for essentially one device model and one HFT module.  We can publish device comments in multiple languages across all of our websites.  We have access to change almost anything, without involving our outside agencies, allowing for lower maintenance costs. Because of the flexibility of our database, it is imperative that it's understood the data being entered feeds to outside websites which can generate customer dissatisfaction if it's incorrect. There is logic built in to eliminate as much erroneous data as possible, but always use with caution and understand the functionality of what you do and how that affects others, and ultimately the customer facing websites.


Database Structure

The Master Database consists of many layers of tables.  Entering the data into the tables in order allows for the full data structure to be created.  It can also cause much confusion if the basic table structure is not understood.   

First Layer Tables

  • Markets
  • Device Manufacturers
  • Device Types
  • Device OS
  • Vehicle Trims
  • IOP Test Steps
  • Features

Second Layer Tables  

  • Vehicle Make (uses Market)
  • Carriers (uses Market)
  • IOP Test Template (uses IOP Test Steps)
  • Devices (uses Device Manufacturer/Device Type/Device OS)

Third Layer Tables

  • Modules (uses Market(s), IOP Test Template, and feature(s))
  • Vehicle Model (uses Vehicle Make)

Fourth Layer Tables

  • Vehicle Release Years (this consists of Vehicle Make/Vehicle Model/Vehicle Trim/Vehicle Model Year/Module)
  • IOP Device Testing Results (Device/Device SW/Carrier/Module)


These tables are all being created so we can create the ultimate data relationship - Vehicle Release Year with IOP Testing Results!!


 For more information on how to navigate the Admin site and general site functionality, please see Admin Site Functionality.