Develop A Framework For Improvement In Pharmaceutical Erp System Using Design Pattern

Abstract Applications have importance in software Engineering. The same is true for ERP system in pharmaceutical. In current days Pharmaceutical companies working in ERP system, which have same look and feel. This similarity motivates us to develop framework for pharmaceutical ERP System. Traditional Pharmaceutical ERP System have same nature but ERP system developers not familiar with knowledge used in pharmacy system and this traditional approach does not support reusability and extendibility. Design pattern main feature is to provide reusability and extendibility. So, our motive is to use design pattern to develop framework for Pharmaceutical ERP System

1.         Introduction

Basically work in ERP system in pharma storage department production /manufacturing, financial, Human Resource department design a specific framework using design pattern. A Design pattern is not a finished design that can be transformed directly into the code. It is template for how to create solution for given problem in given context. This paper includes Comparative analysis of maintenance cases and a design framework based on study results. Enterprise Resource Planning (ERP) solution designed to meet the requirements of fast growing pharmaceutical enterprises. The solution enables pharmaceutical enterprises to define a flexible systematic approach to monitoring and improving their performance in the industry. the pharmaceutical industry needs an ERP application that effectively integrates the functions and data of all departments

Planning of the Resources of an Enterprise. Resources mainly comprise four m’s—man, machine, material and money. The optimum utilization of these resources will result in higher efficiency and better performance. The need is of accurate information and effective decisions. We have to increase the level of computerization for generating information. What is required is ERP applications that effectively integrates the functions and data of all departments, and reduces redundancy Pharmaceutical companies have typical business processes. The market of products is dynamic with frequent introduction of newer upgrades. There are a lot of regulatory requirements to be complied with and these require extensive control over production, stores, QC processes and data. Hence, ERP is needed to keep track of the data.In addition to strong order-to-cash processing, Enterprise provides tight control over both process and mixed-mode manufacturing environments.

 Enterprise’s planning and manufacturing capabilities offer complete ECN tracking with online approvals, multi-level formula definition and management, batch controls with multiple batch sizes, multi-level yield management, ingredient-based lot control and integrity, lot designation at time of work order creation, finished goods lot control, and the preservation of lot integrity when repackaging or renumbering a given product Pharma Company, production/Manufacturing Department drug manufacturing and. Drug formulation related pharmaceutical base and to provide this information to other department with unified and customized interface. this project help make the material Requisition  and approved material receipt and filling &sealing details cleaning and dispensing process details and row material and packing material details and make the  batch   manufacturing register record the all activity drug manufacturing activity And to automate all the working procedures of different departments maintain a single common database of

Pharmacy company Production/ Manufacturing Management All work perform in Pharma Company manually Production/manufacturing Coming out the problem for manage all resources they can not properly coordinating all department Related to production activity.The project  manage the all activity related to production department of Pharma company this  is concern with the development of a  application that helps remove the manually work  and that project more help production manager appropriate activity related to production simply find out and properly co-ordinate all department of pharmacy company . Remove the all manually work throw this software etc. 

2.         Overview Of Design Patterns

Design pattern as the general outline of a solution to a commonly occurring problem that can be reused over and over. A design pattern has four essential elements:

ü      a pattern name that allows efficient communication about the pattern—in fact, we will be referring to patterns by name in the balance of this paper,

ü      a problem statement that describes in general terms when to apply the pattern,

ü      a solution that "describes the elements that make up the design, their relationships, responsibilities, and collaborations," and

ü      Consequences of applying the pattern, including tradeoffs.

Using design patterns often incurs costs in terms of space and time, but increases the flexibility, extensibility, and maintainability of the system. There are three varieties of patterns Creational, Structural, and Behavioral. Creational patterns separate the creation of objects or classes from their use in the system. For example, Builder separates the construction of a complex object from the creation of the simpler components that comprise it. In particular, one creates an interface Builder with a method to build each type of component. Concrete subclasses build components for the specific system. A Director calls the Builder to create the components needed for a complex object. Structural patterns provide ways to combine classes or objects into larger structures. Many of these patterns provide a uniform interface between a complex object or class structure and the rest of the system. For example, the Adapter pattern converts the interface of a server class to the interface that its clients expect. This allows the developer to easily adapt the system to different server classes. Another structural pattern, Proxy, represents a surrogate that controls access to another object. Proxies have multiple uses, including allowing requests to a real object in a different address space (remote proxies), caching information about the real object to postpone accessing it (virtual proxies), or Enterprise  ERP software provides complete compliance management for pharmaceutical manufacturers and distributors. delivers a fully-integrated ERP software solution that is both functionally rich and designed to support of the pharmaceutical industry’s business software requirements .Enterprise enables pharmaceuticals manufacturers and distributors to produce and ship the right product, at the right time, and in full compliance with regulatory agencies. The object-oriented design pattern introduced in this paper uses the notion of organizational system as a vehicle for obtaining a better comprehension of a continuous process  application domain. It provides a framework for representing the application domain from a systemic point of view. The pattern is a reusable set of generic classes that can be specialized or used as templates for accommodating the specific requirements of particular application in the domain of continuous production industries. Using our design pattern has the following

benefits:

ü       A better understanding of the ends, process, actors, rules, job structure, events and entities of a continuous process system is achieved.

ü      The role of a continuous process application is understood from a major and wider business perspective.

ü      It reduces the cost and time needed for developing a continuous process application.

Although the pattern is oriented to continuous process applications in industrial Organizations, it could be adapted to be used as a reference framework for

ü      organizational modeling in Business Process Reengineering

ü      designing information systems architectures  and

ü      designing enterprise integration models .

Design patterns mean that we do not have to solve every problem from “first principles”, but can instead rely on the experience of others who have come up with reusable solutions Despite the versatility of most known Pharma ERP software systems there are situations where companies still use legacy applications. Similar situations grow from new business needs based on contemporary tehnologies not covered by ERP software that must be build from the scratch as new applications. All these software packages must be integrated in order to cut data redundancy and to form one hnctional system. A major programming language representative for the former could be C#.Net  Pharma  ERP software is supposed to be treated as the central point inside company's software so one should know that its integration implies adapting other software to fulfill ERP's specifications. This is consequence of complexity of ERP system, especially MRP (Manufacturing Resources Planning) and MPS (Master Production Scheduling) modules.They have to consolidate oscillations in supply chain management by balancing demand and production. Demand enters system through forecasted and actual sales. According to demand system plans production which then backflushes to purchasing. If any of these subsystems is realized outside ERP e.g. Order Fulfillment via Internet (e-commerce) it has to be aligned to ERP, othervise MRP I1 module can not work. Therefore. it could be a good idea that legacy applications integration must be foregone by their reengineering, thereby procedural code will be mapped into design artifacts. Today's favorite design artifacts are design patterns and as the programming paradigm is object oriented they are mainly expressed in that way. Some experiences about reengineering legacy application using design patterns can be found there exist different approaches, for instance, in case of Tim constraints when reengineering is out of question and in case of object-oriented technology lack of skills also pays its tribute. One can design simple but only one purpose solution that is bound to single ERP and its DLL. Again we propose applying design pattern but in this case more exactly, design patterns known as Builder, Factory Method and Bridge.We see their role as a mechanism to widening functionality to more ERPs where appropriate design patterns, among their others functions, encapsulate DLL from different ERPs in a uniform way Such an extension is treated as a wrapper around designated ERP but could be easily modified for another ERP. That gives better Market  prospect in comparison to single ERP solution. The same packaging principle gives excellent results on the other side of integration (e.g. legacy and new applications).  

