Coated Glass and Aluminium Composite Facers for PIR/PUR Boards
Compare two separate PIR/PUR facer directions: coated glass facer and aluminium composite facer. Review each by layer structure, air permeability or barrier target, lamination, foam-interface fit and board-line conditions.
Document availability
All listed document types: Available upon request
Documents are matched to the selected route, model, application and applicable report scope.
S10 product brief at a glance
Where this route fits best
Specification overview for route review
Technical review focus
Validation and document basis
How this route sits inside the buyer system
Layer stack is conceptual and must be adapted to the buyer final board construction.
Facing / surface layer
280-300gsm ultra-low-airflow coated glass facer
Bonding / interface zone
Adhesive, lamination, slurry, foam or board-facing interface depending on the selected system.
Core
PIR/PUR roof, wall and sandwich boards
System validation
Buyer-side production trials confirm final route suitability.
Route review path before sampling
Final suitability depends on foam chemistry, line speed, lamination, peel validation and buyer-side production trials.
PIR/PUR board manufacturers should review air permeability, foam-interface fit, peel stability and line continuity under the selected board construction.
Models, material type and area weight need to match the selected board construction.
Document availability depends on selected route, model and construction scope.
Request-gated document status
Availability is confirmed by selected route, model, application scope and internal review.
Product Brief
Shared after route, board application and review context are clear.
TDS
Reviewed by selected route, model and buyer-side board construction.
MSDS / SDS
Provided where the selected glass facing route and request scope apply.
Fire test documents
Evidence may be reviewed only where report scope matches the selected route and construction.
Compliance / Sustainability
Availability depends on selected route, declared scope and current verification context.
Is this route suitable for every board system?
No. It is a route for early review. Final suitability depends on buyer-side construction, process and validation.
Can I request technical documents?
Documents may be available upon request, depending on selected model, route, tested construction and report scope.
What information should I provide before sampling?
Share board core/system, current facing route, target performance, width/roll needs, document scope and the issue you want to solve.
Need to review whether S10 fits your board system?
Share your board application, selected route direction and document needs. GRECHO can coordinate the next review step.
