Getting Type-Test References Right the First Time
DNO applications were being rejected because type-test references were wrong. The problem: garbage data from upstream systems. The solution: authoritative validation.
100%
Type-Test Reference Accuracy
Clean
DNO Applications
Reduced
Approval Cycle Time
The Challenge
Design software exports often contained incorrect 'type test references'-model numbers instead of proper ENA codes. These invalid references caused DNO applications to be rejected or delayed, requiring manual rework to look up and correct the references. The problem: garbage data from upstream systems was flowing unchecked into compliance paperwork.
Business Impact
DNO applications rejected or delayed due to invalid type-test references. Manual rework required to look up correct ENA codes. Extended approval cycles delaying project completion. Compliance manager time wasted on preventable data quality issues.
Who This Affected
Key Pain Points
Design software exports containing garbage type-test references
Model numbers instead of proper ENA codes flowing into DNO applications unchecked
DNO applications rejected due to invalid references
Delays and rework required when applications contain incorrect equipment data
Manual lookups required to find correct codes
Compliance staff wasting time manually correcting data that should have been right from the start
The Solution
Built product catalog with authoritative type-test references sourced from ENA 'Live Devices' database. Validation logic in application pack generation checks equipment references against the catalog, preventing garbage data from reaching DNO applications. The system ensures that only accurate, ENA-validated references appear in compliance paperwork.
Features Implemented
- ✓Product catalog with authoritative type-test references from ENA database
- ✓Validation logic in DNO application pack generation
- ✓ENA 'Live Devices' lookup integration
- ✓Data quality checks preventing invalid references from propagating
- ✓Override capability for edge cases with audit trail
Implementation Approach
Product catalog was populated with correct type-test references from the ENA 'Live Devices' database. Application generation logic validates equipment references against this catalog before creating G98/G99 packs. When design software data contains garbage references, the system flags the issue and uses the authoritative catalog value instead.
The Results
Clean Applications
DNO applications contained accurate type-test references, eliminating a major rejection cause
Fewer DNO Queries
Reduced back-and-forth with DNOs over equipment reference issues
Reduced Cycle Time
Applications approved faster without delays for reference corrections
"The type test reference they are sending is garbage… that garbage data is coming from the design software. We'll build this to be beautiful and accurate."
— Compliance Manager
Why This Story Matters
Compliance Manager
Why It Matters
Data quality in DNO applications isn't optional-garbage references cause rejections and delays that compound workload.
Key Focus
Implement authoritative validation to prevent upstream data quality issues from reaching compliance paperwork.
Related Case Studies
Explore more stories of solar companies solving real challenges