Guided setup for trained configurators. Complete one stage at a time; technical protocol details remain available when required.
0ACTIVE CONNECTIONS
Current stage1. Decision Scope
Choose the Decision Application and the exact dimension that will receive physical data.
›
84 dimensionsChoose the decision application, then choose the exact dimension receiving physical device data.
START HERE
Select the Physical Device or Decision Forge Dimension to Configure
Loading complete dimension catalog…
Choose a configured device, device definition, or any Decision Forge dimension. Its complete settings will load below.
STEP 1
Physical Connection Settings for the Selected Device
Essential connection settings are shown. Advanced framing, ICD, security and authorization controls remain hidden until requested or required by the selected format.
TCP Client opens a persistent socket from Decision Engine to the device’s IP address and port.
JSON uses the built-in decoder. Select another data format to configure its decoder and ICD requirements.
After this connection starts, send the configured payload with HTTP POST to the endpoint shown in its live connection card.
Inbound safety boundary:
this screen receives sensing, status and telemetry. Command or effector output is intentionally separated and requires an independently reviewed authorization gate, safety interlock and audit path.
Every saved dimension for the selected device is listed below. To add a new device definition, select its data format, paste one real message, decode and discover its numeric and Boolean fields, set the limits and units, and save it without rewriting the connection system.
Use Hex or Base64 for binary packets. The selected format decoder converts the sample into a field tree for dimension discovery.
Use
Dimension ID
Name
Decoded Field Path
Type
Units
Minimum
Maximum
Required
More Settings
Paste a device message and click “Discover Every Dimension.”