You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The open-source, AI-powered Unified Namespace (UNS) Operations Center. Visualize MQTT topic trees, build dynamic SVG HMIs, transform data via ETL, and leverage an embedded Autonomous AI Agent for alerting and historical time-series analysis.
Design, test, validate and demo your Unified Namespace architecture: topic trees, payload schemas and stateful simulation, without touching a single physical system.
UNS-native, cybersecurity-aware multi-agent reference architecture for U.S. small-to-mid manufacturers. Industrial agentic intelligence aligned with ISA-95, NIST AI RMF, and CMMC L2.
UNS Bridge Connector is an observer-only integration add-on for Microsoft Dynamics 365 Business Central. It connects Business Central to a Unified Namespace (UNS) and makes shopfloor execution data visible in ERP context. The app ingests non-authoritative execution facts (for example quantities produced, scrap, aggregate work order KPIs).
IIoT telematics simulator in Rust and Python: fleet of virtual tractors with J1939 style data, store-and-forward spooling, MQTT, and Kafka integration for agtech/Industry 4.0
Aber, the shopfloor data platform: Sparkplug B ingestion, a TimescaleDB historian, and a Supabase-backed directory, dashboard and audit trail, deployed with one Helm chart.
Decoupled, event-driven IIoT and web-based SCADA platform implementing the Unified Namespace (UNS) pattern, MQTT Sparkplug B v3.0, and ISA-101 High-Performance HMI standards. Engineered with a bifurcated Hot/Cold path pipeline and reactive web runtimes.
The workspace Tatsoft uses to build FrameworX industrial automation projects with Claude Code: working agreement, delivery skills, templates, and a worked water treatment project. Targets FrameworX 10.1.5 and later.
Measure 100% of a manufacturing process, including the manual steps: an open IoT node on every machine, feeding OEE and MPS. Concept, first pitched as FIDO in 2015.