Professional Documents
Culture Documents
Project Configuration Tool - Release Notes - StruxureWare Building Operation v1.9.1
Project Configuration Tool - Release Notes - StruxureWare Building Operation v1.9.1
Project Configuration Tool - Release Notes - StruxureWare Building Operation v1.9.1
This document is written for and on behalf of Schneider Electric and is supplied on the express terms
that it is to be treated as confidential and that it may not be copied, used or disclosed to others except
as authorized in writing by this Company. This document is intended for internal use only.
Table of contents
1. Introduction .................................................................................................................................................4
1.1 Change History .............................................................................................................................4
2. Project Configuration Tool Release v1.0 Availability ...................................................................................5
3. Project Configuration Tool Release v1.0 .....................................................................................................6
4. Known Defects in Project Configuration Tool 1.0 ........................................................................................7
5. Important Engineering Information ..............................................................................................................8
5.1 General Engineering .....................................................................................................................8
6. APPENDIX A – Project Configuration Tool Release v1.0 Deliverable ........................................................9
7. APPENDIX B – Known Issues ....................................................................................................................10
8. APPENDIX C – Procedures ........................................................................................................................11
8.1 Installing .......................................................................................................................................11
8.2 Upgrading information for Beta users ...........................................................................................11
8.3 Upgrading a project form the Project Configuration Server ..........................................................12
8.4 PCT nested virtualization settings for VMware .............................................................................12
8.5 Configure Project Configuration Tool Client port settings .............................................................16
1. Introduction
The Project Configuration Tool (PCT) is a new tool designed to enhance a building solution
engineers’ ability to deliver quality and consistency, while reducing the time required to develop
and deploy StruxureWare™ Building Operation projects. The release notes provide information
on the use and application of the product as an addition to the larger wealth of information
available via the Web Help.
A description of the primary features and operation of the first release is contained in Section 3.
Section 4 provides the known defects. Section 5 is information on engineering. Appendix A will list
the location for the deliverables, and Appendix B will provide installation instructions.
Project Configuration Tool is an engineering platform completely separate from the live SmartStruxure
solution platform. All SmartStruxure servers created with Project Configuration Tool are run virtually,
simulating all Enterprise Server and StruxureWare Building Operation server device functionalities
except for communication with attached devices.
Project Configuration Tool is run as a service that you can access from Services in Windows Task
Manager.
All communication settings to StruxureWare Building Operation servers and devices can be set
beforehand, without any risk of accidental communication with servers or devices on-site since the
virtual servers communicate with their own addresses. However, since the virtual servers do not
communicate with the physical field control devices, you cannot discover, learn, or commission
devices when you are working in a project.
You create the project virtual StruxureWare servers and the virtual StruxureWare server
configurations, such as networks, devices, and schedules. The configurations are stored in the
Project Configuration Tool, either on a local PC or on a remote server.
However, all programs and backup schedules added in a virtual server are disabled from execution in
Project Configuration Tool by default, to increase the virtual server performance. If necessary, each
server can be configured to execute all added programs or backup schedules. Use multi-select to
change several virtual servers simultaneously.
1. Creating and deploying servers made from backup templates containing BACnet interface,
will not work.
2. If deploying to a v1.8 solution, BACnet IP Network is offline after deploying from PCT.
Workaround: After deploy, change address manually and warm start the server.
3. Commands like “Commission” etc., does not work in PCT. WorkStation will hang forever and
the process must be killed using Task Manager.
4. If you want the client to remember another port number or address than the default, click on
the link “Setup for use with remote server” and type the address and/or port number.
5. Multi select many servers and upgrade them may result in an upgrade error. Solution: Restart
Project Configuration Tool Client and perform a new upgrade.
8. APPENDIX C – Procedures
8.1 Installing
For full installation instructions for Project Configuration Tool Release v1.0, please reference Web
Help.
1. Pre-requisites:
a. SBO WorkStation that matches the version of the SmartStruxure servers that are
created in the projects
b. System requirements:
i. Windows 7 or later 64 bit only
ii. Processor minimum: Intel Core i5-3340M @ 2.70GHz (Recommended: Intel
Core i7-4800MQ @ 2.70GHz )
iii. Memory minimum: 8 GB (Recommended: 16 GB or higher)
iv. Hard disk minimum: 50 GB
v. Virtual hardware acceleration enabled in BIOS. See appendix below.
3. In order for the PCT to run successfully, the PCT Server must operate with hardware
virtualization turned on. Please refer to the Appendix of this document for the procedure to be
used for two different laptops. You may need to reference the hardware guide for your
specific PC to determine how to turn on virtualization. A tool to check if virtual hardware
acceleration is available on your computer can be found here, however, you must restart the
computer and open BIOS in order to see the status: https://www-
ssl.intel.com/content/www/us/en/support/processors/processor-utilities-and-programs/intel-
processor-identification-utility.html
Windows 10 users
If you use Windows 10 and tried to install a Beta-version of PCT without success, then you must
ensure that this network setting is set after upgrade to v1.0.0.xxx.
http://help.sbo.schneider-electric.com/Topics/show.castle?id=11651&locale=en-
US&productversion=1.8&a=1
The host must be at ESXi 5.1 or greater with the VM compatibility at ESXi 5.1 and later.
https://pubs.vmware.com/vsphere-
51/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc%2FGUID-2A98801C-68E8-47AF-99ED-
00C63E4857F6.html
Once the VM has been fully patched, log into the vSphere client and install/upgrade VMware Tools.
Once the installation completes, shutdown the VM. Once the VM is down, right click on the VM in
vSphere Client and select “Upgrade Virtual Hardware” If the option is not in the menu then the VM is
up to date.
Once the upgrades are complete, proceed to the vSphere web portal for your environment.
Within vSphere Web Client, navigate to the VM (still shut down) highlight. Right click
and “Edit Settings”. At the bottom of the window, verify that the VM has the correct
compatibility level (5.1 or higher).
If the Compatibility Mode is now correct, expand the CPU icon and the ability to expose the
virtualization attributes is now available. Check both “Hardware virtualization” and “Performance
counters” options and select “OK.”
Restart the VM either here or at your vSphere client. You should now be able to run PCT without
errors.
Here you can set server address and port if other than default and also the address to the Project
Configuration Tool client. If you have restrictions for corporate firewall settings, you can also configure
the client to open a specific port. If port is set to ‘0’, a random port will be requested from the
operating system.
If your system is setup using NAT, you can also specify the listening port.