> For the complete documentation index, see [llms.txt](https://daniel-jaroszewski.gitbook.io/syswatch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daniel-jaroszewski.gitbook.io/syswatch/import-data.md).

# Import Data from File

It is possible to define an input stream for SysWatch. In the case of a sensor file and in the case of a diagnostic file, the relevant information can be uploaded into SysWatch. The file must be a CSV file with a semicolon as a separator. Alternatively, the parser also checks for tab delimitation.

## **Sensor data**

Two different file formats can be imported, which are automatically differentiated from one another:

***Variante 1:***** \[AnlagenCode]\_Beliebiger-Text\_V1.csv**

| ***Timestamp***         | **ParameterCode** | ***Value*** |
| ----------------------- | ----------------- | ----------- |
| 01.01.2018 00:00:00.000 | ParameterCode 1   | 108         |
| 01.01.2018 00:00:00.000 | ParameterCode 2   | 5           |
| 01.01.2018 00:01:00.000 | ParameterCode 1   | 102         |

***Variante 2:***** \[AnlagenCode]\_Beliebiger-Text\_V2.csv**

| ***Timestamp***         | **ParameterCode 1** | **ParameterCode 2** | ***…*** |
| ----------------------- | ------------------- | ------------------- | ------- |
| 01.01.2018 00:00:00.000 | 108                 | 5                   |         |
| 01.01.2018 00:01:00.000 | 102                 | 7                   |         |
| 01.01.2018 00:02:00.000 | 110                 | 8                   |         |

## **Fault memory data**

1\. The minimum information for analyzes with diagnostic data can be found under "Essential fields".

2\. "Descriptive fields" can be set automatically during the parsing process or afterwards by the user (IMPORTANT: The event code must be unique).

3\. The "environment data" and "operating counter" are also used here as additional status descriptions, but are not automatically included in the structure by default.

### Fields

DateStart Datum Kommt

DateEnd Datum Geht

EventID Eindeutiger Ereignis-Code

EventText Definitionsbeschreibung des Ereigniscodes

SystemID System-Code

SubSystemID SubSystem-Code

ComponentID Component-Code

SubComponent ID SubComponent-Code

DiagnosisType Diagnose Typ (Protocol, Warning, Error)

Prio Priorität (Zusätzlicher Integer)

DuringOperation Markierung, ob die Aufzeichnung im Betrieb statt fand (true/false)

Sensor-Snapshots

GPS-Koordinaten

***Beispiel:***

| ***DateStart***     | ***DateEnd***       | ***EventID*** | ***SystemID*** | ***DiagnosisType*** | ***…*** |
| ------------------- | ------------------- | ------------- | -------------- | ------------------- | ------- |
| 01.01.2018 00:00:00 | 01.01.2018 00:01:00 | 71F0          | ZSG1           | Protocol            |         |
| 01.01.2018 00:00:00 | 01.01.2018 00:01:00 | 719A          | Energieanlage  | Warning             |         |

## Maintenance data 


---

# 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://daniel-jaroszewski.gitbook.io/syswatch/import-data.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.