Acumatica Cloud ERP Provides Foundation to Digitally Transform Pharmaceutical Distributor
Customer Company Size
SME
Region
- America
Country
- United States
Product
- Acumatica Financial Management
- Acumatica Distribution Management
- Acumatica Customer Management
Tech Stack
- Acumatica Cloud xRP platform
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Cost Savings
- Productivity Improvements
Technology Category
- Platform as a Service (PaaS) - Application Development Platforms
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Logistics & Transportation
- Quality Assurance
Use Cases
- Track & Trace of Assets
- Regulatory Compliance Monitoring
Services
- Cloud Planning, Design & Implementation Services
- Software Design & Engineering Services
About The Customer
ProPharma Distribution, LLC is a company based in Westminster, Colorado. They specialize in the wholesale distribution of surgical pharmaceuticals. The company was created to deliver personalized customer service to the surgical care industry, providing medications facilities rely on. ProPharma Distribution initially used QuickBooks but outgrew it and moved to Microsoft Dynamics. However, the company faced challenges with the complex setup of the system and the lack of communication between different elements of the system. They also had to manually track every medication for FDA Pedigree compliance, a complex and error-prone process.
The Challenge
ProPharma Distribution, a pharmaceutical distributor, was facing challenges with their existing system, Microsoft Dynamics GP and CRM. The system was complex and the different elements did not communicate with each other, leading to high labor costs for manual change management. They also faced issues with eConnect, which was added to pass orders from Dynamics CRM to GP to the warehouse. The company also had to manually track every medication for FDA Pedigree compliance, a complex and error-prone process. The legacy system eventually crashed due to a power surge, leading to data corruption and a complete shutdown of the company's operations.
The Solution
ProPharma Distribution implemented Acumatica, a cloud-based platform, to address their challenges. Acumatica provided a stable, reliable, and interconnected platform for growth. The integrated CRM and ERP eliminated the need for add-on pieces that complicated their prior setup with Microsoft Dynamics. Acumatica's mobile access allowed remote salespeople to log in from anywhere with a simple internet connection. Users did not have to limit their use or sign out to allow others to access the system. The company could scale up without having to change anything, they could simply add more users. The biggest benefit would come when DCAA completes the software development to make FDA Pedigree tracking fully digital. Acumatica’s singular Cloud xRP platform and the software’s flexibility make it possible to customize in many ways.
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
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.
