The engineering problem
An interference result is only useful when the team understands what it represents. Frequency relationships, antenna patterns, propagation assumptions and receiver criteria can each change the outcome. Repeating these calculations by hand creates opportunities for inconsistent inputs.
Our engineering approach
We first agree the scope of the analysis and the appropriate engineering models. We then build reusable calculation modules and a scenario runner that retains inputs, model versions and intermediate results. Screening results remain clearly distinguished from detailed engineering conclusions.
What a project can deliver
- Wanted/unwanted calculation workflows
- Parameter sweeps and batch scenario evaluation
- Explicit protection criteria and model assumptions
- Reviewable intermediate results and engineering reports
Start with a repeatable two-system coexistence calculation, then extend to larger station datasets after validation.
What to bring to a first discussion
The systems and frequency ranges being compared, transmitter and receiver parameters, antenna information, the proposed propagation method and the protection criterion. A reference scenario helps establish what the model must reproduce before batch processing begins.
Questions about this service
What is the difference between screening and a detailed interference study?
Screening reduces a large set of potential interactions using agreed assumptions. A detailed study may require additional propagation, terrain, antenna-pattern or operating information. The software should label the level of analysis and expose its limitations rather than present every flagged interaction as confirmed interference.
Can we compare different engineering assumptions?
A scenario runner can vary specified inputs while retaining a common baseline. Each result should preserve the parameters, model version and applicable threshold so engineers can distinguish the effect of a changed assumption from a changed dataset.