NAE Commissioning for C•CURE-victor Integration ...cgproducts.johnsoncontrols.com › MET_PDF ›...

NAE Commissioning for C•CURE-victorIntegration Application Note

LIT-12013151

Release 10.0

Building Technologies & Solutionswww.johnsoncontrols.com2018-12-17

ContentsContentsIntroduction...................................................................................................................................... 3

Example customer outcomes.............................................................................................................. 3

Related Documentation........................................................................................................................3

Application details............................................................................................................................4

Component Requirements................................................................................................................... 4

Network Automation Engines (NAEs)................................................................................................. 5

Design Considerations..........................................................................................................................5

Integration overview........................................................................................................................6

Creating an integration object....................................................................................................... 7

Transferring device and point information.................................................................................10

Generating a C•CURE export file....................................................................................................... 11

Generating a victor export file...........................................................................................................11

Generating an MCT .imp file.............................................................................................................. 13

Using an .imp file to import field devices and points.....................................................................18

Inserting field devices and points into an SCT archive database from MCT............................... 19

Manually adding devices and field points.................................................................................. 20

Creating a device object..................................................................................................................... 20

Creating field point objects................................................................................................................23

C•CURE point mapping tables...................................................................................................... 28

Door points definition.........................................................................................................................28

Input points definition........................................................................................................................28

Output points definition.....................................................................................................................28

Area points definition......................................................................................................................... 28

victor point mapping tables..........................................................................................................29

Video Recorder points definition.......................................................................................................29

Camera points definition....................................................................................................................30

Troubleshooting............................................................................................................................. 31

Software terms............................................................................................................................... 32

NAE Commissioning for C•CURE-victor Integration Application Noteii

IntroductionThis document describes how to commission a Network Automation Engine (NAE) for a Tyco®C•CURE® or victor® integration into Metasys. The NAE models that support this integration are theNAE55 and the server-based NAE85. This integration connects to Tyco C•CURE 9000 Access Controland victor Video Management systems in order to display the information listed in C•CURE pointmapping tables and victor point mapping tables in the Metasys® UI .This document does not describe how to mount, wire, or power an NAE. This document doesnot describe how to build or download an archive database for a Metasys system site, or how toconfigure an NAE to monitor and control a building automation system (BAS).

Example customer outcomesThe following list includes examples of Smart Building opportunities that you can enable if youconfigure Metasys to automate multiple building systems.

• You can create a frictionless building system behavior to help occupants while saving energywhen the lights, HVAC, and plug load appliances are not on all the time. For example, you canconfigure valid badge access to activate lights, HVAC, and plug loads for the space.

• You can add extra security measures that can be automated to achieve a safer environment. Forexample, to raise awareness of a failed access attempt, you can configure an invalid badge scanto flash the lights adjacent to the badge reader.

• When Metasys is also integrated with Simplex, you can configure a fire alarm event to unlockdoors to allow for faster evacuation.

• You can configure numerous video analytics, for example, detected motion or crowd formation,to provide triggers in Metasys to automate lighting and HVAC behavior.

• You can obtain building and space utilization data from a count of valid and invalid badge scans.

• You can control the operating states of multiple building systems through a consolidatedschedule or set of rules for the building, such as HVAC, lighting, and security all following thesame building occupancy schedule. For example, on a snow day for a school, you can adjust theoperations of all systems from a single schedule.

Related DocumentationUse the following table to find information that is related to the content in this document.

Note: You can access documentation for victor and C•CURE 9000 from the American DynamicsTechnical Library: http://www.americandynamics.net/TechnicalLibrary/TechLibAD.aspx. Youmust register for an account to access some of the documents.

For Information on Refer toDaily operation of the Metasys systemnetwork, navigating the UI, monitoringand controlling BAS networks

Metasys System Help

To access help from the Metasys graphical userinterface, from the Help menu, click Help.

Definition of terms, concepts, andacronyms commonly used to describeMetasys System Extended Architecture

Metasys System Extended Architecture Glossary(LIT-1201612)

Overview of the Metasys system networkfeatures and functions

Metasys System Extended Architecture Overview TechnicalBulletin (LIT-1201527)

3NAE Commissioning for C•CURE-victor Integration Application Note

http://www.americandynamics.net/TechnicalLibrary/TechLibAD.aspx

For Information on Refer toGeneral network and InformationTechnology definitions and concepts

Network and Information Technology ConsiderationsTechnical Bulletin (LIT-1201578)

