# High-level Overview

This documentation is an introduction to the overall structure and design of the Tricloud Nexus platform. It explains how components work together to provide a seamless and scalable IoT solution.

<figure><img src="/files/BtExh9H8MO0efWKMkyZB" alt=""><figcaption></figcaption></figure>

***

### Platform Features

All management, operations, and configuration happen in the **Nexus Management Portal**, organized into three pillars:

### Applications

An application is a packaged set of one or more **modules** that work together to do a specific job. It is a “bundle” that includes the modules, their configuration, versions, and how they are connected. The Nexus platform provides the following functionality:

* **Build** and version modules and applications, using built-in, custom and third-party containers.
* **Design** and model data storage, collection and models.
* **Integrate** with external systems and services.

[More information](#applications)

### Operations

Operations cover day-to-day work that keeps systems reliable and safe. It includes the following areas:

* **Manage** security, provisioning, and deployments on devices.
* **Maintain** the platform by using diagnostics, remote service tools, and Update Center.
* **Monitor** alarms, data flow, and device health in real time.

[More information](#operations)

### Insights

Insights is about turning your data into answers people can use. It covers the following areas:

* **Explore data** with built-in query tools and AI assistance
* **Drive improvements** using dashboards, module/app rollouts, and targeted optimizations
* **Apply analytics** and custom ML/AI models to turn data into actions

[More information](#insights)

***

### Execution of Modules & Applications

Tricloud Nexus features a Module and Application Store, that enables automated deployment of containers from cloud to edge, for execution in a near real-time environment.

You can build applications in the platform based on a selection of multiple modules, thereby packaging a set of modules for a specific use-case. 3rd party containers can be imported as modules to the platform as well.

All modules and apps are handled with full traceability and versioning, making it easy to re-deploy to previous versions id necessary.

By having a module and application store you get full control of your deployed solution and gain the possibility to deploy eg. AI algorithms to the edge on a continuous basis. The easy deployment of new improved models will help accelerate your continuous improvement efforts.

***

### Data Collection (DataOps)

**Connect** to virtually any data source or OT system like PLC, SCADA, MES or robotics.

Connect to standalone IoT devices measuring temperture, humidity, flow or vibration.

Connect to barcode scanners for traceability or Computer Vision cameras for streaming video or quality control operations.

Connect to company wide UNS Brokers for access to enterprise real-time data.

Connect to FTP or file shares to either transfer or analyze files at the edge or cloud.

**Collect** data from data sources, validate it, aggregate and enrich it with metadata, and assign it to the asset hierarchy for a unified structure.

Structure data according to the ISA-95.2 standard and use the unified asset hierarchy to handle deployment to many edge devices.

Use Nexus Management Portal for configuration or integrate 3rd party systems through the API or CLI for fully automated workflows.

**Process** data before storing in cloud. Optionally aggregate and compress data before storing in cloud for increased performance and operational cost optimization.

**Store** data in the cloud, to one or more endpoints / historians, including Datalake, SQL databases, Azure Fabric and more.


---

# 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://docs.tricloudnexus.io/platform-architecture/high-level-overview.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.