Operations Center
Monitor, Investigate, and Act Across Your Entire Endpoint Fleet
Orqit Operations Center is the unified console for fleet visibility, device analytics, compliance, digital employee experience, and remote remediation—on the same platform as ITSM and ITAM.
- 1 · MonitorFleet health & alerts
- 2 · InvestigateDevice console & timeline
- 3 · ActRemote scripts & deploy
Product views
One console for the full endpoint loop
Compact previews of Overview, Device Console, and Remote Operations—designed to scan, not overwhelm.
Overview
Operations Center (Device Analytics V3 under /device-analytics) gives IT teams one place to monitor endpoint health and security posture, investigate with Device Console and Timeline, and act with remote scripts, commands, software deployment, and restart/shutdown where supported—without leaving Orqit.
Audience
Who this is for
- Helpdesk and L2/L3 support engineers troubleshooting device-linked issues
- IT Operations and endpoint administrators managing fleet health
- Security-minded IT teams watching endpoint posture and compliance
- IT managers and enterprise IT leadership needing estate visibility
Challenges
Problems we address
-
Tool sprawl for endpoints Separate consoles for monitoring, remote jobs, compliance, and experience make Monitor → Investigate → Act slow.
-
Limited fleet truth Without online/offline status, health scores, and critical queues, teams react only after users complain.
-
Device context outside the service platform Asset records and tickets live elsewhere while endpoint telemetry sits in another product.
-
Patch and security gaps are hard to prioritize Missing patches, low security scores, and compliance violations need a single operational view.
Context
How Orqit approaches this
Many IT organizations run separate tools for ticketing, asset records, endpoint monitoring, remote management, compliance, and employee experience. Orqit Operations Center brings fleet monitoring, investigation, and remediation into the same Enterprise Operations Platform as IT Service Management and IT Asset Management—so device context and asset links stay in one tenant. From Overview attention queues, open Critical devices or alerts; from Device Console, refresh telemetry, open the linked ITAM asset, restart when supported, or jump to Timeline.
Capabilities
Platform capabilities
Enterprise Endpoint Operations & Device Intelligence
Fleet Overview
Total devices, online/offline/unknown, health, security, patch compliance, critical counts, attention tiles, trends, and alerts.
Device Analytics scores
Health, DEX, security, patch compliance, battery, and performance signals rolled up from agent telemetry.
Device Explorer
Search, filter, saved views, column picker, export, bulk actions, and per-device investigation.
Inventory
Hardware, storage, battery, performance, security, network, and patches across the estate.
Timeline & investigation
Device, security, compliance, remote, software, and hardware-oriented events with filters and investigation summaries.
Digital Employee Experience
DEX scores, distribution, boot and crash-oriented signals, and low-experience device cohorts.
Compliance
Rule-based compliance scores, violations by severity, affected devices, and posture fields for remediation targeting.
Remote Operations
Scripts, commands, software deployment, live jobs, history, stop/retry paths, plus restart/shutdown where supported.
Device Console
Per-device rails for summary, hardware, software, storage, battery, performance, security, network, users, patches, remote, and timeline.
Alerts
Open, critical, and resolved alert views with MTTR average for the alerts workspace.
Workflow
How it works in practice
-
1
Monitor
Use Overview for fleet health, security, compliance, DEX, and alerts—plus attention queues for disk, battery, patch gaps, low security, offline devices, and open alerts.
-
2
Investigate
Open Device Explorer or Device Console to inspect telemetry, inventory, Timeline events, and AI Intelligence insights when enabled.
-
3
Act
Run remote scripts or commands, deploy software, restart or shut down where supported, and verify outcomes in live jobs and history.
Outcomes
Results teams care about
Faster endpoint diagnosis
Scores, inventory, and Timeline sit in one console so operators spend less time assembling context.
Proactive fleet attention
Critical, offline, missing-patch, and low-DEX views help teams act before tickets pile up.
Same platform as service and assets
Operations Center runs in Orqit beside ITSM and ITAM—with strong device-to-asset linking for hardware records.
Security and compliance visibility
Firewall, antivirus/Defender, encryption/BitLocker, TPM, Secure Boot, and patch signals feed posture and compliance views.
Use cases
Where teams apply this
Helpdesk device troubleshooting
Look up a device by hostname, user, or serial; review scores; open Device Console or remote actions.
Endpoint health monitoring
Track estate health, critical devices, and attention tiles from Overview.
Fleet visibility
Search and filter the managed estate with saved views and export.
Patch compliance
See patch compliance KPIs, missing-patch views, and per-device patch rails.
Security posture monitoring
Watch Defender, encryption, firewall, and related security signals across the fleet.
Remote remediation
Run scripts and commands, restart devices when supported, and track job history.
Software deployment
Deploy packages from Remote Operations with live status and history.
Employee experience monitoring
Use DEX scores and low-experience cohorts to find struggling devices.
Compliance management
Define and evaluate compliance rules, review violations, and investigate affected devices.
Governance & security
Built for audit and least-privilege
- Device Analytics permissions control who can view the estate and who can run administrative remote actions.
- Remote jobs and device deletion are privilege-sensitive—grant admin capabilities carefully.
- Telemetry and alerts are tenant-scoped within Orqit’s multi-tenant model.
AI usage
Co-pilot within your guardrails
AI Intelligence summarizes fleet health, predicted failures, anomalies, root-cause clusters, and recommendations, and includes Ask about your fleet for natural-language questions. These are decision-support surfaces grounded in estate telemetry—not a substitute for operator judgment or change control.
Analytics
Operational visibility
Fleet Overview shows what needs attention first: critical and offline counts, online/offline/unknown status, total devices, average health, critical devices, average DEX, security score, patch compliance, plus attention tiles for disk failures, battery wear, patch gaps, low security, offline >24h, and open alerts—with Fleet Health Index trends below.
Details
In depth
See it in the product
Overview answers “what needs attention?” in seconds: critical and offline counts, status strip, KPI cards (total devices, avg health, critical, avg DEX, security score, patch compliance), and attention tiles (disk failures, battery wear, patch gaps, low security, offline >24h, open alerts), with an AI Intelligence tab beside Overview.
Device Console is the investigate surface for a single endpoint: enrollment/status tags, OS and hardware identity, Summary health breakdown, and rails for Hardware, Software, Storage, Battery, Performance, Security, Network, Users, Patches, Remote, Timeline (plus Raw for admins). Header actions include Refresh, Remote, Open Asset (when linked), Restart, and Open Timeline.
AI Intelligence (Overview → AI Intelligence) summarizes fleet health, predicted failures, anomalies, root-cause clusters, and recommendations, plus a natural-language Ask about your fleet prompt for decision support—not a replacement for change control.
Remote on Device Console is the act surface: Terminal / PowerShell (or shell on non-Windows), Scripts, Software, Files, Registry (Windows), Processes, Services, Drivers, Network, and Performance tools, with session heartbeat and job status.
Compliance shows continuous estate scoring: overall fleet compliance, compliant / non-compliant / unknown counts, critical violations, active rules, severity breakdown, and a searchable rules table with per-rule drill-down (for example hardware and BitLocker rules).
Why endpoint operations belong beside ITSM and ITAM
IT teams often juggle separate products for service desk work, asset records, endpoint monitoring, remote management, compliance checks, and employee experience. That split makes every investigation a swivel-chair exercise.
Orqit Operations Center keeps Monitor → Investigate → Act inside the same Enterprise Operations Platform as IT Service Management and IT Asset Management. Operators stay in one tenant for fleet attention, device detail, and remediation—while hardware assets can be opened from linked devices when reconciliation has associated them.
Monitor → Investigate → Act
Monitor
Fleet Overview highlights online/offline status, health, security posture, patch compliance, DEX, critical devices, attention queues, trends, and alerts so teams know what needs eyes first.
Investigate
Device Explorer, Device Console, Inventory, Timeline, and AI Intelligence mode help explain *why* a device is struggling—scores, telemetry, events, and recommendations—before anyone guesses.
Act
Remote Operations supports scripts, commands, and software deployment with live jobs and history. Restart/shutdown style actions are available where the agent and permissions support them. Outcomes are verified in job status—not assumed.
What we do not claim
- Automated compliance-fix compose as a always-on remediation engine (compliance monitoring + remote actions are the shipped path)
- Automatic create ITSM ticket from every device alert pipeline (ticket deep-link fields may exist in data models; that is not a complete out-of-the-box alert→ticket workflow)
Key scores explained
| Score | What it helps you see |
|---|---|
| Health | Composite endpoint health used to prioritize critical and at-risk devices (informed by security, DEX, patch, and disk headroom signals). |
| DEX | Digital Employee Experience score for identifying low-experience devices and cohorts. |
| Security | Endpoint security posture score backed by signals such as firewall, antivirus/Defender, and encryption-related state. |
| Patch compliance | How complete patch posture looks across the estate and on individual devices. |
| Battery health | Battery wear and related attention so aging laptops surface before they fail in the field. |
Fleet operations
Administrators can:
- Search devices and filter by status, platform/OS, health, security, DEX, patch, alerts, and attention-oriented views
- Use seeded saved views (for example online, offline, critical, missing patches, low security, low DEX)
- Customize columns such as hostname, serial, asset tag, user, department, OS, scores, battery, storage, agent version, and last seen
- Export fleet data and run bulk-oriented actions from the explorer
- Open any device into Device Console for deep investigation
Endpoint intelligence (inventory)
Inventory organizes estate facts into operational categories:
- Hardware — manufacturer, model, and hardware attributes (including TPM-related fields where reported)
- Storage — disk capacity and health-oriented signals
- Battery — wear and battery health context
- Performance — performance-oriented telemetry used in investigation
- Security — firewall, antivirus/Defender, encryption/BitLocker, Secure Boot, and related posture fields
- Network — network context for the device
- Patches — patch posture for compliance and remediation planning
Remote Operations
Device Console Remote (Remote Operations Center) and the fleet Remote workspace let operators act on endpoints:
- Terminal and PowerShell (shell scripting on non-Windows) with instant or queued execution
- Scripts and software deployment-oriented tools
- Files, Registry (Windows), Processes, Services, Drivers, Network, and Performance tools in the remote toolset
- Session heartbeat, activity, and job status (pending / running / failed / queue)
- Fleet-level scripts, commands, software deployment jobs, live jobs, and history
- Restart or shut down when the agent mapping and permissions allow
Automated “compliance-fix compose” as a separate always-on remediation engine is not claimed here—compliance monitoring plus remote actions is the shipped path.
Digital Employee Experience (DEX)
The Experience hub surfaces average DEX, low-experience device counts (against tenant thresholds), boot-oriented timing, application crash counts where collected, DEX distribution buckets, and bottom-quartile devices. IT can move from a poor experience signal to Device Console or fleet filters without leaving Operations Center.
Compliance and security
The Compliance workspace provides continuous estate compliance:
- Fleet compliance score with compliant / non-compliant / unknown device counts
- Critical violations and active rules, with severity charts
- Searchable rules table (category, severity, compliant/non-compliant/unknown, last evaluated) and per-rule drill-down
- Rule categories such as hardware and security (for example BitLocker required)
- Create new compliance rules from the console when permitted
Alongside Compliance, security posture signals feed Overview and Device Console—firewall, antivirus/Defender, encryption/BitLocker, TPM, Secure Boot, and patch compliance scoring. Use these views to prioritize investigation and remote action—not to invent audit certifications Orqit does not claim.
Alerts
The alerts workspace tracks open alerts, critical alerts, resolved alerts, and MTTR average (minutes) so operators can see volume and responsiveness alongside Timeline investigation summaries.
How Operations Center connects to the Orqit platform
Operations Center is not a bolted-on RMM island. It runs inside Orqit with:
- IT Service Management — same platform for tickets and service work when device issues escalate to human workflows
- IT Asset Management — implemented device ↔ hardware asset linking and reconciliation, including Open Asset from Device Console when linked
- Workflow Automation — available on the same platform for broader operational automation (not claimed as an automatic compliance→workflow trigger from every violation)
- Knowledge Base — available for operator-authored guidance in the same tenant
- User management and identity — users and assignments that appear on devices (user/department context in the explorer) live in the same Orqit identity model; pair with Self-Service Password Reset when unlock volume is the problem
Honest boundary: deep-linking a ticket ID on timeline entities exists in the data model, but automatic “create ITSM ticket from every device alert” is not advertised as a complete out-of-the-box pipeline.
Who uses Operations Center?
- Helpdesk teams diagnosing device-linked issues
- IT Operations and endpoint administrators
- Security-focused IT practitioners watching posture gaps
- IT managers needing estate KPIs and attention queues
- Enterprise IT leadership consolidating endpoint ops with service and assets
Related reading
- Monitor → Investigate → Act
- Device Analytics
- Fleet Management
- Software Deployment
- Endpoint Monitoring
- Pricing — Operations Center capabilities are positioned on Pro
FAQ
Common questions
What is Orqit Operations Center?
Operations Center is Orqit’s enterprise endpoint operations console—Device Analytics V3 under /device-analytics—for monitoring fleet health, investigating devices, tracking DEX and compliance, and running remote remediation.
What is Device Analytics?
Device Analytics is the telemetry and scoring layer behind Operations Center: health, DEX, security, patch, battery, and related endpoint signals that power Overview, Devices, Inventory, and Device Console.
What endpoint operating systems are supported?
Operations Center ingests platform and OS fields from the endpoint agent. Deep security telemetry and many UI filters emphasize Windows; macOS appears in fleet targeting where agent data exists. Do not assume every OS has equal depth.
What information does the endpoint agent collect?
Typical agent telemetry includes inventory and status used for health/DEX/security/patch scoring, hardware and storage facts, battery and performance signals, security posture fields, network context, patches, and alerts—subject to agent configuration and platform.
Can administrators remotely manage devices?
Yes. Remote Operations supports scripts, commands, software deployment, live jobs, and history. Device Console also supports restart/shutdown style actions where the agent and permissions allow. Sleep/hibernate/Wake-on-LAN are not claimed as shipped here.
Can Orqit monitor endpoint security?
Yes. Security posture views include signals such as firewall state, antivirus/Defender, disk encryption/BitLocker, TPM presence, and Secure Boot, alongside security scores and related Overview gap strips.
Does Orqit provide patch compliance?
Yes. Overview and device views surface patch compliance scoring and missing-patch oriented fleet views, with per-device patch detail in Device Console.
What is DEX?
Digital Employee Experience (DEX) is an experience score derived from endpoint signals (including boot and crash-oriented telemetry where collected). The Experience hub shows average DEX, distribution, and low-experience devices.
Can Operations Center work with ITSM and ITAM?
Operations Center runs in the same Orqit tenant as ITSM and ITAM. Device-to-ITAM asset linking and reconciliation are implemented so operators can open related hardware assets. Ticket creation from every device event is not claimed as an automatic built-in workflow.
Who can access Operations Center?
Access is permissioned (Device Analytics view/admin capabilities). Typical IT Support and Admin roles can be granted access depending on tenant configuration.
Next step
Ready to modernize IT operations?
Launch a pilot workspace or book a walkthrough — with estimated seat savings versus legacy suites, plus 24/7 support.
Entity graph