Discover, save, and import
Discover reachable equipment, retain discovery records, refresh values, review point capabilities, and import supported components. Network tools include a BBMD probe.
Integrations & Modules
Centralize the systems you already have.
Instead of replacing existing systems, PI creates a common operational environment above them — connecting devices and applications through the interfaces they already provide.
Centralize the systems you already have
One interface for a building made up of many technologies.
Where a device or system provides an accessible control, command, API, or communications interface, PI can bring that capability into the Command Center.
- Telnet
- SSH
- RESTful APIs
- BACnet
- Network communications
- Manufacturer interfaces
- Custom integrations
- Application-specific modules
Lighting+HVAC+Shades+Sensors+Schedules+Building Controls
Dedicated integration workspaces
Review what was discovered before bringing it into operation.
Available workflows depend on the product, connection, configuration, and deployment. Confirm the target model and firmware during commissioning.
Review projects and controllers
Prepare a project-file import or fetch supported controller information, save discovery records, and review the device mapping before import.
Pair and organize a bridge
Discover and register a bridge, review its lights, sensors, and groups, then prepare and import supported devices.
Review lighting configuration
Pull or review supported SR configuration data, then import the lighting definitions into PI.
Control and review playback
Use supported Roku discovery and polling to retrieve app, input, audio, channel, and media information for configured AV interfaces.
Bind the connection deliberately
Choose an available network interface for supported connection instances and review saved server network observations when diagnosing changes.
Commissioning matters A workflow in the software does not establish compatibility with every product or replace testing with your installed hardware. See the commissioning checklist →
Integration readiness
Define what the integration must exchange before selecting the connection.
A useful integration is more than a protocol name. Its scope should identify the target product, readable information, permitted controls, authentication, network path, data mapping, failure behavior, version support, and maintenance owner.
Product & version
Record the manufacturer, model, firmware, API, protocol, and supported PI version.
Readable status
Define the values, states, alarms, identifiers, and diagnostic information PI may read.
Permitted commands
Identify authorized actions, parameters, acknowledgement behavior, and safety boundaries.
Authentication & network path
Document credentials, certificates, addressing, ports, segmentation, and connection lifecycle.
Mapping & errors
Map device data into PI and define timeouts, retries, offline states, and recovery behavior.
Lifecycle ownership
Assign documentation, testing, version review, support, and compatibility maintenance.
Use existing drivers first
Reuse a proven connection instead of starting over.
When a compatible driver already exists, teams can select it from the available library, review its supported commands and feedback, and reuse it across authorized projects.
Find
Search or browse available drivers by manufacturer, product, system, or supported interface.
Download
Export compatible driver packages for backup, controlled sharing, or use on another authorized PI installation.
Upload
Import an existing driver package rather than recreating its commands, parameters, mappings, and feedback.
Validate
Confirm the driver version, target equipment, supported features, security requirements, and live operation before deployment.
Build around your workflow
PI translates the building’s technology into the building’s workflow.
A corporate headquarters doesn’t operate like a hospital, broadcast facility, university, hotel, laboratory, or entertainment venue. Application-specific modules bring together the controls, information, diagnostics, and workflows that matter to a particular facility.
Prepare Conference Room
Example to configure: coordinate supported lighting, shades, temperature, and AV commands with the room-status information available in your installation.
Prepare Studio for On-Air
Example to scope: evaluate available room status, lighting, environmental conditions, and communication checks before the space goes live.
See how your building is being used
Use the history your system actually records.
PI provides host-performance history and saved network observations for troubleshooting. Equipment trends, occupancy analytics, energy reports, and long-term retention should be scoped against the available source data and reporting requirements.
How often is this space actually being used?
When does occupancy typically begin?
Which areas remain active after hours?
How long is equipment running?
Are conditions repeatedly occurring before a failure?
Are schedules aligned with actual utilization?
Automate more than schedules
Automation that responds to how the building is actually used.
Building automation shouldn’t stop at turning equipment on at 8:00 AM and off at 6:00 PM. Configured tasks can run from calendar events or live-status triggers; group schedule profiles and saved mode flows organize normal-hours and after-hours operation.
Time+Occupancy+Equipment Status+Sensor Data+System Conditions