Outsource Low-Voltage and ICT Design from India: A Guide for US Engineering Firms

Why US firms outsource this work

Low-voltage and ICT packages are a large share of the drawing set on many commercial, healthcare, education and data centre projects, yet they are often the last packages to be finished. Fire alarm, structured cabling, CCTV, access control, audio-visual and building management drawings all depend on the architectural model and the mechanical and electrical coordination. When those inputs move, the ELV drawings move with them.

The pressure usually comes from three places. First, the design team has a fixed number of senior engineers, and a single large project can take up most of them. Second, Revit and BIM production has grown, so a drawing that once took a day in AutoCAD now involves family creation, model coordination and schedule extraction. Third, clients expect more documentation for the same fee, including equipment schedules, bills of quantities and cause-and-effect matrices.

Outsourcing production work to India is one way to add capacity without adding permanent headcount. It works best when the scope is defined in advance, the standards are shared, and the US team keeps control of design decisions. It works poorly when it is used to hand over a design problem that nobody has yet solved.

What can be outsourced

The work that transfers well is production work with clear inputs: drafting and detailing from an approved design basis, model build-out from a template, schedule and quantity extraction, and revision updates from marked-up comments. The table below groups common packages by how well they suit remote production.

Some work sits outside what should be outsourced without a local arrangement. Stamped drawings, code-based performance calculations that require a licensed engineer's judgement, and any document submitted to a building department under a professional's seal fall into this group.

ICT and structured cabling

For structured cabling, the remote team typically prepares telecommunications room layouts, equipment room plans, rack elevations, backbone and horizontal pathway routes, and cable and patch panel schedules. The design basis (cabling category, fibre count, redundancy, and the cabling topology the client requires) must be supplied in writing. The cabling standards that most US projects reference include the ANSI/TIA-568 series for performance and component requirements, ANSI/TIA-569 for pathways and spaces, ANSI/TIA-606 for administration and labelling, and ANSI/TIA-607 for grounding and bonding. BICSI publishes design guidance that many firms use alongside those standards. The adopted National Electrical Code (NFPA 70) edition and local amendments still govern installation.

CCTV, access control and electronic security

Camera layouts are easiest to outsource when the client has already set the coverage objectives, the required pixel density per camera, the lighting conditions and the recording retention period. The remote team can then produce coverage drawings and device schedules from those criteria. Access control work follows the same pattern: the door list, the hardware sets and the reader types are client inputs, and the remote team draws them into the layout and schedules. Security control room layouts and equipment schedules are routine production tasks once the operating model is agreed.

Camera coverage should be checked against the client's actual site risk, not only the drawing. Privacy requirements also vary by state and by workplace, so the client's counsel should confirm the placement of cameras in areas such as restrooms or employee break spaces.

Fire alarm documentation

Fire alarm work is where the line between production and design is most important. In the United States, fire alarm systems are designed and documented under NFPA 72, the National Fire Alarm and Signaling Code, as adopted and amended by the state or local jurisdiction. The authority having jurisdiction (AHJ) reviews and accepts the design. A remote team can draft device layouts, riser diagrams and equipment schedules, but the zoning philosophy, the notification design and the cause-and-effect matrix should come from the engineer responsible for the design. See our NFPA 72 design guide for the design points that the AHJ will check.

Revit, CAD and BIM production

BIM and CAD work is often the largest share of outsourced hours. The requirements that decide whether it goes smoothly are the template, the family library, the naming convention and the level and workset structure. Projects that use ISO 19650 concepts or the National BIM Standard-United States (NBIMS-US) generally define these in a BIM execution plan. The remote team should receive that plan, the client's Revit template and a sample sheet before production starts. Without them, the first few weeks are spent on rework.

Codes, standards and the AHJ

A US project is governed by a stack of requirements, and it helps to separate them clearly.

