TRUSTED ADVISOR APPLICATIONS
Show the expertise behind your work.
Trusted Advisor status recognises a company’s ability to build DQMH applications and guide customers in using the framework.
01 / ELIGIBILITY
A company commitment.
Trusted Advisor status is awarded to a company. Your team should demonstrate proficiency in designing and implementing DQMH applications, advising customers, and keeping its LabVIEW developers proficient with the framework.
- At least one Certified LabVIEW Architect (CLA), or someone with equivalent experience and proficiency.
- The NI DQMH Framework badge for every developer working with DQMH.
- A DQMH-based LabVIEW project developed by your company for the Consortium to review.
02 / THE PROCESS
From quote to payment to review.
Introduce your team and project.
Tell us your team size, the work you do with DQMH, and the project you would like reviewed. Include a short description, the number of modules, and your development setup: source control, build process, workflows, and automation.
Receive an application quote.
The application fee starts at US$1,800 and includes your first year of membership. The Consortium quotes the fee based on the size and nature of the project and the review work involved. Annual renewal is US$1,800 for five users, with additional users at US$360/year each. Download the PDF quote for budget approval, then pay through its private link.
Prepare your submission.
Payment must be received before the Consortium starts reviewing the application. A quote or payment does not approve admission. The required developers’ badges must also be in place before code review begins. Arrange the project handover with the Consortium after the initial enquiry.
Have your work evaluated.
The review assesses your team’s understanding of DQMH, its ability to deliver customer projects, and its ability to advise others. Admission depends on the review outcome; payment alone does not grant Trusted Advisor status.
03 / YOUR SUBMISSION
Prepare a project we can review.
Required
- A LabVIEW project based on DQMH, ideally representative of your team’s real-world work.
- The LabVIEW version used to maintain the project.
- The DQMH version used to maintain the project.
- All other dependencies needed to run the software. A VIPC file is encouraged.
Helpful supporting material
Include project documentation, test configuration, static-analysis results, and CI/CD information where available. Share your own style guide and VI Analyzer tests if your team uses them.
Recent LabVIEW and DQMH versions are preferred for reviews. If your project needs an older environment, explain the reason and agree the review setup with the Consortium.
04 / WHAT WE LOOK AT
More than whether the code runs.
The DQMH Style Guide and corresponding VI Analyzer tests provide an initial view of your code. The review also considers:
- Overall architecture and adherence to DQMH better practices.
- User interface and documentation.
- Dependency management and build specifications.
- Project organisation and coding practices.
- DQMH-specific patterns and understanding of the framework.
