Beximco Pharma

Leading producer and exporter of pharmaceuticals in Bangladesh is Beximco Pharmaceuticals Limited. When the company was first incorporated in 1976, it began by importing and selling goods from Bayer in Germany and Upjohn in the United States. Beximco Pharma began producing these goods under a licensing agreement in 1980, and the business introduced its own formulation trademarks in 1983. Beximco Pharma has developed steadily since its small beginning. being shipped now to more than 50 nations, including the highly regulated markets of the United States, Europe, Canada, and Australia.

They have bought Synovia Pharmaceuticals and Novista Pharmaceutical. Fusion Infotech got awarded with system migration converting SAP to Oracle as beximco is the mother company. This is a very sizable enterprise-level project that must be finished with allotted resources in a specific amount of time.

Due to its magnitude, managing and monitoring this project was exceedingly challenging. The project’s scope includes 20+ Technologies and 12 Functional Tracks that are further divided into 50+ Functional Sub-tracks.

For the project, more than 1300 high-level change requirements were found, and these requirements were divided into functional tracks and functional sub-tracks. 

Keeping real-time information accessible for teams was a significant problem because the project was being carried out in distributed setting with huge teams 

The organization used a variety of tools that operated independently with no integration to manage the project lifecycle.

For this Project, it was extremely important and difficult to complete all Lifecycle Phases (Planning, Design, Build, Test, and Deployment) on time. A crucial component of this project is the AP Requirements. Different Project Teams were established for each Functional Track and Functional Sub-Track, and they were tasked with gathering data regarding the variations between the current Oracle system and the suggested SAP system. The Kovair ALM Studio Requirements Management module then classified all of these details as “GAP Requirements.” Information was kept throughout the lifespan, including Business Requirement, Solution in Existing Template, Proposed Solution, Owners, and Disposition Methods.