ACOUSTIC DETECTION · BUYER & TECHNICAL GUIDES / 621
Acoustic drone detection project: Handling a Building Expansion as a New Scope Request
An acoustic drone detection project does not automatically become a larger purchased system merely because the facility portfolio grows. A building expansion should be described as a new scope request against the original baseline: identify what is genuinely added, what remains delivered, and what existing material must be reviewed because the facility information has changed.
KEY TAKEAWAY
Acoustic drone detection project scope starts with the original baseline
Use the accepted order, configuration, interface list, account model, documentation set and acceptance basis as the comparison point. Then separate new buildings, new users, new interfaces, revised site information and retained deliverables. This lets a supplier quote additions without silently reopening unchanged parts of the first purchase.
01
Start with the delivered baseline, not the new floor plan
The first task is to establish what the original purchase actually delivered.
A larger site changes the customer need, but it does not by itself amend an order. Gather the accepted quotation, statement of work, configuration record, licence or account description, interface schedule, drawings supplied for review, training or handover record, and acceptance documents. Mark each item as delivered, pending, excluded, customer-supplied or dependent on another party.
This comparison prevents a common mistake: treating a new building as proof that every quantity, user role and integration obligation should be recalculated. Change-control guidance from the UK Government Project Delivery Function describes a baseline as something protected through structured assessment. The same discipline is useful in ordinary commercial purchasing, even when the project is much smaller.
Use a scope ledger
Create one line for each deliverable rather than one vague line for the whole system. For example, an existing acoustic module, processing software version, event interface, administrator account, user guide and acceptance test may each have a different status. A new building can add work to some lines while leaving others unchanged.
Record the evidence for each status. A signed acceptance record may show that the original interface was delivered; a supplier email may only show that a future option was discussed. Do not turn exploratory language into an entitlement without an approved commercial or technical document.
Separate quantity from entitlement
The expansion may require additional sensing hardware, but the same question cannot be assumed for software users, sites, accounts, support or documentation. A quantity increase is a purchasing decision. An entitlement is a permission or service boundary. Treat both as explicit lines in the request.
02
Describe the new building as a defined addition
A useful request states what has changed about the customer estate and what outcome the added work must support.
Name the added building or facility area, its project status, responsible owner and relationship to the originally purchased site. Explain whether the request is for a separate building, an extension of the existing facility or a shared administrative estate. This distinction affects asset records, site labels, documentation and potentially the commercial basis of software access.
Avoid using a broad phrase such as “cover the whole campus” as the deliverable. Instead, ask the supplier to identify the proposed additions, dependencies and exclusions. Acoustic information is influenced by environmental context, and research reviews identify background noise and multiple-source conditions as continuing technical challenges. The expansion request should therefore ask for a project review, not promise an inherited result for a different facility.
New users are a separate workstream
Operations, facilities, security, IT and maintenance teams may need different access roles. List the new groups, approximate user categories, approval owner and whether they need viewing, administration, reporting or support access. Do not assume that adding a building automatically adds named users or changes the original account model.
Ask whether the requested accounts are included in an existing customer arrangement, require a revised licence, or need a separate tenant, site or role structure. The supplier should answer from the governing documents rather than from a generic product label.
Keep facility facts reviewable
Provide only the facility information needed for the supplier’s assessment, such as updated building identifiers, responsible contacts, relevant environmental description and approved interface owners. Mark preliminary drawings and assumptions clearly. A changed building name, boundary or responsible organization can make old manuals and acceptance records misleading even when the purchased module itself is unchanged.
03
In an acoustic drone detection project, list additional interfaces separately
An added building often creates more information-handling work, not just more equipment.
New interfaces may include a facilities dashboard, identity service, network segment, event-management application, reporting destination or maintenance workflow. List each requested connection separately, identify its owner and state whether it is new, reused or merely being reviewed. New Ark’s public PCBA delivery description likewise treats power, networking, alerting, management platforms, software protocols and documentation as matters for a defined project boundary.
Do not describe a proposed interface as already supported because the original purchase connected to a similar system. Similar names can conceal different authentication, message fields, data permissions, retention rules or acceptance responsibilities. A request should ask for an interface assessment and a quotation for any new mapping, development, testing or documentation.
Make reuse visible
For an unchanged integration, say “retain existing interface” and identify the version or document that governs it. For an extension, say which endpoint, user group or facility label is being added. For a replacement, explain why the original interface cannot be reused. These three statements prevent a supplier from pricing the whole integration again or from assuming that a new connection is free.
The request should also identify customer responsibilities. The customer may provide network access, identity administration, test data, application credentials or an approved test window. Those prerequisites are part of scope clarity, not promises that a supplier can satisfy them without customer participation.
Keep detection meaning bounded
An acoustic event, a classification result and a confirmed aircraft identity are not interchangeable. If the new interface displays results in another application, name the fields and states that must be carried over without turning an information feed into an operational response instruction. The request should preserve uncertainty and unavailable states where the original design includes them.
04
Review reused project materials against changed facility information
Reusing documents saves effort only when their assumptions still describe the expanded project.
Make a document-impact list. It may include the site description, asset register, network or interface diagram, user-role matrix, operating notes, training slides, test cases, acceptance record and support contacts. Mark each as retain, revise, replace or not applicable. This is more precise than asking a supplier to “update all documents.”
A document can remain technically correct and still be commercially or operationally misleading. For example, an old diagram may show the original building name, an old escalation contact or a single-site assumption. The supplier should quote revisions that result from the new building while retaining unchanged material as an identified baseline.
Ask for a change impact statement
The statement should identify affected configuration items, assumptions, dependencies, acceptance evidence and customer approvals. It should also state what was assessed and found unchanged. Government change-control guidance recommends recording the description, impact, related risks and status of a request; that compact record works well for a facilities expansion review.
Use statuses such as requested, assessed, approved, deferred, implemented and closed. These labels do not replace the contract, but they show whether a proposed building addition is still an idea, an agreed scope item or a completed deliverable.
Do not inherit old suitability claims
The original facility’s noise, weather exposure, structures and surrounding activity may not represent the added building. A qualitative review can identify what must be reassessed without promising a detection range, accuracy or coverage outcome. Passive listening is not proof of site safety, certification or permission to install in a hazardous area; those matters remain for the authorized project team to confirm.
05
Ask the supplier to quote additions and retained items separately
A transparent quote makes the expansion decision easier to approve and easier to audit later.
Request at least two views in the quotation. The first is the new scope: additional hardware or modules, new accounts or roles, new interfaces, revised documents, project review, testing and any customer training. The second is retained scope: the original items that remain valid and are not being repurchased. If an existing item needs a compatibility review but not replacement, show that review as its own line.
This structure avoids two opposite errors. The supplier should not silently include the entire original purchase again, and the buyer should not assume that every original deliverable extends at no cost to a materially different facility. Pricing, licensing, support, schedule and acceptance assumptions should be attached to the relevant line rather than hidden in a single expansion total.
Request options without invented certainty
Where there are legitimate alternatives, ask for clearly named options such as “new-building addition with retained original integration” and “new-building addition with revised shared interface.” Ask the supplier to state prerequisites, exclusions and recurring implications for each option. Do not ask for a headline promise before the site facts and commercial documents have been reviewed.
Tie acceptance to deliverables
For every new line, define the evidence of completion: delivered module list, account confirmation, interface document, revised drawing, test record, training record or approved change log. Acceptance should show what was added and what was intentionally retained. It should not imply that a new document alone proves a performance outcome.
06
Close the request without reopening unchanged purchase scope
The final change record should be narrow enough to govern the expansion and clear enough to preserve the original agreement.
Write the request as an amendment or change order to the identified baseline. Include the reason for expansion, affected facilities, new deliverables, retained deliverables, exclusions, customer prerequisites, review owners, acceptance evidence and the decision status. If the supplier identifies an issue in the original scope, record that issue separately rather than disguising it as a building addition.
Once approved, update the configuration and document registers only for the affected items. Keep the original purchase reference visible, and assign the expansion its own revision or change identifier. This preserves traceability for future maintenance, repeat purchasing and a later building phase.
Use a simple decision sentence
A useful approval can say: “Approve the listed additions for Building B; retain the original Building A deliverables and interfaces; review the named documents for changed facility information; exclude unlisted buildings, users and integrations.” The sentence is not a substitute for the detailed attachment, but it prevents a broad approval from being read as a blank cheque.
Keep future phases independent
If another building may be added later, describe it as a possible future phase rather than an assumed quantity. A supplier can then explain which design or account decisions are genuinely reusable without treating an unapproved phase as purchased work.
QUESTIONS FOR YOUR PROJECT
Buyer checklist for a building-expansion change request
- Which original quotation, configuration, interface schedule and acceptance record define the baseline?
- Which buildings, areas, user groups and account roles are genuinely new?
- Which existing modules, interfaces, licences and documents are being retained unchanged?
- Which additional interfaces need assessment, mapping, development, testing or documentation?
- Which facility facts, drawings, contacts or environmental assumptions must be reviewed?
- What customer prerequisites and approvals are required before the supplier can perform the new work?
- What evidence will show completion for each added deliverable, and what is explicitly excluded?
- Does the quotation show new scope, retained scope and any compatibility review as separate lines?
REFERENCES
Sources for this article
Publisher names, dates and relevant contributions are listed below. Confirm offered product details with the supplier.
UK Government Project Delivery Function, The Teal Book: Chapter 22: Change control · Published 29 July 2024; last modified 1 July 2026
Supports using a baseline, impact assessment, change register, decision status and traceability when evaluating additions to approved project scope.
New Ark, Acoustic Detection PCBA & Array Integration · Accessed 2026-11-20
Supports describing acoustic modules, interfaces, software protocols, documentation, environmental fit and support responsibilities as project-scoped matters subject to written agreement.
Kang et al., AIP Advances, From classical approaches to recent advancements: A holistic review of acoustic detection for unmanned aerial vehicles · Published 2 December 2025
Supports the qualitative point that acoustic detection research addresses signal acquisition, recognition and localization while continuing to face background-noise, multiple-target and application challenges.
ARTICLE FAQ / 621
Questions on Acoustic drone detection project: Handling a Building Expansion as a New Scope Request
Practical questions about this article and the proposed product scope.
RECORDACOUSTIC DETECTION LIBRARY
TALK TO NEW ARK
Turn the expansion into a reviewable scope
New Ark can discuss a project-scoped acoustic core, interface boundary and documentation path for an added facility. Bring the original configuration, the new-building facts and the requested deliverable split so the next discussion can distinguish additions from retained work.

