Every remote site is unique. What works perfectly at one location may perform poorly at another just 50 kilometres away. Terrain, weather patterns, existing infrastructure, operational requirements, and dozens of other factors influence which connectivity approach will succeed.
Before selecting technology or signing contracts, a proper site assessment helps ensure you choose solutions that actually work for your specific situation. This guide outlines the key factors to evaluate.
Location and Physical Factors
Geographic Coordinates
Your exact location determines satellite coverage quality. While most satellite services cover all of Australia:
- GEO satellite elevation angles vary with latitude—lower angles in southern regions
- LEO coverage density varies by location
- Some MEO services have optimised coverage in specific regions
Terrain and Obstructions
Satellite connectivity requires clear line-of-sight to the sky:
- Hills and mountains — May block signals from certain directions
- Trees and vegetation — Particularly problematic for LEO which needs wide sky view
- Buildings and structures — May limit installation options
- Open pit mines — Walls can obstruct low-angle signals
LEO constellations require approximately 100° of clear sky view. GEO requires clear line-of-sight to a specific point (typically north for Australian locations).
Existing Infrastructure
What's already on site affects both options and costs:
- Power availability — Mains, generator, solar? Capacity for additional load?
- Mounting structures — Suitable locations for antennas?
- Cabling infrastructure — Conduits, paths for new cables?
- Buildings — Equipment shelter, rack space?
- Existing connectivity — What's currently in place that might be retained or upgraded?
Mobile Coverage
Check whether any mobile coverage exists at your location:
- Even weak 4G signal may enable hybrid solutions
- Consider coverage at different points across the site
- Planned network expansion may change options
Environmental Factors
Weather Patterns
Different weather affects different technologies:
- Heavy rainfall — Causes rain fade on satellite signals, particularly Ka-band
- Cyclones — May damage equipment, cause extended outages
- Extreme heat — Affects electronics, may require cooling
- Dust and sand — Accumulation on equipment, affects cooling
- Snow and ice — Accumulation on antennas, heating may be required
Historical weather data for your location informs technology selection and equipment specification.
Seasonal Variations
Consider year-round conditions:
- Wet season vs dry season rainfall
- Temperature extremes across seasons
- Vegetation changes affecting obstructions
- Flood risk affecting equipment placement
Operational Requirements
Applications and Use Cases
What needs to work over this connectivity?
- Office/IT — Email, web, cloud applications
- Video conferencing — Latency requirements
- OT/SCADA — Reliability requirements, dedicated bandwidth
- Autonomous systems — Real-time control requirements
- Crew welfare — Streaming, personal communications
- Monitoring systems — Data volumes, reporting frequency
Bandwidth Requirements
Estimate based on:
- Number of concurrent users
- Application requirements
- Peak vs average usage patterns
- Growth expectations
Reliability Requirements
What happens when connectivity fails?
- Critical systems that can't tolerate outages
- Regulatory monitoring requirements
- Safety system dependencies
- Financial impact of downtime
This determines whether single-path connectivity is acceptable or multi-path redundancy is required.
Latency Sensitivity
Which applications are latency-sensitive?
- Real-time voice and video
- Remote control applications
- Interactive systems
- Trading or time-sensitive transactions
GEO satellite's 600ms+ latency may preclude some applications.
Timeline and Budget
Deployment Timeline
How quickly does connectivity need to be operational?
- Immediate (days) — Portable solutions, rapid deployment equipment
- Short-term (weeks) — Standard satellite terminals, minimal infrastructure
- Standard (months) — Full site design, infrastructure development
Site Lifecycle
How long will the site operate?
- Temporary (months) — Favour portable, low-commitment solutions
- Medium-term (1-5 years) — Balance upfront investment with operating costs
- Long-term (5+ years) — Infrastructure investment may be justified
Budget Framework
Consider total cost of ownership:
- Capital costs (equipment, installation)
- Operating costs (monthly service fees)
- Maintenance and support costs
- Upgrade path costs
- Downtime costs (factor in reliability differences)
The Assessment Process
Desktop Assessment
Initial evaluation using available information:
- Collect coordinates and site plans
- Check satellite coverage databases
- Review mobile coverage maps
- Gather historical weather data
- Document operational requirements
- Identify preliminary technology options
Site Visit
For significant deployments, physical site inspection:
- Verify sky view and obstructions
- Assess mounting locations
- Evaluate power and infrastructure
- Test existing connectivity if any
- Discuss requirements with site personnel
- Identify any desktop-assessment gaps
Solution Design
Based on assessment findings:
- Recommend technology approach
- Specify equipment requirements
- Develop installation plan
- Estimate costs (capital and operating)
- Define service levels and expectations
- Plan for testing and commissioning
Common Assessment Mistakes
Assuming One Site = All Sites
Organisations with multiple sites sometimes assume what works at one location will work everywhere. Each site deserves individual assessment.
Underestimating Obstructions
Obstructions that seem minor can significantly affect LEO connectivity. Full 100° sky view assessment is important.
Ignoring Seasonal Factors
Assessing during dry season may not reveal wet season issues. Consider year-round conditions.
Focusing Only on Bandwidth
Bandwidth is important but not the only factor. Reliability, latency, and support matter too.
Overlooking Growth
Current requirements are a starting point. Consider how the site might evolve over its lifecycle.
Frequently Asked Questions
Can I do a site assessment myself?
Basic assessment is possible with available tools—coverage maps, weather data, site observation. For complex sites or significant investments, professional assessment ensures nothing is overlooked and recommendations are based on experience with similar deployments.
How long does a site assessment take?
Desktop assessment can be completed in a day or two with good information. Site visits typically require a day plus travel. Complete solution design may take 1-2 weeks depending on complexity.
Does Orion charge for site assessments?
Desktop assessments are typically provided without charge for qualified opportunities. Site visits may incur travel costs depending on location and engagement scope. Detailed engineering design is scoped based on specific requirements.
Request a Site Assessment
Our team has assessed hundreds of remote sites across Australia. We can help you understand your options and recommend solutions that will actually work for your specific location.
Request Assessment