1. AX LICENSING & NICS Topics: 1 – License File
2 – Niagara Interoperability Conformance Statement (NiCS)
3 – Interoperability Examples

2. AX Licensing & NICS 1 – An “Open” Approach
EST: 15:00
1 – An “Open” Approach
2 – NICS – Niagara Interoperability Conformance Statement
3 – License File Contents
4 – Interoperability Examples
Module 2 Menu
This module should take about 60 minutes.
When you’ve completed this presentation on EC-gfxProgram Basics, click on the “QUIZ” button below to take a short quiz Then click the brown “NEXT MODULE” arrow below to advance to the next e-module – Module X: Module Name.
Click to review Instructions >

3. AX Licensing and NICS Navigation Instructions
At any time during a topic, you may click on the blue “BACK TO MENU” arrow at the bottom to return to the main menu.
BACK TO MENU
Select any button on the main menu to navigate to the topic of choice.
When done with that topic, look for the red “BACK TO MENU” arrow to return to this menu.
BACK TO MENU

4. AX Licensing and NICS Navigation Instructions
MORE INFORMATION LINKS: Select these links whenever prompted to view examples and additional info.
You will see instructions in this box regarding what to click and what you will see.
In some cases, there may be semi-transparent green highlighted areas like this that are hyperlinked.
ADDITIONAL MENU LINKS: Select these links whenever prompted to obtain more information on a specific topic.
Hysteresis
Limit / Linear
ADDITIONAL NAVIGATION LINKS: Select these links to navigate from sub-topics back up to the topic level.
BACK TO TOOLBOX
Navigation consists of one or more of the following
QUIZ LINKS:
Select these links to test your knowledge at the end of each module.
NEXT MODULE LINKS:
Select this link when you’ve completed the current module and wish to advance to the next module.
NEXT MODULE

5. AX Licensing and NICS Icons
MOUSE ICONS: Where needed when describing different processes, the following mouse icons are used to define whether to use left-, double- or right-click mouse options.
Left-click 2
Double left-click
Right-click
STEPS ICONS: Indicate ordered steps of a procedure. 1 2 3
The “drag-and-drop” method is only one of several methods to bring proxy points into the station’s database.
NOTE ICON: Where needed when describing different concepts, a note icon will provide additional information.

6. USING AN “OPEN” APPROACH Topic 1
AX LICENSING & NICS
Topic 1– What is Smart Room Control?
In this topic, you will explore:
USING AN “OPEN” APPROACH Topic 1
BACK TO MENU

7. Proprietary vs. Open
A brief look at “Proprietary/Closed v. “Open” Building Automation Systems

8. The Problems With Being “Closed” - Proprietary and Closed
Proprietary Front End!
Proprietary Programming and Graphics Toolsets
Problems:
Single Sourced
Proprietary Protocols
Proprietary Toolsets
Proprietary Software
Limited Integration
End Result… “Locked In”
Proprietary Network Level!
Rudimentary System Architecture and Overview of “Closed/Proprietary” Systems
Proprietary Field Level Network!

9. The Problems With Being “Closed” - Proprietary and “Open”
Proprietary Front End!
Proprietary Programming and Graphics Toolsets
Problems:
Single Sourced
Some Proprietary Protocols
Proprietary Toolsets
Some “Open” Standards
Proprietary Front End
End Result…. “Locked In”
Proprietary / Open Network Level
Lack of Choices for “Ongoing” Service, Lack of Choice, Lack of “Tools, Basically a “Proprietary System”
Open Standards for Field Level Network

10. The Niagara Framework Niagara Frameworks was created to:
Meet the need for a universal protocol agnostic automation architecture built on open standards
Merge multi vendor automation into one single platform
Accessible thru standard web browsers
Enable cloud-based applications programming
Niagara Frameworks was created to:
Meet the need for a universal protocol agnostic automation architecture built on open standards
Merge multi vendor automation into one single platform
Accessible thru standard web browsers
Enable cloud-based applications programming

11. Proprietary Programming and Graphics Toolsets
The Problems With Being “Closed” - Proprietary and “Open” with Niagara Framework
Proprietary or Open
Front End!
Proprietary Programming and Graphics Toolsets
Problems:
Vendor locking
Restrictive licensing
OPEN Niagara Network Level
Lack of Choice for “Ongoing” Service, Lack of Choice, Lack of “Tools, Basically a “Proprietary System”
Open Standards for Field Level Network

12. NICS – Niagara Interoperability & conformance statement Topic 2
AX LICENSING & NICS
Topic 1– What is Smart Room Control?
In this topic, you will explore:
NICS – Niagara Interoperability & conformance statement Topic 2
BACK TO MENU

