Controlled Scope
Approved systems, databases, sources and permissions define the deployment boundary: what CIRMS can access and which operations it is authorized to perform.
Architecture
From a single HERCULES deployment to hierarchical HERCULES–ATLAS and planned multi-ATLAS models for large-scale environments.
Deployment models
One architecture.
Different operational scales.
Select a deployment model to explore the relationship between managed resources, HERCULES and ATLAS.
Single HERCULES architecture
One operational environment
A single HERCULES deployment provides centralized operational control for one managed environment through a hub-and-spoke communication model. It connects databases, applications, infrastructure, services and other operational resources to one execution layer.
Through GL3, HERCULES performs Intelligent Automation, monitoring, health checks, resource management and data acquisition. Through GL4, it transforms collected operational data into governed, structured and AI-ready knowledge.
The hub-and-spoke model uses standardized interaction patterns, simplifying administration and allowing additional resources and systems to be integrated as requirements grow without changing the underlying CIRMS architecture.
- One HERCULES machine serves one managed operational environment.
- GL3 provides Intelligent Automation, monitoring, health checks, resource management and data acquisition.
- GL4 transforms collected operational data into governed, structured and AI-ready knowledge.
Best fit: organizations that need one central operational platform inside a single environment or site.
Architecture visualization. This illustration presents the operational relationship between one HERCULES deployment, connected resources and the GL3 / GL4 layers. It is a conceptual platform view, not a live dashboard.
Structure summary
Simplified page schematic for the same deployment model.
01 / SINGLE HERCULES
One managed environment
Databases
Applications
Infrastructure
Services
HERCULES
Operational execution
GL3
GL4
GL3
Automation &
Data Acquisition
Data Acquisition
GL4
AI Data
Readiness
Readiness
HERCULES–ATLAS architecture
Central coordination. Local execution.
This architecture introduces ATLAS as the centralized coordination and oversight layer above multiple HERCULES machines operating across different environments, sites or technology domains.
Each HERCULES continues to execute locally and independently, performing GL3 Intelligent Automation and Data Acquisition together with GL4 AI Data Readiness. ATLAS consolidates operational information from those environments and provides an organization-wide view for centralized monitoring, coordination and governance.
The hierarchical model supports distributed execution with centralized oversight and informed decision support. The planned GL5 evolution is intended to extend these capabilities with AI models, intelligent analysis and conversational intelligence while maintaining human oversight.
- HERCULES remains responsible for local execution and AI Data Readiness within its managed environment.
- ATLAS consolidates visibility, coordination and governance across multiple HERCULES deployments.
- The model supports organization-wide oversight while preserving distributed operational execution.
Best fit: organizations operating several environments, business units or sites that still need one coordinated command layer.
Architecture visualization. This illustration shows HERCULES instances operating locally while ATLAS provides centralized coordination, oversight and consolidated insight across environments.
Structure summary
Simplified page schematic for the hierarchical model.
02 / HERCULES–ATLAS
Distributed execution · Central oversight
ATLAS
Coordination & organization-wide view
HERCULES
Data services
GL3
GL4
Databases
HERCULES
Infrastructure / OS
GL3
GL4
Managed infrastructure
HERCULES
Applications / services
GL3
GL4
Connected systems
Multi-ATLAS architecture
Distributed oversight at larger scale.
For large-scale, geographically distributed or multi-domain organizations, the planned CIRMS architecture can extend to multiple interconnected ATLAS machines, each coordinating groups of HERCULES environments.
This model is intended to support distributed oversight, operational resilience, scalability and organization-wide resource management while preserving local HERCULES execution. Proposed architectural goals include redundant supervision, coordinated continuity mechanisms and continuous operational visibility across multiple domains.
Future GL5 integration is intended to extend the architecture with AI models, intelligent analysis and decision support while maintaining centralized governance, traceability and human oversight.
- Multiple ATLAS nodes coordinate separate groups of HERCULES environments across large or distributed organizations.
- The design direction targets resilience, scalability, redundant supervision and continuous operational visibility.
- The model remains a planned architectural direction rather than a production deployment or failover guarantee.
Planning note: this model illustrates a target direction for future scale-out scenarios. It should be read as a concept architecture, not as proof of tested failover behavior.
Planned architecture visualization. This illustration communicates the intended direction for broader coordination and resilience across many HERCULES environments. It does not describe a guaranteed production topology.
Structure summary
Simplified page schematic for the planned multi-ATLAS model.
03 / MULTI-ATLAS
Planned architecture
ATLAS
Coordination group 1
ATLAS
Coordination group 2
ATLAS
Coordination group 3
Interconnected oversight layer
HERCULES
Operational environment
GL3
GL4
Connected resources
HERCULES
Operational environment
GL3
GL4
Connected resources
HERCULES
Operational environment
GL3
GL4
Connected resources
Planned model: distributed oversight and redundant supervision are architecture goals.
Enterprise Deployment & Data Control
Enterprise deployment.
Organizational control.
CIRMS is designed to operate close to the environments it manages. Each deployment defines the systems, data sources, permissions and operational boundaries available to HERCULES and ATLAS. External services and AI integrations are introduced only within the agreed deployment scope.
Local Operational Execution
HERCULES operates within or close to the managed environment, while ATLAS provides higher-level coordination where included in the deployment.
Traceable Data Preparation
GL4 exposes registration, acquisition, preparation, validation, readiness and health status, so teams can inspect how operational data becomes prepared knowledge.
Human Oversight
Automation and future AI-assisted actions remain subject to organizational controls, authorization and responsibility. People define the scope and review the outcomes.
External processing is a deployment decision. Any external service or AI provider must be assessed for the information it may receive, its access permissions and the agreed processing arrangements. Data movement is defined per deployment, not assumed from an architecture diagram.
Discuss deployment scopeHERCULES executes.
GL3 automation and data acquisition, GL4 AI Data Readiness, healthchecks, monitoring, reports and dashboards.
ATLAS coordinates.
Governance, coordination and an organization-wide view across HERCULES machines.
GL5 is planned.
Future integration is intended to extend the architecture with AI models, intelligent analysis and conversational intelligence while maintaining governance and human oversight.
Next steps
Discuss your deployment scope.
Discuss your environment, operational requirements and AI Data Readiness with Project TOHOL®.