> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2-node-supervisor-administrator-manual/introduction/purpose.md).

# Purpose

This document describes Node Supervisor application that is a desktop application used to install and manage multiple S2 Node Server processes.

S2 Node Server is a software that is run as a service and that creates a bridge between S2 radio network and the B3 system. S2 Node Server reads the S2 radio network configuration from B3, polls the nodes for readings and delivers them to B3 system. Comparing it to B2 system, S2 Node Server is an additional software block between S2 PC node and the system itself.

The positions of the hardware and software elements are shown on the diagram below:

![](/files/y5Z3deurMtJUZZFLh4pL)


---

# 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://help.boomerang3.com/s2-node-supervisor-administrator-manual/introduction/purpose.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.