13. What is a NiCS? To be fully open, manufacturers must have an open
The NiCS (Niagara Interoperability Conformance Statement) provides a structure (or schema) that companies can use to define the various levels and types of Niagara interoperability that their products will support.
To be fully open,
manufacturers
must have
an open
license & NiCS.

14. NiCS – Niagara Interoperability & Conformance Statement
<feature name="brand" accept.station.in="*" accept.station.out="*" accept.wb.out="*" brandId="distech" accept.wb.in="*"/>
Device
Compatibility
Integration Tool Compatibility
accept.station.in = “*”
accept.station.out = “*”
accept.wb.in = “*”
accept.wb.out = “*”
brandId = “distech”
BACK TO MENU

15. NiCS Attributes
<feature name="brand" accept.station.in="*" accept.station.out="*" accept.wb.out="*" brandId="distech" accept.wb.in="*"/>
brandId: OEM chooses an ID as the identifier for its product line
Can only have ONE brandId entry; Cannot be changed once licensed
accept.station.in: a list of brands that the local station will allow AX data to come IN from
accept.station.out: a list of brands that the local station will allow AX data to be shared with
“*” – wildcard designation to allow all brands
accept.wb.in: a list of integration tool brands that this station will allow to be connected to it for engineering of its application
accept.wb.out: a list of station brands that this integration tool is allowed to connect to for engineering of its application
“*” – wildcard designation to allow all brands
BACK TO MENU

16. Open Field Network Level
A Truly Open BAS
Freeware Toolsets
Niagara /Bacnet IP Network Level
Open Field Network Level

17. Niagara Framework What Protocols does Niagara work with? BACnet®
LonWorks®
MODBUS®
Drivers developed to integrate proprietary networks

18. Why “Open” Benefits the End User
Preserve existing investments in devices and integrating them with new standards-based technologies.
Ability to access and control their systems thru standard web browser.
Better overall facility management and control.
Reduced the potential for vendor lock-in
Reduced Total cost of Ownership

19. LICENSE FILE CONTENTS Topic 3
AX LICENSING & NICS
Topic 1– What is Smart Room Control?
In this topic, you will explore:
LICENSE FILE CONTENTS Topic 3
BACK TO MENU

20. License File
<license version="3.6" vendor="Tridium" generated=" " expiration=" " hostId="Win-D0BE-9BC0-293E-45F3">
<feature name="brand" accept.station.in="*" accept.station.out="*" accept.wb.out="*" brandId="distech" accept.wb.in="*"/>
BACK TO MENU

21. License File Definitions
All license files require an opening “<license … >” line where the last line in the file is the closing “</license>” tag.
<license version="3.6" vendor="Tridium" generated=" " expiration=" " hostId="Win-D0BE-9BC0-293E-45F3">
All contents (line items) are stated as “<feature name=…/>” PLUS an encrypted “<signature>…”</signature> line.
<feature name="brand" accept.station.in="*" accept.station.out="*" accept.wb.out="*" brandId="distech" accept.wb.in="*"/>
………. All other features ……….
<signature>MCwCFCMmnP9okcoGilWtoOPAxBNwQQ3KAhRIGCXHQGd6onwF/T6KguZqjLdZEQ==</signature> </license>
BACK TO MENU

22. License File Definitions
<license version="3.6" vendor="Tridium" generated=" " expiration=" " hostId="Win-D0BE-9BC0-293E-45F3">
version: designates the highest release of AX that can be installed
If newer release is installed, the JACE will fail on start-up – License File Error
vendor: always Tridium
generated: date when the license file was generated
expiration: expiration date of the license file
After expiration date, the Workbench will fail on start-up – License Expired Error
BACK TO MENU

23. License File Definitions
<license version="3.6" vendor="Tridium" generated=" " expiration=" " hostId="Win-D0BE-9BC0-293E-45F3">
hostid: alpha-numeric code that is generated upon installation of the Workbench software on a Windows-based platform – MUST match the host ID of the JACE
QNX-based JACEs are assigned a host ID similar to Windows:
“Qnx-NPM E8F-2420”
serialnumber: applies only to a license for a QNX-based JACE – assigned from the factory – MUST match the serial number of the JACE
BACK TO MENU

24. Interoperability examples Topic 4
AX LICENSING & NICS
Topic 1– What is Smart Room Control?
In this topic, you will explore:
Interoperability examples Topic 4
BACK TO MENU

