Pegasus Airlines f lies high with webMethods
Customer Company Size
Large Corporate
Region
- Asia
- Europe
Country
- Turkey
Product
- webMethods Integration
- webMethods API Management
Tech Stack
- APIs
- Middleware
- Big Data
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Cost Savings
- Productivity Improvements
- Digital Expertise
Technology Category
- Application Infrastructure & Middleware - API Integration & Management
Applicable Industries
- Aerospace
Applicable Functions
- Discrete Manufacturing
- Sales & Marketing
Use Cases
- Process Control & Optimization
- Cybersecurity
Services
- System Integration
- Training
About The Customer
Pegasus Airlines is a Turkish low-cost airline that has been in operation for 20 years. It is the largest budget airline in Turkey, offering scheduled domestic and international services to 111 destinations in 42 countries. Based in Istanbul, Pegasus has over 5,000 employees and is the second largest airline in the country. The airline has faced some challenging times recently, including a landing incident in Istanbul in 2020 and the global COVID-19 outbreak. These events have led to a decrease in passenger levels and disrupted schedules, making it even more crucial for the airline to reduce costs and improve its operating efficiencies.
The Challenge
Pegasus Airlines, Turkey’s largest budget airline, was facing challenging times due to a landing incident and the global COVID-19 outbreak. This led to diminished passenger levels and disrupted schedules, making it imperative for the airline to reduce costs and improve operating efficiencies. In 2017, the airline was searching for a robust middleware platform to adapt quickly and flexibly to customers’ requirements. It had concerns about its new middleware platform and was unsure whether it was improving agility or service levels and reducing incidents/resolution times. The airline was unhappy with the operational costs due to its monolithic infrastructure with application silos having point-to-point integration. Its goal was to set up a robust and secure IT architecture and capitalize on technology innovation.
The Solution
To achieve its goals, Pegasus chose SoftwareAG's webMethods Integration. The webMethods Integration platform introduced an agility layer into the overall IT architecture that enabled Pegasus to respond faster to change. It now serves as the baseline platform for the airline’s service and process orchestration and automation. By introducing an agility layer into Pegasus’ IT environment, the airline could lift the burden of maintaining outdated and obsolete technologies and point-to-point integrations away from IT. This gave the IT department the technology base—and more time—it needed to innovate based on business needs. In 2019, Pegasus approached Software AG to discuss mediating its API traffic; it was looking for a solution to reroute API calls, log them and enrich them with additional information. It also wanted the capability to securely expose APIs to third-party developers and partners for use in web, mobile and Internet of Things (IoT) applications. Its other goal was to protect the APIs from unregistered usage—and thus its back-end systems from malicious attacks.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Airbus Soars with Wearable Technology
Building an Airbus aircraft involves complex manufacturing processes consisting of thousands of moving parts. Speed and accuracy are critical to business and competitive advantage. Improvements in both would have high impact on Airbus’ bottom line. Airbus wanted to help operators reduce the complexity of assembling cabin seats and decrease the time required to complete this task.
Case Study
Aircraft Predictive Maintenance and Workflow Optimization
First, aircraft manufacturer have trouble monitoring the health of aircraft systems with health prognostics and deliver predictive maintenance insights. Second, aircraft manufacturer wants a solution that can provide an in-context advisory and align job assignments to match technician experience and expertise.
Case Study
Aerospace & Defense Case Study Airbus
For the development of its new wide-body aircraft, Airbus needed to ensure quality and consistency across all internal and external stakeholders. Airbus had many challenges including a very aggressive development schedule and the need to ramp up production quickly to satisfy their delivery commitments. The lack of communication extended design time and introduced errors that drove up costs.
Case Study
Developing Smart Tools for the Airbus Factory
Manufacturing and assembly of aircraft, which involves tens of thousands of steps that must be followed by the operators, and a single mistake in the process could cost hundreds of thousands of dollars to fix, makes the room for error very small.
Case Study
Accelerate Production for Spirit AeroSystems
The manufacture and assembly of massive fuselage assemblies and other large structures generates a river of data. In fact, the bill of materials for a single fuselage alone can be millions of rows of data. In-house production processes and testing, as well as other manufacturers and customers created data flows that overwhelmed previous processes and information systems. Spirit’s customer base had grown substantially since their 2005 divestiture from Boeing, resulting in a $41 billion backlog of orders to fill. To address this backlog, meet increased customer demands and minimize additional capital investment, the company needed a way to improve throughput in the existing operational footprint. Spirit had a requirement from customers to increase fuselage production by 30%. To accomplish this goal, Spirit needed real-time information on its value chain and workflow. However, the two terabytes of data being pulled from their SAP ECC was unmanageable and overloaded their business warehouse. It had become time-consuming and difficult to pull aggregate data, disaggregate it for the needed information and then reassemble to create a report. During the 6-8 hours it took to build a report, another work shift (they run three per day) would have already taken place, thus the report content was out-of-date before it was ever delivered. As a result, supervisors often had to rely on manual efforts to provide charts, reports and analysis.