Overview of system configurations forvictor and C•CURE 9000, and detailedinformation about the administration ofvictor unified client installations

victor Unified Client victor Application ServerAdministration/Configuration Guide

Overview of the standalone C•CURE 9000installation process

C•CURE 9000 Installation Quick Start Guide

Overview of the standalone victorinstallation process

victor Installation Quick Start Guide

Overview of the victor/C•CURE 9000unified client installation process

victor/C•CURE 9000 Unified Client Installation Quick StartGuide

Use of the Mass Changes Tool toconfigure the integration of C•CURE orvictor device information

Mass Changes Tool Guide

To access help from the Mass Changes Tool graphicaluser interface, from the Help menu, click Guide.

Use of the System Configuration Tool(SCT) to create and configure an archivedatabase offline

Metasys System Configuration Tool Help (LIT-12011964)

Application detailsComponent RequirementsTo integrate a Metasys system with a C•CURE or victor system, you require the followingcomponents:

• One of the following installations:

- C•CURE 9000 server at version 2.70 or later

- victor server at version 5.2 or later

- C•CURE-victor Unified server, with C•CURE 9000 at version 2.70 or later and victor atversion 5.2 or later

• Active victor web service licenses for the installed components. See Design Considerations.

• NAE85 at Release 10.0 or later installed on its own server, or NAE55 at Release 10.0 or later

• Network connectivity between C•CURE 9000-victor web service and the NAE

• Mass Changes Tool (MCT) at version 2.6.99.0 or later

• The System Configuration Tool (SCT) at Release 13.0 or later

NAE Commissioning for C•CURE-victor Integration Application Note4

Network Automation Engines (NAEs)An NAE is a web-enabled, Ethernet-based, supervisory engine that connects BAS networks toIP networks and the web. You can use an NAE to monitor and control BAS field devices from acomputer. To launch the user interface for the NAE, use the Launcher application that is installedwith the NAE software. To upgrade or reinstall the Launcher application, refer to the LauncherInstallation Instructions (LIT-12011783).All NAEs provide scheduling, alarm and event management, trending, energy management, dataexchange, and password protection. NAE85s require a Microsoft® Windows Server® operatingsystem.

Figure 1: Network layout

Design ConsiderationsTo integrate a Metasys system with a C•CURE or victor system, consider the following points:

• Ensure that all devices are set up and running properly before attempting to integrate withMetasys networks.

• Use the License Activator application to check the availability of the web service license forC•CURE and victor. You only require a license for C•CURE or victor if that component is installed.Both C•CURE and victor use the victor web service.


Figure 2: License options for web services

Integration overviewTo integrate C•CURE or victor with a Metasys system, complete the following steps:

1. Create an Integration object in the NAE, and configure the settings so that the NAE cancommunicate with the victor web service. For more information, see Creating an integrationobject.

2. Export device and point information from C•CURE or victor and transfer it to the NAE. For moreinformation, see Transferring device and point information.

Note: You can manually add individual C•CURE and victor devices and points in the NAE. Formore information, see Manually adding devices and field points.


Creating an integration object1. Use the Site Management Portal (SMP) to connect to the engine.

2. From the Insert menu, click Integration.

3. On the Select Object Type page, select VND integration, then click Next.

4. On the Destination page, select the NAE object, then click Next.

Figure 3: Integration object - VND integration - Destination

5. On the Identifier page, in the upper-right corner of the window, enter a unique identifier forthe integration, then click Next.


Figure 4: Integration object - VND integration - Identifier

6. On the Configure page, click the Hardware tab.

7. In the Vendor DLL field, enter the appropriate integration file name from the following table:Note: The driver file names are case sensitive.

Table 1: Driver file names for the NAE55 and NAE85 engines

Network engine Driver file nameNAE55 libVictor_CCureDriver.soNAE85 Victor_CCureDriver.dll

8. To set integration parameters, in the Vendor Configuration Data list, click the ellipses icon.The Modify List window appears.

9. For each parameter listed in Table 2, in the Modify List window, enter the appropriate value.Some values may be added automatically.

Note: Enter values for the parameters from 1 to 4 that match the version of C•CURE orvictor that is installed. Verify the value for these parameters with the C•CURE or victoradministrator. If one of the parameters from 1 to 4 is incorrect, the NAE cannot connect tothe web service.


Table 2: NAE vendor configuration data setup of the C•CURE-victor trunk

Parameter Value to enter[1] The IP address of the host where the victor web service is installed and running[2] The instance name used in the victor web server[3] The user configured in C•CURE and victor to use the web service. For security