25. Device-to-Device Compatibility
Brand “A” JACE
accept.station.in = “*”
accept.station.out = “*”
Brand “B” JACE
accept.station.in = “*”
accept.station.out = “*”
Brand “A” and Brand “B” JACEs:
CAN pass data between each other
Station compatibility matched
BACK TO MENU

26. Device-to-Device Incompatibility
Brand “A” JACE
Brand “B” JACE
Brand “C” JACE
accept.station.in = “*”
accept.station.out = “*”
accept.station.in = “*”
accept.station.out = “*”
accept.station.in = “C”
accept.station.out = “C”
Brand “A” and Brand “B” JACEs: CAN pass data between each other
Station compatibility matched
Brand “C” JACE:
CANNOT pass data to either Brand “A” or “B” JACEs
Station compatibility NOT matched
BACK TO MENU

27. Device-to-Supervisor Compatibility
accept.station.in = “*”
accept.station.out = “*”
Brand “A” JACE
accept.station.in = “*”
accept.station.out = “*”
Brand “B” JACE
accept.station.in = “*”
accept.station.out = “*”
Brand “B”
AX Supervisor
Brand “A” and Brand “B” JACEs: CAN pass data between each other
Station compatibility matched
Brand “B” AX Supervisor:
CAN pass data to either Brand “A” or “B” JACEs
Station compatibility matched
BACK TO MENU

28. Integration Tool-to-Device Compatibility
Brand “A” JACE
accept.wb.in = “*”
accept.wb.out = “*”
accept.wb.in = “B”
accept.wb.out = “*”
accept.wb.in = “B”
accept.wb.out = “*”
Brand “B” Workbench
Brand “B” JACE
Brand “B” Workbench:
CAN engineer Brand “A JACE
Brand “A” accepts ANY tool
Brand “B” Workbench:
CAN also engineer Brand “B” JACE
Workbench compatibility matched
BACK TO MENU

29. Integration Tool-to-Device Incompatibility
Brand “A” JACE
accept.wb.in = “*”
accept.wb.out = “*”
accept.wb.in = “B”
accept.wb.out = “*”
accept.wb.in = “*”
accept.wb.out = “*”
Brand “A” Workbench
Brand “B” JACE
Brand “A” Workbench:
CAN engineer Brand “A” JACE
Workbench compatibility matched
AND Brand “A” accepts ANY tool
Brand “A” Workbench:
CANNOT engineer Brand “B” JACE
Brand “B” ONLY accepts Brand “B” tool
BACK TO MENU

30. Compatibility Example
Brand “A” JACE
Brand “B”
AX Supervisor
Brand “B” JACE
accept.station.in = “*”
accept.station.out = “*”
accept.wb.in = “*”
accept.wb.out = “*”
accept.station.in = “*”
accept.station.out = “*”
accept.wb.in = “B”
accept.wb.out = “*”
accept.station.in = “*”
accept.station.out = “*”
accept.wb.in = “B”
accept.wb.out = “*”
Station compatibility matched
Brand “A” / “B” JACEs and Brand “B” Supervisor:
CAN pass data between each other
Brand “B” AX Supervisor  Brand “A” JACE:
Brand “A” accepts ANY tool
CAN engineer Brand “A” JACE
Brand “B” AX Supervisor  Brand “B” JACE:
Workbench compatibility matched
CAN engineer Brand “B” JACE

31. Why NOT An Always “Open” NiCS?
Some applications use Niagara for critical or specialized applications.
Modifying the application with another Workbench brand could compromise safety or cause equipment damage.
Some vendors want to allow only “authorized” representatives of the vendor to make changes to the application.
This could be for quality or competitive reasons.
BACK TO MENU

32. How Do You Get An “Open” NiCS?
BEFORE YOU BUY:
Specify Open NiCS
Open NiCS specification available from Distech
All software licenses must have the following NiCS:
Device Compatibility
Integration Tool Compatibility
accept.station.in = “*”
accept.station.out = “*”
accept.wb.in = “*”
accept.wb.out = “*”
EXISTING PROJECT
Ask your vendor to modify their license to allow for interoperability with other Niagara systems.
BACK TO MENU

33. BACK TO
Licensing-NICS
MENU
(CLICK HERE)

34. It’s Quiz Time REVIEW Click the QUIZ button to begin.
It’s time to review what you’ve learned.
Click the QUIZ button to begin.
If you wish to review first, click the REVIEW button below.
REVIEW

35. The QUIZ is still under development
The QUIZ is still under development. So click again and we’ll take you to the next module.
NEXT MODULE