Overview
Mimir AIP’s data model is built around Projects as the top-level container, with resources organized hierarchically. All application data flows through the CIR (Common Internal Representation) format for consistency across storage backends.Entity Relationship Diagram
Core Entities
Project
Project
Top-level organizational unit grouping all resources for a domain or use case.
pkg/models/project.go:15
- One-to-many with Pipelines, Ontologies, Storage Configs, ML Models, Digital Twins, Schedules
- Projects are isolated — resources cannot cross project boundaries
active, archived, draft
Pipeline
Pipeline
Ordered sequence of processing steps for data ingestion, transformation, or output.
pkg/models/pipeline.go:24
- Belongs to one Project
- Can be triggered by multiple Schedules
- Spawns PipelineExecutions when run
ingestion— Fetch data from external sourcesprocessing— Transform or analyze dataoutput— Write results to destinations
Ontology
Ontology
OWL/Turtle vocabulary defining entity types, properties, and relationships for a domain.
pkg/models/ontology.go:10
- Belongs to one Project
- Referenced by ML Models (defines training features)
- Referenced by Digital Twins (defines entity structure)
- Optionally linked to Storage Configs (structures schemas)
draft, active, archived
Storage Config
Storage Config
Connection definition for a storage backend where CIR data is persisted.
pkg/models/storage.go:133
filesystem— Local or network-mounted directoriespostgres— PostgreSQL relational databasemysql— MySQL relational databasemongodb— MongoDB document stores3— S3-compatible object storageredis— Redis key-value storeelasticsearch— Elasticsearch search engineneo4j— Neo4j graph database
- Belongs to one Project
- Optionally references one Ontology
- Stores multiple CIR objects
ML Model
ML Model
Machine learning model definition linked to an ontology, trained by workers.
pkg/models/mlmodel.go:32
decision_tree— Fast, interpretable classificationrandom_forest— Ensemble methodregression— Linear/polynomial regressionneural_network— Deep learning
draft, training, trained, failed, degraded, deprecated, archived
Relationships:
- Belongs to one Project
- References one Ontology
- Used by Digital Twins for predictions
Digital Twin
Digital Twin
Live in-memory graph of entities and relationships, queryable via SPARQL.
pkg/models/digitaltwin.go:10
- Belongs to one Project
- References one Ontology (defines entity types)
- References multiple Storage Configs (data sources)
- Contains multiple Entities
- Supports multiple Scenarios
- Can trigger Actions
active, syncing, error
Entity
Entity
Instance of an ontology class within a digital twin.
pkg/models/digitaltwin.go:38
- Belongs to one Digital Twin
- Optionally references CIR data (via
source_data_id) - Has multiple relationships to other Entities
Data Flow Structures
CIR (Common Internal Representation)
CIR
Normalized format for all data flowing through Mimir AIP.
pkg/models/cir.go:35
api— REST API responsefile— Local or remote filedatabase— SQL query resultstream— Real-time data stream
csv— Comma-separated valuesjson— JSON objects or arraysxml— XML documentstext— Plain textbinary— Binary data
Pipeline Execution
Pipeline Execution
Record of a pipeline run, tracking status and results.
pkg/models/pipeline.go:46
pending, running, completed, failed
Trigger types:
manual— User-initiated executionscheduled— Triggered by a Scheduleautomatic— Triggered by an Action
Schedule
Schedule
Cron-based trigger for recurring pipeline executions.
pkg/models/schedule.go
- Belongs to one Project
- Triggers multiple Pipelines
Advanced Structures
Scenario (What-If Modeling)
Scenario
Hypothetical modifications to a digital twin for impact analysis.
pkg/models/digitaltwin.go:61
active, archived
Action (Conditional Trigger)
Action
Automated pipeline trigger based on digital twin conditions.
pkg/models/digitaltwin.go:114
Prediction
Prediction
ML model prediction result, optionally cached.
pkg/models/digitaltwin.go:98
Query Structures
CIR Query
CIR Query
Query structure for retrieving CIR data from storage.
pkg/models/storage.go:91
SPARQL Query
SPARQL Query
Standard SPARQL query for digital twin entities.
pkg/models/digitaltwin.go:183
Data Lifecycle
Next Steps
CIR Format
Deep dive into the Common Internal Representation format.
Architecture
Understand system components and deployment.
API Reference
Explore REST API endpoints for all entities.