reasons, after you click OK, the value in this field is encrypted.[4] The password configured in C•CURE and victor to use the web services

For security reasons, after you click OK, the value in this field is encrypted.[5] The client name

This parameter is a reference that you define. Enter an appropriate value to identifythe integration in calls to the web service.

[6] The polling time period to read the information from the C•CURE and victor systems[7] Whether to capture a log file of the driver and save it onto a USB drive

To enable the log, enter Y. To disable the log, enter N.[8] The communication port from which to log events

For possible values, see Table 3. To log events, also set parameter 7 to Y.[9] The USB drive to which the log file is saved

To log events, also set parameter 7 to Y.

Table 3: Diagnostic port settings

Identifier Compatible enginemodels

Connection Comment

0 all models -- No serial diagnostic output1 all models RS-232C (A)2 NAE55xx RS-232C B3 NAE55xx FC Bus

FC A4 NAE55xx FC Bus

FC B

Communication parameters:

115200 bits per second

8 data bits

no parity

1 stop bit

You can only use a port if it is notused for serial communication with

3rd party equipment.

For debug mode, the USB and serial COM logs are independent. If you enable debug modewith no USB pen drive connected, messages are sent only through serial cable. If you enabledebug mode with no serial COM port available, a log file is created only on USB drive. If youuse the USB log capture, insert the USB pen drive before you enable the log capture. Also, dis-able the log before you remove the USB pen driveAs shown in the following figure, a description is added for each parameter to identify itsmeaning. This description is added automatically and you do not need to enter it during con-figuration.


Figure 5: Integration object - VND integration - vendor configuration data

10. Click OK to close the Modify List page.

11. Click Next to go to Summary page, then click Finish.

12. On Extension Wizard page, click Done.

The engine is now connected to the victor web service. To easily transfer device and pointinformation from C•CURE or victor to the NAE or an offline archive, see Transferring device andpoint information. Alternatively, to manually complete the integration, see Creating a device objectand Creating field point objects.

Transferring device and point informationYou can export device and point information from both C•CURE 9000 and victor systems. You canimport this information into MCT, convert it to a format that is compatible with a Metasys System,and then import the integration information directly into an NAE. This workflow significantlysimplifies the integration process, compared to manually adding devices and points (see Manuallyadding devices and field points).

Note: As an alternative to the direct import of information into an NAE, you can also transferthe information from MCT into an SCT archive database. Before you begin the process ofarchive database configuration, perform an Upload to copy the integration settings from theNAE to an SCT archive database. After you complete configuration of the archive database,perform a Download to copy the configuration from the SCT archive database to the NAE. Fordetailed information, refer to the Download section in the Metasys System Configuration ToolHelp (LIT-12011964).

Important: If you use MCT to repeat the transfer of device and point information, you canonly add new devices and points. If you re-import the same devices or points into an NAE orSCT archive, an error occurs and the import fails. You cannot use the transfer process to deletedevices or points from the NAE or SCT database.


Generating a C•CURE export fileTo create the offline database, first export the C•CURE 9000 configuration.

1. Launch the C•CURE 9000 Administration Station software.

2. From the Hardware tree view, select the cluster to export, right-click it and select Copy to.

Figure 6: Start Data Export process

3. Navigate to the desired location to save the file, enter a file name, then click Save.

4. After the process completes, a confirmation message appears. Click OK. Use this XML file in theMCT. See Generating an MCT .imp file.

Generating a victor export fileTo create an offline database for the victor configuration, install the victor WS Config Tool on a PCthat is on the same network as the victor server. Use the WS Config Tool to generate an XML filethat contains the entire configuration. You can then use the XML file in MCT.To install the WS Config Tool, complete the following steps:

1. Right-click the VictorWSConfigTool_100_Setup.exe file, then click Run as Administrator.

2. From the list, select Victor WS Config Tool, then click Next.


Figure 7: Select setup

3. To create a shortcut on the desktop, select the Create a desktop shortcut check box. ClickNext.

4. Click Install to confirm the installation.

5. Click Finish to complete the installation.

6. Launch the WS Config Tool. The Victor web services Configurator window appears. Enter therequired information.


Figure 8: Application form

- Victor WS Host: the IP/hostname of the PC where the victor server is installed

- Victor WS Reference: the reference used by the web service in the configured server

- User/Password: credential to access the web service into the server

- Client name: name used to identify this application client

- Partition ID: the partition number related to the required export. It is configured in thevictor server

7. Click Process.

