Customer Company Size
Mid-size Company
Region
- America
Country
- United States
Product
- G Suite
- Bitglass Cloud
Tech Stack
- Cloud Computing
- Mobile Device Management
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Productivity Improvements
- Digital Expertise
Technology Category
- Infrastructure as a Service (IaaS) - Cloud Computing
- Cybersecurity & Privacy - Cloud Security
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Business Operation
Services
- Cloud Planning, Design & Implementation Services
- Cybersecurity Services
About The Customer
AMAG Pharmaceuticals, Inc., (NASDAQ: AMAG), is a company that engages in the development and commercialization of a therapeutic iron compound to treat iron deficiency anemia (IDA). The company’s principal product includes Feraheme (injection for intravenous (IV) use, which was approved for marketing in the United States in June 2009 by the U.S. Food and Drug Administration, for use as an IV iron replacement therapy for the treatment of IDA in adult patients with chronic kidney disease (CKD). The company was founded in 1981 and is headquartered in Lexington, Massachusetts.
The Challenge
AMAG Pharmaceuticals, a company that develops and commercializes a therapeutic iron compound to treat iron deficiency anemia, decided to adopt G Suite as the all cloud backbone for the company. This decision was made to enhance productivity as G Suite offers a high performance productivity suite that is flexible and easy-to-use. However, combining BYOD and cloud meant that AMAG lost visibility and control of its data, risking security and compliance. Existing security solutions were not readily applicable to cloud apps and raised privacy concerns, since employees didn’t want IT monitoring their personal cloud apps or mobile devices.
The Solution
To address the challenge of data visibility and control, AMAG Pharmaceuticals deployed the Bitglass Cloud solution. This solution enables the company to transparently secure cloud and mobile usage without deploying software on premises. Bitglass monitors and controls usage of cloud apps via contextual access-control policies by user, device, and geography. With its Omni multi-protocol proxies, Bitglass is able to secure all traffic from any endpoint without complex configuration. In addition, Bitglass protects AMAG files at access with its robust cloud DLP engine. Using configurable keyword regular expression rules, AMAG can even redact sensitive content on unmanaged mobile devices. Bitglass also enables AMAG to selectively wipe corporate data from mobile devices without agents. Employees may use the native productivity clients on their personal device without the user experience hassles or privacy concerns of device management software. If a device is lost or compromised, AMAG can selectively wipe corporate data from the device and block continued access.
Operational Impact
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
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
ELI LILLY ADOPTS MICROMEDIA’S ALERT NOTIFICATION SYSTEM
Pharmaceutical production is subject to a strict set of enforced rules that must be adhered to and compliance to these standards is critically necessary. Due to the efforts of WIN 911’s strategic partner Micromedia, Lilly was able to adopt an alarm notification infrastructure that integrated smoothly with their existing workflows and emergency hardware and protocols. These raw energy sources enable the industrial process to function: electricity, WIN-911 Software | 4020 South Industrial Drive, Suite 120 | Austin, TX 78744 USA industrial steam, iced water, air mixtures of varying quality. Refrigeration towers, boilers and wastewater are monitored by ALERT. Eli Lilly identified 15000 potential variables, but limitations compelled them to chisel the variable list down to 300. This allowed all major alarms to be covered including pressure, discharge, quantity of waste water discharged,temperature, carbon dioxide content, oxygen & sulphur content, and the water’s pH.