# Requirements

### Requirments

inSCADA requires hardware resources in proportion to the scale of your applications. The parameters that determine the scale of your application are effective in consuming hardware resources. They are

* Variable,Tag, I/Os Numbers,
* Number of tags with Value Expression content,
* Number of tags with Log Expression content,
* Number of Alarms,
* Number of Scheduled Script and the Script Content,
* Number of Connections,
* Number of Online Users at the same time.

inSCADA uses a minimum of 2GB of RAM and 1 GB of disk space on the system it is installed.

For small-scale projects and development activities, you can install them on a computer with the following features.

| Hardware     | Description     |
| ------------ | --------------- |
| CPU          | Intell Core i3  |
| MEMMORY      | 4 GB RAM        |
| DISK SIZE    | 100 GB          |
| OS           | Windows / Linux |
| Display Size | 1280x1024       |

inSCADA is designed for the most efficient use of hardware resources.

| Software     | Descriptions    |
| ------------ | --------------- |
| OS           | Windows / Linux |
| Java Version | 1.8             |
| Browser      | Chrome/Firefox/ |
| Database     | PostgreSQL 9.6  |
|              |                 |

{% hint style="info" %}
inSCADA is a web based application. It is therefore best practice that users run inSCADA on a network and connect to the server via a web browser on different computers.
{% endhint %}

You can also determine the scale of your applications by comparing them with the features of our sample test equipment below.

For example, we ran an application with 4 Modbus TCP Connections, 2 DNP3 Outstations Connections, close to 2000 Value expression, and Log expression with approximately 5,000 variables in a 4 GB Linux Mint computer with i5 processor. Data updates in screen could be under even 1 sec.   


---

# Agent Instructions: 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:

```
GET https://inscada.gitbook.io/ins/en-1/installations/untitled.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.