Reusable automation bots
Execute focused administrative tasks with reusable ATOMS—the modular, atomized bots behind CIRMS workflows.
Automation. AI-ready knowledge. Intelligence.
Operate with control.
Prepare for intelligence.
Explore the capabilities behind CIRMS GL3 and CIRMS GL4—and the planned CIRMS GL5 evolution. From repeatable operational work to knowledge prepared for AI.
One platform. Clear responsibilities.
The right capability.
At each step.
Automate the work. Prepare the knowledge.
Build toward intelligence on a foundation you can inspect.
01 / AUTOMATEAvailable now
CIRMS GL3
Intelligent Automation & Data AcquisitionRun defined workflows, monitor resources and collect the operational information your teams need.
Explore automation02 / PREPAREAvailable now
CIRMS GL4
AI Data ReadinessTransform operational data into versioned documents, chunks and validated vector representations.
Explore data readiness03 / INTELLIGENCEPlanned development
CIRMS GL5
AI IntelligenceThe planned next step: apply AI models and conversational assistance to prepared CIRMS knowledge.
Explore planned capabilitiesCIRMS GL3Available now
Put repeatable work
under control.
Intelligent Automation & Data Acquisition combines reusable bots, workflow execution, resource monitoring and operational reporting in one working environment.
Give technical teams a consistent way to see what ran, what needs attention and what information has been collected.
Operational outcomeRepeatable execution. Visible system health. Usable operational data.
CIRMS GL3 product overview Workflow orchestration & jobs
Coordinate defined operational tasks and review execution activity, job outcomes and errors from a central interface.
Operational data acquisition
Collect and normalize information from connected infrastructure, databases, applications and services for reporting and downstream preparation.
Resource & environment visibility
Review managed hosts, databases, service status and environment information without assembling a picture from separate screens.
Health checks & diagnostics
Review configuration, backup presence, disk space, failed jobs and security settings. Distinguish healthy checks, warnings and failures.
Dashboards, reports & notifications
Use automation, healthcheck and monitoring views alongside Automation, RDBMS and Business Reports to investigate status and communicate findings.
From overview to investigation. Review execution history, host activity and health categories to focus attention on the affected resources.
CIRMS GL4Available now
Turn operational data
into AI-ready knowledge.
AI Data Readiness transforms the data acquired through GL3 into structured, curated knowledge through a traceable preparation pipeline.
See the source strategy, row changes, document lifecycle and readiness result—not just whether a job finished.
AI-platform neutral foundation. CIRMS GL4 prepares operational knowledge independently from the conversational or reasoning model selected downstream.
Preparation outcomeVersioned knowledge assets with visible processing and readiness status.
CIRMS GL4 product overview 
Controlled source registration
Register eligible source tables with defined metadata and row identity. Support source-key and keyless strategies within the validated registration rules.
Source-aware change detection
Select a supported acquisition strategy for each source. Track inserted, updated, deleted and unchanged rows as the knowledge foundation is refreshed.
Curation & schema validation
Turn raw data into a structured dataset and validate its schema before the later preparation stages continue.
AI documents & version history
Generate AI documents from curated data and track active, inactive, new and unchanged documents alongside current and historical versions.
Reusable chunks & vector embeddings
Divide documents into chunks, distinguish new from reused content, and track generated and approved vector representations.
Readiness & health monitoring
See object readiness, stage status, execution duration and issues requiring attention. Keep readiness and scan health visible as separate signals.
Inside the GL4 process
Follow the preparation. Inspect each stage.
Stages 0–7, from source metadata to readiness completion. Select a stage for details.
STAGE 0Metadata refreshDetails
Read source structure and identity information so preparation starts with the current source definition.
STAGE 1Raw dataDetails
Acquire source rows using the selected strategy and retain the raw input for subsequent preparation.
STAGE 2Data curationDetails
Validate the physical schema and prepare structured data for consistent downstream processing.
STAGE 3AI documentsDetails
Generate the document representation and manage its relationship to current and historical versions.
STAGE 4Chunk generationDetails
Divide documents into manageable chunks and track new and reused content.
STAGE 5Vector embeddingDetails
Create vector representations with the configured embedding process and track their status.
STAGE 6Semantic validationDetails
Validate the prepared assets and their vector relationships before final readiness completion.
STAGE 7Readiness completionDetails
Record the completed preparation outcome and expose readiness and health information for monitoring.
Source-aware, not one-size-fits-all. Registration, identity and change detection are validated for eligible tables. Acquisition methods depend on source support and configuration.
CIRMS GL5Planned development
Bring knowledge into
the decision process.
The planned AI Intelligence product is intended to connect enterprise AI models and conversational assistance to the operational data and prepared knowledge foundation built through GL3 and GL4.
The direction is human-supervised analysis: help people understand their environment, explore questions and review recommendations in context.
Choice of intelligence. The planned GL5 architecture is intended to support governed integration with both external AI providers and CIRMS intelligence models rather than tying the platform to a single model provider.
Roadmap, not current functionality.
Discuss the CIRMS GL5 roadmap GL5 is planned development. The capabilities below are intended scope, not a release commitment or an available AI assistant.
Conversational access & semantic search
Planned natural-language interaction with CIRMS knowledge, helping people find relevant operational information without navigating every report.
AI-assisted analysis & insights
Planned application of enterprise AI models to prepared knowledge for reasoning, recommendations and cross-department analysis.
Human-supervised decision support
Planned assistance for operational and managerial decisions, with business context and human review rather than unbounded autonomous action.
Capability comparison
Know what each
product is responsible for.
GL3 operates. GL4 prepares. GL5 is the planned intelligence extension. Shared foundations do not change who performs each function.
Explore by capability
Primary Delivered by this productFoundation Supplied by an earlier layerPlanned Intended GL5 capability— Not this product’s role
Swipe across the table to compare all three products.
| Capability | CIRMS GL3Available now | CIRMS GL4Available now | CIRMS GL5Planned development |
|---|---|---|---|
| Reusable bots & job orchestrationATOMS, defined workflows, execution activity and job outcomes. | Primary | Foundation | Foundation |
| Resource monitoring & health checksConfiguration, services, backup presence, disk space and failed jobs. | Primary | Foundation | Foundation |
| Operational dashboards & reportsAutomation, healthcheck, monitoring, RDBMS and business views. | Primary | Foundation | Foundation |
| Operational data acquisitionCollect and normalize the information used by later stages. | Primary | Foundation | Foundation |
| Source metadata & row identityControlled table registration, source-key and keyless strategies. | — | Primary | Foundation |
| Change detection & row countersSource-dependent acquisition and insert, update, delete and unchanged counts. | — | Primary | Foundation |
| Data curation & schema validationPrepare structured datasets and validate the schema. | — | Primary | Foundation |
| AI documents & version historyTrack document state and current or historical versions. | — | Primary | Foundation |
| Chunks & vector embeddingsTrack new and reused chunks, generated and approved vectors. | — | Primary | Foundation |
| Semantic validation & readinessTrack processing stages, object readiness and health issues. | — | Primary | Foundation |
| Conversational access & semantic searchPlanned natural-language access to prepared CIRMS knowledge. | — | — | Planned |
| AI analysis & decision supportPlanned reasoning, insights and recommendations with human oversight. | — | — | Planned |
No matching capabilities.
Try a broader term or clear the filters to see the full comparison.
This is a functional responsibility map, not a licence-tier comparison. Supported sources, enabled modules and deployment scope are agreed for each environment.
Before you get started
Clear answers.
Clear expectations.
Understand the product boundaries, source requirements and planned capabilities.
More questions about CIRMSIs CIRMS GL4 an AI model or a chatbot?
No. CIRMS GL4 prepares data: curation, AI documents, chunks, vector embeddings and semantic validation. AI models and conversational assistance belong to the planned CIRMS GL5 product.
Is CIRMS GL5 available today?
CIRMS GL5 is planned development. The capabilities shown here describe the intended direction, not currently available functionality or a committed release date. CIRMS GL3 and CIRMS GL4 are the available products presented on this page.
How does CIRMS GL4 handle different source tables?
The current table-based preparation path uses controlled source registration and source-key or keyless identity strategies. Depending on source support and configuration, change detection can use Change Tracking, CDC, rowversion, an explicit watermark or a full-snapshot strategy. Eligibility and configuration are validated; not every method is available for every source.
Are the dashboard screenshots live results?
No. They are actual CIRMS interface captures supplied by TOHOL. Their dates, counts, health scores and execution results belong to the captured environment; they are not live readings, benchmarks or service guarantees.
Where should an organization start?
Start with the operational environment and the work to automate through CIRMS GL3. Identify eligible information for CIRMS GL4 preparation, then review the dashboards and readiness results. Discuss CIRMS GL5 separately as a planned extension built on that foundation.
Your environment. Your priorities.
Start with the operational outcome.
Walk through CIRMS GL3 automation and CIRMS GL4 AI Data Readiness with TOHOL. Discuss your systems, source eligibility and the capabilities that fit your organization.