• Model codes and national standards. NFPA 70 (NEC), NFPA 72, and the ANSI/TIA series are published as national documents. They become enforceable only when a state or local jurisdiction adopts them, often with amendments, and the adopted edition can lag the latest published one.
• State and local adoption. The building department or AHJ determines which edition applies to a given project and which local amendments change it. Confirm this at the start of the job, not after the drawings are issued.
• Industry guidance. BICSI design practice, manufacturer installation requirements and UL listings define how equipment is applied and what documentation a reviewer expects. UL listing confirms product safety testing; it does not confirm that a particular installation meets the code.
• Client design standards. Owners, hospital systems, universities and hyperscale operators often publish their own standards, which can be stricter than the code. These must be supplied and agreed before design starts.
• Cybersecurity and privacy. Networked security systems fall under the NIST Cybersecurity Framework and CISA guidance on device hardening. Surveillance data may be subject to state privacy laws, including the California Consumer Privacy Act where it applies.

Professional responsibility is the point that must be settled in every contract. The engineer of record, licensed in the project's state, is responsible for the design and for any sealed documents. A remote production team does not replace that role, cannot seal drawings in the United States unless it holds the required local licence, and cannot obtain permits or approvals. ASDV Consultant does not claim to provide PE stamping, permitting or statutory approval. Those services need a qualified local professional, and the contract should name who holds each responsibility.

How a remote engagement runs

A reliable remote engagement follows a fixed sequence. Skipping steps is the most common cause of delay.

Deliverables checklist

Before a package is released, the following should be confirmed:

• Revision letter, drawing title block and sheet index match the transmittal.
• Design basis, code edition and AHJ amendments are noted on the relevant sheet or in the design notes.
• Equipment schedules match the drawings for quantities, model numbers and locations.
• Cable, device and door counts reconcile between schedules, BOQ and drawings.
• Model clash check is complete and the clash report is attached for Revit deliverables.
• Xrefs and linked models are current; no unpurged or unresolved references remain.
• Open comments from the previous revision are closed or listed with reasons.

A worked example: a CCTV and access control package

Consider a four-storey office building with a basement car park, a lobby, a ground-floor retail unit and a roof plant area. The architect has issued a coordinated Revit model, and the client has asked the consultant to deliver CCTV coverage drawings, access control riser diagrams and door schedules for the whole building, with a bill of quantities for the security package.

Before any drawing is started, the local team needs four things from the client. The first is a coverage objective for each area, such as face-level recognition at the lobby entrance, vehicle identification at the car park barrier, and general situational awareness across the plant area. The second is the list of doors with their hardware sets, including the locking type, the reader type and whether the door is part of the fire alarm release scheme. The third is the recording and retention requirement, which drives storage calculations. The fourth is the security risk assessment that justifies the coverage choices. The remote team does not create these inputs; it documents them.

Once the inputs are issued, production follows a clear order. The team places camera positions in the model, generates coverage cones or drawn fields of view, and checks each area against the stated objective. Lighting conditions at the car park entrance and the lobby glazing are noted on the drawings because they affect camera selection. Device schedules are then extracted from the model, so the counts on the drawings and in the BOQ come from the same source. Door schedules are drafted from the door list, and any door without a complete hardware set is flagged back to the client rather than assumed.

Two checks typically catch the most errors on a package like this. The first is a reconciliation between the coverage drawings, the device schedule and the BOQ, which should agree on the number of cameras, readers and controllers by floor. The second is a review of the cable routes against the pathway design, because a camera that is correctly placed on the drawing may have no practical route for its cable. The responsible engineer reviews the design decisions, while the remote team verifies that the drawings match those decisions.

The point of the example is that the remote team's output depends on the quality of the inputs. A package with a clear objective list and a complete door schedule can be delivered in a predictable number of review rounds. A package without those inputs tends to generate comments that are really design questions, and those questions cannot be answered by the production team.

Quality control and revision control

Quality control for outsourced production is mostly a matter of making checks visible and repeatable. A checklist that is applied to every release matters more than a general promise of quality. For ELV packages, the internal QA/QC stage should cover at least the following: the drawing standard and title block, the sheet index, the scale and north point, the legend and symbol list against the schedule, the revision cloud and revision table, and the reconciliation of counts across drawings, schedules and the BOQ.

