Integrating ERP and Manufacturing in Pharma

Oct. 1, 2008
The pharmaceutical industry has been aggressive in sharing data between enterprise resource planning (ERP) systems and manufacturing systems.

The reasons for integrating business systems with the plant include inventory management, the delivery of orders from the ERP to manufacturing, quality monitoring, work status, recipe transfer and asset management. Recently, regulatory control has become part of the mix. ERP systems now manage manufacturing data needed by regulatory bodies.

Unlike most industries in which leading, large manufacturers are the ones that are sharing data between the plant and the enterprise, the pharma industry is widely adopting integration as a way to streamline operations and ensure compliance. The integration is being used to collect plant data, as well as to send ERP data down to the plant. AMR Research Inc., in Boston, offers a breakdown of industry adoption of plant-ERP integration. While most of the data flow is from the plant to the enterprise system, there is also a counter flow from the ERP to the plant.

• 59% of pharma manufacturers now send automated inventory updates from the plant to the ERP system.
• 54% use automated communication of production orders from the ERP system to the manufacturing system.
• 39% use automated quality updates from the manufacturing system to the ERP system.
• 34% are sending automated updates from the plant to the ERP system on work-in-progress.
• 30% synchronize recipes between the ERP and manufacturing systems.
• 24% of plants communicate equipment availability from the plant to the ERP system.

Related Feature - Sending Plant Data to the Enterprise System
To read the feature article relating to this story, go to www.automationworld.com/feature-4623

Sponsored Recommendations

Optimize food production with SEW-EURODRIVE’s hygienic, energy-efficient automation and drive solutions for precision, reliability, and sustainability.
George Reed, with the help of Factory Technologies, was looking to further automate the processes at its quarries and make Ignition an organization-wide standard.
Goodnight Midstream chose Ignition because it could fulfill several requirements: data mining and business intelligence work on the system backend; powerful Linux-based edge deployments...
In the automation world, the Purdue Model (also known as the Purdue reference model, Purdue network model, ISA 95, or the Automation Pyramid) is a well-known architectural framework...