> 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-user-guide.md). # Service Display Monitor: User Guide This guide provides step-by-step instructions on how to setup, use and optimize your Solink [Service Display Monitor](/docs/understand-your-business/ai-features/service-display-monitor-getting-started.md). {% embed url="" %} ## Before You Begin * You must have an account with permission to edit layouts on the SDM. See [this FAQ](/docs/understand-your-business/ai-features/service-display-monitor-getting-started/service-display-monitor-faqs.md#why-cant-i-see-the-edit-button) for more information. * You must have at least one camera enabled with Vision Analytics for vehicle detection. See [Enable Vision Analytics](/docs/understand-your-business/ai-features/vision-analytics/enable-vision-analytics.md) for more information. * You must have at least one AI-monitored zone for an area with vehicles, such as a drive-thru lane. See the following guides for more information: * [Zone Tracking Events](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md) (how to create an AI-monitored zone) * [SDM Camera Placement Guide](/docs/understand-your-business/ai-features/service-display-monitor-getting-started/service-display-monitor-camera-placement-guide.md) *** ## Assign AI Tags The first step to getting the SDM operational is to assign an AI tag to one of your AI-monitored zones within the Solink platform. To assign an AI tag: 1. Launch an AI-enabled camera on the Video page, specifically for vehicles (see [Enable Vision Analytics](/docs/understand-your-business/ai-features/vision-analytics/enable-vision-analytics.md) if you have not yet configured a camera for AI vehicle detection). 2. Navigate to the [Zone Tracking Events](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md) tab (AI > Zone Tracking > Events tab): 3. Select an AI tag in the dropdown list: 4. Select **Save** to apply the changes. Once you have assigned an AI tag, you can pair this zone to a widget in the SDM. Once paired, the widget in the SDM tracks and displays the data from this zone - see the following section to learn to how to launch the SDM and create your first widget and layout. **Tip**: See [SDM Widget Types](#sdm-widget-types) below for more information on recommended pre-made AI tags to use for specific widgets. *** ## Launch SDM Select the SDM button near the top-right of the Solink platform to launch it. *** ## SDM Layouts The SDM is made up of a **layout** containing widgets - data points tied to your AI-monitored zones. ### Create a New Layout You must create a new layout when using the SDM for the first time. Select the large "+" button in the middle of the screen when you first launch the SDM to create your first layout. You can also create a new layout afterwards whenever you want a fresh start — for example, when you’re testing a different mix of widgets or building a layout for a new menu rollout. To create a new layout: 1. Select the **Layout dropdown menu in the top-right > New Layout button to create a new layout**: 2. Type a name for the layout. 3. Select **Create** to create your new layout. Now you can create widgets for this layout. See the following sections for more information. ### Delete Layout If you need to delete the layout, select the More Actions icon next to the layout (three dots) > **Delete**: ### Edit Layout Select the **Edit** button in the top-right corner of the page to edit a layout, including: * Re-arrange widget placement * Edit widgets * Delete widgets *** ## SDM Widgets Your layout consists of widgets that display AI-monitored zone data. ### Create SDM Widget To create a new widget: 1. Select **Edit** in the top-right corner. 2. Select **Add Metric** to add a new widget. Note that if you are at the [maximum number of widgets](/docs/understand-your-business/ai-features/service-display-monitor-getting-started/service-display-monitor-faqs.md#how-many-widgets-can-i-put-on-one-layout), you are not able to add an additional widget until you delete another one. Now you can configure the following: * **AI Tags**: Choose the camera zones that power this widget. Tags like **MENU**, **WINDOW**, and **STACK** come from the AI tags you applied to your zones. * **Name**: Give a name to the widget. It is recommended to keep it simple, like "Menu Board 1", for clarity. * **Widget Type**: Set what metric the widget displays. See [SDM Widget Types](#sdm-widget-types) below for more information. * **Count/Default Threshold**: The value that turns the widget red. For **Count** widgets, enter a single number. For **Time**, enter minutes and seconds. * **Horizon/Time Horizon**: Determine whether the widget displays in **Real time** or a rolling total (**Sum of last hour**). Use **Sum of last hour** for widgets that track throughput or total drive-offs. * [**Day Parts**](#day-parts): An expandable section that lets you set different thresholds for different times of day. See [**Day Parts**](#day-parts) below for more information. ### SDM Widget Types Available widget types for the SDM include: #### Count Tracks how many vehicles are in a tagged zone (real time) or how many zone visits occurred in a time window. Use for stack depth, cars at the menu board, or queue length. * **Recommended Widget Tags**: Use "Stack" if the zone tracks the vehicle stack in drive-thru or oil change bay (vehicles lined up in the zone). Use "Queue" if the zone tracks single vehicle queue area (menu board, drive-thru window). Use Bay 1/2/3 to track daily throughput. #### Time Tracks how long vehicles stay in a tagged zone. Use for tracking service time at the window or menu board wait time. * **Recommended Widget Tags**: "Menu Board", "Service Window", "Bay", etc - all to track vehicle time spent at those areas. #### Drive-Off Tracks vehicles that left the lane before completing the order (drive-off detection on the zone), totalled over a time window. Use this widget to spot abandonment or line issues over a shift or day part. * **Recommended Widget Tags**: "Queue" #### Live Feed Shows rotating live video from cameras tied to your tags. Use this widget to ensure staff see the lane while numbers update on other widgets. If you use more than one camera, it rotates between them on a rotation interval (default 5 seconds, configurable 2–60 seconds). **Note**: You can have up to 2 Live Feed widgets per layout. * **Recommended Widget Tags**: Any tag on zones/lines on the cameras you want on screen (e.g. Queue, Bay 1) #### Total Journey Time Tracks **average time** from journey start zone to end zone (full lane), for completed trips only. Use for end-to-end speed of service (e.g. menu to pickup). * **Recommended Widget Tags**: Use the tag(s) associated with the end zone (often "Menu Board" in the start zone + "Service Window" in the end zone, or your journey start/end names). This widget requires a start and end zone configured. See [Track Single-Lane Vehicle Time](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md#track-single-lane-vehicle-time) for setup information. *** ## Day Parts **Day Parts** are the time windows that make up your operating day — for example, breakfast, brunch, or afternoon rush. They appear in the **Day Parts** panel on the right side of the layout editor: Day Parts allow you to set different service standards in the SDM based on time of day. For example, if your lunch hour between 12-1 PM is typically busier, you can create a dedicated Day Part for this block of time, assign it to a specific widget, then set a different Threshold (see [Count Threshold](#create-sdm-widget)) specifically for this block of time to create an additional sense of urgency during the lunch rush. ### Create a Day Part To create a new Day Part: 1. Ensure you are in [Edit](#edit-layout) mode. 2. Select the **+** icon in the top-right of the **Day Parts** panel. 3. In the **New Day Part** window, enter a **Day Part Name** — for example, **Afternoon Rush**. 4. Under **Active Days**, check each day of the week the day part should run, and set its start and end times. 5. If the times are the same every day, select **Copy to all** next to the first day to apply that day’s times across the rest of the week. 6. Select **Save**. The new day part appears as a block on the schedule. ### Assign Day Part to Widget Once you have day parts, you can override a widget’s default threshold during specific windows. This is useful when your service expectations change throughout the day — for example, tighter targets during Afternoon Rush. To assign a Day Part to a widget: 1. Ensure you are in [Edit](#edit-layout) mode. 2. Select the "gear" icon for the widget you want to edit. 3. Navigate to the **Day Part-Specific Thresholds** section. 4. Check the box next to the Day Part you want to assign to this widget and set a new threshold for this day part. For example, if you set 25 seconds, the widget turns red when it exceeds 25 seconds only during the period of time for the selected Day Part. It still follows the **Threshold** during the hours outside of the Day Part. --- # 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-user-guide.md?ask=&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.