Building the Next-Gen Pharma Supply Chain Software

Building the Next-Gen Pharma Supply Chain Software

Building the Next-Gen Pharma Supply Chain Software

One dashboard. Every answer.

One dashboard. Every answer.

One dashboard. Every answer.

Duration:

Duration:

Aug 2024 - Dec 2024 (5 months)

Aug 2024 - Dec 2024 (5 months)

Role

Role

Supply Chian Trainee

Supply Chian Trainee

Company :

Company :

Aurigene Pharmaceutical Services (Dr. Reddy Labs Subsidiary)

Aurigene Pharmaceutical Services (Dr. Reddy Labs Subsidiary)

Status:

Status:

In Development

In Development


Project Context


Aurigene Pharmaceutical Services is a CRO & CDMO serving global pharmaceutical companies. In this space, time is everything. A delayed shipment or missing compliance document can halt production and impact client deliveries.

When I joined, the company used SAP for purchase orders and requisitions, but everything else was manual. Logistics teams coordinated vendor pickups through calls and emails. R&D raised material requests that required multiple manual approvals. Quality teams tracked compliance documents separately. Finance processed invoices independently. Every handoff between teams required manual follow-up, creating bottlenecks and delays.

The company was building integrated software to automate these disconnected workflows: real-time shipment tracking, automatic notifications when materials are ready, digital GRN generation, and seamless coordination across procurement, logistics, quality, and finance.

Aurigene Pharmaceutical Services is a CRO & CDMO serving global pharmaceutical companies. In this space, time is everything. A delayed shipment or missing compliance document can halt production and impact client deliveries.

When I joined, the company used SAP for purchase orders and requisitions, but everything else was manual. Logistics teams coordinated vendor pickups through calls and emails. R&D raised material requests that required multiple manual approvals. Quality teams tracked compliance documents separately. Finance processed invoices independently. Every handoff between teams required manual follow-up, creating bottlenecks and delays.

The company was building integrated software to automate these disconnected workflows: real-time shipment tracking, automatic notifications when materials are ready, digital GRN generation, and seamless coordination across procurement, logistics, quality, and finance.

My Role

I analyzed how the supply chain works today. That meant understanding what happens when team requests materials, how buyers process those requests, how logistics arranges vendor pickups, and how each team coordinates with others.

I documented these workflows step by step, identifying where manual coordination created delays. For example: when R&D raises a material request, who approves it? When logistics schedules a pickup, who needs to be notified? When a shipment arrives, how does quality get alerted to inspect it?

I worked with stakeholders across R&D, procurement, logistics, stores, and finance to understand their specific needs and pain points. This documentation informed the engineers building the software about what each team requires from the system. The work was unglamorous but necessary. Before anyone builds software, someone has to map the messy reality of how things work today.

I analyzed how the supply chain works today. That meant understanding what happens when team requests materials, how buyers process those requests, how logistics arranges vendor pickups, and how each team coordinates with others.

I documented these workflows step by step, identifying where manual coordination created delays. For example: when R&D raises a material request, who approves it? When logistics schedules a pickup, who needs to be notified? When a shipment arrives, how does quality get alerted to inspect it?

I worked with stakeholders across R&D, procurement, logistics, stores, and finance to understand their specific needs and pain points. This documentation informed the engineers building the software about what each team requires from the system. The work was unglamorous but necessary. Before anyone builds software, someone has to map the messy reality of how things work today.

SHHH... IT'S A SECRET

Although I can't share the details of my project publicly, if you are interested in learning more about my experience please send me an email.

SHHH... IT'S A SECRET

Although I can't share the details of my project publicly, if you are interested in learning more about my experience please send me an email.

Let's Connect!

Let's Connect!

👋🏽 Thanks for stopping by! Here is more of me if you are interested :)

👋🏽 Thanks for stopping by! Here is more of me if you are interested :)

👋🏽 Thanks for stopping by! Here is more of me if you are interested :)

👋🏽 Thanks for stopping by! Here is more of me if you are interested :)

6:28 AM