公司规模
Large Corporate
地区
- Europe
国家
- United Kingdom
产品
- IBM Maximo Asset Management
实施规模
- Enterprise-wide Deployment
影响指标
- Productivity Improvements
- Cost Savings
技术
- 功能应用 - 企业资产管理系统 (EAM)
适用行业
- 药品
适用功能
- 维护
用例
- 预测性维护
- 资产生命周期管理
服务
- 云规划/设计/实施服务
关于客户
Penn Pharma 是一家 PCI 公司,为医疗保健行业提供综合药物开发、临床试验供应和制造服务。该公司成立已有 35 年,在英国拥有约 300 名员工。其全球母公司 PCI 在全球拥有约 2,800 名员工。Penn Pharma 最近投资了一座新的最先进的高防护设施,并希望开发一种主动、可预测的维护规划方法。
挑战
PCI 公司 Penn Pharma 认识到需要一套维护和校准规划系统来提高其新封闭式制造工厂的可用性和服务水平。该公司希望开发一种主动的、可预测的维护规划方法。该公司意识到,企业级维护管理系统还可以帮助满足适用于制药制造的严格法规以及注重安全的客户的日益增长的期望。
解决方案
Penn Pharma 决定部署 IBM Maximo Asset Management 来改变其新工厂的维护计划,并聘请 IBM 高级业务合作伙伴 Peacock Engineering 以托管服务的形式提供解决方案。使用 IBM Maximo 作为维护任务的调度工具,Penn Pharma 获得了集中控制点。该公司的工程师现在可以访问他们自己的个性化仪表板,这些仪表板可以即时查看到期的工作以及完成这些工作的最有效顺序。通过消除基于纸张的流程,迁移到 IBM Maximo 有助于提高工作效率。
运营影响
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
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.