Customer Company Size
Large Corporate
Region
- Europe
Country
- United Kingdom
Product
- IBM Maximo Asset Management
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Productivity Improvements
- Cost Savings
Technology Category
- Functional Applications - Enterprise Asset Management Systems (EAM)
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Maintenance
Use Cases
- Predictive Maintenance
- Asset Lifecycle Management
Services
- Cloud Planning, Design & Implementation Services
About The Customer
Penn Pharma, a PCI company, is a firm that delivers integrated drug development, clinical trial supply and manufacturing services for the healthcare industry. The company has been established for over 35 years and employs approximately 300 people in the UK. Its global parent company, PCI, employs around 2,800 people worldwide. Penn Pharma recently invested in a new state-of-the-art high-containment facility and wanted to develop a proactive, predictive approach to maintenance planning.
The Challenge
Penn Pharma, a PCI company, recognized the need for a maintenance and calibration planning system to increase availability and service levels at its new contained manufacturing facility. The company wanted to develop a proactive, predictive approach to maintenance planning. The company realized that an enterprise-class maintenance management system could also help meet the stringent regulations that apply to pharmaceutical manufacturing, and the growing expectations of its safety-conscious clients.
The Solution
Penn Pharma decided to deploy IBM Maximo Asset Management to transform maintenance planning at its new facility, and engaged IBM Premier Business Partner Peacock Engineering to deliver the solution as a hosted service. With IBM Maximo as a scheduling tool for maintenance tasks, Penn Pharma has gained a centralized point of control. The company’s engineers can now access their own personalized dashboards, which provide instant visibility of the jobs that are due, and the most efficient order in which to complete them. By eliminating paper-based processes, the move to IBM Maximo contributes to more efficient working practices.
Operational Impact
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
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.