Not every project needs the same level of drafting detail. Aerotas uses optional add-ons to expand a deliverable when a customer needs more drafted information, more specialized treatment of certain features, or a package that aligns to a stricter project requirement.
When add-ons make sense
Add-ons are most useful when the base product is close to correct but not fully aligned with the final deliverable expectation. That can happen on projects with extra feature categories, customer-specific CAD expectations, or a need for more drafting depth in limited parts of the site.
Why it is best to define them early
The best time to specify add-ons is during the quote request, not after production is already underway. Clear scope alignment helps Aerotas price accurately, allocate the right drafting effort, and avoid downstream revision cycles that slow delivery.
Current status: this article explains the role of optional add-ons in the workflow. The exact public-facing add-on matrix from the legacy site still needs to be republished as a follow-up asset.
If you are unsure what to request
Describe the end use of the map, the client standards you need to meet, and any features that matter unusually much on the site. That is usually enough to determine whether the base product is sufficient or whether add-ons should be included in the quote.