37

Present Scenario - Webs

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Present Scenario - Webs
Page 2: Present Scenario - Webs
Page 3: Present Scenario - Webs

Present Scenario• Multiple Network

• Many agencies involved

• Various type of Network

• Overlapping Networks

• Reliability not goodcontinued

Page 4: Present Scenario - Webs

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 orexternal malicious attempts at network access

Page 5: Present Scenario - Webs

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 fixedcontinued

Page 6: Present Scenario - Webs

What is the need for Transition ?• Cost Considerations

• Optimum utilization of resources

• High speed data transfer

• COTS Hardware and Software

• Real time monitoring of circuitscontinued

Page 7: Present Scenario - Webs

What is the need for Transition ?• No Single service provider can meet SLA

requirement (99.999 for GAGAN)

• Effective liaison with reduced number ofdedicated manpower

• Opportunity for gaining experience for futurein house management capability

Page 8: Present Scenario - Webs

What is FTI

• The FTI network will place equipment at each AAIsite to support the migration of all existing AAIcommunications circuits to the FTI network. Thisequipment will provide AAI with dedicated circuitbandwidth and will multiplex all of thecommunications circuit at a site onto bulkbandwidth communications transport circuitswith required levels of serviceability.

Page 9: Present Scenario - Webs

FTI Infrastructureof AAI

CPE &Management DashBoard

NOCC SOCCMediaOFC/VSAT/Microwave

Page 10: Present Scenario - Webs

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

Page 11: Present Scenario - Webs

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

Page 12: Present Scenario - Webs

POST FTI SCENARIO• Achieve a common infrastructure, to meet

operational and mission critical voice, dataand video requirements.

• Obtain the required telecommunicationsservices at the ordered performance levels.

• Pay commercial prices that can beoptimized over time by the use of pricemanagement mechanisms for futureservices.

continued

Page 13: Present Scenario - Webs

POST FTI SCENARIO• Receive centralized, detailed, timely network

management information that can be viewedanytime by AAI management as well.

• Provide a single source for network statusand service ordering, billing and invoicingImplement new technologies that can bequickly introduced.

• Maximize the use of existing commercialsystems in the areas of network managementand business processes.

Page 14: Present Scenario - Webs

GLOBAL SCENARIO• FAA & EUROCONTROL have taken lead for the

establishment of managed communicationinfrastructure .

• FAA managed telecommunication infrastructure isa single scalable nationwide communicationnetwork implemented in 12 year span supportingmore than 22,000 services at 4000 locations.

• The pan –European network service(PENS) is aninternational communication infrastructure jointlyimplemented by Eurocontrol & 38 European airnavigation service providers(ANSP) in order tomeet existing & future air traffic communicationrequirements.

Page 15: Present Scenario - Webs

Scope of Work

• Exclusion of low volume circuits like VAH (Valueadded Hotlines), Dial up Circuits & local hot linesfrom scope of work

• RC lines/Media within Airport operational areashall be considered after stabilization of the FTInetwork.

• RC lines/Media outside Airport operational areaare included in scope of work.

Page 16: Present Scenario - Webs

Scope of work Continued..

• It should be service provider’s responsibilityto provide HVAC (Heating, Ventilation andAir-conditioning) equipments in the roomprovided to MSP for housing of Networkequipments.

• Service provider should provide cabling up toAAI’s equipments rather than up to commonservice delivery points (SDP).

• Service provider should provide its owndedicated earthing to connect CPE.

Page 17: Present Scenario - Webs

Scope of Work Continued..

• Provide space free of charge for installingCustomer Premises equipments (CPE)

• Provide chargeable space if required forlogistics support such as deployment ofmanpower, stores depot etc as per AAI’sCommercial policy

• Provide metered raw AC essential powersupply to energize service provider’sequipments.

Page 18: Present Scenario - Webs

Recommended SLA’s

Serviceability/Availability

Un-serviceabilitytime allowedper month

Services/Applications

99.999% 27 Sec Gagan99.99% <4 min Radar Data,

RCAG, ATFM ,ADS-B

99.9% <44min AMSS & DSC

Page 19: Present Scenario - Webs

FTI network Implementation EstimatedTimelines

• The FTI network implementation timeline begins atcontract signing. A timeline of activities in orderincludes:

• 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

Page 20: Present Scenario - Webs
Page 21: Present Scenario - Webs

Cost recovery/Revenue model

While this new system will providerequired SLA & necessary provisions forour future needs of operational growth& global harmonization issues, it will alsoensure reasonable source of revenue tooffset the expenditure incurred in thisproject by allowing other aviationentities to share data & connectivitywithout compromising security of ournetwork.

Page 22: Present Scenario - Webs

Cost recovery/Revenue model Contd.

