About Frequentis
In the past few years FREQUENTIS has developed from a small Austrian-based
company into a mid-sized company group with subsidiaries all over the world
- you may find us in Germany, the Czech Republic, Slovakia, the United Kingdom,
Canada and the USA.
Additionally, regional offices have been founded to keep close contact to
the customers on site. Together with joint ventures and strategic partnerships
they form the basis for a world-wide customer-oriented know-how network.
An average growth rate of more than 30% per year shows that the customers
appreciate the efforts taken by FREQUENTIS.
Subsystem Common Services
The Common Services Subsystem provides utilities used by - as you might guess
by the name -several other subsystems. Visible to the user, these are mainly:
EAD-Explorer
The EAD-Explorer is the first Front-End application you see when you enter
the world of EAD. It provides a Single-Sign-On (one log-on for all) for the
different EAD subsystems. It provides a centralized and integrated access
to all EAD applications and abolishes the heterogeneous subsystem structure.
Legal Recording
All changes in the system's database are logged for legal proof - this is
what is meant by legal recording. This logging is done by every subsystem.
Common Services provides a common centralised deposit for this logging procedures
and provides tools for investigating this deposit. You will be able to track
any data changes down to a user, authority, time slot within an EAD application
or throughout different applications.
International NOTAM Operations (Frequentis)
About Frequentis
See description Common Services
Subsystem INO
The INO (International NOTAM Operation) provides facilities for creating,
processing, checking, distributing and retrieving international NOTAM and
other relevant message data to be handled by EAD. The INO receives requests
related to International NOTAM Operation, processes them and returns replies
to clients. The INO provides the following functionality:
Message Creation
Message Creation comprises functions to create, edit, store or delete messages.
The following messages are supported:
- NOTAM,
- SNOWTAM,
- ASHTAM,
- BIRDTAM,
- AFTN Freetext.
Messages are created by using the content of the SDO database. The system
verifies the messages against a pre-defined set of rules and the SDO database.
In case of an error, the system will react by the appropriate error handling.
If no error occurs, the message will be stored, distributed, and made available
for Retrieval.
INO Message Processing
INO Message Processing receives different types of messages. The system verifies
the format against a pre-defined set of rules and the SDO database. In case
of an error, the system reacts by the appropriate error handling. An erroneous
message is either stored in a queue for manual processing or rejected and
sent back to the message originator. Whether an erroneous message is stored
in the message queue or not depends on the message type and the system configuration.
PIB and Message Retrieval
PIB and Message Retrieval comprise different report generator modules to retrieve
NOTAM and to format Pre-flight Information Bulletins, NOTAM summaries, and
other NOTAM Retrieval products. To reduce the amount of information that must
be typed in again and again in case of frequently used inquiries, the EAD
staff maintains predetermined profiles. The following kinds of PIB are provided:
Aerodrome PIB, Area PIB including special Area PIB, Route PIB, Narrow Route
PIB.
Basic Data Maintenance
Basic Data Maintenance comprises various functions used to add new NOTAM related
operational data and to read, update or delete existing operational data (Distribution
Lists, System Parameters, NOF Profiles, NOTAM Selection Criteria, NOTAM Code);
INO Client Interface Support for ESI
The INO supports a data interface for ESI. Via the ESI an External Client
System can subscribe and unsubscribe to NOTAM distribution. Furthermore, the
NOTAM data itself is distributed via the ESI. Additionally, Message Creation,
PIB and Message Retrieval are provided via ESI.
Use of COTS Products
The INO Data Provider implementation is based on ORACLE Forms and ORACLE database
technology.
The INO Data User and Public User are based on state-of-the-art Java Web-Technology.