8. Navigate to the desired location to save the file, enter a file name, then click Save.

9. In each confirmation message, click OK. The XML file is saved and contains the full victorconfiguration. Use this XML file in the MCT. See Generating an MCT .imp file.

Generating an MCT .imp fileYou can use MCT at version 2.6 and later to create a new device and the field points related to theC•CURE 9000 or victor integration.

1. Open the MCT and select File > New.

2. Select the Victor - CCURE9000 Integration icon, then click Next.


Figure 9: New File - Victor Integration

3. In the upper-right corner of the Victor - CCURE9000 Integration window, click the ellipsesbutton.

4. Select the export file created from the C•CURE 9000 Administation Station or from the victorWS Config Tool.

5. Click Generate to load the file into the MCT. A tree view is generated from the XML file thatcontains the selected properties. You can use the same window to configure settings forMetasys.


Figure 10: Load export file from C•CURE 9000


Figure 11: Sample load export file from victor

Figure 12: Points to import and related properties

6. To include Metasys UI objects, complete the following steps:

a. Click the Metasys UI tab.

b. Select Include Metasys UI objects.

c. In the Equipment Definition tree view, select the second level folder, click the edit icon,


and then update the name to either security_ccure or security_victor, dependingon the source of the export.

d. In the Equipment tree view, select the second level folder, click the edit icon, and thenupdate the name to either equipment_ccure or equipment_victor, depending on thesource of the export.

Note: If you do not rename the equipment definition folder and the equipment folder,then you cannot integrate both C•CURE and victor in the same site.

Figure 13: Metasys UI configuration options

7. To complete the configuration, click OK. A tree view is generated from the XML file thatcontains the selected properties. You can use MCT to configure an integration that containseither the full set of data or a selected subset of the data. For further information about thefeatures of MCT, in the MCT application, select Help > Guide.


Figure 14: MCT user interface

8. Use one of the following methods to import the integration into an NAE or SCT archive:

- To use an .imp file, select File > Save, save the .imp file to your computer, then see Usingan .imp file to import field devices and points.

- To insert the integration directly into an SCT archive from MCT, see Inserting field devicesand points into an SCT archive database from MCT.

Note: If you import the integration into an NAE or SCT archive, information is only added.You cannot use the import process to modify or delete existing information. Deleteobjects in the NAE or SCT archive to remove them, or to prepare to import updatedversions of the objects.

Using an .imp file to import field devices and pointsTo save an .imp file from MCT, select File > Save.To import the .imp file into an NAE, use SMP to connect to the NAE, select the C•CURE-victor trunk,right click on it and select Import Integration.


Figure 15: Import an .imp file

Inserting field devices and points into an SCT archive databasefrom MCTIf you use SCT to configure the integration, you can transfer device and point information directlyfrom MCT to SCT.

1. In MCT, from the File menu, click Insert into SCT Database.

2. Enter a User ID and Password to connect to SCT installed on the same computer.

Figure 16: Connecting to SCT from MCT

3. Click Connect.

4. Select the Archive database, then select the VND Integration.


Note: If the archive database does not include a VND integration, open the archive in SCTand perform an Upload from the NAE copy the integration object to the archive.

5. Click OK. The objects are created inside the selected integration. If you chose to includeMetasys UI objects, they are created inside the ADS.

Manually adding devices and field pointsAs an alternative to the use of MCT, you can use SMP to manually add individual devices and fieldpoints to integration. This process is slower than the transfer of device and point information, butmay be appropriate in some cases.

Creating a device object1. In the All Items Tree, select the C•CURE-victor Integration, then select Insert > Field Device.

Figure 17: Integration Object - Insert Field Device

2. On the Destination page, click Next.

3. On the Selected Definition Mode page, select Manual, then, in the Vendor Reference field,enter a unique name. Click Next.


Figure 18: Device Object - Manual

4. On the Identifier page, in the upper-right corner of the window, enter a unique identifier, thenclick Next.


Figure 19: Device Object - Identifier

5. On the Configure page, select the Hardware tab.

6. In the Vendor Configuration Data list, click the ellipses icon to add configuration parametersfor the device.

7. Click Add to add new parameters and set correct value for each one.


Figure 20: Device Object - Vendor Configuration Data

The following table lists the Vendor Configuration Data and their meaning.

Table 4: NAE Vendor Configuration Data setup of C•CURE-victor Device

Parameter Description[1] The GUID used to identify the object in C•CURE-victor. The value is configured in

