> For the complete documentation index, see [llms.txt](https://support.onlogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.onlogic.com/support-articles/faqs/what-is-onlogics-quality-and-testing-process.md).

# What is OnLogic's Quality & Testing Process?

## <mark style="color:blue;">OnLogic Testing Process</mark>

All systems built by OnLogic go through a rigorous quality inspection and testing process. This page provides an overview of that process.

### Supply Chain <a href="#supply-chain" id="supply-chain"></a>

<figure><img src="/files/QW8q0z5zfJvmVWZ2RBVK" alt="" height="156" width="131"><figcaption></figcaption></figure>

OnLogic maintains a team of supplier quality engineers that work locally with our suppliers across the world. In addition to visiting the factories to conduct physical inspections, they monitor quality data and follow up with suppliers on any issues identified.

### Product Introduction <a href="#product-introduction" id="product-introduction"></a>

<figure><img src="/files/bbSrH80fxZHBpVntPi7h" alt="" height="165" width="300"><figcaption></figcaption></figure>

When a new product is added to our portfolio, it goes through a verification process. Compatibility, functionality, and regulatory certifications are verified.

### Components <a href="#components" id="components"></a>

<figure><img src="/files/MqXf7B5rGFH9kIrv39Ii" alt="" height="137" width="300"><figcaption></figcaption></figure>

Any changes made to existing components are reviewed by a cross functional team. If needed, the product introduction process is repeated to ensure a smooth transition to the new component revision. Components are stored in our climate controlled and ESD (electro-static discharge) safe warehouse prior to assembly. Strict ESD handling guidelines are in place.

### Assembly <a href="#assembly" id="assembly"></a>

<figure><img src="/files/19CqJbUJ6T3Hp9S9NGFU" alt="" height="300" width="243"><figcaption></figcaption></figure>

Systems are assembled by a team of well trained technicians. Specific work instructions for each configuration are followed and regularly reviewed by engineering team members. During each step of assembly, critical inspection points are checked off.

Example inspection points:

* Fans installed correctly
* Thermal paste application is to spec
* Expansion cards fully seated
* Auto power on is set
* Memory installed correctly
* No ports are blocked
* Visual and Mechanical Inspection

### Testing <a href="#testing" id="testing"></a>

<figure><img src="/files/zpaXa6aj1fNqxVtvtfRC" alt="" height="217" width="300"><figcaption></figcaption></figure>

Once assembled, systems go into our testing process where another set of inspections are conducted. Much of these are automated by our custom testing software.

Testing is specifically tailored to the components inside the system. Below is a list of common tests.

* BIOS version verification
* Add-on USB port(s) tested
* Network ping test to internal server
* Hardware IDs of all storage and PCI devices verified against order
* Hardware functional test
* CPU and disk temp monitored
* Results reported to server and verified against known good baseline


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.onlogic.com/support-articles/faqs/what-is-onlogics-quality-and-testing-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.