Studio360 – GDT Design Guide
Designing for IMPACT
Steve Gregory
10/12/2022
Confidential Property of Schneider Electric
Internal
Studio360 – GDT Design Guide Control Panel Nodes with one
controller
Control Panel Nodes with multiple
Controllers
Network Location Nodes with Unique
Systems
Network Location with Typical
Systems and Schedules
Exporting Points for IMPACT
Confidential Property of Schneider Electric | Page 2
Internal
GDT Configuration
System Types
When building a system in the GDT, there are 4 different configurations that we will consider:
1. Control panel node with one controller – typically and ASP with one or more systems
2. Control panel node with multiple controllers – controller per system
3. Network location – controller per system (Unique)
4. Network location – controller per system with schedule (Typical)
Confidential Property of Schneider Electric | Page 3
Internal
GDT Configuration
System Types – 1.Control Panel with one controller
In this configuration, a control panel
contains one controller that hosts one or
more systems.
An example would be an ASP with:
• Multiple AHUs
• Ventilation Fans
• Various Monitoring points
Note: The system name here is used to
prefix the software tag for each point in
that system.
Confidential Property of Schneider Electric | Page 4
Internal
GDT Configuration
System Types – 1.Control Panel with one controller
Once the control panel has been added to the network
tree:
• Name the ASP in the Network View. This can also
be done by changing the BomTag of the ASP in the
Material tab of the Panel Hardware.
• Configure the ASP System Name in the properties
of the controller in the Network View which
automatically copies to all the IO modules.
Note: The system name configured here, is the ‘PartSystemName’
field in the report which is used as the controller's name in IMPACT.
Note: This must be set
manually for an ASP
Confidential Property of Schneider Electric | Page 5
Internal
GDT Configuration
System Types – 2.Control Panel with multiple controllers
In this configuration, a control panel
contains multiple controller, each hosting
one systems.
Examples would be:
• ASB controllers hosting AHUs
• RPC controllers hosting FCUs
Note: to configure a control panel node with a controller per
system, tick this option on the points tab of the control panel:
Confidential Property of Schneider Electric | Page 6
Internal
GDT Configuration
System Types – 2.Control Panel with multiple controllers
Once the control panel has been added to the network
tree:
• Name the Controllers in the Network View. This can
also be done by changing the BomTag of the
controllers in the Material tab of each system.
• The controller System Name in the properties of the
controller in the Network View is automatically
populated by the system name.
Note: The system name configured here, is the ‘PartSystemName’
field in the report which is used as the controller's name in IMPACT.
Confidential Property of Schneider Electric | Page 7
Internal
GDT Configuration
System Types – 3.Network Location – Controller Per System (Unique)
In this configuration, a network location
contains multiple systems with dedicated
controllers.
Examples would be:
• RPC hosting an FCU
• MPC hosting a PAC
• ASB hosting a CRAH
Confidential Property of Schneider Electric | Page 8
Internal
GDT Configuration
System Types – 3.Network Location – Controller Per System (Unique)
Once the network node has been added to the network
tree:
• Name the Controllers in the Network View. This can
also be done by changing the BomTag of the
controllers in the Material tab of each system.
• The controller System Name in the properties of the
controller in the Network View is automatically
populated by the system name.
Note: The system name configured here, is the ‘PartSystemName’
field in the report which is used as the controller's name in IMPACT.
Confidential Property of Schneider Electric | Page 9
Internal
GDT Configuration
System Types – 4. Network location – Controller per system with schedule (Typical)
In this configuration, a network location
contains systems that are detailed using
a typical system with a ‘typical of’
schedule.
Examples would be:
• MPVs hosting VAVs
• RPCs hosting an FCUs
• MPCs hosting a PACs
Confidential Property of Schneider Electric | Page 10
Internal
GDT Configuration
System Types – 4. Network location – Controller per system with schedule (Typical)
The schedules are used to detail instances
of each system
Confidential Property of Schneider Electric | Page 11
Internal
GDT Configuration
Using the IMPACT Points Export Report
From the Reports tab on the Network Root, select
the ‘IMPACT Points Export’ Report.
Select the devices you wish to export. You can
export some or all of the devices in one report.
Save the report to the desktop, ready for Importing
to IMPACT.
Confidential Property of Schneider Electric | Page 12
Internal
GDT Configuration
Using the IMPACT Points Export Report
Points to note in the exported points list:
• PartSystemName = Used as Controller Name
• BomTag = Used as Module Name
• PointName = Used as IO Channel name
These three fields must be populated in the report.
These three fields, when combined together, must be unique in
the system as they are used to identify each point.
If the PartSystemName is missing, it is usually due to the
SystemName not being configured in the ASP, refer to notes on
configuration type 1
While special characters are generally handled in Studio, Impact
and EBO, it is advisable to avoid using them where possible.
Especially characters like & % / \ < > ( ) ‘ “
Confidential Property of Schneider Electric | Page 13
Internal
Confidential Property of Schneider Electric | Page 14
Internal
Internal
