下载PDF
Mankind Pharma uses information insight to create growth opportunities
技术
- 功能应用 - 企业资源规划系统 (ERP)
- 分析与建模 - 实时分析
- 处理器与边缘智能 - 嵌入式和边缘计算机
适用行业
- 药品
适用功能
- 离散制造
- 采购
- 产品研发
用例
- 预测性维护
- 库存管理
- 供应链可见性(SCV)
服务
- 云规划/设计/实施服务
- 数据科学服务
- 系统集成
挑战
Mankind Pharma 是印度发展最快的制药公司之一,由于其广泛的业务运营缺乏可视性和整合性,因此面临挑战。由于缺乏统一的方式来控制和监控业务活动,决策者很难获得优化运营和制定相应战略所需的可靠见解。这阻碍了该公司充分利用印度蓬勃发展的制药市场的增长机会。例如,招募新的运输和货运代理需要数周时间,而在此期间,可能会错过宝贵的扩张机会。
关于客户
Mankind Pharma 是印度增长最快的五家制药公司之一。该公司成立于 1995 年,拥有 11,000 多名员工,营业额超过 5.6 亿美元。作为一家综合性制药公司,Mankind Pharma 拥有一个由 16 家制造厂、59 家运输和转运 (C&F) 代理商和 7,500 家经销商组成的综合网络。该公司希望充分利用印度蓬勃发展的医药市场中的机会,预计到 2018 年,该市场的规模将超过 470 亿美元。
解决方案
Mankind Pharma 决定将其业务统一到集成 SAP 应用程序上,这些应用程序运行在领先的 IBM 服务器和存储技术上。该公司与 IBM 全球商业服务部合作,在短短七个月的紧张实施时间内将 100 多个实体整合到单个 SAP ERP 平台上。整个基础设施由 IBM 全球技术服务部专业管理,提供最佳可用性和可靠性,同时使 Mankind Pharma 免于系统维护的费用和工作量。新解决方案提供了前所未有的业务活动可视性,并将规划准确性提高了 40%,帮助团队做出更明智的决策。
运营影响
数量效益
相关案例.
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.