> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/hardware-products/hardware/petroleum-devices/commander/commander-site-controller-installation-guide/device-overview.md).
# Device Overview
The Commander Site Controller is the site controller for Petro C-Store environment. It boosts the capability and features of ethernet-compatible Point of Sale (POS) workstations by expanding both processing power and communication bandwidth, thus enabling more efficient management of peripherals.
The hardware is designed with future requirements in mind, featuring built-in support for additional serial ports, CPU boards, and extra fan or power connections that might be necessary. Verifone will certify the implementation of these expansion capabilities.
System peripherals, including fuel dispensers, dispenser card readers (DCRs), and car wash controllers, are directly connected to the Commander Site Controller. Additionally, the Commander Site Controller incorporates the functionality of a V950™ for conducting on-site backups.
The Commander Console offers enhanced functionality through four distinct software modules: Journal Browser, Configuration Client (for browser-based configuration), Transaction Manager, and Report Navigator.
Figure 1: Commander
Site Controller
and
Workstations
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.verifone.com/hardware-products/hardware/petroleum-devices/commander/commander-site-controller-installation-guide/device-overview.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 `build a script that syncs our docs to a CMS` 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.
