Airport Modernization

1. Airport Modernization An Object Oriented Approach By Gp Capt JN Rampal, VSM (Retd)

2. AGENDA • Introduction • Airport : Some Definitions • Airport : Functional View • Airport : Stages of development • NextGen Growth Options • A Peep in the future • NextGen Growth : Generic Strategy • Object Oriented Paradigm • Example process architecture • Modernization Plan approach • Structure of Layered Plan • Other Strategy Issues • Conclusion

3. Introduction • An Airport is a complex set of assets , processes and human resources. • To build efficient Airport operations, we need to bring together state of the art technology, project management methodologies and the most talented people together. • This presentation is a brief description of the issues involved in such an exercise.

4. Airport : Sample Definitions • An Airport is a service point for air travel, for passengers and cargo. or • An Airport is a place where runways, dispersal areas and facilities are provided which passengers and cargo can use. or • An Airport is an aggregation of real estate, systems and people , which interact to create the air travel service.

5. Airport : Functional View • Passengers and cargo go to the airport because they need to be air transported. • They use functionalities at the airport for receiving the air transportation service. • The functionalities are provided using the assets , which are part of the airport installation : assisted by facilitators, who manage the airport.

6. Airport : Stages of Development (1) : Bare Bones Initial Stage: ( A few flights a day) • Runway • A perimeter taxi track • Few parking bays, hangars • Air traffic control (generally satellite to a major airport) • Communication with area control only [ No congestion in or just outside of airport] interruption by unwanted actions.

7. Airport : Stages of Development (2) : Getting Bigger Initial Growth Stage : ( Many flights a day, multiple destinations) • Runway • Many taxi tracks • Add on parking bays, hangars • Air traffic control (many functions added) • Communication with many nodes [ Increased Complexity but still manageable. Infrequent overloads and congestion caused deadlocks]

8. Airport : Stages of Development (3) : Getting Rather Big High Growth Stage :( Large number of flights a day, large number of destinations) • Add on Runway (wherever possible) • Many taxi tracks , cross runways • Parking bays, hangars, wherever space available. • Air traffic control (many systems and functions added) • Air ground and data Communication extensive [ Complexity frequently defies manageability. Frequent overloads and congestion deadlocks]

9. Airport : Stages of Development (4) : Too Big to Handle Saturation Growth Stage : ( Very large number of flights a day, multiple destinations) • Continuous operations with no empty slots between. • Unable to add resources. Constraints seem to unavailability at the right place at the right time. • Overload of information, but unable to use information for taking decisions in time. • Chaos. [ Complexity beyond manageable bounds. Perpetual overloads and congestion deadlocks]

10. NextGen Growth : Options • Additional airport . Split load and keep using the same system design. or • Modernize : Change over to a system which provides higher throughput . Device a new architecture to provide efficient operations even with 90% utilization.

