Skip to Content
IONAWhat's the difference between an IONA & a JACE controller

What's the difference between an IONA & a JACE controller

IONA and JACE are both building automation controllers from Tridium, but they serve different purposes and have distinct characteristics. This guide provides a comprehensive comparison to help understand the differences and choose the right controller for your application.

Overview

Both IONA and JACE controllers:

  • Niagara Framework: Both run the Niagara Framework
  • Building Automation: Both designed for building automation
  • Protocol Support: Both support multiple protocols
  • Tridium Products: Both manufactured by Tridium

However, they differ in architecture, capabilities, and target applications.

Architecture Differences

IONA Controller

Architecture:

  • Integrated I/O: Built-in I/O points on the controller
  • Compact Design: Compact, all-in-one design
  • Direct Connection: Direct connection to field devices
  • Unified Platform: I/O and control in single unit

Characteristics:

  • Physical I/O: Physical I/O terminals on controller
  • Point Count: Limited by built-in I/O capacity
  • Expansion: Supports expansion cards for additional I/O
  • Installation: Typically installed near field devices

JACE Controller

Architecture:

  • Network-Based: Primarily network-based controller
  • Protocol Gateway: Acts as protocol gateway and supervisor
  • No Built-in I/O: Typically no built-in physical I/O
  • Distributed System: Connects to distributed I/O devices

Characteristics:

  • Network Focus: Focus on network connectivity
  • Protocol Integration: Integrates multiple protocols
  • Supervisor Role: Acts as supervisor/workstation
  • Scalability: Highly scalable through network devices

Key Differences

Physical I/O

IONA:

  • Built-in I/O: Has physical I/O terminals on controller
  • Direct Connection: Direct connection to sensors/actuators
  • I/O Types: Supports various I/O types (AI, AO, DI, DO)
  • Point Capacity: Limited by built-in I/O (varies by model)

JACE:

  • No Built-in I/O: Typically no physical I/O terminals
  • Network Devices: Connects to I/O via network devices
  • Protocol-Based: Uses protocols (BACnet, Modbus, etc.) for I/O
  • Unlimited I/O: I/O capacity limited by network, not controller

Use Cases

IONA Best For:

  • Small to Medium Applications: Smaller building automation projects
  • Direct I/O Needs: Applications requiring direct I/O connection
  • Cost-Effective Solutions: Cost-sensitive applications
  • Simplified Installation: Applications requiring simplified installation
  • Local Control: Applications needing local I/O control

JACE Best For:

  • Large Applications: Large, complex building automation systems
  • Protocol Integration: Systems requiring multiple protocol integration
  • Supervisor Role: Applications needing supervisor/workstation functionality
  • Scalable Systems: Systems requiring high scalability
  • Network-Centric: Network-centric automation systems

Performance and Capacity

IONA:

  • Point Capacity: Limited by built-in I/O (typically hundreds of points)
  • Processing Power: Sufficient for local control applications
  • Memory: Adequate for typical applications
  • Network Capacity: Supports multiple network protocols

JACE:

  • Point Capacity: Very high (thousands to tens of thousands of points)
  • Processing Power: Higher processing power for complex applications
  • Memory: More memory for large applications
  • Network Capacity: Extensive network protocol support

Cost Considerations

IONA:

  • Lower Initial Cost: Typically lower initial cost
  • All-in-One: I/O included, reducing component count
  • Simplified Installation: Lower installation costs
  • Cost-Effective: Good value for smaller applications

JACE:

  • Higher Initial Cost: Typically higher initial cost
  • Additional Components: May require additional I/O devices
  • Complex Installation: May have higher installation costs
  • Scalability Value: Better value for large, scalable systems

Feature Comparison

I/O Capabilities

IONA:

  • Built-in I/O: Physical I/O terminals on controller
  • I/O Types: Analog inputs/outputs, digital inputs/outputs
  • Expansion: Supports expansion cards for additional I/O
  • Direct Connection: Direct connection to field devices