presents insight into nominated packaging systems. i Introduction /The Internet as a global network and local networking known as corporate Intranets ask for modified approach in an application design. One of the most obvious characteristics of such applications is a heterogeneous environment. It is understandable that in such environment applications also could be distributed. In a modern, object-oriented approach they consists of objects that communicate regardless of their location, platform and development language.teams in different programming languages but supported by appropriate ORBS. Those hybrid integrated systems have positive attributes as intermediary solutions but in depth reengineering of legacy applications is almost unavoidable when those systems are planned to function for longer period of time.A final result should be a system mainly consisting of abstract classes where concrete classes are subclasses of particular abstract classes. Collaboration between all those classes makes system adaptable/configurable to many situations. The classes with their collaborations form structure called a framework. Designing the framework assumes detailed knowledge about the application domain. This knowledge must be formalized and systemized in modules which will describe elementary ideas that will form simple reusable software components known as Design patterns.Basically a common technique of system integration compares them according to the waste and flexibility. Waste presents the amount to which integration method adds overhead, errors and information transfer delays. Flexibility presents capability of integrated information system to adapt various business and organizational changes.“People and paper” are still used as “integration techniques’’ especially during transition phase. It is slow, error prone and expensive, yet highly flexible. It is therefore recommended during periods of finding the right answer for integration issues. File transfer is data oriented approach in which loader-generator interaction is started periodically (manually or timer-based). The process is not performed in real time and systems are isolated with periodic data synchronization. Transfer file formats are adapted to organization needs or standard. In this category we can also put data synchronization through database replication. Such way of data interchange can be slow and inefficient with higher volume of data. It may be enhanced by using database triggers and get near real time performance. However this requires detailed knowledge of ERP database structure because it can corrupt overall system performance. 

3.         The O-O Design Pattern

The central component of our design pattern is the process associated with a production unit. A continuous production process is a composite object whose components are other processes which, in turn, are made of sub-processes at a lower level. A transformation process, for instance, is a composite process that can be decomposed into a hierarchy of processes at  several levels of depth. The processes of a production unit are of three different types or classes : decision making processes, transformation processes and information processes. A unit has a decision making process (DMP) that supervises a transformation process by means of the information managed and provided by the information process. A DMP regulates a transformation process by setting production constraints. An information process is updated by a transformation process. decision systems must work according to those changes. The information system must provide updated information to the decision support systems and must transmit the decisions to the actors that drive the process by using the channels of the information system.

Seven Proposed design patterns for implementing Pharma ERP system are as follows:- 

1  Interface : Can be used to design a set of service provider classes that offer the same service so that a client object can use different

classes of service provider objects in a seamless manner without having to alter the client implementation

2 Abstract parent class: Useful for designing a framework for the consistent implementation of the functionality common to a set of related class.

3 Private methods: Provide a way of design a class behaviour so that external objects are not permitted to access the behaviour that is meant only for the internal use.

4 Accessor  methods: Provide a way of accessing an objects state using specific method .This approach discourages different client object from directly accessing the attributes of an object, resulting in a more maintainable class structure.

5 Constant data manager :Useful for designing an easy for maintain ,centralized,repository   for the constant data in an application.

6 Immutable object: Used to ensure that the state of an object cannot be changed may be used to ensure that the concurrent access to a data object by several client object does not result in race conditions.

7 Monitor: A way of designing an application object so that it does not produce unpredictable when more than one thread tries to access the object at the same time in a multithreaded environment. 

In this paper forces the following point

The design solution for object communication must resolve the following forces:

Encapsulation.  Distributed communication issues should be encapsulated from the functionality. 

Classes. Distributed communication should be transparent for functionality classes, the object-oriented interaction model should be preserved.

Extensibility. The solution should be extensible to the variations described in the problem analysis section. .

Modularity. Distributed communication should be separated from application functionality. In Particular, the underlying communication mechanisms should be isolated and it should be possible to provide different implementations.

Reusability. The solution for distributed communication should be reusable in different situation      

When grouped together, these variations form part of a cluster of patterns that visually represents common approaches to copying data. Clustering, used in this context, simply means a logical grouping of some set of similar patterns and their relationships. Usually the relationship is one of refinement, as shown above. Other relationships can be added, however. This guide adds a relaxed relationship, which means "can use, but there is no refinement between the patterns. This notion of a cluster is quite useful for expanding the view of patterns to encompass an entire solution, and for identifying clusters of patterns that address similar concerns in the solution space.