11. NextGen Growth : Option Predicament • Even if we split load and have an additional airport, the traffic grows and imposes the modernization requirement on the two sister airports. (The rapid growth of air travel in India, today and in the foreseeable future, underlines the tendency even more. • Why not leverage the current investment for higher productivity with incremental investment ? So, Modernization is Hobson’s choice.

12. Airport : A Peep into the Future NextGen Growth :( Very large number of flights a day, to any number of destinations) • Multiple Runways (weather and real estate permitting) • Traffic planned taxi tracks, loops and branch-offs • Ground space utilization planned & optimized • Multiple level support facilities • Air traffic control (new architecture and processes) • Air ground and data Communication refurbished • Process and automation added with the help of IT . [ Complexity very high, but always monitored and managed. Overloads and congestion deadlocks always avoided by pre- emptive action]

13. NextGen Growth : Generic Strategy (1) • Saturation growth is the limit for current technologies of airport operations. NextGen growth is possible only with a paradigm change. • The new implementations will be driven by IT, automated (intelligent) systems and Object oriented architecture concepts. • The system architecture will be top-down, modular, flexible, predominantly automated, self monitoring and continuously improving systems.

14. NextGen Growth : Generic Strategy (2) Some other imperatives of NextGen Model • In synchronism with business/revenue and implementation models. • Flexible in terms of operational role • Process and functionality driven • Open system architecture to take on new technologies in future • Iterative and controlled implementation, without undue disruptions in operations

15. Object Oriented Paradigm • The operations are aggregation of process flows, which are defined by use-cases, i.e. the way a user does a particular thing. [Operational process is firmly tied to actual operations]. • The process flows comprise of execution of functionalities by (intangible) entities called objects [implementation with the help of top down, flexible, scalable architecture]. • The assets are embedded in object definitions. i.e. the asset usage is related to the function definition. [Helps in optimum asset pool size and their balanced usage].

16. Consequences of an Object Oriented Approach • Top down flexible, scalable architecture. • Implementation possible on an ‘Information Technology’ foundation. • Efficient, real-time monitoring & control, continuously improving capabilities. • Cost effective both in terms of capital and running costs. • Possible to bring in new technologies and systems without disrupting operations.

17. Operational Process : A Representative Model Operations Control ------------------------------------------------------------ | | | Asset Process Flow Information Management Management Management (Sharable asset Allocation, and | (Monitoring, disbursement release) | and control) (contd)

18. Operational Process : A Representative Model Process Flow management • | | | • Thread 1 Thread 2 …….. Thread N • Process flow Process flow Process flow • arrival Departure Maintenance • | | | • {Object arrival {Object Information { Object schedule • Object baggage Object baggage Object service • Object turnaround Object security Object testing • Object clearance Object customs Object test flying • Object Information Object boarding Object certify • ……………….} Object departure Object schedule • ………………..} ……………..}

19. Modernization Plan Approach • Define current and projected capabilities (after modernization). • Define OO architecture model. • Derive process flows and object functionalities. • Define ‘evolution path’ • Project plan. • Implementation and deployment.

20. Modernization Plan Framework Layer 4 Application (process flow) | Layer 3 Objects build up ( Assets, payload processes) | Layer 2 Information Exchange framework | Layer 1 Physical

21. A Simple Plan Define current and projected capabilities | Object oriented parametric analysis | To do list (processes/objects/assets) | Layered plan (vertical 4 layer analysis) | Horizontal partitioning for iteration definition | Implementation (Iterative and staggered) | System integration, harmonization, optimization, testing and acceptance | Rework iterations | Acceptance and deployment

22. Other Strategy Issues • Project plan design could also dictated by other related considerations e.g. implementation model (DBB, BOO, BOT), cash flows etc. • External stakeholders e.g. ICAO , AAI, IAF, MOCA etc may impose additional functionalities and information exchange requirements for the airport operations. • A modernization plan is generally a massive aggregation of many plans (ordered layer-wise, partition-wise, partitioned amongst vendors work-volume wise). In such cases, integration, co-ordination and synchronization becomes an additional and critical part of the plan.

23. OO Advantage • An OO system is highly amenable to computer modeling and simulation, at all stages of implementation, We can run simulations to check efficacy of implementation, problem areas before installing the system physically. • Conversion of a conventional model to an OO model would have immense advantage in the long term as the complications start reducing. In the conventional asset building approach, the complications start mounting with the build up. • The performance monitoring, analysis and upgrade being a part of OO architecture, the improvement of performance is a part of airport capability. • The modular structure also makes it easy for introduction of new technologies and systems. • Lastly, OO approach is a money saver in the long run and the best way to minimize and ameliorate operational risks.

24. Conclusion Object Oriented Operational Process implementation are the enablers of next-Gen airport operations Bissaj Advance Technologies can help to, • Provide technology and operations related consultancy. • Model/audit the airport operations process. • Advise on process/system architecture. • Provide assistance to optimize implementation.