Pharma software development from the ERP to the iPad.
Pharma software development has to work where the work happens: on an iPad in a pharmacy, in the lab, at goods-in. We analyse the process chain end to end and build what is missing.
Judged end to end
We assess the process across everyone involved, from the office through the portal to the pharmacy.
Alongside your ERP consultancy
We work with the consultancy you have and steer between the business, IT and delivery.
Excel is the map
Where people keep their own spreadsheets despite a group ERP, the system is missing a function.
Life sciences software: what we build.
-
The ordering portal that stayed standard
A pharma company runs ordering portals for pharmacies, set up with the SAP toolkit and deliberately left standard. Field sales are meant to operate them on an iPad.
More on this
The portal offers no search by customer number, although the number is held in the SAP online shop. So the rep keeps a spreadsheet of his own. Sign-off happened at a desk; nobody tested with an iPad inside a pharmacy.
-
A thin interface in front of the portal
Search by customer number, name and town, capture the order, hand it over to SAP. The core system stays standard and usability sits in front of it.
More on this
We connect through the existing SAP interface, and to Microsoft Dynamics 365 Business Central the same way. Steering: ERP Project Management.
-
A live test where the work happens
With the device people carry, at the place they use it, on a task from the working day. Two hours in a pharmacy uncover more than a two-week acceptance test.
-
Lab software for inspection records
Capture at the point of work, with mandatory fields, plausibility checks and history. We agree the scope with your QA.
More on this
We build documented, with change tracking, so your review and release processes can work with it. We build; we do not validate. The same patterns in production: Manufacturing & Industry.
-
Replace grown Excel solutions
First understand what the file was built for, then replace it. The domain knowledge inside it is the actual value.
More on this
The same goes for Access applications carrying a core process. How we go about it: Excel and VBA modernization.
Where does your process chain break?
Paper batch records, spreadsheets beside the LIMS, deviations by email: describe the process. We say what can be digitized.
Common questions from pharma and life sciences.
We already have an SAP consultancy. Why do we need you?
For SAP you have the right people. In group projects, though, often nobody owns the process from beginning to end. Every sub-project delivers, and a rep with an iPad still cannot work. That is the gap we fill.
Why not customize the SAP portal itself?
Sometimes that is exactly right, and we say so. Customizing the core system costs money, adds maintenance at every upgrade and takes time. A thin application in front of it can be changed faster as the process develops.
What does a live test on site actually mean?
We come along: to the pharmacy, into the lab, to goods-in, and do a task from the working day there. A test system lacks the conditions under which an application fails: time pressure, poor signal, gloves, somebody waiting.
Can you work in a regulated environment?
Yes, and in practice that is a question of method: documented requirements, change tracking in the application, close coordination with your QA. Which formal records your organization requires is settled before the project starts.
Do you also do serialization and traceability?
We build the applications around it: capture screens, traceability across sites, interfaces to the systems holding the data. The regulatory shape of it stays with your own department.
How quickly do we see an effect?
A process analysis with live tests and prioritized recommendations typically lands within a few weeks. A thin application in front of a portal is quicker, because we develop AI-assisted and keep scope small.
Read on.
Where does your chain break?
Show us the spreadsheets that grew up beside your ERP. We say which point is worth tackling first.
Judged end to end.
Describe the process and where it snags: which system, which role, which device.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.