JACE:

  • Network I/O: I/O via network-connected devices
  • Protocol Support: Supports BACnet, Modbus, LonWorks, etc.
  • Unlimited Expansion: Unlimited I/O via network devices
  • Distributed I/O: Distributed I/O architecture

Network Capabilities

IONA:

  • Protocol Support: Supports multiple protocols
  • Network Interfaces: Ethernet and serial interfaces
  • Gateway Function: Can act as protocol gateway
  • Limited by I/O: Network capacity secondary to I/O

JACE:

  • Extensive Protocol Support: Very extensive protocol support
  • Multiple Networks: Supports many simultaneous networks
  • Advanced Gateway: Advanced protocol gateway capabilities
  • Network Focus: Primary focus on network connectivity

Software and Applications

IONA:

  • Niagara Framework: Full Niagara Framework support
  • Application Development: Supports application development
  • Web Interface: Built-in web interface
  • Workbench Compatible: Compatible with Niagara Workbench

JACE:

  • Niagara Framework: Full Niagara Framework support
  • Advanced Applications: Supports advanced, complex applications
  • Web Interface: Built-in web interface
  • Workbench Compatible: Compatible with Niagara Workbench
  • Supervisor Features: Advanced supervisor features

Selection Criteria

Choose IONA When:

  • Direct I/O Needed: Application requires direct I/O connection
  • Small to Medium Size: Small to medium-sized applications
  • Cost Sensitive: Cost is a primary consideration
  • Simplified Installation: Simplified installation preferred
  • Local Control: Local I/O control is primary requirement

Choose JACE When:

  • Large Scale: Large, complex automation systems
  • Protocol Integration: Extensive protocol integration needed
  • Supervisor Role: Supervisor/workstation functionality needed
  • High Scalability: High scalability requirements
  • Network-Centric: Network-centric architecture preferred

Integration Considerations

IONA Integration

Integration Points:

  • Direct I/O: Connect sensors/actuators directly
  • Network Protocols: Connect to other systems via protocols
  • Expansion Cards: Add I/O via expansion cards
  • Niagara Network: Integrate into Niagara network

JACE Integration

Integration Points:

  • Network Devices: Connect to network I/O devices
  • Protocol Gateways: Act as protocol gateway
  • Supervisor Network: Connect multiple systems/networks
  • Enterprise Integration: Enterprise-level integration

Migration Considerations

IONA to JACE Migration

When to Migrate:

  • Outgrowing Capacity: IONA capacity limitations reached
  • Scalability Needs: Need for higher scalability
  • Protocol Requirements: Need for more protocol support
  • Supervisor Needs: Need for supervisor functionality

Migration Considerations:

  • Application Porting: Port applications to JACE
  • I/O Migration: Migrate I/O to network devices
  • Network Restructure: Restructure network architecture
  • Training: Training on JACE platform

JACE to IONA Migration

When to Consider:

  • Cost Reduction: Need to reduce costs
  • Simplified Architecture: Prefer simplified architecture
  • Direct I/O: Prefer direct I/O connection
  • Smaller Application: Application size reduced

Migration Considerations:

  • I/O Consolidation: Consolidate I/O to IONA
  • Application Simplification: Simplify applications
  • Network Simplification: Simplify network architecture
  • Feature Review: Review feature requirements

Best Practices

IONA Best Practices

  • Right-Size Application: Match IONA to appropriate application size
  • I/O Planning: Plan I/O requirements carefully
  • Expansion Planning: Plan for expansion if needed
  • Network Design: Design network appropriately

JACE Best Practices

  • Scalability Planning: Plan for scalability from start
  • Network Architecture: Design network architecture carefully
  • Protocol Planning: Plan protocol integration
  • Resource Management: Manage system resources effectively

Additional Resources

  • IONA Product Documentation
  • JACE Product Documentation
  • Controller Selection Guide
  • Building Automation System Design Guide
IONAWhat expansion cards does the IONA support