公司规模
Mid-size Company
地区
- America
国家
- United States
产品
- G Suite
- Bitglass Cloud
技术栈
- Cloud Computing
- Mobile Device Management
实施规模
- Enterprise-wide Deployment
影响指标
- Productivity Improvements
- Digital Expertise
技术
- 基础设施即服务 (IaaS) - 云计算
- 网络安全和隐私 - 云安全
适用行业
- 药品
适用功能
- 商业运营
服务
- 云规划/设计/实施服务
- 网络安全服务
关于客户
AMAG Pharmaceuticals, Inc. (NASDAQ: AMAG) 是一家从事治疗缺铁性贫血 (IDA) 的治疗性铁化合物的开发和商业化的公司。该公司的主要产品包括 Feraheme(静脉注射剂,于 2009 年 6 月获得美国食品药品管理局批准在美国上市,用于治疗患有慢性肾病 (CKD) 的成年患者的 IDA 的静脉铁替代疗法。该公司成立于 1981 年,总部位于马萨诸塞州列克星敦。
挑战
AMAG Pharmaceuticals 是一家开发和销售治疗缺铁性贫血的治疗性铁化合物的公司,该公司决定采用 G Suite 作为公司的所有云主干。这一决定是为了提高生产力,因为 G Suite 提供了灵活且易于使用的高性能生产力套件。然而,将 BYOD 与云相结合意味着 AMAG 失去了对其数据的可见性和控制力,从而存在安全性和合规性风险。现有的安全解决方案不易应用于云应用,并引发隐私问题,因为员工不希望 IT 监控他们的个人云应用或移动设备。
解决方案
为了应对数据可见性和控制方面的挑战,AMAG Pharmaceuticals 部署了 Bitglass Cloud 解决方案。该解决方案使公司能够透明地保护云和移动使用,而无需在现场部署软件。Bitglass 通过用户、设备和地理位置的上下文访问控制策略来监控和控制云应用程序的使用。借助其 Omni 多协议代理,Bitglass 能够保护来自任何端点的所有流量,而无需复杂的配置。此外,Bitglass 还利用其强大的云 DLP 引擎保护访问的 AMAG 文件。使用可配置的关键字正则表达式规则,AMAG 甚至可以编辑非托管移动设备上的敏感内容。Bitglass 还使 AMAG 能够有选择地从移动设备上擦除公司数据,而无需代理。员工可以在个人设备上使用本机生产力客户端,而无需担心设备管理软件带来的用户体验麻烦或隐私问题。如果设备丢失或受到损害,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.