Download PDF
Business Continuity in the Cloud: Takeda Pharmaceutical Company's Remote Access Scaling
Technology Category
- Application Infrastructure & Middleware - Event-Driven Application
- Cybersecurity & Privacy - Network Security
Applicable Industries
- Pharmaceuticals
- Telecommunications
Applicable Functions
- Product Research & Development
Use Cases
- Remote Control
- Tamper Detection
Services
- Cloud Planning, Design & Implementation Services
- Hardware Design & Engineering Services
The Challenge
Takeda Pharmaceutical Company, the oldest pharmaceutical firm in the world, faced a significant challenge following its merger with Shire PLC. The merger resulted in a 'quite-disjointed' network architecture that needed to be integrated and secured. The company's IT team, led by CISO Mike Towers, was tasked with managing systems for a global workforce of over 70,000 employees spread across 110 countries. The company had begun rolling out Zscaler Internet Access (ZIA) in late 2018 to secure employee internet egress via the cloud and provide a consistent user experience. However, the merger accelerated Takeda's migration to the cloud, pushing the company to move towards a Zero Trust, user-to-destination model as quickly as possible. The challenge was to provide secure employee connectivity for every type of worker via local internet breakouts, while maintaining a consistent policy across all locations.
About The Customer
Takeda Pharmaceutical Company is a Tokyo-based pharmaceutical firm, recognized as the oldest in the world. The company has a significant global presence, with over 52,000 employees spread across 110 countries and 575 locations. Takeda's 2019 acquisition of Shire PLC expanded its footprint to more than sixty office and research locations worldwide. The company's IT team, based in Cambridge, Massachusetts, manages systems for its global workforce of over 70,000 employees. Takeda is a values-driven company, with a focus on internal development and the use of proprietary technologies, applications, and intellectual property.
The Solution
Takeda standardized on ZIA, displacing its 'next-generation' firewalls. This gave the company greater flexibility in enabling secure employee connectivity. Zscaler's policy-based administrative controls helped Takeda become more agile, allowing the company to maintain a consistent policy regardless of where employees were located. In 2019, Takeda began rolling out Zscaler Private Access (ZPA) to deliver secure connectivity to internal resources. This was a significant cultural change for the company, but it allowed Takeda to extend remote access and retire VPN hardware. The company shifted its control and provisioning approach, focusing on providing employees with the applications they needed to get their work done, rather than where those applications resided. When the coronavirus outbreak hit in early 2020, Takeda was able to quickly pivot to ZPA, enabling the company to secure its transition to fully-remote operations.
Operational Impact
Quantitative Benefit
Related Case Studies.
Case Study
Case Study: Pfizer
Pfizer’s high-performance computing software and systems for worldwide research and development support large-scale data analysis, research projects, clinical analytics, and modeling. Pfizer’s computing services are used across the spectrum of research and development efforts, from the deep biological understanding of disease to the design of safe, efficacious therapeutic agents.
Case Study
Fusion Middleware Integration on Cloud for Pharma Major
Customer wanted a real-time, seamless, cloud based integration between the existing on premise and cloud based application using SOA technology on Oracle Fusion Middleware Platform, a Contingent Worker Solution to collect, track, manage and report information for on-boarding, maintenance and off-boarding of contingent workers using a streamlined and Integrated business process, and streamlining of integration to the back-end systems and multiple SaaS applications.
Case Study
Process Control System Support
In many automated production facilities, changes are made to SIMATIC PCS 7 projects on a daily basis, with individual processes often optimised by multiple workers due to shift changes. Documentation is key here, as this keeps workers informed about why a change was made. Furthermore, SIMATIC PCS 7 installations are generally used in locations where documentation is required for audits and certification. The ability to track changes between two software projects is not only an invaluable aid during shift changes, but also when searching for errors or optimising a PCS 7 installation. Every change made to the system is labour-intensive and time-consuming. Moreover, there is also the risk that errors may occur. If a change is saved in the project, then the old version is lost unless a backup copy was created in advance. If no backup was created, it will no longer be possible to return to the previous state if and when programming errors occur. Each backup denotes a version used by the SIMATIC PCS 7 system to operate an installation. To correctly interpret a version, information is required on WHO changed WHAT, WHERE, WHEN and WHY: - Who created the version/who is responsible for the version? - Who released the version? - What was changed in the version i.e. in which block or module of the SIMATIC PCS 7 installation were the changes made? - When was the version created? Is this the latest version or is there a more recent version? - Why were the changes made to the version? If they are part of a regular maintenance cycle, then is the aim to fix an error or to improve production processes? - Is this particular version also the version currently being used in production? The fact that SIMATIC PCS 7 projects use extremely large quantities of data complicates the situation even further, and it can take a long time to load and save information as a result. Without a sustainable strategy for operating a SIMATIC PCS 7 installation, searching for the right software version can become extremely time-consuming and the installation may run inefficiently as a result.
Case Study
Vodafone Hosted On AWS
Vodafone found that traffic for the applications peak during the four-month period when the international cricket season is at its height in Australia. During the 2011/2012 cricket season, 700,000 consumers downloaded the Cricket Live Australia application. Vodafone needed to be able to meet customer demand, but didn’t want to invest in additional resources that would be underutilized during cricket’s off-season.
