One of the benefits of incorporating a Rigado Bluetooth low energy module into a product is the ability to easily register and list the product with the Bluetooth SIG since all testing has already been completed. Before a product can be listed, the Bluetooth SIG requires an active membership. See the Bluetooth SIG website for membership information.
The steps outlined in this article guide a member company through the process of preparing a submission for listing using existing Qualified Design IDs (QDID). At the Bluetooth SIG website, this is identified as a "Declaration" under Path 1 at this page.
- Create Project
- Select "Traditional Project" under Project Type, and "End Product" from the Product Type drop-down. Enter a Project Name and optionally your hardware and software version. No need to select any layers at this time. Enter an expected qualification date. Click Save.
- Now open the new project. The example here is "BMD-300 Test".
- Select "Combine with QDID" from the drop-down.
- Search for a QDID and then click "Combine" under product listing in the results. Then select OK. This will return you to step 4. Just repeat for each QDID.
See this Help Center article for a list of current QDIDs.
- You should now have each QDID associated with your project. (Note that the QDIDs are shown using their Declaration ID).
- Now click on "Core ICS", and the "PROD" to change the ICS from a Component (tested) to an End Product). Click Save.
- Now click on Consistency Check. You should see the following with no invalids.
NOTE - As of Jan 12, 2017, there is currently a Test Case Waiver for the following two invalid cases that may be encountered:
- If [LL] (9/2) is Supported then [LL] (6/21 and 6/23) are Mandatory
- If [LL] (9/2) is Supported then [LL] (7/21 and 7/23) are Mandatory
The Test Case Waiver ID is 918 and can be viewed here: https://www.bluetooth.org/tse/tcwaiver_view.cfm?tcw_id=918
Provided these are the only two invalid cases you have, you should be able to reference this Test Case Waiver ID in the listing and continue.
NOTE - If the "Summary ICS" shows an invalid, click on the link provided and then the Invalid item. Swap the two items so the "No Longer Used" item is not enabled, then re-run the consistency check.
- You can now click on "Test Plan" to generate the test plan spreadsheet. Check each entry to show "PASS" and indicate which QDID's evidence you are claiming for each test case. At this time, this procedure does not automatically assign the QDIDs to each of the tests. This needs done manually.
One way to generate a list of which QDID applies to each test is to generate a project for each QDID separately, combine with that QDID, and the generate a test plan. Each plan will then have all the test cases covered by that QDID, and they can be assumed to have passed because the product is listed. Then go back into the project and combine all QDIDs and create the overall test plan spreadsheet.
An example test plan is shown here:
Here is a PDF that has some of the requirements for the test plan and claiming test items by reference to a QDID of a tested component (Bluetooth SIG membership required): Bluetooth Program Requirements Document (PRD).
When a Test Plan is completed, it becomes the Test Declaration that gets updated. For some more information, here is a response from the BQE regarding this:
To combine tested components into a new design for end-product is a typical sample for most Bluetooth devices in current market.
The advantage for combining tested components is all conformance tested results can be inherited from referenced QDID without re-testing if they were assessed within 3 years.
Once getting a test plan from a project, please assess all test cases in test plan, and have your results addressed with TDU (tested declaration upload) to get this project prepared for submission.
At this point, upload the completed Test Plan (now Test Declaration), and it now allows the project to start the qualification process.
Note: There is a requirement for having a Compliance folder, as defined in the above linked PRD in section 3.2.