Platform architecture
Communication services, point models, logic engines and HMI have separate responsibilities. The Java core on Android turns equipment data into variables used by visualization and control.
01 / Phoenix Embedded
Phoenix Embedded
Control, scenarios and HMI in one platform
An on-site control and visualization platform, from connected devices and engineering variables to programmable scenarios and custom interfaces.
Architecture and technology
A shared identity for every point
ENID identifies a point, while ACV holds its value, type and state. Sensors, interface controls and programs can reference the same engineering point.
Scenario programming and execution
Expressions and conditions handle configured rules; Pascal handles multi-step programs. Typed variables bind programs to points, with independent scenario threads and an execution-step budget rather than a hardware timing guarantee.
Operation and integration
Local dashboards combine status and commands. Project-compatible services connect field devices and supervisory systems; command receipt and observed equipment response are evaluated separately.
From input to outcome, step by step
Select a stage to see its role in the system.
01
Device
Read data from a sensor or field controller.
Models and configurations
7, 10 and 13-inch panels within this family
Project-specific local control and visualization configurations
Applications and selection
Buildings and facilitiesInfrastructure and control roomsProject-specific dashboards
Selecting for your project
Specify panel size, host hardware, enabled services and point capacity for the selected version.
Discuss project requirements