公司规模
Mid-size Company
地区
- America
国家
- United States
产品
- Cisco Cloudlock
技术栈
- Google Apps
- Google App Engine
实施规模
- Enterprise-wide Deployment
影响指标
- Digital Expertise
- Customer Satisfaction
技术
- 基础设施即服务 (IaaS) - 云计算
适用行业
- 药品
适用功能
- 商业运营
用例
- 监管合规监控
- 远程资产管理
服务
- 云规划/设计/实施服务
关于客户
AMAG Pharmaceuticals, Inc. 是一家上市生物制药公司,开发和商业化治疗和诊断氧化铁纳米颗粒。该公司利用其专有技术治疗缺铁性贫血。AMAG 生产用于静脉 (IV) 的 Feraheme® (ferumoxytol) 注射液。该公司致力于成为医疗保健界的领先合作伙伴,确保在支持有效研究以及支持强有力的教育工作方面进行出色的合作。AMAG 还认真考虑其作为企业公民的义务,通过捐款支持重要的慈善事业。该公司拥有 175 名员工。
挑战
AMAG Pharmaceuticals 是一家上市生物制药公司,是业内首批采用云服务并迁移到 Google Apps 的公司之一。然而,这一举措带来了一系列新挑战。作为一家上市制药公司,AMAG 必须遵守 SOX 和 FDA 法规,同时还要保护公司的知识产权。随着 Google Apps 的采用以及在 Google Docs 中创建和存储文档,AMAG 的 IT 团队意识到需要一种解决方案,能够提供对用户采用、文档增长、文档分类以及文档暴露的控制和可见性的可见性,以满足合规性和治理要求。
解决方案
AMAG Pharmaceuticals 实施了 Cisco Cloudlock 来管理对 Google Docs 的访问。借助 Cisco Cloudlock,AMAG 的 IT 团队能够查看域中的所有文档并查看其共享设置。他们可以完全控制文档权限,监控和接收暴露警报,并查看在其域中创建或共享的文档的所有更改。Cisco Cloudlock 还通过对新暴露的文档和现有文档权限更改的电子邮件警报对整个域进行持续监控。应用程序内也可以提供相同的报告,并能够查看特定文档。用户可以选择一个时间范围并一次查看其域在指定时间内发生的所有更改。Cisco Cloudlock 的审计域中所有用户和所有文档(以及跟踪所有更改)的功能为 AMAG 提供了生成审计报告所需的工具,以遵守法规或内部治理政策。
运营影响
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
相关案例.
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.