Revision control needs the same discipline. Each issue should carry a revision letter, a date and a short description of what changed. Comments from the client should be logged in a register with a reference to the drawing and the sheet, a status and a response. The register is the basis for deciding whether a comment is within the agreed revision allowance or is a change to scope. Without a register, the two parties often remember the same round of comments differently, and disputes about scope follow.

File naming and folder structure should be agreed before production begins. A simple convention that includes project number, discipline, sheet number, revision and status is usually enough. Project files should be kept in a single shared location with restricted access, and superseded revisions should be archived rather than deleted, so that the history of a design can be traced.

Model-based packages need additional checks. Linked models must be the current versions, and the coordinate and level settings must match the host file. Clash detection should be run against the architectural, structural and mechanical models at each issue, and the clash report should be attached to the transmittal. Families should be loaded from the agreed library, not created locally without review, so that the device data in the schedules stays consistent across projects.

Data handling and cybersecurity during the engagement

Outsourced design files often contain site security information: camera positions, door hardware, control room layouts and network diagrams. For a security system, that information is itself sensitive, and it should be handled as such. The contract should set out who may access the files, where they are stored, how they are transferred, and how they are returned or destroyed at the end of the engagement. Non-disclosure terms should cover the individuals who work on the project, not only the company.

Technical controls should match the sensitivity. Access to project folders should be restricted by named user, with multi-factor authentication where the file system supports it. Files should not be sent by unencrypted email when they contain network addresses, credentials or floor plans of secure areas. Passwords and device credentials for the systems being designed should never be included in drawings or shared in the design files; the drawings should reference where the credentials are held by the client.

The client's own cybersecurity requirements also apply to the design. Networked cameras, access controllers and building management devices are connected equipment, and the design should specify segregated networks, hardened configurations and firmware update processes. The NIST Cybersecurity Framework and CISA guidance on securing networked devices are useful references when writing these requirements into the specification. A design that addresses only the physical installation and not the network configuration leaves a gap that the client's IT and security teams will need to close later.

Choosing a partner

When evaluating an India-based partner, ask for evidence rather than claims. The points that matter most in practice are:

• Relevant experience. Ask for examples of similar packages on comparable projects, with names removed where confidentiality requires it, and for a sample drawing set.
• Software and standards. Confirm the Revit and AutoCAD versions in use and whether the team can work to your template and naming rules.
• QA/QC process. Ask who checks each drawing, what the checklist covers, and how checks are recorded.
• Communication and time zones. India (IST) is 9.5 to 10.5 hours ahead of US Eastern time and 12.5 to 13.5 hours ahead of US Pacific time, depending on daylight saving. Plan review calls in the early morning US time or late afternoon India time, and agree a fixed daily overlap window.
• Data confidentiality. Ask about the file storage system, access control, non-disclosure terms and how project data is removed at the end of the engagement.
• Revision control. Confirm the file naming, revision letters and the number of comment rounds included in the scope.
• Resource continuity. Ask how staff changes are handled and whether named individuals are assigned.
• Sample review. Before committing to a long engagement, run a paid or defined trial on a small package and review the output against your own standard.

Common mistakes

Most failed outsourcing projects share the same few causes.

• Unclear scope. "Design the CCTV" is not a scope. A scope lists the areas, the drawing sheets, the device types and the deliverable format.
• Missing inputs. Drawings that are not coordinated with the architect's latest model produce rework on every revision.
• Undefined CAD and Revit standards. Without a template, each drawing takes longer, and the review cost rises.
• No responsibility matrix. If nobody has agreed who checks the cause-and-effect matrix, it may not be checked at all.
• Missing design criteria. A camera layout without a coverage objective cannot be checked.
• Inadequate QA/QC. A remote team with no internal checking step passes errors to the reviewing engineer.
• Unclear revision limits. Without a stated number of comment rounds, the scope grows silently.
• Unclear local approval responsibility. If nobody is named as the engineer of record for sealing and submission, the drawings cannot be issued for permit.
• Uncontrolled scope changes. Each added floor or system should be issued as a change order with a revised date and fee.

