Technology Category
- Application Infrastructure & Middleware - Middleware, SDKs & Libraries
- Sensors - GPS
Applicable Industries
- Life Sciences
- Pharmaceuticals
About The Customer
Ferring Pharmaceuticals is a biopharmaceutical company founded in 1950. The company is focused on developing products for reproductive health, urology, gastroenterology, endocrinology, and orthopedics. Based in Saint-Prex, Switzerland, Ferring has production sites in several countries including Argentina, China, Czech Republic, Denmark, Germany, Israel, Mexico, Scotland, and Switzerland. The company has a market presence in 60 countries and employs 5,000 people worldwide. Over the years, Ferring has become a pioneer in developing and selling pharmaceutical products based on natural, pituitary-produced peptide hormones. Today, Ferring conducts research and development in collaboration with scientific institutes, biotechnology firms, and other pharmaceutical companies globally.
The Challenge
Ferring Pharmaceuticals, a biopharmaceutical company based in Switzerland, was grappling with an inefficient, paper-based travel approval process. The company's employees found the process stressful and time-consuming, often leading to backlogs and delays in approvals. The manual process was not only slow but also prone to errors, causing further delays. Managers could only approve travel requests when physically present in the office, leading to last-minute approvals, sometimes just hours before the scheduled travel. Additionally, the administrative staff faced difficulties in producing documentation for reports or compliance audits as all travel paperwork was stored as hard copies. The company needed a solution that would digitize and automate its travel approval workflows, enable remote approvals, and simplify the process of searching for and accessing documentation.
The Solution
Ferring Pharmaceuticals turned to the Nintex Platform to digitize its travel approval process. The company implemented Nintex Workflow and Nintex Forms, which eliminated manual request processes, removed paperwork bottlenecks, and enabled managers to approve requests quickly from any location. Nintex Workflow is an easy-to-use workflow designer that improves business processes and delivers a rapid return on investment. Nintex Forms is a web-based designer that allows for the quick and easy creation of forms within SharePoint. Ferring designed and built a SharePoint library for travel approvals, and used Nintex Workflow and Nintex Forms to facilitate submission and approvals. This solution not only automated the process but also improved data accuracy.
Operational Impact
Quantitative Benefit
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.