> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# WiFi deployment from survey to customer report

> Take an Ekahau predictive survey, provision the access points, validate coverage and throughput in the office, and deliver a before-and-after report the customer's office manager actually understands.

A new customer office moves into a 1,800 m² floor and needs WiFi 6E across the open plan, the meeting rooms, and the warehouse pick area. The MSP runs the Ekahau survey, configures the access points, validates the deployment with iperf and a walk test, and hands over a report the customer signs off on.

## Systems involved

| System                                          | Role                                                   |
| ----------------------------------------------- | ------------------------------------------------------ |
| Ekahau / Hamina                                 | Predictive and validation survey data.                 |
| Aruba Central / Cisco Meraki / UniFi Controller | AP provisioning and live state.                        |
| Studio terminal                                 | SSH to the wireless controller for radio-level config. |
| iperf3 servers                                  | Throughput test from the floor.                        |
| Studio diagrams                                 | Floor plan with AP placement and coverage overlay.     |
| ConnectWise PSA                                 | Project tasks and field tech dispatch.                 |
| Gmail                                           | Customer scoping and sign-off comms.                   |
| Microsoft Teams `#proj-acme-wifi`               | Internal project channel.                              |

## Walkthrough

<Steps>
  <Step title="Import the predictive survey">
    Copilot ingests the Ekahau plan: AP positions, signal targets, channel plan, transmit power, expected throughput per zone. The plan is converted into a Studio diagram with the floor plan as the background.
  </Step>

  <Step title="Pre-stage the controller config">
    Generate the SSID config, the radio profile, the WPA3 RADIUS settings, and the per-AP overrides through the Aruba Central connector. Push the staging config to a test group first.
  </Step>

  <Step title="Field tech deployment day">
    The tech mounts the APs at the planned coordinates. Each AP comes online and registers with the controller. Copilot watches the controller and posts in `#proj-acme-wifi` as each AP joins, with serial number and MAC.
  </Step>

  <Step title="Validation survey">
    The tech walks the floor with the validation survey app. Heatmap data uploads. Copilot compares against the predictive plan and flags any zone where measured signal is more than 6 dB below predicted.
  </Step>

  <Step title="Throughput verification">
    From the warehouse pick stations, run iperf3 against the on-floor server. Copilot captures the per-station results, charts them against the SLA target, and flags the two stations with marginal performance.
  </Step>

  <Step title="Tune the radios">
    SSH into the controller. Copilot suggests transmit power and channel adjustments for the two underperforming APs. Stage the changes, push, re-test.
  </Step>

  <Step title="Customer report">
    Generate a Markdown artifact: floor plan with measured coverage overlay, per-zone signal table, throughput results, two before-and-after images, recommendations for any future expansion. Renders to PDF.
  </Step>

  <Step title="Hand-off">
    Email the report through Gmail to the customer's office manager and IT contact. Post the PDF in the project channel. Mark the PSA project complete with the artifact attached.
  </Step>
</Steps>

## Where Studio earns its keep

* The predictive plan, the validation data, and the controller config sit in one workspace, not three different vendor portals.
* The radio tuning happens against the same diagram the field tech is reading, so the changes are obvious and reversible.
* The customer report shows measured-against-promised, which is the only chart that matters at sign-off.
* The project channel captures the deployment as it happens — the next office for the same customer is a copy-and-tweak of this run.

## Related

<CardGroup cols={2}>
  <Card title="Network diagrams" icon="map" href="../../network-diagrams" arrow="true" cta="Draw it">
    Bring the floor plan in as a diagram background and overlay the AP placements.
  </Card>

  <Card title="Files and artifacts" icon="file" href="../../files-and-artifacts" arrow="true" cta="Deliver">
    Generate the customer-ready PDF inside the workspace.
  </Card>
</CardGroup>