A construction site lighting drone proposal should state whether it is offering one larger platform or several compact units, and which work zones that arrangement is intended to serve. Do not choose the architecture by adding advertised coverage areas. First compare the proposed unit count, the scope attached to each unit and the evidence needed for the same project brief.

One large system and several smaller systems are not interchangeable simply because their lamp figures look comparable. The buyer is comparing different equipment arrangements. A useful procurement decision can identify which proposals deserve further assessment without pretending that a product page is a site-lighting design.

Count work zones before counting aircraft

Describe the actual activities requiring support. A single open work area, two separated repair bays and a sequence of tasks performed at different times create different questions for a supplier. The brief should identify those differences before a preferred unit count becomes an assumption shared by every bidder.

Separate simultaneous requirements from sequential ones. Two locations used during the same shift are not necessarily two locations needing light at the same time. Equally, a proposal describing relocation between tasks does not answer a requirement for concurrent support. Record the intended timing as project information, then ask the provider to respond to that information.

This is not a prescription for how many aircraft to operate. It is a way to prevent suppliers from solving different problems while appearing to quote against the same enquiry. Any proposed operating arrangement remains subject to the appropriate technical, site and operational review.

Build two genuinely comparable proposal boundaries

A one-platform proposal should identify the area or sequence of areas it is intended to serve. A multiple-unit proposal should identify the role of each proposed unit and any assumptions about concurrency. Neither should be accepted as a complete answer merely because it names a familiar model and supplies a total price.

For each architecture, distinguish equipment supplied once for the project from equipment supplied for each unit. Do not assume that several aircraft share a controller, power source, tether station or accessory set. Those relationships need to be stated in the actual offer; a unit count alone does not establish them.

Keep these descriptions alongside the same work-zone brief. If one respondent assumes a single clear area while another assumes two separated bays, resolve that difference before comparing their model selections. The first useful comparison is between the problems they propose to solve.

A mixed alternative should be labeled separately. For example, a provider might propose one larger system for a common area and a compact unit for a separated task. That is a third architecture to assess, not a free improvement to either original offer. Give it its own equipment count, timing assumptions and commercial scope so the comparison does not quietly change halfway through evaluation.

Use published model fields as screening information

The current UG2L portable tethered lighting drone description lists a 150W lamp, up to 20,000 lumens and a published 12-meter working height. The current UG6LS lighting and broadcast drone description lists a 1,000W lamp, 120,000 lumens and a published 50-meter working height.

These fields help identify the kinds of product proposals being discussed. They do not establish a common illuminance result, an approved operating height at the site or the electrical input required by the complete packages. A smaller published working-height number is not evidence that a specific indoor or obstructed location is suitable.

UG6LS also publishes a loudspeaker function. If broadcast is not part of the project brief, keep it outside the lighting-architecture score rather than using an unrelated feature to decide the result. If it is required, identify which work zones need that function and request a separate configuration response.

See what lamp arithmetic can and cannot tell you

The following arithmetic is illustrative only. It sums page-published lamp fields; it is not a measured comparison of site performance or total power consumption.

The table does not show that one row replaces another. It does not describe where the light arrives, the relevant work-plane level, shadows, glare or the arrangement of separate areas. Nor does the lamp-rating total include every aircraft, conversion, control or ground-equipment load.

Do not turn these totals into an efficiency ranking or an operating-cost estimate. Their useful role is more modest: they expose exactly which published quantities a comparison is using. If a proposal's conclusion depends on a different quantity, such as task-area illuminance, it needs evidence for that quantity.

Do not add advertised square meters

A multiple-unit offer may look attractive when someone multiplies a page's coverage-area figure by the proposed unit count. That calculation does not establish coverage for the actual arrangement. The same applies when a single large published area is treated as proof that every part of a fragmented site will be adequately illuminated.

The buyer should request a proposal against the defined work zones and the appropriate lighting criteria. Record the configuration and conditions to which any supplied evidence applies. If comparable evidence is unavailable, retain that as an unresolved performance question rather than filling the gap with headline arithmetic.

The existing worksite illumination and aircraft-visibility guide explains separate acceptance outcomes. This article addresses an earlier procurement choice: whether one equipment arrangement or several should be developed for that assessment.

Compare a single-zone and a separated-zone brief

Consider an illustrative buyer evaluating support for one open inspection area. It could request a one-platform proposal and a multiple-unit alternative against the same stated task. The evaluation should ask how each provider defines its arrangement and what evidence supports considering it further. The example does not identify a winning model.

Now consider two separated repair bays that the project says must be supported concurrently. A proposal that assumes moving one unit between the bays has changed the brief. The buyer can either reject that assumption or formally change the timing requirement. It should not compare the revised assumption with a concurrent proposal as though they were equivalent.

A third possibility is a sequence of non-concurrent tasks. Here, the comparison may legitimately include a provider's proposed sequence, subject to review. The key is to state the sequence and its conditions, not to assume a relocation time, staffing level or operating method that no responsible party has confirmed.

Keep unit count separate from staffing and resilience

Several units do not automatically establish a particular staffing requirement, and one platform does not automatically establish a simpler operating arrangement. Request the proposed staffing and responsibilities for the actual equipment and site. Those answers belong in the offer, not in an estimate inferred from the number of aircraft photographs.

Similarly, do not call a multiple-unit proposal redundant unless the supplier defines what service remains available after the specific event the buyer is concerned about. Units assigned to different work zones may have entirely different proposed roles. Their presence alone does not prove that one can replace another.

If continuity is a central contract requirement, keep that question explicit and obtain applicable evidence. If it is not part of the present architecture comparison, omit the resilience claim. Removing an unsupported benefit is better than allowing it to become the deciding reason for an otherwise unverified proposal.

Compare commercial scope without invented savings

Ask each provider to itemize the configuration it is actually quoting, including per-unit equipment and any project-level items. Separate the purchase quantity from optional power provision, demonstration arrangements, support and other services. Unknown costs should remain unconfirmed rather than being entered as zero.

Do not calculate fuel, labor or maintenance savings from the lamp table. Different unit counts can involve different proposed equipment and service boundaries, but the financial consequences require actual quotations and operating assumptions. An architecture comparison should make those assumptions visible without supplying invented values.

For the energy-chain discussion, use the power and duty-cycle planning guide. Keep its whole-system questions separate from the simple lamp-rating arithmetic used here. Neither a smaller lamp nor a larger published duration determines the complete project power plan.

Record why an architecture advances to assessment

The shortlist record should identify the work-zone and timing brief, the proposed equipment count and the reasons the arrangement merits further evaluation. It should also identify unresolved performance and configuration questions. This makes the decision traceable without claiming that a procurement comparison has approved deployment.

The practical lesson is that “one or several” is not answered by a single output total. It is answered by comparing explicitly described proposals against the same task, timing and evidence requirements. This approach also makes a supplier's alternative useful: the buyer can see exactly which part of the brief it changes.

Review the tethered lighting drone collection to identify the actual products under discussion. Send United UAV the number of work zones, whether they are concurrent, the intended lighting outcome and the information needed to compare a one-platform proposal with a multiple-unit alternative.

Contact United UAV about your lighting-drone configuration. Request a configuration-specific response to the same work-zone brief rather than a promise that advertised coverage areas can be added together.