Evaluate PlantGuard inside your environment.

How a pilot runs

Eight steps, in order. Each is agreed with your team before it starts; we do not publish durations here because they depend on your change-control process and fleet size, and we would rather agree them with you than promise them to everyone.

1. Initial technical discussionYour environment, what you need to learn from the pilot, who owns it on each side, and whether the pilot must be fully offline.
2. Environment and scope definitionWhich sites, subnets, device families, domain(s) and consoles are in scope; which are explicitly out.
3. Deployment requirementsServer specification, Windows edition, accounts (a read-only AD service account is recommended), certificates for LDAPS and HTTPS, firewall rules for SNMP, SSH, WMI, syslog and traps.
4. On-premises installationYour administrator runs the installer on your server; the 30-day evaluation license is built in and verified offline. We assist remotely or on-site as you prefer — we never need remote access to the server.
5. Asset discovery and integrationInventory import or discovery, SNMP/SSH/WMI credentials in the encrypted vault, Active Directory over LDAPS, syslog and trap forwarding, and any backup, endpoint or physical-access console in scope.
6. Baseline assessmentPlantGuard's deterministic rules produce the first findings, the Plant Health Score with its six sub-scores, and the AD Compliance baseline. Anything without evidence is marked not assessed, not guessed.
7. Findings reviewA working session with your engineers: open findings with their evidence, correlated risks, the lifecycle plan, and — if you enable the local engine — the AI Advisor answering your own questions with citations.
8. Pilot evaluation reportWhat was discovered, what it means, what the product could and could not see in your environment, and what a production deployment would involve. Produced from the pilot installation's own reports; every number in it is traceable.