1. Home
  2. Knowledge Base
  3. Vendor Tool Certification Program
  4. 03. Understanding the Certification Process

03. Understanding the Certification Process

In this article we discuss what the certification process is and how it works.  We cover the overall flow (rather than the timeline, as the timeline varies in some cases).  This is an overview of the certification process.  The process itself is complex, as it needs to ensure several major goals as well as be rigorous enough to qualify vendors that truly pass.

Understanding the Process

The process is complex in order to ensure integrity, and to level the playing field among all vendors seeking Data Vault 2.0 certification.  While complex it is easy to follow – as it is laid out in a step-by-step fashion.  Each step must be completed as a predecessor to the next step, there is no method for skipping steps.  Skipping steps will result in failure of the certification.  Once the certification process has been failed, an attempt has been used and is removed from the queue.  As stated in the Enrollment and Renewal Process, the vendor is granted a maximum of 4 certifications per two year period.  This limitation however is on the certification award itself – and is different from the number of submissions allowed during each process entry.

Learning About the Baseline

The steps below indicate the major high level process.  The high level process is broken down further, later in this article.

  1. Enroll or Re-Enroll (see Enrollment and Renewal Process)
  2. Log in to https://Learn.DataVaultAlliance.com
  3. Go to My Account
  4. Go to My Courses
  5. Complete all videos in DV101 Baseline Hands On course
  6. Download all artifacts from DV101 Baseline Hands On Course
  7. Complete all videos (lessons) in VTCP-DV101-Baseline-Meta-Config Course
  8. Download all artifacts from VTCP-DV101-Baseline-Meta-Config Course
  9. Work with the tool / modify the tool until it generates the required artifacts and metadata to match the Baseline criteria
  10. Continue with the VTCP Baseline Submission Process (below)

Step 9 in the above process flow can take as long as needed.  However it is important to note that the Enrollment Expiration date is set already, regardless of how long it takes the vendor to reach Step 10 in the above process.  The vendor is responsible for meeting contractual deadlines in a timely manner.

Common Questions and Answers

  • What if my technical person doesn’t have access to these courses?
    • Contact Us immediately, so we can assign the proper access rights to the courses.  The only delay here would be: did you sign the VTCP contract? no access will be granted until the contract is signed.
  • What if we already adjusted our tool to produce the Baseline (from the last set of iterations)?
    • We change and update the Baseline at least once a year, it is good to always download the new versions of the baseline, AND watch the course videos as a refresher, in order to keep your tooling compliant with the latest expectations.   When we adjust the baseline, we also adjust the certification criteria.

VTCP Baseline Submission Process

The vendor must notify DVA once this point has been reached.  Then, DVA will issue a login (for the technical resource) to our certification website designed to handle the certification process.  The technical resource can then continue on their own accord with uploading, executing certification tests, and retrieving results on an automated basis.

Readiness Prerequisites Checklist

The following prerequisites must be met before the vendor will be enabled to proceed with this process:

  1. Can the tool produce DDL files that match the Baseline DDL structures?
  2. Can the tool produce DML statements that match in functionality the Baseline DML data movement processes?
  3. Can the tool produce meta-config data sets that match the Baseline Meta-Config data files?  (including the insert statements)

IF the answer is YES to all of these questions, then the vendor may proceed with the steps below.  If the answer is NO, then the vendor must work with the tool until it meets these prerequisites.

Baseline Submission Process

The vendor may submit the Baseline as many times as they wish while the enrollment in VTCP is valid and active (not expired).  There are no penalties for failing a baseline test submission.  There will be no certification issued for passing a baseline test submission.  That said: the baseline test  submission process must achieve a passing mark (no failures) before the vendor is allowed to move to the next step below (see: Completing the Certification Process)

Reminder: The technical resource will receive a login to the Certification Website prior to this step.

The steps for the VTCP Baseline Submission Process are listed below.

  1. Prepare the ZIP file consisting of the BASELINE artifacts
  2. Login to the certification website
  3. Hover over: STEP 1 Submit Baseline, and CLICK the button
  4. Fill in the form for the Baseline, upload the ZIP file
  5. Click SUBMIT
  6. <Wait 5 to 10 minutes for testing to run and complete>  Tests will execute in the background.
  7. WHILE WAITING: the technical resource may view results, get help, view workflow status, or view workflow inbox
  8. Once the tests have completed running (in the background), the results will be made available and an email is sent to the technical resource that the testing is complete.
  9. To Determine a PASS / FAIL on the submission click view latest resultsor view workflow status – both options will state if the overall submission passed or failed.   A single failure in the testing process will constitute a failed submission.
Retention Period for Results

We have a varying retention period for the test results.

  • Baseline Test Cases – Individual Test Results
    • Baseline test results will be kept for a maximum of one year. EXCEPT as indicated below
    • Exception: When a single existing submission is re-run by the administrator (due to technical failure of some kind), any existing results for that single submission / upload will be deleted, and all tests for that submission will be re-started.

ALL submissions are logged in the workflow status log.  A running history of all submissions will be kept for a period of 5 years in the workflow status log only.  The individual baseline test cases

Was this article helpful?

Related Articles

Shopping Cart