Scribd
Upload
46 views4 pages

SMC

This document provides an overview of the SMC function for operational management of technical services within air traffic control. It describes principles, system architecture, responsibility transfers, configuration management, monitoring and control functions, coordination, reporting, emergency procedures, equipment operation, and routine tasks. The SMC function involves delineating service requirements, interfaces, and tactical responsibilities to define technical and operational structures and ensure reliable system performance.

Uploaded by

Bujamin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
46 views4 pages

SMC

This document provides an overview of the SMC function for operational management of technical services within air traffic control. It describes principles, system architecture, responsibility transfers, configuration management, monitoring and control functions, coordination, reporting, emergency procedures, equipment operation, and routine tasks. The SMC function involves delineating service requirements, interfaces, and tactical responsibilities to define technical and operational structures and ensure reliable system performance.

Uploaded by

Bujamin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

1.

Overview of SMC Function

1.1.1 Principles and Purpose of Operational Management.


The SMC function entails the operational management of technical services within the air
traffic control (ATC) structure. This involves delineating service requirements, interfaces,
and boundaries of tactical responsibility. It includes defining the hierarchy of authority
for both technical and ATC structures. Service requirements is defined in the system
itself and functional needs of the M-NAV. Interfaces are adequate to service provided to
be understandable for users, to have needed functionalities to be able to understand the
status and issue clear commands and control orders. Clear responsibilities are established
in operational manuals of every department at M-NAV.

1.1.2 Technical System Architecture.


The SMC function operates within a technical system architecture comprising
surveillance, communications, navigation, data processing, and facility subsystems.
These include radar stations, communication equipment, navigation aids, data processing
systems, and facility infrastructure such as power supply and environmental control.

1.1.3 Transfer of Responsibility for a Service


This section describes the transfer of operational and technical responsibility for a
service within the SMC function. It includes configuration management and monitoring
access, delineating responsibility transitions effectively. Responsibility of the specific
system is defined within the named department in M-NAV and dependent of the level of
the authorization of the personnel in their ATSEP license, level A or level B.

1.2. System Configuration

1.2.1 Range of Configurations Various configurations, such as equipment or channel


switching and parameter settings, are available within the SMC function to adapt to
operational needs. Every equipment has a specific topology and principles of maintaining
high level of availability, continuity, integrity and precision. SMC personnel should
understand and be able to perform correct action when needed.
1.2.2 Techniques for Configuration Changes General techniques for making
configuration changes, including physical switching methods, are outlined in this section.
SMC personnel should understand specific and unique topology and configuration of
each equipment, physical and logical connections, hardware and software setup and
configuration, standards of external connections and interfaces.
1.2.3 Procedures for Implementing Major System Changes Planned major system
changes require adherence to safety requirements, authorization, coordination,
implementation plans, fallback strategies, and activation of new software versions or
system transfers. M-NAV has procedures for system change management.
Changes to the functional system will require prior approval before implementation and
may be subject to review:
The functional system is defined as 'a combination of procedures, human resources and
equipment including hardware and software organized to perform a function within the
context of Air Traffic Management/Air Navigational Services (ATM/ANS) and other
ATM network functions' and can be broken down as follows:

- changes to the way the components of the functional system are used.
- changes to equipment, either hardware or software.
- changes to roles and responsibilities of operational personnel.
- changes to operating procedures; Supplementary Instructions,
- changes to system configuration, excluding changes during maintenance, repair and
alternative operations that are already part of the accepted operational envelope.
- changes that are necessary as a result of changing circumstances to the operational
context under the managerial control of the provider that can impact the service, e.g.,
provision of service under new conditions.
- changes that are necessary as a result of changing circumstances to the local physical
(operational) environment of the functional system; and

- changes to the working hours and/or shift patterns of key personnel which could impact
on the safe delivery of services.

1.3. Monitoring and Control Functions

1.3.1 Available Monitoring Functions


Monitoring functions include Built-In Test Equipment (BITE), status monitoring,
parameter monitoring, and software/hardware watchdogs. Depending of system
complexity one or more methods are implemented in monitoring functions.
1.3.2 Available Control Functions
Control functions encompass switching, parameter adjustments, and configuration
settings. Controls are dependant of systems specifics and are mainly HMI based. User
access levels are present to protect the system from accidental or intentional wrong
systems control.
1.3.3 Management and Coordination of Maintenance Activities
The importance of SMC in managing and coordinating maintenance activities is
emphasized to ensure the reliability and integrity of systems. Coordination is essential for
SMC for the reason of high level of interconnection between different systems and
working procedures. High level of understanding of working environment is important to
be able to know how and when to remove a system or equipment from operation and how
and when to return to normal operation. Coordination between involved entities should
be maintained at any time.
1.3.4 Analysis Tools
Tools for analyzing possible malfunctions, such as SASS-C, SASS-S, RAPS, Network
monitoring tool, track and noise monitoring tools, are identified as one of the ways to
access correct way to assure correct functioning of the appropriate systems.

1.4. Coordination and Reporting

1.4.1 Necessity of Coordination and Reporting


Coordination and reporting are essential to manage facility interrupts, resolve multiple
outages, comply with legal requirements, and inform relevant parties through NOTAMs,
Occurrence reporting, logbooks and dossiers files. Coordination is defined in CNS/ATM
Technical manual and manuals for the specific departments to which the appropriate
system belongs.

1.5. Emergency Coordination

1.5.1 Situations Requiring Coordination


Emergency situations requiring coordination include communication failures, aircraft
loss, military actions, fires, floods, security threats, and medical emergencies. Complete
list of the situation nad appropriate actions needed to be taken are defined in company
manual.

1.5.2 Parties Involved in Coordination


Parties involved in emergency coordination may include SVN supervisors, SVT
supervisors, management, police, military, medical personnel, and accident investigation
branches KINSIV.
1.5.3 Responsibilities during Emergencies
SMC members have responsibilities during emergencies, which are illustrated and
defined in CNS/ATM Technical manual, Department manuals, SMC manual, Emergency
manual.
1.5.4 Succession of Authorities
A hierarchy of responsibility is established to ensure continuity of operations if
nominated personnel or functions are unavailable. In appropriate Contingency Manual
are defined roles that should be maintained. In Department manuals are definition under
what conditions and at what level of personnel deficiencies should appropriate measures
should be taken. At worse case scenarios and absence of personnel like last measure to
maintain safety, closure of designated FIR space is defined.

1.6. Equipment Operating

1.6.1 HMI Principles and Ergonomics


The Human-Machine Interface (HMI) principles, including permissions, control tokens,
and ergonomic conventions, are defined for the SMC central system and its subordinate
systems. HMI is designed to be visually clear to understand and with additional levels of
menus that enable the responsible personnel with authorization level to access and
monitor, control and change parameters and values of the specific system.
1.6.2 Routine Tasks and Criticality
Routine tasks such as daily, weekly, monthly checks, audio circuit voice checks, ATM
system, audio recording checks, archive media changes, routine checks of the systems,
calibration on ground and flight inspection, power supply measurement, operations are
outlined, emphasizing their criticality and any legal requirements.

This manual serves as a comprehensive guide for ATSEP personnel responsible for the
monitoring and control of air traffic management systems, ensuring safe and efficient
operations.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy