Project Drivers and LLLC Proposal Specification Language
This guide connects common project drivers with luminaire-level lighting controls (LLLCs) features and provides recommended specification language to support energy efficient lighting proposals.
Audience & Intended Use
This guide has been crafted to support the sales process between contractors and their customers.
|
Contractors |
Building Owners and Managers |
|---|---|
|
Supports project proposals by connecting customer priorities with LLLC features and provides specification language that supports the value propositions. |
Helps decision makers document project priorities and ensures the proposed system meets expectations. |
Contractors who successfully sell projects with luminaire-level lighting controls frequently share the same advice when it comes to developing project proposals.
Project Proposals DOs
1. Walk the site with the owner or facilities manager and inquire about:
- Current space use
- Future space use
- Challenges with the existing system
2. Document the customer’s drivers and priorities
3. Include LLLC specification language to demonstrate understanding and provide context for the proposal
4. When possible, include utility incentives and present the proposal with an estimated ROI
Project Proposal DON’Ts
- Suggest a solution (even LLLC) without first understanding customer needs
- Assume the customer always wants the cheapest and simplest solution
- Introduce technical jargon like “individual addressability” or “mesh networks” without providing context
- Assume system setup and programming time will exceed labor savings from other areas
- Rely on energy code alone to drive project specification
Project Drivers and Specification Language Support
The following table lists common project drivers, identifies LLLC performance features, and provides recommended performance specification language to support the project proposal. Not all systems include every feature, so select and adapt only items relevant to the specific product proposed.
| Primary Project Drivers | LLLC Performance Feature | Recommended Performance Specification Language to Support Proposal |
|---|---|---|
| Low Installation Cost |
|
To minimize labor and material costs, the proposed LLLC system features:
|
|
Low Operating Cost
|
|
To ensure low operating costs, the system will be configured with a sequence of operations that incorporates the following control strategies:
|
|
Space Flexibility
|
|
To accommodate space changes and tenant preferences the control system will feature:
|
| Ease of Use |
|
To ensure ease of use, the system will offer configuration from:
|
| Reliability |
|
To ensure reliability, the controls system relies on a mesh network capable of rerouting signals and automatically rejoining networks in the event of outages. If not on a mesh network, controls system should highlight how wireless signals are routed around buildings materials, which might attenuate signal strength (i.e., sub 1Mhz frequency). |
| Secondary Project Drivers | LLLC Performance Feature | Recommended Performance Specification Language to Support Proposal |
|---|---|---|
|
Cyber Security
|
|
To ensure the controls do not create a cyber risk, the system when applicable will:
|
| Accessibility |
|
To ensure accessibility, the system will:
|
| Scalability |
|
To ensure scalability, the system can expand network range and capabilities via
|
|
Code Compliance
|
|
To ensure code compliance, the LLLC system features integrated motion and photo sensors and a programmable fixture load controller, which will be programmed to a sequence of operations that meets or exceeds applicable code requirements. |