Differences

This shows you the differences between two versions of the page.

--- mistudio:architecture_overview [2026/09/18 13:49] – ↷ Links adapted because of a move operation tputman
+++ mistudio:architecture_overview [2026/09/18 15:57] (current) – tputman
@@ Line 9: / Line 9: @@
 …and extends it into a **visual, distributed, real-time system for building industrial applications**.
-But instead of writing code…
+Instead of relying only on traditional code, MIStudio allows applications and data flows to be built by connecting visual components.
-You connect blocks.
 ===== The Mental Model =====
@@ Line 23: / Line 21: @@
   * You **wire them together** to create behavior
-No hidden logic.
+The [[mistudio:design_editor:start|MIStudio Design Editor]] is used to build the visual interface using graphics and controls.
+The [[mistudio:logic_editor:start|MIStudio Logic Editor]] is used to connect data sources, components, and application logic.
-No black boxes.
+Together, the Design Editor and Logic Editor provide the visual and logical parts of an MIStudio application.
-Everything is visible and inspectable.
+Connections and component relationships are visible and inspectable in the Logic Editor.
 -----
@@ Line 37: / Line 37: @@
 It's a full data integration platform.
-{{.:pasted:20260324-133237.png?1200| MIStudio Overview}}
+{{.:pasted:20260324-133237.png?1200|MIStudio Overview}}
 <note>
@@ Line 69: / Line 69: @@
 ===== Data is the System =====
-In MIStudio, there is no separation between:
+In MIStudio, data, logic, and integration can be combined within the same application flow.
-  * Data
-  * Logic
-  * Integration
-They are all part of the same flow.
 Example:
@@ Line 84: / Line 78: @@
   * Alerts drive REST or PLC actions
-All without writing traditional code.
+This allows many workflows to be built visually without relying entirely on traditional code.
 -----
@@ Line 101: / Line 95: @@
 Rather than forcing everything into a single abstraction, MIStudio:
-> Connects them all together in a unified flow
+> Connects them together in a unified flow
 -----
@@ Line 135: / Line 129: @@
   * **Long-term maintainability**
-Key differences:
+Key characteristics include:
   * Strong typing and structured data
@@ Line 146: / Line 140: @@
 ===== Integrated Intelligence (AI + Heuristics) =====
-MIStudio treats AI as just another component in the flow.
+MIStudio can treat AI as another component in the application flow.
-{{.:pasted:20260324-132804.png?1200 | MIStudio AI Flow}}
+{{.:pasted:20260324-132804.png?1200|MIStudio AI Flow}}
 You can:
@@ Line 155: / Line 149: @@
   * Interpret results
   * Feed them back into the system
-  * Combine with rules and heuristics
+  * Combine them with rules and heuristics
 Example use cases:
@@ Line 174: / Line 168: @@
   * What the system does
   * How data moves
-  * Where decisions are made
+  * Where connections and decisions are made
-No reverse engineering required.
 -----
@@ Line 182: / Line 174: @@
 ==== 2. Data + Logic + Integration in One Place ====
-No need for:
+MIStudio can combine:
-  * Separate ETL tools
+  * Data flows
-  * Separate automation engines
+  * Application logic
-  * Separate integration layers
+  * Protocol integrations
+  * Visual displays
-It’s all one system.
+within the same application environment.
 -----
@@ Line 194: / Line 187: @@
 ==== 3. Works at the Edge and in the Cloud ====
-Deploy anywhere:
+MIStudio applications can be designed for deployment across environments such as:
   * Edge devices
@@ Line 205: / Line 198: @@
 ==== 4. Rapid Development Without Losing Control ====
-You get:
+MIStudio combines:
-  * Speed of low-code
+  * The speed of visual and low-code development
-  * Control of traditional engineering
+  * Access to configurable components and application logic
 -----
@@ Line 214: / Line 207: @@
 ==== 5. Extensible by Design ====
-New capabilities can be added as:
+New capabilities can be added through:
   * New components
@@ Line 220: / Line 213: @@
   * New integrations
-Without rewriting existing systems.
+This allows an application to expand as requirements change.
 -----
@@ Line 230: / Line 223: @@
 > Node-RED is a great idea.
-> MIStudio is what happens when you take that idea seriously for industrial, scalable, real-world systems.
+> MIStudio applies a similar visual-flow concept to industrial, scalable, real-world systems.
 -----
@@ Line 238: / Line 231: @@
 With MIStudio, you can:
-  * Build complete industrial applications visually
+  * Build industrial applications visually
-  * Integrate any data source or protocol
+  * Integrate different data sources and protocols
-  * Add intelligence, rules, or AI anywhere
+  * Add intelligence, rules, or AI to application flows
-  * Adapt quickly as requirements change
+  * Adapt applications as requirements change
-All while maintaining:
+while maintaining:
   * Structure
@@ Line 259: / Line 252: @@
   * An **integration layer across protocols**
   * A **foundation for intelligent automation**
+The [[mistudio:design_editor:start|MIStudio Design Editor]] provides the visual application-building environment, while the [[mistudio:logic_editor:start|MIStudio Logic Editor]] provides the component, data-flow, and logic environment.
 Built on the same principle as TransSECS:
@@ Line 268: / Line 263: @@
 ===== Related Pages =====
-  * [[mistudio:getting_started:start|Getting Started]]
+  * [[mistudio:getting_started:start|MIStudio Getting Started]]
   * [[mistudio:getting_started:what_is_mistudio|What is MIStudio?]]
+  * [[mistudio:design_editor:start|MIStudio Design Editor]]
+  * [[mistudio:logic_editor:start|MIStudio Logic Editor]]
   * [[mistudio:getting_started:project_structure|Project Structure]]
   * [[mistudio:getting_started:create_project|Create a Project]]
@@ Line 277: / Line 274: @@
   * [[mistudio:getting_started:connect_data_source_to_graphic|Connecting a Data Source to a Graphic]]
   * [[mistudio:getting_started:test_data_sources|Using Test Data Sources]]
-  * [[mistudio:design_editor:start|MIStudio Graphics]]