Presentation: Provides the central interface for accessing and operating the Gluware application suite.

Orchestration: Supplies platform-level scheduling and orchestration services used by applications.

Deployment: Supported on-premises hypervisors or the customer’s cloud-provider environment, with the Gluware Primary Orchestration Engine and Gluware Zone Engine(s) for central and distributed processing.

Collector: Abstracts multi-vendor device interaction to read configuration and operational state.

Executor: Translates and renders normalized automation into vendor- and platform-specific write operations through CLI or API interfaces.

Intent: Provides deterministic, model-aware validation and translation for the target infrastructure.

Collector: Discovers and interrogates devices for hardware, software, configuration, and inventory information. Ad hoc queries inspect saved or live-captured configuration. Backup/restore and reboot are described separately as execution operations.

Observability: Maintains inventory representing discovered network state.

Executor: Provides documented device reboot and supported backup/restore operations. The execution contribution is distinct from inventory and advisory visibility.

Discovery: Builds and runs seeded-device discovery plans using ARP and CDP/LLDP, or subnet crawls.

Fleet management: Site Explorer creates sites and assigns devices; Device Explorer adds/imports/exports devices, supports API additions, discovery, multi-edit, grouping, search, filtering, sorting, and configuration inspection.

Advisory inputs: Cisco Support API supplies EoL/EoS, SmartNet, and PSIRT information; NIST/NVD integration supplies multi-vendor CVE information for supported devices.

Intent: Uses the optional OS Catalog to associate approved images with device SKUs and selects images for deployment plans.

Orchestration: Coordinates OS Plan validation, image transfer/deployment, scheduling, and execution review. Defined state checks and recovery paths can participate in the wider process.

Executor: Performs supported software upgrade or downgrade deployment operations against managed infrastructure.

Image delivery: Distributed Gluware File Server instances improve image-transfer performance across the enterprise network.

Intent: Defines reusable configuration-model constructs and node associations. Model Validation, Initial Preview, and Connected Preview have distinct validation and live-device interaction scopes. Git integration synchronizes CME (Config Model Editor) constructs into a repository for backup and restore; Config Drift & Audit owns audit policies.

Observability: Reads current state and assesses differences between actual and desired configuration.

Executor: Supports declarative execution of modeled configuration through the platform.

CLI/API modeling and assessment: Models intended configuration with declarative enforcement; state assessments run on demand, during provisioning pre/post checks, or via Network RPA tasks. Optional Git integration synchronizes constructs for backup/restore.

Observability: Captures and analyzes actual configuration state, detects drift, and evaluates compliance. Historical snapshots support comparisons across points in time, while audit rules can target specific Concept Items. Device Manager supplies discovered OS and advisory information as context for automation, and drift or audit events can feed remediation processes.

Intent: Uses baselines and audit policies to define desired or approved state.

Collector: Captures configuration and operational command results through standard or vendor/OS-scoped custom command sets. Installed modeling Concept Items can scope audit inputs. CME owns separate node state assessment policies that Network RPA may coordinate with audits.

Assessment operation: Runs on demand, scheduled with email notification, from syslog events, or through Network RPA workflows.

Audit management: Git-based repositories synchronize and back up/restore audits; integrated logging and reporting support review and evidence.

Orchestration: Builds and executes end-to-end processes with logic, triggers, scheduling, tasks, and integrations. Coordinates Gluware applications and external systems, delegating network execution to the relevant applications and adapters. Job and task logging support traceability.

Presentation: Provides visual process creation, execution monitoring, and activity and log views.

Intent: Expresses the desired operational process, conditions, and actions through process logic.

Operating views: Workflow Library manages creation, import, search, sort, edit, execution, history, clone, export, and delete. Workflow Activity exposes results, execution detail, logs, re-runs, and Business Process Model and Notation (BPMN) export.

Templates: Template Builder designs LiquidJS-based output in workflow context and tests it with workflows, instances, and variables.

Orchestration: Connect external ITSM, CMDB, DDI, and other systems to Gluware automation processes.

Presentation: Support service-management interfaces, corresponding to the framework’s ITSM Integration function.

Intent: Allows NetBox to supply Source-of-Truth data representing intended device and network state.

Observability: Synchronizes discovered device and inventory data from Gluware back into NetBox.

Orchestration: Allows synchronization and NetBox operations to participate in broader automated processes.

Synchronization boundary: Linking, mappings, exclusions, property ownership, and schedules determine which device/site information moves between systems. This is distinct from applying network configuration intent.

Presentation: Exposes automation through service-management processes, corresponding to the framework’s ITSM Integration function.

Orchestration: Allows ServiceNow events, tickets, and change processes to initiate or participate in Gluware processes.

Integration boundary: Native CMDB synchronization maps device/CI records and properties. Service Connector tasks handle supported ticket/service operations in Network RPA; process design determines approval and event behavior.

Orchestration: Allows Network RPA to incorporate Ansible playbooks into larger Gluware automation processes.

Executor: Provides an external execution mechanism when Ansible performs infrastructure changes.

Task configuration: The Network RPA Ansible task references an Ansible server Global instance configured in CME. That dependency does not transfer playbook execution to CME.

Presentation: Provides customizable dashboards and widgets for application, administrative, scheduling, and operational information.

Presentation: Provides customizable reports, queries, and exports of Gluware data.

Observability: Exposes collected and derived network state, inventory, configuration, drift, audit, and lifecycle information.

Presentation: Provides the system interface corresponding to the framework’s API Gateway function.

Orchestration: Allows external systems to invoke and coordinate Gluware automation processes.

Intent: Allows developers to define custom network features and automation logic through data models and business logic.

Orchestration: Supports the creation of custom Network RPA tasks and integration logic.

Executor: Allows custom features to extend infrastructure operations through the underlying platform.

Presentation: Provides a natural-language and agentic interface for interacting with network automation.

Intent: Translates user goals into intended automation and applies deterministic validation.

Orchestration: Uses agentic reasoning and MCP services to coordinate Gluware capabilities and external services.

Orchestration: Coordinates agents, Gluware automation capabilities, and external services.

Intent: Uses DIAL-powered validation to check proposed AI actions before execution.

Presentation: Provides a standardized MCP interface for external AI systems and services.

Presentation: Provides the file/folder management interface.

Supporting service: Stores the OS image and related files required by OS Manager. This is an execution dependency, not an independent network Executor.

Distributed image delivery: File Server instances can be distributed across the enterprise and associated with target devices for better transfer performance.

Presentation: Provides the interface for reviewing changes and artifact history.

Intent: Provides versioned storage and restoration for supported CME constructs and audit-policy artifacts.

Supporting service: Also versions RPA processes. Artifact restoration is distinct from a network-state change.

Optional Git integration: Synchronizes supported constructs and policies with repositories for backup/restore; it is not positioned as requiring a separate feature license.

Presentation: Provides package discovery and installation interfaces for the appropriate organization.

Supporting service: Installs application, modeling, and custom-task packages. Package installation does not itself provision managed network infrastructure.

Observability: Provides contextual vulnerability assessment using device OS, configuration, and operational context.

Supporting inputs: Device Manager supplies fleet and advisory information. The analysis contribution is based on the officially described capability; it is distinct from live-state collection.

Orchestration: Connects relevant exposure to supported response and remediation processes.

Execution path: Software and modeled configuration operations use the appropriate platform capabilities; the specific process determines which component executes each action.