Honeywell IRM Folders Structure and Best Practices
This guide clarifies the proper folder structure for Honeywell Integrated Rack Manager (IRM) configuration, specifically addressing nested folder questions.
IRM Folder Hierarchy
The IRM folder structure follows a specific hierarchy:
Note: Nested IrmFolders are valid but not recommended
Folder Types Explained
IrmFolder
- Purpose: Primary organizational container
- Location: Directly under IrmNetwork or nested inside other IrmFolders
- Can contain: IrmSubfolders, IrmDevices, or other IrmFolders
- Use case: Major building sections, equipment groups, floors
IrmSubfolder
- Purpose: Secondary organizational container
- Location: Inside IrmFolders only
- Can contain: IrmDevices only (no further nesting)
- Use case: Equipment categories within a building section
Answer: Nested IrmFolders vs IrmSubfolders
Both structures are technically valid:
Recommendation: Use IrmSubfolders when you don't need further nesting. Reserve nested IrmFolders for complex hierarchies.
Best Practices
When to Use IrmFolders
- Multi-building campuses (one folder per building)
- Large buildings with distinct sections
- When you need 3+ levels of hierarchy
- When grouping diverse equipment types
When to Use IrmSubfolders
- Organizing devices within a building/area
- Simple two-level hierarchy is sufficient
- Grouping similar equipment (all AHUs, all VAVs)
- When further nesting is not needed
Naming Conventions
Consistent naming improves navigation:
Performance Considerations
- Deep nesting (5+ levels) can slow navigation
- Very large folders (100+ devices) benefit from subfolders
- Balance between organizational clarity and browsing speed
Periodic Folder Specifics
The Periodic folder has special considerations:
| Item | Notes |
|---|
| Purpose | Contains devices polled on regular intervals |
| Scan timing | Set at folder level, inherited by contents |
| Typical use | Non-critical monitoring points |
| Avoid | Time-critical control points |
Structure recommendation for Periodic:
Common Mistakes to Avoid
- Over-nesting - More than 4 levels becomes hard to navigate
- Inconsistent patterns - Mix of IrmFolders and IrmSubfolders at same level
- Generic names - "Folder1", "New Folder" provide no context
- Wrong parent - Putting critical points in Periodic folder
- Flat structure - All devices directly under IrmNetwork (no organization)
Migration Tips
If reorganizing an existing IRM structure:
- Document current structure before making changes
- Plan new hierarchy on paper first
- Move devices during maintenance window
- Update any external references (graphics, schedules, trends)
- Verify communication after reorganization
Reference
For official guidance, consult:
- Honeywell WEBs-N4 documentation
- IRM driver documentation in Workbench Help
- Tridium driver documentation (IRM is based on Niagara drivers)