技术
- 应用基础设施与中间件 - 中间件、SDK 和库
- 传感器 - 全球定位系统
适用行业
- 生命科学
- 药品
关于客户
Ferring Pharmaceuticals 是一家生物制药公司,成立于 1950 年。该公司专注于开发生殖健康、泌尿科、胃肠科、内分泌科和骨科产品。辉凌总部位于瑞士圣普雷克斯,在阿根廷、中国、捷克共和国、丹麦、德国、以色列、墨西哥、苏格兰和瑞士等多个国家设有生产基地。该公司在 60 个国家/地区开展市场业务,在全球拥有 5,000 名员工。多年来,辉凌已成为开发和销售基于天然垂体产生的肽激素的药品的先驱。如今,辉凌与全球科研机构、生物技术公司和其他制药公司合作进行研发。
挑战
总部位于瑞士的生物制药公司 Ferring Pharmaceuticals 正在努力解决效率低下、纸质旅行审批流程的问题。该公司的员工发现这个过程压力很大且耗时,经常导致审批积压和延误。手动过程不仅速度慢,而且容易出错,导致进一步的延误。经理们只能在亲自到办公室的情况下批准差旅请求,从而导致最后一刻才获得批准,有时甚至是在预定差旅前几个小时。此外,由于所有旅行文件都以硬拷贝形式存储,行政人员在制作报告或合规审计文件时面临困难。该公司需要一种解决方案,能够将差旅审批工作流程数字化和自动化,实现远程审批,并简化搜索和访问文档的过程。
解决方案
Ferring Pharmaceuticals 利用 Nintex 平台将其旅行审批流程数字化。该公司实施了 Nintex Workflow 和 Nintex Forms,消除了手动请求流程,消除了文书工作瓶颈,并使经理能够从任何地点快速批准请求。 Nintex Workflow 是一款易于使用的工作流程设计器,可改进业务流程并提供快速的投资回报。 Nintex Forms 是一个基于 Web 的设计器,允许在 SharePoint 中快速轻松地创建表单。 Ferring 设计并构建了一个用于旅行审批的 SharePoint 库,并使用 Nintex Workflow 和 Nintex Forms 来促进提交和审批。该解决方案不仅实现了流程自动化,还提高了数据准确性。
运营影响
数量效益
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.