Solar CCTV Deployment Checklist for Malaysia
Use this solar power for CCTV deployment checklist to verify loads, solar access, autonomy, PoE, backhaul, monitoring and commissioning evidence.
By Maxsol Team

A solar CCTV project should not proceed to procurement until the team has documented the complete electrical load, site-specific solar access, required autonomy, equipment interfaces, environmental exposure and maintenance arrangements. Camera wattage alone is not enough: recording devices, PoE conversion, wireless backhaul, heaters, infrared lighting and conversion losses can materially change the power requirement.
The most useful solar power for CCTV deployment checklist is therefore an evidence checklist. Each design assumption should be supported by a datasheet, site measurement, survey photograph, network test or written operating requirement. If a value remains unknown, mark it as a design risk rather than replacing it with a convenient estimate.
Solar CCTV pre-deployment checklist at a glance
Before approving equipment or installation, confirm that the project file contains:
- A complete day and night load schedule
- Camera power figures for all operating modes
- Recording and communications equipment loads
- DC voltage, PoE, pinout and data interface details
- Solar access evidence for the least favourable design period
- Battery autonomy and recovery objectives
- Load-priority and low-voltage shutdown rules
- Mounting, enclosure and cable-entry requirements
- Wireless path or mobile backhaul evidence
- Remote monitoring requirements
- Safe maintenance and physical access arrangements
- Commissioning measurements for energy and network performance
- Acceptance criteria agreed before installation
This review complements, rather than replaces, detailed energy calculations. For the calculation process, use the off-grid CCTV solar sizing guide after collecting the evidence below.
Document cameras, recording and backhaul loads
Start with an equipment schedule that includes every device drawing power from the solar system. Do not base the design only on the camera’s nominal daytime wattage.
Record day, night and peak operating states
A camera may consume different amounts of power depending on whether infrared illumination, white light, analytics, pan-tilt-zoom movement, lens heating or other functions are active. Obtain documented values for the intended operating mode and verify whether the stated figure is typical, maximum or measured.
For each device, record:
| Load item | Evidence to collect | Operating detail to confirm |
|---|---|---|
| Fixed or PTZ camera | Datasheet and, where possible, measured input power | Day, night, infrared and movement states |
| Network video recorder | Datasheet or input measurement | Disk count, recording load and operating schedule |
| PoE switch or converter | Input and output ratings | Conversion loss, idle use and output limit |
| Wireless bridge or router | Datasheet and site test | Full-load consumption and link mode |
| Mobile modem | Datasheet or measurement | Idle, connected and peak transmission demand |
| Auxiliary lighting | Rated and measured power | Switching schedule and duration |
| Control or monitoring unit | Datasheet | Continuous or intermittent operation |
| Fans, heaters or enclosure devices | Rated power | Trigger conditions and duty cycle |
Use watt-hours per day, not watts alone, when preparing the energy budget. A 10W load operating continuously uses more daily energy than a higher-powered device that runs only briefly.
Include recording architecture
Decide where video will be recorded before sizing the power system:
- On-camera storage: Lower central equipment demand, but retrieval and storage management must be planned.
- Local NVR at the solar site: Adds continuous load and may require more enclosure space, cooling and battery capacity.
- Remote recording over a network: Reduces local recording hardware but makes backhaul availability and bandwidth critical.
- Hybrid recording: Can improve resilience but adds configuration and storage-management requirements.
Document frame rate, resolution, codec, retention objective and event-recording policy. These affect storage and network demand even when they do not directly change the camera’s rated input power.
Treat backhaul as part of the permanent load
Wireless bridges, access points, routers, mobile modems and network switches may operate 24 hours a day. Their consumption must be included even when no one is actively viewing video.
For example, the Maxsol CPE295 outdoor wireless CPE documents 5.8GHz operation, a 2×2 14dBi directional MIMO antenna, one Gigabit LAN port, IEEE 802.3af/at or 9–48V DC power support, and 6.5W full-load consumption. These details can support an initial architecture review, but range or rate labels must not be treated as guaranteed site throughput. Alignment, interference, vegetation, obstructions and the remote endpoint still require validation.
Survey shade, mounting and environmental exposure
A desktop estimate cannot show whether a panel will be shaded by a tree, roof edge, pole, signboard or future vegetation. Conduct a site survey and preserve the findings in photographs, drawings and survey notes.
Assess the design month, not only a clear day
The array should be reviewed against the least favourable practical solar period used for the project design. In Malaysia, cloud cover, heavy rainfall and seasonal weather patterns can reduce daily solar collection even when daytime temperatures remain high.
Collect or confirm:
- Solar resource assumptions and their source
- The selected design month or design period
- Panel orientation and proposed tilt
- Morning and afternoon shading
- Nearby vegetation and expected growth
- Obstructions from buildings, towers and terrain
- Space for panel installation and maintenance
- Whether water, dirt or leaves may accumulate
- Cable length between the panel, controller, battery and load
Record shade at more than one time of day. A photograph taken around midday may miss significant morning or late-afternoon obstruction.
Review mounting and structural conditions
The survey should establish where the solar panel, equipment enclosure, camera and antenna will be mounted. Confirm that the structure can accept the proposed equipment and that installers can orient and secure each component without blocking another.
Check:
- Pole dimensions and available mounting area
- Panel clearance from the camera’s field of view
- Wind exposure and vibration
- Access for fastening and cable routing
- Risk of accidental impact or tampering
- Drainage around ground-mounted equipment
- Antenna alignment clearance
- Separation from sources of electrical noise
- Earthing and surge-protection design requirements
Structural suitability, fastening methods and local installation requirements should be confirmed by the responsible project professionals.
Define enclosure conditions
“Outdoor” does not mean that every component can be installed in any exposed location. Procurement documents should state the required enclosure rating and operating environment rather than assuming compatibility.
Review:
- Maximum and minimum enclosure temperatures
- Direct sunlight and internal heat build-up
- Rain exposure and wind-driven water
- Condensation and humidity
- Dust, insects and cable-entry sealing
- Corrosive or coastal exposure where relevant
- Battery and controller clearances
- Drainage and ventilation requirements
- Locking and tamper resistance
Confirm ratings for the complete installed arrangement, including glands, connectors and unused cable entries—not only the empty cabinet.
Confirm voltage, PoE and data interfaces
A matching connector does not prove electrical compatibility. Build an interface schedule showing the source, destination, voltage, current, polarity, connector, pinout and network standard for every connection.
Check the complete power path
Trace power from the panel through the controller and battery to each load:
- Solar panel output to charge controller
- Controller to battery
- Battery or controller load output to converter
- Converter or PoE source to camera and network equipment
- Any separate DC output used by wireless or recording devices
At each point, confirm:
- Nominal and permitted voltage range
- Maximum expected current
- Cable conductor size and distance
- Connector type and polarity
- Fuse or overcurrent protection
- Voltage drop under peak load
- Startup or inrush demand
- Low-voltage shutdown behaviour
A nominal 12V battery system does not remain at exactly 12V through every charging and discharge state. All connected equipment must tolerate the real operating range or use an appropriate regulated converter.
Do not assume all PoE is interchangeable
PoE can refer to standards-based negotiation or to power applied using a particular passive pinout. These arrangements are not automatically compatible.
The Maxsol POE24V DC-to-PoE converter accepts 12–36V DC and provides an adjustable 12–57V PoE output, Gigabit Ethernet and an LCD voltage display. Its documented continuous load when converting 12V to 48V is no more than 30W.
Those facts alone do not establish IEEE PoE negotiation. Before pairing any converter with a camera, radio or switch, verify:
- Required input voltage at the powered device
- Active IEEE PoE versus passive power
- Output polarity
- Powered pairs and pinout
- Required power at maximum operating state
- Cable length and voltage drop
- Converter continuous output limit
- Ethernet speed and cabling requirements
Incorrect voltage or pinout can damage equipment. Record compatibility in the design schedule rather than relying on connector appearance.
Confirm the data path
For each camera, document whether the connection is copper Ethernet, fibre, Wi-Fi, a point-to-point bridge or mobile backhaul. Confirm port speed, duplex, VLAN requirements, addressing, management access and any protocol needed by the recording platform.
For wireless paths, a pre-installation review should include:
- Clear line of sight and Fresnel-zone considerations
- Path distance and endpoint coordinates
- Antenna height and orientation
- Frequency planning
- Expected interference
- Required usable throughput
- Latency and packet-loss acceptance limits
- Behaviour after a power interruption
- Local recording if the link fails
A link being established is not sufficient evidence that it can carry the intended video reliably.
Set autonomy, recovery and load-priority objectives
Autonomy is the period the system must continue operating when solar input is inadequate. It is a project requirement, not a universal number that can be assigned to every CCTV site.
Define what must remain operational
Agree on the required operating state during low-energy conditions:
- All cameras and backhaul remain active
- Selected priority cameras remain active
- Recording continues while live transmission is reduced
- Infrared or auxiliary lighting is disabled
- The system changes to event-only recording
- Non-essential network equipment is shut down
- A low-energy alert is sent before shutdown
Load prioritisation can reduce the risk of an uncontrolled total shutdown, but only if the power architecture supports separate outputs or managed switching.
Specify recovery behaviour
The system must also recover safely after a low-voltage shutdown. Document:
- Shutdown threshold
- Restart threshold
- Delay before loads are restored
- Load restart sequence
- Whether devices restart automatically
- Whether network settings persist
- Whether recording resumes without intervention
- How repeated on-off cycling will be prevented
If all loads restart simultaneously, startup demand may exceed normal running demand. Measure or verify this behaviour during commissioning.
Compare candidate systems against the load evidence
The Maxsol CS12060 solar power system documents a 120W monocrystalline panel, a 12.8V 60Ah 768Wh LiFePO4 battery, an MPPT controller and three DC12V outputs. These specifications allow comparison against a documented load schedule, but they do not establish a universal CCTV runtime.
Usable operating time depends on the complete load, conversion losses, controller settings, battery operating limits, solar conditions, temperature, cable losses and recovery requirements. Treat this product as an architecture example rather than assuming it forms a tested compatible bundle with a particular camera, converter or wireless bridge.
For an overview of how the components fit together, see the guide to building a solar-powered CCTV system for remote areas.
Plan monitoring, maintenance and physical access
Remote solar CCTV still requires maintenance. The design should make faults visible and allow technicians to reach the equipment safely without dismantling unrelated components.
Decide what will be monitored
Useful monitoring points may include:
- Battery voltage or state information available from the selected controller
- Solar charging status
- Load current
- Low-voltage events
- Controller alarms
- Camera online status
- Recording status
- Wireless link quality
- Network latency and packet loss
- Enclosure temperature
- Door or tamper status
Confirm which values are genuinely available from the selected equipment and how they will be accessed. A system should not be specified as remotely manageable unless its interfaces, software and communications path support the required functions.
Provide practical maintenance access
The panel may require cleaning, vegetation may require trimming, and connectors or batteries may eventually need inspection. Review whether technicians can reach these items with the intended tools and access equipment.
The maintenance plan should state:
- Inspection frequency based on site conditions
- Panel cleaning criteria
- Vegetation-control responsibility
- Battery and terminal inspection method
- Enclosure seal and gland checks
- Camera lens and housing inspection
- Antenna alignment checks
- Firmware and configuration ownership
- Spare fuse, connector and cable requirements
- Fault escalation and site-access procedure
Avoid placing serviceable equipment where opening the enclosure disturbs camera alignment or wireless antenna positioning.
Address security and configuration control
Physical locks alone are not enough. Keep an equipment register containing model identifiers, serial numbers where applicable, network addresses, port assignments and approved configuration backups.
Passwords, remote access and firmware management should follow the organisation’s security procedures. Default credentials should not remain in service, and unnecessary management exposure should be disabled.
Commission with measured energy and network evidence
Commissioning should prove that the installed system matches the approved design. A camera image on a sunny afternoon is not sufficient acceptance evidence.
Measure the power system
Record measurements under known operating conditions, including:
- Panel voltage and current where safely measurable
- Controller charging state
- Battery voltage at rest and under load
- Total load current
- Individual branch loads where practical
- Daytime and night-time consumption
- Voltage at the furthest powered device
- Converter input and output voltage
- Peak load during camera or radio startup
- Low-voltage shutdown and restart behaviour
Compare the results with the design schedule. Investigate unexplained differences rather than simply updating the paperwork to match the installation.
Verify the network and video path
Commission each camera from source to recording destination. Record:
- Link speed and duplex
- Camera availability
- Video resolution and configured frame rate
- Recording and playback operation
- Usable wireless throughput
- Latency, packet loss and link stability
- Remote management access
- Time synchronisation
- Recovery after a controlled power interruption
- Local recording behaviour during backhaul loss
Wireless testing should be performed with the intended alignment, mounting height and channel plan. A short bench test does not represent the final path.
Capture an acceptance baseline
The commissioning pack should include:
- Final equipment and interface schedule
- As-built wiring and network diagram
- Configuration backups
- Photographs of panel orientation and cable entries
- Initial energy measurements
- Initial network measurements
- Alarm tests
- Shutdown and restart test results
- Outstanding risks or deviations
- Maintenance and access instructions
These records provide a baseline for diagnosing later changes such as vegetation growth, panel contamination, battery deterioration, altered camera settings or increased network interference.
Common pre-deployment mistakes
The most frequent design failures begin as undocumented assumptions. Watch for these warning signs:
- Sizing from camera wattage while excluding communications and conversion loads
- Using average solar conditions instead of a defined design period
- Assuming a PoE connector confirms protocol and voltage compatibility
- Selecting a wireless bridge from its distance label alone
- Ignoring night-time infrared or lighting demand
- Treating battery capacity as fully usable energy
- Failing to define recovery after low-voltage shutdown
- Installing an enclosure without checking internal temperature
- Providing remote equipment without remote fault visibility
- Leaving no safe route for cleaning, inspection or replacement
- Accepting the system without measured power and network results
Evidence required before procurement
Procurement can proceed with lower uncertainty when the project team has completed these five evidence groups:
- Load evidence: Datasheets, measured loads, operating schedules and peak states.
- Site evidence: Solar assumptions, shade survey, mounting details and environmental conditions.
- Compatibility evidence: Voltage ranges, PoE protocol, polarity, pinout, ports and data standards.
- Operational evidence: Autonomy, load priorities, recovery rules, monitoring and maintenance responsibilities.
- Acceptance evidence: Defined commissioning measurements and pass/fail criteria.
Any unresolved item should appear in the procurement documents as a condition to be confirmed—not hidden inside a general statement that equipment must be “compatible”.
Final selection step
Use the completed checklist to compare the linked Maxsol architecture examples with the project’s actual requirements. Review the solar system, DC-to-PoE converter and wireless CPE separately against the required port count, measured load, transmission distance, input and output power, environmental conditions and management needs. Do not assume the products are a tested bundle; confirm every interface and document the evidence before installation.