Besides the above, since all the surveillance data pertainingto radar, ADS-B etc from different area control/locations canbe made available in the FTI cloud along with VHFcommunication Air/Ground data, with appropriateagreement and suitable contract formality we will be in aposition to work with the neighboring ANSPs and developmore efficient RNP routes in our Sub-Region. (e.g. ADS-Bdata of Coco island (Myanmar) and Port blair).

This arrangement will enhance safety, less fuel consumptionthereby reducing carbon emission and more RNFC to AAI

Page 23: Present Scenario - Webs

Proposed System Design

Initial model will be a mix of MPLScloud & existing point to point links(MLLN) however the MSP will beauthorized to have freedom torework & go for fresh contract forexisting MLLN circuits to meet theAAI’s SLA requirement.

Page 24: Present Scenario - Webs

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 providerfor management

• Fully resilient services with auto No resiliency can be offered as in layer 2switchover can be offered like circuit service provider do not have thedual last mile , dual flexibilityrouter , and dual POP.

• Managed and Unmanaged CPE options No proactive monitoring can be offered aswith proactive monitoring so that if a we just providing a layer two service ,link goes down can be detected anytime a circuit goes down customerautomatically needs to reactively log a compliant

• Hub and Spoke and Full Mesh Point to point and Hub and spokeconnectivity options available connectivity options are available.

• Service Provider provides the IP Service provider does not provide IPaddress address

Page 25: Present Scenario - Webs

Proposed System Design contd.

The MSP will provide Dedicated NetworkOperations Control Centre (NOCC) & SecurityOperations Control centre (SOCC) enablingdynamic management of Bandwidth havingredundant multilayer media connectivity. Bythe provisioning of NOCC/SOCC, effective SLAmonitoring & security of data can beascertained.

Page 26: Present Scenario - Webs

Proposed System Design Contd.

The system will be technology and protocoltransparent, providing integration andinterpretation of data pertaining to divergentsystems. The contract period under thismodel would be for 15 years, however thesame can be extended on mutually agreedconditions. The requirement of technologyrefresh will be assessed & reviewed at every5 years.

Page 27: Present Scenario - Webs

Proposed System Design Contd.

The above assessment entails asuitable arrangement ofproviding end user equipmentslike router, multiplexers andswitches etc. of appropriatecapacity & redundancy to coverour future bandwidth needs.

Page 28: Present Scenario - Webs
Page 29: Present Scenario - Webs
Page 30: Present Scenario - Webs

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 anyfailure of the new FTI system for sustaining uninterruptedoperations.

• Further, MSP may also include some part of the existing Telecominfrastructure in their network for locations not covered byPOP(Point of Presence) of their Telecom media provider.

• Remaining telecom media will be surrendered once the reliabilityand the stability of new FTI system is ascertained.

Page 31: Present Scenario - Webs

Tendering Model• Average budgetary cost of the project will be

about 52 Crores per annum .Expenditure onthis account/project will be under OPEXinstead of traditional CAPEX.

• Global tender route• Quality and Cost-Based Selection(QCBS) to

ensure only competent eligible with proventrack record bid

Page 32: Present Scenario - Webs

Secured Internet Gateway

• The SOCC shall have the capability tomanage encryption for AAI authorizedUsers accessing network resources fromoutside of the network, or using thepublic internet to access networkresource through a secure networkgateway

Page 33: Present Scenario - Webs

Intrusion Prevention System• Intrusion prevention systems (IPS), also

known as intrusion detection andprevention systems (IDPS), are networksecurity appliances that monitornetwork and/or system activities formalicious activity. The main functions ofintrusion prevention systems are toidentify malicious activity, loginformation about this activity, attemptto block/stop it, and report it.

Page 34: Present Scenario - Webs

continued• Intrusion prevention systems are

considered extensions of intrusiondetection system because they bothmonitor network traffic and/or systemactivities for malicious activity. The maindifferences are, unlike intrusiondetection systems, intrusion preventionsystems are placed in-line and are ableto actively prevent/block intrusions thatare detected.

Page 35: Present Scenario - Webs

Common regional VPN for AsiaPacific Region

• In line with the PENS (Pan EuropeanNetwork), a decision was taken inAPANPIRG/24 to establish a taskforceconsisting of subject matter expert tostudy Common Regional Virtual PrivateNetwork (CRVPN) for Asia Pacific Region.India is also participating actively in thisstudy as one of the members because itis on similar lines of FTI.

Page 36: Present Scenario - Webs

Continued• This task force will report the outcome of

this study to APANPIRG/25 throughAeronautical Communication ServicesImplementation Co-ordination Group(ACSICG) and CNS Sub Group of APANPIRG.If decided favourably, all the point to pointcommunication links working withindifferent countries in Asia Pacific regionshall be connected with each other incloud environment. This would also pave away for implementation of SWIM underthe block B1 of ASBU.

Page 37: Present Scenario - Webs