Home / Solutions / Tunnel and Road Lighting Energy Saving

Tunnel and Road Lighting Energy Saving

Tunnel and road lighting should first establish a register by lighting circuit, section and operating mode. CW then aggregates consumption and status, and CC100, I/O and HMI can serve as candidates for local control. Traffic, illuminance and environmental data usually come from third-party systems. Control strategies must meet lighting safety and traffic operation requirements and be validated in a small, reversible pilot; an energy saving figure cannot be committed on the basis of a product combination alone.

Energy DataSavings Verification

Solution overview

The solution is positioned as zoned lighting monitoring and a controlled optimization pilot. It protects lighting function and safety boundaries first, then evaluates changes in energy use.

Applicable industries

  • Road tunnels

Primary user roles

  • M&E O&M
  • Traffic IT engineers
  • Project integrators

Problems addressed

  • Lighting runs at full power for long periods while traffic and environmental conditions are not used in control
  • Lighting circuits, sections and operating modes lack a unified register
  • Control upgrades lack safety boundaries, fallback and effect verification

Recommended product combination

System architecture and data flow

Tunnel and Road Lighting Energy Saving System TopologyFour-layer data flow across perception, edge control, platform and application for Tunnel and Road Lighting Energy Saving.01Perception layer
Lighting circuit status and energy data, together with third-party traffic, illuminance or environmental dat…
02Edge / control layer
CC100 with I/O can execute local strategies within the pilot scope, retaining manual and fallback modes.
03Platform layer
FEXLINK records zoned data, strategy versions and test results.
04Application layer
M&E staff review operating status and evaluate lighting and energy use changes.

Perception layer

Lighting circuit status and energy data, together with third-party traffic, illuminance or environmental data, form the inputs.

Edge / control layer

CC100 with I/O can execute local strategies within the pilot scope, retaining manual and fallback modes.

Platform layer

FEXLINK records zoned data, strategy versions and test results.

Application layer

M&E staff review operating status and evaluate lighting and energy use changes.

Data flow

  1. Build the register of lighting sections, circuits and operating modes
  2. Acquire power, switching status and external environmental data
  3. Establish the reference period and zoned baselines
  4. Execute control strategies within the authorized scope
  5. Record lighting status, fallback and energy use changes

Integration and interfaces

  • Traffic, illuminance and traffic control data usually come from third-party systems; interfaces and responsibility must be confirmed
  • The lighting circuit control method should follow the existing distribution and control principle
  • When connecting to the tunnel M&E platform, define read-only or control authority first

Applicable standards

  • Road tunnel lighting, traffic operation and electrical design standards are confirmed against project location
  • Control circuits and local operation requirements follow applicable safety codes
  • Pilot strategies, minimum illuminance and fallback conditions are frozen before implementation

Acceptance and delivery boundaries

Suggested acceptance dimensions

  • Lighting sections, circuits, controlled objects and operating modes correspond one-to-one
  • The reference period covers typical traffic and weather conditions
  • Control actions have authority and manual fallback
  • Lighting status and strategy execution results are traceable
  • Energy use changes are measured on the same boundary
  • Pilot conclusions include illuminance or operating constraint review

Limitations and exclusions

  • The solution does not commit to a fixed energy saving rate or automatic adaptation to every tunnel scenario
  • Control functions cannot replace traffic operation, fire protection or emergency lighting requirements
  • The specific interfaces and control capability of CC100, I/O and HMI must be confirmed separately

Operational value

  • Turns zoned lighting energy and operating status into verifiable data
  • Provides a test basis for time-based, zoned or external-condition strategies
  • Reduces operating risk from retrofits made without a pilot

Selection guidance

  • Confirm the lighting circuit control method and the permitted adjustment range first
  • Run control pilots only in sections with safety boundaries and fallback conditions
  • Without third-party traffic or environmental data, start with zoned monitoring and manual strategy evaluation

Typical implementation patterns

  • A typical evaluation pattern selects one lighting circuit section, establishes zoned baselines and a manual strategy, then evaluates external traffic and environmental interfaces. The pattern is a framework awaiting validation and does not mean a specific tunnel or road project has been implemented.

Before retrofit → With the solution

Before retrofit

  • Lighting runs at full power for long periods while traffic and environmental conditions are not used in control
  • Lighting circuits, sections and operating modes lack a unified register
  • Control upgrades lack safety boundaries, fallback and effect verification

With the solution

  • Turns zoned lighting energy and operating status into verifiable data
  • Provides a test basis for time-based, zoned or external-condition strategies
  • Reduces operating risk from retrofits made without a pilot

How to evaluate the effect

01

Measurable signal

Lighting circuit status and energy data, together with third-party traffic, illuminance…

02

Data source

CW Edge Computing Gateway · CC100 PLC Local Controller

03

Review method

Lighting sections, circuits, controlled objects and operating modes correspond one-to-one

04

Acceptance boundary

The solution does not commit to a fixed energy saving rate or automatic adaptation to every tunnel scenario

Frequently asked questions

Can dimming follow traffic flow automatically?

It requires reliable traffic and environmental data, a dimming-capable interface and a safety strategy, and must be validated in a pilot.

Can CC100 control lighting circuits directly?

The I/O, relay or communication method and the lighting circuit design must be confirmed. It cannot be judged from the PLC name alone.

How is lighting safety verified?

Follow the project lighting standards and emergency requirements, set minimum lighting, manual and fallback modes, and confirm them through site inspection.

How much energy can be saved?

No uniform figure can be committed. It depends on luminaires, traffic, climate, control strategy and reference period, and must be measured.

Are new sensors required?

It depends on whether existing traffic, illuminance and environmental data is available. Third-party interfaces must be verified first.

Request a matched product combination and project review

Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.

Contact FEXLINK