CIRMS GUI Screenshots

CIRMS Home — Centralized Operational Overview

The CIRMS Home dashboard provides a consolidated view of the deployed platform, combining product and instance information, available tools and modules, GL3 and GL4 object distribution, system health, AI readiness and recent execution information. It acts as the operational entry point into the CIRMS environment, allowing users to move quickly between Automation, Healthcheck, Monitoring, AI Data, AI Models, AI Agents, Reports and Data Warehouse functions.

• Product, build, platform and instance details
• RDBMS and business tools and modules
• GL3 / GL4 object distribution and readiness indicators
• System health, AI-ready objects and execution timing

Automation Command Center — Execution and Operational Visibility

The Automation Command Center provides centralized visibility into automated execution across managed environments. It presents execution activity, target hosts, warnings and errors, environment distribution, RDBMS information, version distribution and historical automation activity in one operational view. The dashboard helps teams review execution status, identify failed or problematic tasks and understand how automation is distributed across hosts and environments.

• Atom execution history, heartbeat and activity
• Host, target-host and environment status
• Warnings, errors and execution counts by atom
• Build information and RDBMS version distribution

Healthcheck Command Center — Proactive Monitoring and System Integrity

The Healthcheck Command Center provides a structured view of infrastructure and database health across the managed environment. It summarizes healthcheck results, healthy and unhealthy resources, critical and warning conditions, overall health score and the latest execution status. Detailed healthcheck groups cover database and RDBMS health, configuration, performance and capacity, maintenance and operations, services, and security and access.

• Database and RDBMS health assessments
• Configuration, performance, capacity and security checks
• Critical, warning and total issue counts
• Historical health trends and infrastructure status

AI Data Command Center — AI Data Readiness and Knowledge Preparation

The AI Data Command Center provides visibility into the GL4 AI Data Readiness pipeline, from source registration and metadata processing through curation, document generation, chunking, vectorization, semantic validation and final readiness. It brings together registered-object status, AI-ready and not-ready objects, row-change counters, acquisition strategy, transformation metrics, documents, versions, chunks, vectors and readiness attention indicators.

• Stage 0 → 7 AI Data Readiness pipeline
• Row-change and transformation counters
• Identity, change-detection and acquisition strategies
• Documents, versions, chunks, vectors and readiness attention

Automation Reports — Trace Every Automated Object in GL3

Automation is only trustworthy when its activity can be reviewed. The Automation Reports area gives GL3 operators structured access to execution history, unique and summarized Atom executions, Atom-to-host relationships, Matrix configuration, process warnings and environment inventory.

This reporting layer is important because every automated object should remain observable after execution: teams need to know what ran, where it ran, how often it ran, which configuration was used and whether warnings or errors were raised. That turns automation from a black box into an auditable operational process.

• Atom execution history and unique execution reporting
• Atom-to-host and Matrix configuration relationships
• Automation process warnings and package errors
• Environment inventory and alive-host reporting

RDBMS Reports — Event History and Full Audit Visibility in GL3

The RDBMS Reports area organizes the database events collected by GL3 into operational and audit-focused reports. It covers inventory, file growth and shrink activity, DBCC execution, backup and restore activity, error-log findings, object changes, permissions and access events.

For controlled operations, it is not enough to know the current database state. Teams also need a reliable history of what happened, when it happened and what changed. These reports support a complete audit view across the RDBMS events captured by GL3, helping administrators investigate incidents, verify operational actions and review access or configuration changes.

• RDBMS inventory, auto-growth, shrink and DBCC activity
• Backup, restore, error-log and object-change reporting
• Database, schema, login, user and role audit events
• Operational evidence for incident review and change auditing