> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/understand-your-business/ai-features/service-display-monitor-getting-started/service-display-monitor-camera-placement-guide.md).

# Service Display Monitor: Camera Placement Guide

Ensure optimal camera placement and AI-monitored zone coverage for your drive-thru setup when using the Service Display Monitor.

This article provides guidance on ideal camera placement for your [Service Display Monitor](/docs/understand-your-business/ai-features/service-display-monitor-getting-started.md) (SDM) and Drive-Thru zones.

Refer to this guide to understand the key factors—vehicle visibility, angle, lane clarity, obstructions, and lighting—that directly impact timing accuracy and AI detection performance.

## Baseline Camera Placement Requirements

Any camera used for the SDM should at least meet the following standards:

* Vehicles are fully visible in the camera view
* Camera is placed at a proper angle (not top-down)
* Camera is close enough for detail (not too far away from vehicles)
* No obstructions block vehicles in the camera view
* Lighting is adequate

**Note**: It is highly recommended for your SDM environment to fall under the "Best" or "Better" camera placements, as outlined below. Always avoid the "Bad" camera placement as this is the number one cause of issues related to poor performance.

***

## Best Placement

Use this section to follow the **highest standard of accuracy** for SDM camera placement\*\*.\*\*

Key characteristics:

* 90%+ vehicle visible at stop point
* Vehicle clearly framed (30–60% of image)
* Optimal angle (\~15–30°)
* No occlusions or competing lanes
* Consistent lighting (day + night)

| **Menu Board** | **Service Window** |
| -------------- | ------------------ |
|                |                    |
|                |                    |
|                |                    |

***

## Better Placement

Use this section for a strong SDM setup to improve accuracy and consistency.

Key characteristics:

* 75%+ vehicle visible at stop point
* Improved angle (front + partial side view)
* Lane visible to detect vehicle prior to zone entry
* Minimal occlusions of vehicle

| **Menu Board** | **Service Window** |
| -------------- | ------------------ |
|                |                    |
|                |                    |

***

## Good Placement

Use this section for a decent SDM camera setup. It is still recommended to improve your setup by following the "Better" and "Best" placements outlined above.

Key characteristics:

* 50%+ vehicle visible at stop point
* Clear lane visibility
* Minimal obstruction
* Reasonable lighting conditions

| **Menu Board** | **Service Window** |
| -------------- | ------------------ |
|                |                    |
|                |                    |
|                |                    |

***

## Bad Placement

This section provides examples of camera placements you should avoid completely for your SDM setup.

Common issues:

* Vehicle too small / too far (less than 50% vehicle visible at stop point)
* Steep or top-down angle
* Obstructions (menu boards, poles, signage, parked vehicles)
* Poor lighting (glare, darkness)
* Multiple lanes causing confusion

| **Menu Board** | **Service Window** |
| -------------- | ------------------ |
|                |                    |
|                |                    |
|                |                    |
|                |                    |
|                |                    |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.solink.com/docs/understand-your-business/ai-features/service-display-monitor-getting-started/service-display-monitor-camera-placement-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.