技术
- 应用基础设施与中间件 - 数据交换与集成
- 基础设施即服务 (IaaS) - 云计算
适用行业
- 消费品
- 药品
适用功能
- 产品研发
- 质量保证
用例
- 施工管理
- 基础设施检查
服务
- 云规划/设计/实施服务
- 系统集成
关于客户
强生公司是全球最大的医疗保健企业,也是财富 500 强公司前 50 名。它生产药品、医疗设备和消费品,造福全球十亿人。强生公司拥有杨森制药公司,这是一家利用科学来对抗疾病的公司。杨森 (Janssen) 发明了 1 剂 COVID-19 疫苗,可在全球 100 多个国家/地区预防感染并挽救生命。这个以研究为导向的组织依靠高性能计算 (HPC) 来推动有效、广泛使用的药物的发现和生产。
挑战
全球医疗保健巨头强生公司(Johnson & Johnson)需要大规模的按需计算能力来进行研究,特别是杨森制药公司(Janssen Pharmaceuticals),该公司正在研究 COVID-19 疫苗。该公司需要在不使用时轻松缩减该容量,而这一壮举只有通过云基础设施才能实现。 Janssen 在 Amazon Web Services (AWS) 上运行 10 多个生产高性能计算 (HPC) 集群,供世界各地的科学家和开发人员使用。然而,他们正在寻求一种现成的解决方案来取代开源网格引擎和不再支持其首选供应商的云管理工具。挑战包括适应十多年来发展的现有基础设施和系统、管理复杂的网络设置以及集成到配置和变更管理系统中。此外,每个集群的配置都不同,这增加了复杂性。
解决方案
为了应对这些挑战,Janssen 的工作负载管理软件升级为 Altair® Grid Engine®,并部署 Altair® NavOps® 来管理公司复杂的云部署。该解决方案与AWS云服务无缝集成。该软件包满足 Janssen 对集群自动创建和扩展、遵守内部安全策略和网络、与商业和本土应用程序兼容以及 GXP 合规性的要求。它包括用于资源分配的 cgroup、用于容器化工作负载的 Docker 集成以及 REST API。结果是简化、自动化且可扩展的 Janssen HPC 基础设施。借助 Altair 编排层,Johnson & Johnson 可以在复杂的多租户环境中按需扩展。团队可以使用当前的配置组件根据需要快速轻松地创建其他集群。 Altair 的基础架构即代码解决方案包括完整的 UI/CLI/API 可配置性、灵活的配置和集成选项,以及对必要组件进行模板化和轻松编辑配置差异的能力。
运营影响
数量效益
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
Improving Vending Machine Profitability with the Internet of Things (IoT)
The vending industry is undergoing a sea change, taking advantage of new technologies to go beyond just delivering snacks to creating a new retail location. Intelligent vending machines can be found in many public locations as well as company facilities, selling different types of goods and services, including even computer accessories, gold bars, tickets, and office supplies. With increasing sophistication, they may also provide time- and location-based data pertaining to sales, inventory, and customer preferences. But at the end of the day, vending machine operators know greater profitability is driven by higher sales and lower operating costs.
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
Series Production with Lot-size-1 Flexibility
Nobilia manufactures customized fitted kitchens with a lot size of 1. They require maximum transparency of tracking design data and individual processing steps so that they can locate a particular piece of kitchen furniture in the sequence of processes.