Sites and physical conditions
Buildings, materials, layouts, outdoor areas, movement paths, obstructions, power, cabling, and access constraints.
Stage 01 · Define the outcome
Discover what the wireless environment must actually do.
Before architecture or product selection, Nettelix establishes the sites, users, devices, workflows, constraints, risks, and measurable results that define success.
Requirement ledBegin with the work, not a product list.
Site awareAccount for physical and carrier conditions early.
MeasurableDefine evidence before implementation begins.
What discovery resolves
Turn an unclear wireless problem into a shared definition of success.
The discovery principle
A complaint such as “coverage is bad” is not yet a requirement. Discovery identifies who is affected, where, during which workflow, on what device, against which dependency, and what acceptable performance looks like.
Who and what connects
Employees, guests, contractors, scanners, phones, cameras, vehicles, sensors, gateways, and operational equipment.
What the connection carries
Voice, collaboration, transactions, telemetry, video, automation, life-safety communication, and management access.
Where sessions must persist
Roaming routes, indoor-to-outdoor transitions, vehicle movement, handoff sensitivity, and coverage boundaries.
What failure changes
Lost productivity, halted operations, poor customer experience, safety exposure, support load, and business continuity.
How success will be proven
Coverage, capacity, roaming, application, carrier, failover, documentation, and operating acceptance criteria.
Discovery outputs
Design starts with evidence, not assumptions.
The stage closes when stakeholders agree on the baseline, priorities, dependencies, risks, and definition of done.
Requirements briefUsers, devices, applications, mobility, locations, and business outcomes.
Site baselineExisting technology, RF and carrier conditions, dependencies, and constraints.
Stakeholder mapIT, security, facilities, operations, carriers, vendors, and decision owners.
Risk registerUnknowns, blockers, lead times, operational exposure, and assumptions to prove.
Priority sequenceSites, workflows, pilots, quick wins, dependencies, and program phases.
Success criteriaSpecific acceptance evidence tied to the original operating requirement.
The handoff to Design
Discovery gives engineering a target—not a guess.
Known requirementThe design team understands the business and technical outcome.
Known environmentPhysical, carrier, security, and operational conditions are visible.
Known constraintsDependencies, risks, timing, access, and ownership are documented.
Known proofAcceptance can be engineered into the plan from the beginning.
Define the right wireless problem first.
Bring us the sites, workflows, devices, and symptoms. We will help turn them into an actionable requirement.