Using I/O Studio to create and configure devices in a DeltaV system

How I/O Studio interacts with other DeltaV applications

I/O Studio uses the same DeltaV configuration database as other DeltaV engineering tools. Configuration changes you make using I/O Studio are reflected in other applications such as DeltaV Explorer and the I/O Configuration tool. Similarly, configuration changes you make using other applications are reflected in I/O Studio. Items that are open in I/O Studio when you change them in another application may require a refresh.

I/O Studio detects whether objects are checked in or checked out in Version Control and Audit Trail (VCAT). However, you cannot check items in or out using I/O Studio. You must perform all necessary check-in and check-out operations using DeltaV Explorer.