Most ELV problems on Kuwait projects are not caused by the ELV design itself. They appear when a camera, speaker or access reader is drawn on a ceiling plan that the MEP team later changes, or when a containment route is agreed on one drawing and blocked on another. Early interdisciplinary coordination costs far less than fixing these clashes on site.
Who needs to agree what
ELV and ICT systems touch almost every other discipline. The table below summarises the main interfaces. The right column is the decision that usually gets missed.
| Discipline | What ELV/ICT needs from them | Decision to record early |
|---|---|---|
| Architectural | Ceiling heights and grid, wall finishes, device mounting zones, room layouts, risers | Which ceiling type is used, and where do device positions fall on it? |
| Electrical | Power for ELV panels, UPS, earthing, separation from data cables | Which circuits feed each ELV panel, and where are the separation routes? |
| Mechanical (HVAC) | Clearances at ductwork, air-diffuser positions, cooling for comms rooms | Are smoke detectors and sensors clear of diffusers and grilles? |
| Plumbing and fire protection | Clearances at pipework and sprinkler heads | Are sprinkler heads and pipe routes coordinated with detector and speaker positions? |
| Fire and life safety | Detector and sounder layout, zoning, voice evacuation coverage | Who owns the fire alarm design, and where does ELV hand over to it? |
| IT or client operator | Network equipment, port counts, access network requirements | What is the network topology and the equipment list? |
Ceiling coordination and device placement
The ceiling is where most device clashes occur. Cameras, speakers, detectors, access-control readers and Wi-Fi access points all compete for the same grid tiles and the same space above them. Three practical steps help:
- Use a reflected ceiling plan for every ELV device. Plot devices on the RCP, not only on the floor plan, so the ceiling grid and the lighting positions are visible.
- Check the access space above the ceiling. Devices that need servicing, such as access points and some sensors, need a route and a maintenance clearance.
- Agree the mounting height of wall devices. Readers, call points and intercom units have heights set by the architect and the accessibility requirements. Record them on the elevations.
Cable containment and pathways
Containment is the second major source of clashes. A workable approach is to coordinate in layers. Main risers and cable trays are set first, because they are hardest to move. Horizontal distribution follows, and branch drops to devices come last. Each layer is checked against ductwork, pipework and lighting before it is locked.
Keep low-voltage data and signal cables separate from power cables according to the applicable standard and the project specification. Where they cross, record the crossing and the separation method on the containment drawings. Do not rely on a verbal agreement that cables "will be kept apart on site".
Equipment-room planning
Equipment rooms for ELV and ICT systems, including comms rooms, security control rooms and the main equipment room, are often drawn at the end of the design, when space is already short. Agree their size, power, cooling, access and door position at the start of the architectural layout. Check that the room does not sit under water-carrying pipework and that the containment can reach it from every riser. The hot-climate constraints for these rooms are covered in our Kuwait hot-climate ELV article.
Drawing interfaces and design-stage reviews
Coordination works best when each design stage has a defined review. A simple structure:
- Concept: agree the systems list, the riser strategy, the equipment room locations and the main interfaces with the fire alarm and BMS.
- Design development: review device layouts on the RCP and elevations, and check containment against the MEP model.
- Tender or construction information: issue a clash-free set of drawings for the areas that are fixed, and record open items.
- Construction: review any site changes to devices or containment, and update the drawings through a controlled revision process.
Where a BIM model is used, the same checks run in the coordination model. Confirm the model scope, file exchange format and clash-check frequency with the project BIM execution plan. Do not assume that a clash check by one team covers the interfaces of another.
Common coordination problems
- Devices drawn on the floor plan only. They end up over a light fitting or a diffuser once the ceiling is set.
- Containment routed before the riser is fixed. Routes then have to be redrawn, and the cable schedule no longer matches the drawings.
- Fire alarm and ELV drawings showing different device positions. Use one source for device positions, referenced by both.
- Access-control reader heights that differ between elevation and layout drawings. Record the mounting height once and check it on every drawing.
- Equipment rooms with no cooling or power plan. The equipment fails or is never installed as designed.
Design review checklist
Use this at each design review. It does not replace the project's own quality process.
- Every ELV device appears on the RCP and the relevant elevation, with the same position and height.
- Containment routes are checked against ductwork, pipework, lighting and sprinkler routes.
- Separation between power and data cables is recorded where routes cross or run in parallel.
- Equipment-room size, power, cooling and access are agreed with the architect and the MEP engineer.
- The fire alarm and ELV interfaces are assigned to named designers.
- All open items are logged, with an owner and a date.
Benefits of early interdisciplinary coordination
Coordinating early reduces redrawing, shortens the time spent resolving site queries, and gives the client a clearer picture of cost and programme before construction starts. It also makes handover easier, because the drawings match the installed systems. These are the usual outcomes; the actual effect depends on the project and the team, and no specific saving can be promised in advance.
Guidance for consultants, developers and contractors
Consultants should bring their device layouts to the coordination meetings, not only their concept diagrams. Developers should appoint a coordinating lead who can resolve conflicts between disciplines. Contractors should receive drawings that show the agreed positions and the open items, not only the ones that are settled.
Conclusion
ELV and ICT coordination is mainly about the ceiling, the containment and the equipment rooms. Agree those three early, record the decisions on the drawings, and most of the common clashes never reach site.
Looking for ELV and ICT design coordination, BIM support or outsourced engineering design support for your project in Kuwait? Contact ASDV Consultant to discuss your project scope, deliverables and technical requirements. For the wider ELV scope, see our ELV design consultancy service.
Frequently asked questions
Who should lead ELV and MEP coordination on a Kuwait project?
Usually the main design consultant or the project's coordination lead. ASDV Consultant can support the ELV and ICT part of the coordination within the scope agreed with the client.
Should ELV devices be shown on the floor plan or the ceiling plan?
Both. Floor plans show the position on the floor. Reflected ceiling plans show the position relative to the ceiling grid and lighting, which is where most clashes occur.
When should coordination start?
At concept stage, when the riser strategy and equipment room locations are still open. Waiting until construction drawings leaves few options.