Skip to main content

Cyzag Blueprint Overview

What is Cyzag Blueprint?​

Blueprint is a reference implementation of the Cyzag stack: a .NET + SQL Server backend, a React web frontend, native iOS/Android clients, React Native/Expo, and Kotlin Multiplatform (KMP) shared code. It is not a product; it is a foundation and a lab where we capture patterns, experiments, and what “good” looks like across the stack.

The goal is to provide small, well‑scoped slices that demonstrate end‑to‑end behavior you can reuse in Cyzag projects.

Current Scope: Phase 1​

Blueprint focuses first on Phase 1: Operator Rounds & Asset Condition Monitoring. This foundation includes:

  • Operator Rounds: Structured rounds with checkpoints that guide operators through asset inspections on the plant floor
  • Asset Readings: Capture counters, temperature, pressure, vibration, and other measurements tied to asset attributes
  • Assets & Asset Types: Equipment tracking with customizable attributes per type
  • Asset Attributes: Flexible attribute system for defining measurement points and properties
  • Functional Locations: Plant/site hierarchy showing where assets reside and work happens
  • Offline-first: Mobile apps work without connectivity; readings sync in the background when available
  • Last Known Value & History: Track current state and historical trends for each asset attribute

Phase 1 establishes the data model and workflows that Phases 2 and 3 will build upon without breaking changes.

Design Principles​

  • Offline‑first: the app should be useful without connectivity, with changes syncing when the network returns.
  • Clean CRUD: predictable list/detail/edit flows with clear states.
  • Validations: string validations and basic business rules baked into the UI and API.

What to Expect in the Docs​

These docs cover:

  • Product Roadmap: The three-phase vision and what each phase delivers
  • Features: Phase 1 capabilities (operator rounds, asset readings, offline sync)
  • Domain Model: Core entities (Assets, Asset Attributes, Functional Locations)
  • Future Phases: Overview of Phase 2 (observations, alerts) and Phase 3 (agentic AI, MCP server)
  • Architecture: Security, offline-first design, and technical patterns

Start with Getting Started for a quick local run, then explore the Product Roadmap to understand the vision, and dive into Features and the Domain Model for specifics.