Every asset is the record your desk already uses: an incident names it, a change explains it. Hardware, software licences, SaaS seats, cloud cost, vulnerabilities and maintenance in one place; plant assets through the OT security tools you already run. AEROSS™ is not an OT security tool. Agents propose; your people decide.
Hardware from order to disposal; software licence positions with the workings shown; reclaim of unused software by a request to the person; SaaS seats and cloud cost by owner; vulnerabilities ranked and fixed through the desk; configuration changes explained by an approved change or raised as an incident; maintenance tied to risk and change; plant assets through your OT tool; reports and audit packs; four agents that propose and people who decide.
One record store: the asset is the configuration item the desk already uses. An incident names the asset, a change explains a configuration change, maintenance windows sit on the desk calendar and the item picker finds a laptop by its serial. Nothing to install on the desk side.
Controllers, drives, HMIs and SCADA servers read from Claroty, Nozomi Networks, Dragos, Armis, Microsoft Defender for IoT, Tenable OT Security or a file. Site, area, line and cell; zone and level exactly as your tool reports them; firmware changes reconciled against maintenance windows; CISA industrial advisories. AEROSS™ is not an OT security tool: it does not inspect plant networks or speak to controllers.
A short table on the page compares the Asset Manager with ServiceNow, BMC Helix, Ivanti Neurons, Freshservice and Jira Service Management, and says where another product is ahead. The full matrix, with a source for every entry and the date it was checked, opens underneath and downloads as a dated PDF.
Everything under Available today is live in the production platform. The on-premises edition and Kubernetes cost by namespace are on the roadmap. Remote wipe and remote uninstall are not offered: the Asset Manager never acts on a device itself.
It is a module of Genesis™, switched on by licence, on the same records as the desk. No second database, no sync, nothing to install on the desk side. OT / Plant is a second licence on the same register.
No. You keep it. The Asset Manager reads from it. AEROSS™ is not an OT security tool.
No. Every connection is read-only. A fix, a reclaim or a resize becomes a task or a change request that a person carries out.
Yes. Every position shows its workings line by line, and the audit pack lists every entitlement, every install and the rule applied with its published term.
With the air-gap switch on, the Asset Manager makes no outbound call. Vulnerability feeds, end-of-life dates and licence rules arrive as signed bundles you load yourself.
Through the same AI gateway as the rest of AEROSS™: an external model, your own model, or off, per capability. The figures in a proposal come from your records, never from the model.