Understanding Envysion for Distech to Johnson Controls Migration

Understanding ENVYSION for Distech to Johnson Controls Migration

This guide covers using ENVYSION software when migrating from Distech controllers to Johnson Controls equipment while preserving graphics investments.

What is ENVYSION?

ENVYSION is Distech Controls' graphics and visualization software that runs on top of the Niagara Framework. Key characteristics:

Feature	Description
Platform	Niagara AX/N4 based
Graphics	HTML5 and legacy Flash
Target	Distech EC-Net controllers
Licensing	Included with Distech systems

Architecture Overview

Migration Scenarios

Scenario 1: Distech to JCI - Keep ENVYSION

Approach: Maintain ENVYSION as front-end, integrate JCI controllers via BACnet

Steps:

1. Keep existing ENVYSION/Niagara server
2. Add JCI controllers as BACnet devices
3. Re-map point references in graphics
4. Maintain dual-vendor architecture

Pros:

• Preserves graphics investment
• Familiar operator interface
• Gradual migration possible

Cons:

• Ongoing ENVYSION licensing
• Mixed vendor support complexity
• Point naming mismatches

Scenario 2: Full JCI Migration - Abandon ENVYSION

Approach: Replace ENVYSION with Metasys UI

Steps:

1. Export graphics designs (for reference)
2. Recreate graphics in Metasys
3. Decommission ENVYSION server
4. Full JCI system

Pros:

• Single vendor support
• Native JCI functionality
• Simplified architecture

Cons:

• Graphics recreation cost
• Operator retraining
• Faster timeline pressure

Scenario 3: Niagara Migration - Convert ENVYSION

Approach: Convert ENVYSION to standard Niagara graphics

Steps:

1. Migrate ENVYSION to vanilla Niagara
2. Integrate JCI via BACnet
3. Update point bindings
4. Maintain Niagara platform

Pros:

• Open platform preserved
• Graphics framework retained
• Multi-vendor capability

Cons:

• Graphics conversion effort
• Niagara licensing separate from Distech
• Some ENVYSION features lost

Graphics Compatibility

What Can Be Preserved

Element	Preservable?	Notes
Layout/design	Yes	Export as templates
Static images	Yes	PNG/SVG files reusable
Point bindings	Partial	References need updating
Animations	Partial	May need recreation
Scripts	Partial	Depends on target platform

What Requires Recreation

• Dynamic binding expressions
• ENVYSION-specific widgets
• Controller-specific status displays
• Alarm pop-ups and handlers
• Navigation hierarchies

Point Mapping Considerations

Distech to JCI Point Naming

Distech Convention	JCI Convention	Action
EC-BACnet-1/AI1	NAE1/N2:1/AI1	Update binding
ZoneTemp	ZN-T	May need rename or alias
SetpointEff	STPT-EFF	Align conventions

Recommended Approach

1. Document existing points - Export complete point list from ENVYSION
2. Create mapping table - Distech point → JCI equivalent
3. Use search/replace - Bulk update graphic files
4. Test thoroughly - Verify each graphic page

Step-by-Step Migration Process

Phase 1: Assessment

1. Inventory all ENVYSION graphics
2. Document point bindings per graphic
3. Identify custom scripts/widgets
4. Assess JCI point availability
5. Estimate conversion effort

Phase 2: Preparation

1. Export graphic source files
2. Create point mapping spreadsheet
3. Set up test environment
4. Configure BACnet integration to JCI

Phase 3: Conversion

1. Update point references systematically
2. Test each graphic after conversion
3. Address broken bindings
4. Update navigation structure
5. Verify alarm integration

Phase 4: Validation

1. Operator acceptance testing
2. Verify all points updating correctly
3. Test alarm/event handling
4. Performance testing
5. Documentation updates

Common Challenges

Challenge: Missing Points

Symptom: Graphics show "NaN" or no data Cause: JCI controller does not expose equivalent point Solution: Work with JCI to expose needed points via BACnet, or modify graphic to use available data

Challenge: Scaling Differences

Symptom: Values display incorrectly (e.g., 720°F instead of 72.0°F) Cause: Different scaling/units between systems Solution: Add conversion in binding expression or correct at source

Challenge: Status Representation

Symptom: Status displays show wrong states Cause: Different enumeration values (0/1 vs 1/2) Solution: Update graphic logic to handle new value mappings

Best Practices

1. Maintain old system during transition - Parallel operation validates conversion
2. Convert in phases - Critical graphics first, cosmetic improvements later
3. Document everything - Point mappings will be referenced for years
4. Train operators early - Any interface changes need communication
5. Plan for ongoing maintenance - Mixed systems need clear support boundaries

Tools and Resources

• ENVYSION Graphics Editor (Niagara Workbench)
• Point export utilities in EC-Net
• BACnet discovery tools
• Graphics file comparison tools (diff)
• Spreadsheet for point mapping