/ architecture

Connected by design. Clear in responsibility.

SWAPP carries data and user context. UMAY OS Core is designed to coordinate permitted workflows, while Scientist produces evidence-based investigations. People evaluate the advisory; control authority is not delegated to this flow.

See with SWAPP.Go deeper with UMAY.

SWAPP is the operations workspace. UMAY OS is the umbrella for investigations, specialist agents and durable knowledge.

01 / SWAPP

The operations workspace

Find data with Explorer. Read the context with Trend and Vitals. Connect investigation steps through Event and Plan.

Target architecture · Integration and acceptance work is ongoing.

Explore UMAY OS

SWAPP’s shared data backbone

01

Data sources

Permitted historical data, existing approved read sources and synthetic examples. Source, time window and access scope remain traceable throughout the investigation.

02

Shared service layer

Every module reaches data through the same async clients. Response ceilings, sampling and status-code traps are solved in one place — modules do not rediscover them.

03

Modules

Each module registers with a self-describing manifest; a catalog endpoint feeds the interface. Modules do not reach into one another.

04

Interface

A single-page application; module routes load lazily and language catalogs are split per module, so the first paint stays light.

Security and compliance

The target architecture enforces identity and authorization on the server; model output grants no authority. Sensitive data is processed locally. Writing to SCADA/DCS controls, changing setpoints, start/stop actions and alarm-state changes are outside the advisory scope.