Download PDF
The IT Team at AMAG Pharmaceuticals Implements Cisco Cloudlock for Access Management for Google Doc
Technology Category
- Infrastructure as a Service (IaaS) - Cloud Computing
- Infrastructure as a Service (IaaS) - Cloud Middleware & Microservices
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Business Operation
Use Cases
- Regulatory Compliance Monitoring
- Remote Asset Management
Services
- Cloud Planning, Design & Implementation Services
The Challenge
AMAG Pharmaceuticals, a publicly traded biopharmaceutical company, was one of the first in its industry to adopt cloud services and migrate to Google Apps. However, this move presented a new set of challenges. As a publicly traded pharmaceutical company, AMAG had to comply with SOX and FDA regulations while also protecting the company’s intellectual property. With the adoption of Google Apps and the creation and storage of documents in Google Docs, the IT team at AMAG recognized a need for a solution that would provide visibility into user adoption, document growth, document classification, and control and visibility of document exposure to address compliance and governance requirements.
About The Customer
AMAG Pharmaceuticals, Inc. is a publicly traded biopharmaceutical company that develops and commercializes therapeutic and diagnostic iron oxide nanoparticles. The company utilizes its proprietary technology to treat iron deficiency anemia. AMAG manufactures Feraheme® (ferumoxytol) Injection for intravenous (IV) use. The company aspires to be a leading partner to the healthcare community by ensuring outstanding collaboration in supporting effective research as well as supporting robust education efforts. AMAG also seriously considers its obligations as a corporate citizen by supporting important charitable causes through donations. The company has 175 employees.
The Solution
AMAG Pharmaceuticals implemented Cisco Cloudlock to manage access to Google Docs. With Cisco Cloudlock, the IT team at AMAG was able to gain visibility into all documents in the domain and see their sharing settings. They could fully control document permissions, monitor and receive exposure alerts, and review all changes for documents created or shared with their domain. Cisco Cloudlock also provided ongoing monitoring of the entire domain with email alerts on newly exposed documents and changes in permissions for existing documents. The same report was also available from within the application with the ability to view the specific documents. Users could select a time range and view at once all the changes that happened in their domain for a specified time. Cisco Cloudlock’s features for auditing all users and all documents in the domain (as well as tracking all changes) gave AMAG the tools they needed to generate audit reports to comply with regulations or internal governance policies.
Operational Impact
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
Drug Maker Takes the Right Prescription
China Pharm decided to build a cloud-based platform to support the requirements of IT planning for the next five to ten years which includes a dynamic and scalable mail resource pool platform. The platform needed to have the following functions: all nodes support redundancy, ensuring service continuity and good user experience, simple and easy-to-use user interfaces for end users and administrators and good compatibility and supports smooth capacity expansion.
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.