How ASDV Consultant works with US firms

ASDV Consultant is an India-based ELV, ICT and electronic security design consultancy. We provide remote production support to US engineering consultancies, contractors and system integrators. We are not a US-registered engineering firm, and we do not provide PE stamping, sealed drawings, permitting or statutory approvals. Where a US project requires those, we work alongside the local professional named in the contract.

Our services relevant to US projects include:

• ICT and structured cabling design, including telecom room layouts, rack elevations and riser diagrams.
• Electronic security and CCTV design documentation, including camera layouts and device schedules.
• Fire alarm design documentation, drafted from the engineer's design basis.
• Data centre ICT and low-voltage documentation.
• CAD drafting, Revit and BIM modelling, shop drawing production, and BOQ and quantity take-off.

More information about our US service is available on the USA services page, and you can read more about the process on the USA landing page.

Looking for additional ICT, low-voltage or electronic security design support for your US projects? ASDV Consultant provides remote engineering design, CAD, BIM, Revit and technical documentation support from India, helping engineering consultancies and contractors extend their design capacity. Contact us with your package list and target dates.

Frequently asked questions

Can US companies outsource low-voltage design to India?

Yes, production work such as drafting, model build-out, schedules and BOQs can be done remotely under a defined scope. Engineering decisions, code compliance and sealed documents stay with the qualified local professional.

What ICT design work can be outsourced?

Telecom room layouts, rack elevations, riser diagrams, cable pathway drawings, patch panel and cable schedules, and equipment schedules. The cabling performance requirements come from the client's design basis.

Can CCTV and access control layouts be prepared remotely?

Yes. Camera coverage drawings, device schedules, door schedules and access control riser diagrams can be produced remotely once the coverage objectives, door list and hardware sets are provided.

Can fire alarm design documentation be outsourced?

Drafting and documentation can be outsourced. The design basis, zoning philosophy and cause-and-effect matrix should come from the responsible engineer, and the AHJ review follows the adopted edition of NFPA 72.

Can an Indian team support US Revit and BIM projects?

Yes, provided the team receives the client's Revit template, families, naming rules and BIM execution plan, and works from a current architectural model.

How are US codes and project standards addressed?

The design basis lists the adopted codes, the AHJ amendments and any client standards. These are confirmed in writing before production begins and are checked again during QA/QC.

Who is responsible for PE stamping and local approvals?

The engineer of record licensed in the project's state is responsible for sealed documents, permit submission and approvals. ASDV Consultant does not provide those services. The responsibility matrix in the contract should name the responsible person for each deliverable.

How is drawing quality controlled?

Each package goes through an internal QA/QC checklist before release, covering the title block, schedule reconciliation, model clash checks and open comments. Revision letters and comment logs are kept for each round.

Can outsourcing include BOQ and quantity take-off?

Yes. Quantities can be extracted from drawings or models under agreed measurement rules, and the BOQ can be issued in the client's format with change tracking between revisions.

How can a US company start working with ASDV Consultant?

Send your package list, the drawing sheets or model, the design criteria, the target dates and the expected volume through the contact page. We can then discuss a proposed scope, a responsibility matrix and a sample review plan.

Technical references

• NFPA 70, National Electrical Code: nfpa.org
• NFPA 72, National Fire Alarm and Signaling Code: nfpa.org
• International Code Council, adopted model codes: iccsafe.org
• BICSI, telecommunications design guidance: bicsi.org
• NIST Cybersecurity Framework: nist.gov
• CISA, guidance on securing networked devices: cisa.gov
• buildingSMART USA and the National BIM Standard-United States: buildingsmartusa.org

The ANSI/TIA standards are sold by TIA and ANSI, and must be purchased from the publisher. Confirm the current editions and your state's adopted code before design.