The whole operation.The basis for decisions.
Developed under the UMAY umbrella, SWAPP brings operational knowledge into one workspace. Explore the data, deepen the investigation and support decisions with evidence.
14 modules / Shared data backbone / Human oversight

01 / Working together
See with SWAPP.Go deeper with UMAY.
SWAPP is the operations workspace. UMAY OS is the umbrella for investigations, specialist agents and durable knowledge.
The operations workspace
Find data with Explorer. Read the context with Trend and Vitals. Connect investigation steps through Event and Plan.
The orchestration layer
In the target architecture, Core coordinates permitted interactions with SWAPP and specialist tasks. Local models, tools and knowledge sources connect through versioned contracts.
Server-side authorization
Local models and tools
Single execution owner
From question to sourced investigation
Scientist is designed to examine permitted data with calculation tools, compare alternative hypotheses and expose missing evidence. A sourced advisory is presented for human review.
Versioned calculations
Alternative hypotheses
Sourced advisory packet
The decision stays with people
A specialist evaluates evidence and uncertainty, then accepts, corrects or rejects the advisory. An investigation becomes durable knowledge through human review and verification.
Review the advisory
Record the decision and rationale
Verify the outcome
Target architecture · Integration and acceptance work is ongoing.
Explore UMAY OS02 / Modular platform
Fourteen modules.One workspace.
From finding data to planning an investigation, a focused tool for every task.
14 modules · 5 categories
See all modules03 / Investigation flow
From a signal,to a traceable decision.
Data, context, evidence and human review in one chain.
Find the asset and signals
Start with shared context: asset, signal and data source. The lines below are generated, normalized examples.
Not connected to a live system.

Read the same time window
Compare signals on the same time axis. Moving together does not, by itself, establish causation.
Not connected to a live system.

Test a hypothesis against evidence
Illustrative hypothesis: a load change may affect the vibration pattern. Maintenance history and independent measurements are missing; a root cause is not verified.
- Hypothesis: operating-condition change
- Support: coincident pattern
- Missing evidence: maintenance and measurement records
Not connected to a live system.

Define the next investigation
Advisory: compare source data and maintenance history, then plan a specialist review. This example creates no work order; record changes require human approval.
- Verify the data source
- Examine alternative explanations
- Record the decision and outcome
Not connected to a live system.

An investigation advisory is reviewed by a person. No commands are sent to control systems.