What is FTI - all india conference

Present Scenario
• Multiple Network
• Many agencies involved
• Various type of Network
• Overlapping Networks
• Reliability not good
continued
Present Scenario
• Optimum Utilization of resources not possible
• Limited scalability
• No Monitoring of networks at centralized position
• Long implementation period for new circuit
• Security measures do not guard against internal or
external malicious attempts at network access
What is the need for Transition ?
• Single network
• Single agency involved
• All the services with specified SLA
• All type of network under same roof
• Responsibility can be fixed
continued
What is the need for Transition ?
• Cost Considerations
• Optimum utilization of resources
• High speed data transfer
• COTS Hardware and Software
• Real time monitoring of circuits
continued
What is the need for Transition ?
• No Single service provider can meet SLA
requirement (99.999 for GAGAN)
• Effective liaison with reduced number of
dedicated manpower
• Opportunity for gaining experience for future
in house management capability
What is FTI
• The FTI network will place equipment at each AAI
site to support the migration of all existing AAI
communications circuits to the FTI network. This
equipment will provide AAI with dedicated circuit
bandwidth and will multiplex all of the
communications circuit at a site onto bulk
bandwidth communications transport circuits
with required levels of serviceability.
FTI Infrastructure
of AAI
CPE &
Managem
ent Dash
Board
NOCC
SOCC
Media
OFC/VS
AT/Micr
owave
How Transition will take Place?
• In phased manner
• Service provider is supposed to follow the
project time line as provided by AAI
• Build Own Operate (BOO) model to save cost
in Capital Expenditure
• Present resources may be utilized by service
provider
AAI’s Future Plan
• Air Traffic Flow Management ( ATFM)
• VCCS growth/upgrades (VCCS)
• Automated Dependent Surveillance Broadcast
(ADS-B)
• GAGAN
• New RCAG site plan
• New long range RADAR plan
• New Greenfield's airports
• Re sectorization and ACC consolidation
• Mixed use airspace coordination with the IAF
POST FTI SCENARIO
• Achieve a common infrastructure, to meet
operational and mission critical voice, data
and video requirements.
• Obtain the required telecommunications
services at the ordered performance levels.
• Pay commercial prices that can be
optimized over time by the use of price
management mechanisms for future
services.
continued
POST FTI SCENARIO
• Receive centralized, detailed, timely network
management information that can be viewed
anytime by AAI management as well.
• Provide a single source for network status
and service ordering, billing and invoicing
Implement new technologies that can be
quickly introduced.
• Maximize the use of existing commercial
systems in the areas of network management
and business processes.
GLOBAL SCENARIO
• FAA & EUROCONTROL have taken lead for the
establishment of
managed communication
infrastructure .
• FAA managed telecommunication infrastructure is
a single scalable nationwide
communication
network implemented in 12 year span supporting
more than 22,000 services at 4000 locations.
• The pan –European network service(PENS) is an
international communication infrastructure jointly
implemented by Eurocontrol & 38 European air
navigation service providers(ANSP) in order to
meet existing & future air traffic communication
requirements.
Scope of Work
• Exclusion of low volume circuits like VAH (Value
added Hotlines), Dial up Circuits & local hot lines
from scope of work
• RC lines/Media within Airport operational area
shall be considered after stabilization of the FTI
network.
• RC lines/Media outside Airport operational area
are included in scope of work.
Scope of work Continued..
• It should be service provider’s responsibility
to provide HVAC (Heating, Ventilation and
Air-conditioning) equipments in the room
provided to MSP for housing of Network
equipments.
• Service provider should provide cabling up to
AAI’s equipments rather than up to common
service delivery points (SDP).
• Service provider should provide its own
dedicated earthing to connect CPE.
Scope of Work Continued..
• Provide space free of charge for installing
Customer Premises equipments (CPE)
• Provide chargeable space if required for
logistics support such as deployment of
manpower, stores depot etc as per AAI’s
Commercial policy
• Provide metered raw AC essential power
supply to energize service provider’s
equipments.
Recommended SLA’s
Serviceability Un/Availability serviceability
time allowed
per month
99.999%
27 Sec
Services
/Applications
99.99%
<4 min
99.9%
<44min
Radar Data,
RCAG, ATFM ,
ADS-B
AMSS & DSC
Gagan
FTI network Implementation Estimated
Timelines
• The FTI network implementation timeline begins at
contract signing. A timeline of activities in order
includes:
• Procurement and outfitting of facilities
• Procurement and build of NOCC/SOCC systems
• Beginning
Engineering
of
site
and
telecommunications
• NOCC/SOCC facility completed and staffed
• Beginning site and service installations
• Site and service cutover from AAI to FTI network
Cost recovery/Revenue model
While this new system will provide
required SLA & necessary provisions for
our future needs of operational growth
& global harmonization issues, it will also
ensure reasonable source of revenue to
offset the expenditure incurred in this
project by allowing other aviation
entities to share data & connectivity
without compromising security of our
network.
Cost recovery/Revenue model Contd.
Besides the above, since all the surveillance data pertaining
to radar, ADS-B etc from different area control/locations can
be made available in the FTI cloud along with VHF
communication Air/Ground data, with appropriate
agreement and suitable contract formality we will be in a
position to work with the neighboring ANSPs and develop
more efficient RNP routes in our Sub-Region. (e.g. ADS-B
data of Coco island (Myanmar) and Port blair).
This arrangement will enhance safety, less fuel consumption
thereby reducing carbon emission and more RNFC to AAI
Proposed System Design
Initial model will be a mix of MPLS
cloud & existing point to point links
(MLLN) however the MSP will be
authorized to have freedom to
rework & go for fresh contract for
existing MLLN circuits to meet the
AAI’s SLA requirement.
Layer 3 VPN VS Layer 2 VPN
•
•
•
•
•
•
Customer packets are routed across The Customer Frames are switched over the
Service provider Edge routers
Service provider backbone
Service provider backbone
Layer 2 Service Provided by Service
provider which offers better flexibility provider
for management
Fully resilient services with auto
No resiliency can be offered as in layer 2
switchover can be offered like
circuit service provider do not have the
dual last mile , dual
flexibility
router , and dual POP.
Managed and Unmanaged CPE options No proactive monitoring can be offered as
with proactive monitoring so that if a we just providing a layer two service ,
link goes down can be detected
anytime a circuit goes down customer
automatically
needs to reactively log a compliant
Hub and Spoke and Full Mesh
Point to point and Hub and spoke
connectivity options available
connectivity options are available.
Service Provider provides the IP
Service provider does not provide IP
address
address
Proposed System Design contd.
The MSP will provide Dedicated Network
Operations Control Centre (NOCC) & Security
Operations Control centre (SOCC) enabling
dynamic management of Bandwidth having
redundant multilayer media connectivity. By
the provisioning of NOCC/SOCC, effective SLA
monitoring & security of data can be
ascertained.
Proposed System Design Contd.
The system will be technology and protocol
transparent, providing integration and
interpretation of data pertaining to divergent
systems. The contract period under this
model would be for 15 years, however the
same can be extended on mutually agreed
conditions. The requirement of technology
refresh will be assessed & reviewed at every
5 years.
Proposed System Design Contd.
The above assessment entails a
suitable
arrangement
of
providing end user equipments
like router, multiplexers and
switches etc. of appropriate
capacity & redundancy to cover
our future bandwidth needs.
Transition to new system
• Build Own Operate (BOO) model
• Transition in phased manner
• Service provider is supposed to follow the project time line as
provided by AAI
• Present telecom infrastructure is to remain in operational
readiness and to be utilized by service provider in the event of any
failure of the new FTI system for sustaining uninterrupted
operations.
• Further, MSP may also include some part of the existing Telecom
infrastructure in their network for locations not covered by
POP(Point of Presence) of their Telecom media provider.
• Remaining telecom media will be surrendered once the reliability
and the stability of new FTI system is ascertained.
Tendering Model
• Average budgetary cost of the project will be
about 52 Crores per annum .Expenditure on
this account/project will be under OPEX
instead of traditional CAPEX.
• Global tender route
• Quality and Cost-Based Selection(QCBS) to
ensure only competent eligible with proven
track record bid
Secured Internet Gateway
• The SOCC shall have the capability to
manage encryption for AAI authorized
Users accessing network resources from
outside of the network, or using the
public internet to access network
resource through a secure network
gateway
Intrusion Prevention System
• Intrusion prevention systems (IPS), also
known as intrusion detection and
prevention systems (IDPS), are network
security
appliances that monitor
network and/or system activities for
malicious activity. The main functions of
intrusion prevention systems are to
identify
malicious
activity,
log
information about this activity, attempt
to block/stop it, and report it.
continued
• Intrusion prevention systems are
considered extensions of intrusion
detection system because they both
monitor network traffic and/or system
activities for malicious activity. The main
differences
are,
unlike
intrusion
detection systems, intrusion prevention
systems are placed in-line and are able
to actively prevent/block intrusions that
are detected.
Common regional VPN for Asia
Pacific Region
• In line with the PENS (Pan European
Network), a decision was taken in
APANPIRG/24 to establish a taskforce
consisting of subject matter expert to
study Common Regional Virtual Private
Network (CRVPN) for Asia Pacific Region.
India is also participating actively in this
study as one of the members because it
is on similar lines of FTI.
Continued
• This task force will report the outcome of
this study to APANPIRG/25 through
Aeronautical Communication Services
Implementation Co-ordination Group
(ACSICG) and CNS Sub Group of APANPIRG.
If decided favourably, all the point to point
communication links working within
different countries in Asia Pacific region
shall be connected with each other in
cloud environment. This would also pave a
way for implementation of SWIM under
the block B1 of ASBU.

Download Report