C•CURE-victor, and you can obtain it from the C•CURE-victor administrator.[2] The Point ID from the system configuration. For possible values, see C•CURE point

mapping tables and victor point mapping tables.[3] The SubType ID for the points in order to read the values. For possible values, see

C•CURE point mapping tables and victor point mapping tables.

8. Click OK to close the Modify List page, click Next to go to Summary page, then click Finish.

9. On the Extension Wizard page, click Done.

Creating field point objectsAfter you create a device object, you can insert a field point that represents a single device Item.

1. In the All Items tree, select the device, then select Insert > Field Point.

2. On the Destination page, click Next.

3. On the Selected Definition Mode page, select Manual, select the type of point, then clickNext.


Figure 21: Field Point Object - Type Selection

4. In the Vendor Reference field, enter a unique name, then click Next.


Figure 22: Field Point Object - Data Source

5. On the Identifier page, in the upper-right corner of the window, enter a unique identifier, thenclick Next.


Figure 23: Field Point Object - Identifier

6. On the Configure page, click the Hardware tab.

7. In the Vendor Configuration Data list, click the ellipses icon to add configuration parametersfor the point.


Figure 24: Field Point Object - Vendor Configuration Data

The following table lists the Vendor Configuration Data and their meaning.

Table 5: NAE Vendor Configuration Data setup of Field Point

Parameter Description[1] The GUID used to identify the object in C•CURE-victor. The value is configured in

C•CURE-victor, and you can obtain it from the C•CURE-victor administrator.[2] The C•CURE-victor Point ID from the system configuration[3] The Point ID from the system configuration. For possible values, see C•CURE point

mapping tables and victor point mapping tables.[4] The SubType ID for the points in order to read the values. For possible values, see

C•CURE point mapping tables and victor point mapping tables.

8. Click OK to close the Modify List page, click Next to go to Summary page, then click Finish.


C•CURE point mapping tablesDoor points definitionA single Door object is represented by one Metasys Object:

Metasys objectattribute

ID SUB ID Possible values description (R)eadable(W)ritable

Point definitionStatus 1 0 Normal (0) / Door Forced (1) / Door Held

(2)R

Value 2 1 Door Opened (0) / Door Closed (1) RAccess Status 3 -1 Access Granted (0) / Access Denied (1) /

Normal (2)R

Access Granted 10 -1 Idle State (0) / Access Granted (1) RAccess Denied 11 -1 Idle State (0) / Access Denied (1) RCommand 4 2 Locked (0) / Unlocked (1) R W

Input points definitionA single Input object is represented by one Metasys Object:



Point definitionValue 8 0 Inactive (0) / Active (1) R

Output points definitionA single Output object is represented by one Metasys Object:



Point definitionValue 9 0 Inactive (0) / Active (1) R W

Area points definitionA single Area object is represented by one Metasys Object:



Point definitionPeople count 7 2 Number RMax people admitted 5 0 Number RMin people admitted 6 1 Number R


victor point mapping tablesVideo Recorder points definitionA single Video Recorder object is represented by one Metasys Device object:



Point definitionCommunication Status 20 0 Online (2) / Offline (1)

Linked to the status of the device

(This is not a physical MSEA point)

R

Alert Status 20 2 Unknown (1)

Normal (2)

Overheat (4)

Reboot (8)

LogRotate (16)

AlarmRecoveryCompleted (32)

SensorAlarm (64)

LockDown (128)

R

Storage Status 20 1 Unknown (0 or 1)

Normal (2)

NoVolumes (4)

VolumeMissing (8)

VolumeCorrupt (16)

VolumeFailed (32)

NewVolume (64)

VolumeReAdded (128)

UnhealthyDisk (256)

DiskTemperature (512)

RaidDegradation (1024)

Backup (2048)

DataCulling (4096)

DiskFull (8192)

R

Archive Storage Status 20 3 Unknown (0) / Normal (1) / Degraded (2) R

Note: If the state of a recorder changes to online or offline, there is a two minute delay beforethe event is reported. If you configure Metasys alarms, keep this delay in consideration.


Camera points definitionA single Camera object is represented by one Metasys Object:

Metasys Objectattribute


Point definitionCommunication Status 22 0 Unknown (0) / Offline (1) / Online (2) RCamera Alert Status 22 100 Normal (0) / Alarm (1) RMotion Detected Alert 22 101 Normal (0) / Alarm (1) RVideo Loss Alert 22 102 Normal (0) / Alarm (1) RDry Contact Alarm 22 103 Normal (0) / Alarm (1) RUser Alarm 22 104 Normal (0) / Alarm (1) RAcoustic Sensor Alert 22 105 Normal (0) / Alarm (1) RPerimeter ProtectionAlert

22 106 Normal (0) / Alarm (1) R

Light Change Alert 22 107 Normal (0) / Alarm (1) RSpecific MotionDetected Alert

22 108 Normal (0) / Alarm (1) R

Text Input DetectedAlert

22 109 Normal (0) / Alarm (1) R

External Alarm 22 110 Normal (0) / Alarm (1) RUser Panic Alarm 22 111 Normal (0) / Alarm (1) RForeground AnalyticAlert

22 112 Normal (0) / Alarm (1) R

Direction Analytic Alert 22 113 Normal (0) / Alarm (1) RLinger Analytic Alert 22 114 Normal (0) / Alarm (1) RObject Enter AnalyticAlert

22 115 Normal (0) / Alarm (1) R

Object Exit AnalyticAlert

22 116 Normal (0) / Alarm (1) R

Background AnalyticAlert

22 117 Normal (0) / Alarm (1) R

Edge Face DetectedAlert

22 118 Normal (0) / Alarm (1) R

Edge Blur DetectedAlert

22 119 Normal (0) / Alarm (1) R

Dwell Analytic Alert 22 120 Normal (0) / Alarm (1) RVideo Failure Alert 22 121 Normal (0) / Alarm (1) RCrowd FormationAnalytic Alert

22 122 Normal (0) / Alarm (1) R

Queue MeasurementAnalytic Alert

22 123 Normal (0) / Alarm (1) R

Face RecognitionAnalytic Alert

22 124 Normal (0) / Alarm (1) R


Metasys Objectattribute


Camera Recording RateAlarm

22 125 Normal (0) / Alarm (1) R

Camera TemperatureAlarm

22 126 Normal (0) / Alarm (1) R

License PlateRecognition Alarm

22 127 Normal (0) / Alarm (1) R

Storage Status 22 1 Unknown (0)

Normal (2)

MaxRetention (4)

R

TroubleshootingTable 6: Troubleshooting

Problem SolutionThe integration trunk displays an Offline status Verify that the value in Vendor DLL field is

correct for engine. The value for the dll is casesensitive. Enter the values exactly as shown inTable 1.

Command the engine to Archive and then resetthe engine to bring the integration back online.

The device is online but the points are notcorrectly updated

Check that the related points are correctlyconfigured in C•CURE or victor, and verify thatthe object type is available in Metasys. SeeIntroduction.

If a data source is connected to more than oneobject, the point may only update in one ofthose objects. For example, if a door contactis linked to a Door object and an Input object,changes in state may only be reported throughthe Door object.

Not all of the devices are present in the SMP orSCT

Export the configuration from the C•CURE orvictor server, generate a new .imp file in MCT,and then verify that the missing items arepresent in the list of points.


Table 6: Troubleshooting

Problem SolutionThe integration trunk is online but the devices,or part of them, are offline.

Check that the following vendor parametersrelated to the connection with the victor webservice is correctly configured according theC•CURE-victor installation:

• IP Address• AppRef• Username• PasswordTo verify that the victor web service is runningcorrectly, open a web browser and navigate tohttp://[IP address or hostname of the webservice]/victorWebService. If the web service is runningcorrectly, a web page appears that showsdetails of the web service. If an error page isdisplayed in the browser, there is a fault withthe service.

Verify that the C•CURE-victor license is correctlyinstalled on the server with the correct optionsand matches the installed version of C•CURE-victor. See Design Considerations.

Verify that the imported devices matchthe actual devices in the C•CURE-victorconfiguration, and, for each device, verify thatthe first parameter in the Vendor ConfigurationData contains the correct GUID from C•CURE-victor.

If the devices are not the same, re-importthe .imp file generated from MCT. SeeTransferring device and point information.

Software termsUse of the software embedded in this product or access to the hosted services (includingSaaS and PaaS) applicable to this product, if any, is subject to applicable terms set forthat.www.johnsoncontrols.com/techterms Your use of this product constitutes an agreement to suchterms. If you do not agree to be bound by such terms, you may return the unused product to your placeof purchase.

© 2018 Johnson Controls. All rights reserved. All specifications and other information shown were current as of documentrevision and are subject to change without notice

www.johnsoncontrols.com/techterms

Date post:	03-Jul-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

NAE Commissioning for C•CURE-victor Integration ...cgproducts.johnsoncontrols.com › MET_PDF ›...

Documents