Software Features

We'll now look at all the features of the software in more detail. In order to highlight the various options, tools, and views available we'll make use the sample data that is provided with the software. This data is based upon the scenario of a spectrum manager who is responsible for two Fixed Satellite Service (FSS) GSO satellite networks:

• IMPROSAT, located at 134${}^{\circ }$E

• TSLSAT, located at 130${}^{\circ }$E

In this document, and in the software, these will be referred to as My Networks.

Scenario

Both of these satellites are currently under coordination and have not been brought into use. Bi-weekly, the spectrum manager must check that other systems (notified to the BR and then distributed via IFIC) would not present issues:

• either by being likely to cause unacceptable interference into the spectrum manager's networks

• or by being likely to suffer unacceptable interference from the spectrum manager's networks

A key aspect in assessing what should be done in these situations is to know which network (the spectrum manager's or those in the IFIC) has regulatory priority. This is typically based upon which network was filed first. This is far from a clear cut decision because, while the original submission might have priority, modifications could have been made at a later stage. In this situation some beams (or IFIC Groups) will have priority while others don't. One powerful aspect of Visualyse GSO V3 that will be demonstrated is the ability to deal with Regulatory Priority and the automatic detection of cases where coordination may be needed.

In addition Visualyse GSO V3 could be used for other tasks involved in GSO satellite spectrum management, for example:

• During design phase, to check the complexity of coordination and hence feasibility of a proposed new system, including searching the GSO arc for suitable locations

• When submitting Advance Publication Information (API), to determine which administrations are likely to indicate they have an interest in protecting their system

• When submitting Coordination Requests (CR), to determine which administrations for which coordination will be required

• To check other systems during the API or CR phase, to ensure they will not cause an interference problem, and that any necessary regulatory steps are made to register interests where required

• When Detailed Coordination is required, to perform the analysis based upon C/I calculations, including tools to show the impact of varying specific system parameters in the ability to share, and where each system has priority.

Demo Version Limitations

If you're using the demo version of the software then please be aware that this is subject to the following restrictions:

• While you can edit or redefine you own network assets, these changes cannot be saved

• You are limited to the use of the demonstration data provided for your networks. However, you can use any IFIC or the SRS database.

• You will not be able to save or print.

• You will not have access to certain additional features such as the Priority Map tool.

Apart from these limitations, the demo version shows as much as possible of the complete program. If you have any further questions please do not hesitate to contact us (info@transfinite.com).

Sample Data

Please note that the satellite antenna gains in the supplied demonstration networks and sample IFIC are un-realistic. This results in many DT/T levels being much lower than worst case analysis would indicate.