We actually read these.
Ideas submitted here go to the product team, not into a void. Add yours, vote on others, and comment on what matters to your business.
Talk to our Product Managers live: every other Monday, 1:00–2:00 PM ET → https://www.d-tools.com/cloud-product-office-hours
Component ID System for Device Identification & Connection View Clarity
Feature Idea
Introduce persistent and visible Component IDs for all devices and infrastructure items across the platform, with a primary focus on improving readability and differentiation within Connection View.
Expanded Feature Description
Overview
As projects grow in complexity, users frequently work with:
Multiple identical devices
Repeated equipment types
Distributed systems
Large connection diagrams
Multi-rack deployments
In the current workflow, devices may only display:
Product name
Manufacturer
Generic device type
This creates ambiguity when multiple identical items exist.
Example:
Netgear Switch
Netgear Switch
Netgear Switch
In Connection View, this becomes especially problematic because users cannot easily determine:
Which switch is connected where
Which endpoint belongs to which room
Which device corresponds to a physical installation
Which cable run terminates at which actual component
This feature introduces:
Persistent Component IDs assigned to every infrastructure item.
allowing every device to maintain a unique identity across:
Connection View
Plan View
Rack Elevations
Bills of Materials
Labels
Reports
Service documentation
Core Capabilities
Persistent Unique Component IDs
Capability
Assign a unique identifier to every device and infrastructure component in the project.
Expanded Description
Each item receives a distinct ID such as:
SW-01
CAM-04
DSP-02
AP-12
DISP-03
The ID remains consistent throughout the lifecycle of the project.
Benefits
Eliminates ambiguity
Improves project organization
Creates consistent infrastructure references
Simplifies communication between teams
Strategic Value
Creates:
“identity continuity” across the entire project ecosystem.
Connection View Device Differentiation
Capability
Display Component IDs prominently in Connection View to distinguish between visually identical devices.
Expanded Description
Connection View is the most critical area for device differentiation because signal flow and infrastructure relationships depend on accurately identifying endpoints.
Without IDs:
Display → Switch → DSP
could refer to any device instance.
With IDs:
DISP-01 → SW-03 → DSP-02
users can immediately identify:
Exact physical devices
Signal destinations
Port relationships
Rack associations
Benefits
Easier troubleshooting
Cleaner signal tracing
Better installer comprehension
Reduced engineering mistakes
Improved readability in large systems
Cross-View Infrastructure Identity Consistency
Capability
Ensure Component IDs remain consistent across all project representations.
Expanded Description
The same identifier should appear everywhere the device exists:
View |
Example |
Plan View |
CAM-07 |
Connection View |
CAM-07 |
Rack Elevation |
CAM-07 |
BoM |
CAM-07 |
Cable Labels |
CAM-07 |
This creates:
A shared infrastructure language
Consistent documentation references
Easier cross-team communication
Benefits
Better project coordination
Easier onboarding
Improved documentation quality
Reduced confusion
Automatic Component ID Generation
Capability
Automatically generate intelligent IDs based on configurable naming rules.
Expanded Description
The platform should auto-generate IDs using:
Device category
Room
Rack
Floor
Sequence number
Examples:
CAM-01
SW-IDF-02
DSP-CONF-A
AP-L2-14
Benefits
Faster project setup
Reduced manual naming work
Standardized infrastructure labeling
Better scalability
Future Enhancements
Sequential numbering rules
Auto-prefix assignment
Room-based numbering
Rack-aware IDs
User-Configurable Naming Standards
Capability
Allow organizations to define custom Component ID conventions.
Expanded Description
Different organizations follow different standards.
Users should be able to configure formats such as:
[Room]-[Type]-[Sequence]
or:
[Floor]-[Rack]-[Device]
Examples:
CONF-A-DISP-01
MDF-SW-02
L2-CAM-14
Benefits
Supports enterprise standards
Easier integration with existing workflows
Improved operational consistency
Installer-Friendly Infrastructure Referencing
Capability
Use Component IDs as operational references for field installation and troubleshooting.
Expanded Description
Installers frequently rely on:
Device labels
Cable labels
Rack identifiers
Endpoint references
Without unique IDs:
Installers may confuse identical devices
Signal tracing becomes difficult
Troubleshooting slows down
Component IDs create:
A shared operational language between engineering and field teams.
Benefits
Faster installations
Reduced field errors
Easier troubleshooting
Improved commissioning workflows
Cable & Connection Label Integration
Capability
Automatically incorporate Component IDs into cable labeling workflows.
Expanded Description
Once devices have persistent IDs, the platform can generate:
Cable labels
Endpoint labels
Port schedules
Connection documentation
Example:
SW-03 Port 12 → CAM-07
This creates:
Fully traceable infrastructure documentation
Better cable management
Easier maintenance workflows
Benefits
Improved field accuracy
Faster serviceability
Cleaner documentation
Search & Navigation by Component ID
Capability
Allow users to search, filter, and navigate using Component IDs.
Expanded Description
Users could:
Search “CAM-14”
Locate “DSP-02”
Jump directly to “SW-03”
The system would highlight:
Physical location
Rack placement
Connections
Related documentation
Benefits
Faster navigation
Better large-project usability
Easier troubleshooting
Visual Display Controls for Component IDs
Capability
Allow users to configure how and where Component IDs appear.
Expanded Description
Users may want IDs displayed differently depending on workflow.
Possible controls:
Show/hide IDs
Adjust font size
Position labels
Simplify views
Role-specific display modes
Example Modes
Mode |
Display Style |
Installer Mode |
Full IDs visible |
Client Mode |
Simplified names |
Engineering Mode |
Full technical references |
Benefits
Better usability
Cleaner presentations
Flexible workflows
Large-System Scalability Improvements
Capability
Improve usability of Connection View for enterprise-scale projects.
Expanded Description
Large projects may contain:
Hundreds of devices
Multiple racks
Distributed rooms
Repeated infrastructure types
Without Component IDs:
Connection View becomes visually ambiguous
Troubleshooting becomes difficult
Device relationships become unclear
Component IDs make large-scale systems manageable.
Benefits
Better enterprise scalability
Easier maintenance
Reduced cognitive overload
Long-Term Service & Lifecycle Tracking
Capability
Use Component IDs as persistent references throughout the system lifecycle.
Expanded Description
Years after installation, service teams need to identify:
Specific hardware
Historical replacements
Warranty records
Upgrade history
Component IDs become:
Lifecycle anchors
Service references
Asset management identifiers
Benefits
Better service workflows
Easier retrofits
Improved maintenance history
Intelligent Infrastructure Relationship Mapping
Capability
Use Component IDs to map relationships between devices, ports, and systems.
Expanded Description
Once infrastructure items have persistent IDs, the platform can model:
Signal flow
Port relationships
Device dependencies
Infrastructure hierarchies
Example:
DSP-01 → AMP-02 → SPK-14
This creates:
Smarter troubleshooting
Better system comprehension
More intelligent documentation
Strategic Value
Moves the platform toward:
“infrastructure-aware system modeling.”
Unified Infrastructure Identity Framework
Capability
Create a centralized identity system governing all infrastructure components.
Expanded Description
Component IDs become foundational references for:
Devices
Ports
Connections
Racks
Rooms
Cable runs
Zones
This establishes a structured infrastructure model similar to:
Enterprise IT systems
Structured cabling standards
Professional AV documentation practices
Strategic Value
Transforms the platform from:
“visual device placement”
into:
“a structured infrastructure lifecycle management platform.”
Summary of Core Product Value
These capabilities collectively create:
A scalable and consistent infrastructure identity system integrated across all project workflows.
The feature set enables:
Unique device identification
Better Connection View readability
Cross-document consistency
Improved installer communication
Automated labeling
Easier troubleshooting
Enterprise-scale infrastructure management
Long-term service traceability
Most importantly, it closes the workflow gap between:
“multiple visually identical devices with ambiguous relationships”
and
“a fully traceable infrastructure system where every component has a clear and persistent identity.”
