Use an existing driver or component
Review the supported product, version, license, dependencies, and last-tested information before importing and validating a compatible package.
How it works
These guides organize the real product workspaces by what you need to operate, build, connect, administer, protect, and recover.
Field workflow checklists
These supporting procedures help technical teams verify compatibility, investigate issues, document handoff, and restore an authorized installation.
Review the supported product, version, license, dependencies, and last-tested information before importing and validating a compatible package.
Start with the affected location, identify its serving system, and review the available communication, live-status, and diagnostic information.
Export compatible files, record component versions, document access and integration requirements, and confirm the recovery copy.
Upload the backup to an authorized Windows 11 computer or VM, then verify permissions, connections, mappings, status, and operator views.
Sign in and land in a workspace tailored to your account.
Turn a floor into a visual, interactive map of controls.
Monitor and adjust the building the way people think about it.
Build reusable control interfaces once, use them everywhere.
Teach PI how to talk to a supported connected system.
Notify the right people and control who can see what.
Keep a recoverable copy of your work and move compatible files between authorized Windows 11 installations.
Save the current project files locally or to the cloud location approved by your organization.
Export a dated backup containing the supported configuration and reusable project assets.
Import the compatible files into the same system or a replacement Windows 11 computer or VM.
Confirm driver versions, connections, permissions, mappings, and live status after restoration.
No proprietary appliance required The restored project runs on a compatible Windows 11 computer or Windows 11 virtual machine selected for the deployment.
Guide 08
Use the dedicated workflow for your supported equipment, then verify its behavior before handing it to operators.
Open the relevant BACnet, Vantage, Hue, or Crestron workspace. Configure the connection and complete any required pairing or authentication.
Discover equipment or prepare the supported configuration file. Inspect the returned devices, available capabilities, and intended location mappings.
Import the selected equipment, then confirm identifiers, driver mappings, readable values, and authorized commands against the actual device.
Place the supported widgets, configure any groups or schedule profiles, and verify normal-hours and after-hours behavior with the operator.
Guide 09
Use Network Diagnostics to investigate the PI server’s recorded network context and changes over time.
Open Network Diagnostics and refresh the view to load the latest saved observation. Refreshing this view does not perform an active device scan.
Review the recorded interface, address, gateway, DNS, and system information. Check observation timestamps before drawing conclusions.
Compare the affected instance’s selected network interface and addressing with the recorded host context, then verify communication using the relevant integration tools.
Diagnostic record, not a backup Network snapshots record host observations. Keep project exports and recovery procedures separate.