Conversational Autonomous Robots in GMP Manufacturing | CLS Member Voice
CALIFORNIA LIFE SCIENCES — MEMBER VOICE SAPU Bioscience / Oncotelic Therapeutics
CLS Member Voice Submission

Conversational Autonomous Robots in GMP Manufacturing

Five practical use cases for bringing governed, source-linked information closer to the point of work

By Saran Saund, Chief Business Officer, Oncotelic Therapeutics

The big idea: The next useful application of AI in GMP manufacturing may not be another dashboard. It may be a governed, voice-first interface that retrieves approved information at the point of work, connects each answer to the controlled source, and fits inside a defensible validation boundary.

The practical gap inside digital GMP environments

Anyone who has worked a cleanroom shift knows the moment: gloves on, gown sealed, and you need to check a procedure — but the nearest terminal is two airlocks away. Pharmaceutical manufacturing has gone digital in many ways, but the human interface inside GMP environments has not kept up. Operators in cleanrooms, warehouses, and QC labs regularly need SOPs, batch records, deviation procedures, and safety protocols while gowned, gloved, or simply nowhere near a workstation.

That’s a real problem. The information exists — and it’s usually governed by quality systems — but it is not always reachable at the exact point of work. A fixed terminal, a printed binder, or a call to the supervisor may get the job done, but each one adds friction. And in regulated operations, friction adds up: slower execution, heavier training burden, and documentation practices that are harder to sustain shift after shift.

Start with use cases, not the robot

Nobody needs a generic “robot assistant.” What they need is help with specific, repetitive, quality-sensitive tasks where the operator has to get the right approved answer without breaking the flow of work. Five use cases keep coming up in early GMP conversations:

1
Line clearance and product changeover: read the approved checklist hands-free, show the governing SOP section, accept verbal confirmations, and flag skipped or repeated steps for supervisor review.
2
Material receipt, quarantine, and transfer: guide warehouse operators through label mismatches, CoA checks, hold status, and QA escalation before material enters the process flow.
3
QC sampling and chain-of-custody support: retrieve sampling instructions, prompt container integrity checks, and link the interaction to the controlled source document and relevant form.
4
Training and on-the-floor coaching: provide approved procedural reminders tied to current document versions, reducing variation across shifts without turning AI into a decision-maker.
5
Deviation triage and audit preparation: retrieve immediate containment steps, identify the escalation path, and preserve contextual interaction history for QA review.

These are credible starting points because they map to pain that every GMP team already knows, and they create a natural validation boundary. The system should not release product, approve deviations, or replace QA judgment. It should pull up the right controlled information, present it in context, log the interaction, and route exceptions to the right human.

What a shift could look like

In practice, you would probably start with cleanroom-adjacent and warehouse workflows before moving into higher-classified spaces. The scenarios below are illustrative, but they show why mobility, voice, and source-linked retrieval belong in the same conversation.

1. Incoming material quarantine

A shipment of excipient drums comes in. The warehouse operator is scanning labels when she spots a mismatch on one drum. Normally she’d walk to a terminal or call a supervisor. Instead, she asks the robot stationed in the quarantine zone. It pulls up the relevant section of the controlled warehouse SOP, displays it on screen, and reads the required actions: segregate the drum, apply the hold tag, don’t move it to sampling, and initiate QA review.

The robot doesn’t decide anything. The value is that the operator gets the approved instruction right now, with the source section on screen, while the problem drum is still in front of her. Once the hold is resolved, the same robot can escort the drum to the sampling area — carrying the document trail with it.

2. QC sampling and container integrity

Over in the QC sampling area, a technician is about to open a released raw material drum but wants to double-check the container integrity steps first. She asks the robot. It pulls up the sampling SOP, walks her through seal inspection, lot-number verification, CoA match, and storage-condition check, and shows the relevant form on screen.

This is a natural early use case — repetitive, procedural, and heavy on documentation. If cameras are part of the picture, any image capture should be governed by site policy and should supplement the official sampling record, not replace it.

3. Line clearance and product changeover

This is the one that makes the case by itself. A production operator is fully gowned and about to start line clearance before a product changeover. Her hands are occupied. She can’t touch a screen. She can’t flip a binder.

Operator: “Read me the line clearance checklist for Suite B, product changeover.”
Robot: “Per SOP-PR-008, Section 6.2, Suite B line clearance. Step one: Verify all Product A materials and labels have been removed from the suite. Step two: Inspect all surfaces, equipment, and transfer hatches for residual product. Step three: Confirm cleaning log CR-008B is signed and dated. Step four: Verify environmental monitoring plates have been placed. Shall I continue to step five, or repeat any step?”

This is more compelling than a chatbot on a wall because the operator is walking the suite — checking surfaces at one end, transfer hatches at the other. The robot follows her through each area, reading the next step as she moves. A fixed screen cannot do that.

4. Deviation triage and audit preparation

When something goes wrong on the floor, teams often burn time figuring out what to do first: which containment step, which escalation path, which documents QA will need. A mobile AI interface could pull up the deviation SOP, walk the operator through the immediate actions, and keep a record of the interaction for the investigation file.

This is where the “eyes and ears” of the robot — cameras and microphones — could become genuinely useful. Audio, images, and interaction logs can create real-time context for an investigation. But they can also create regulated records, privacy concerns, and validation obligations. That trade-off needs to be designed, not discovered.

Why voice-first access matters

Voice-first AI fits here because it matches how people actually work on the floor. An operator should be able to say, “What’s the approved cleaning step before material transfer?” or “Which section covers this hold time?” and get an answer that points straight back to the controlled source document.

The key phrase there is “points straight back.” In GMP, an AI system is not a general-purpose adviser and it is definitely not a substitute for QA judgment. Its value lives or dies on whether it can retrieve the right approved source, show where it came from, respect document versions, and stay inside a validated envelope.

Why robotics changes the interface

Adding a robot to the mix gives the AI a body. It can move through the facility, show information on a screen, talk to the operator, and go where the work is — instead of waiting for the operator to come to it. More importantly, it can follow the material. In a typical flow, a drum moves from receiving dock to quarantine hold to sampling suite to released storage. A fixed terminal stays in one room. An autonomous robot can escort the material through each handoff, carrying the relevant document context with it and maintaining a visual chain of custody the entire way. The robot by itself is not the point. The question is whether that kind of continuity — mobility plus governed document retrieval across zones — can reduce friction that no fixed interface ever will.

For most facilities, the realistic starting point is cleanroom-adjacent rather than fully aseptic: warehouse quarantine, QC sampling, training rooms, gowning corridors, material staging, and audit walkdowns. Those environments are demanding enough to generate real feedback while giving quality teams time to figure out cleaning protocols, cybersecurity, access control, and record-management requirements before anyone rolls a robot into a classified suite.

The Oncotelic and TechForce development effort

This is what we are building toward. Oncotelic Therapeutics, through its subsidiary SAPU Bioscience, has signed a Joint Development Agreement with TechForce Robotics to explore this interface for regulated pharma environments. We bring the AI — SAPU’s PDAOAI Cortex platform — and TechForce brings the robots.

PDAOAI Cortex is a retrieval-based AI platform built to query controlled document sets — SOPs, batch records, regulatory references, technical files. In our prototype, the operator speaks a question, the system finds the relevant passages in an indexed document corpus, and a language model generates a spoken and on-screen response. Everything runs on facility-controlled infrastructure, so your regulated documents never leave the building.

TechForce brings the physical layer: autonomous navigation, operator-facing displays, and mobile interaction in real environments. Together, we are testing whether AI-enabled robots can become a practical interface for controlled information — not just a conference demo, but something that works on the floor.

Compliance must be designed in, not asserted afterward

Let’s be direct about this. For pharma manufacturers, the most important question is not whether the system can answer a question during a demo. It is whether the system can be configured, validated, and governed in a way that meets GMP expectations.

Where electronic records or electronic signatures are implicated, 21 CFR Part 11 considerations may include system validation, access controls, audit trails, record retention, authority checks, and change control. Local deployment can help reduce exposure of regulated documents and support data-security objectives, but local deployment alone does not establish compliance. Any production implementation would require site-specific qualification, quality oversight, cybersecurity review, and a clear definition of the system’s intended use.

This is especially important for AI. A credible GMP AI system must distinguish retrieved source content from generated language, avoid unsupported answers, preserve links back to controlled documents, and provide a human-review pathway for decisions that affect quality, safety, or product release.

What needs to be proven

We are not pretending this is ready to deploy tomorrow. Before AI-enabled robotics can move from concept to routine GMP use, the industry needs answers to some hard practical questions: How accurate are responses against controlled documents? How fast? Does voice recognition work in a noisy fill suite? Can you clean the robot to the required standard? Does it play nicely with your existing QMS?

The commercial case needs discipline too. The winning use cases will be the ones where the platform measurably reduces time spent hunting for information, improves training consistency, cuts documentation errors, or speeds up investigations — without compromising quality oversight. Demos are nice. Adoption depends on operational proof and a validation pathway that your quality team can defend to an auditor.

BIO 2026 as a feedback point

We will be showing the joint platform live at BIO 2026 in San Diego — California Life Sciences Pavilion, Booth #1525. You will be able to talk to the robot, see voice-based document retrieval in action, and judge for yourself whether this belongs in your facility. But the real reason we are there is to listen: which use cases matter most to you, what validation requirements keep you up at night, and where the gaps are that we have not thought of yet.

The goal is not to make GMP operations look futuristic. It is to make the right information available, traceable, and usable at the exact moment someone on the floor needs it.

Priority development questions for industry partners

QuestionWhy it matters
Which workflows justify a mobile AI interface?Focuses the platform on operational pain rather than novelty.
What is the intended use under GMP?Defines the validation boundary and prevents compliance overreach.
How are source documents controlled and versioned?Determines whether responses can be trusted and audited.
Where should humans remain in the loop?Protects quality decision-making and avoids unsupported AI delegation.
What measurable outcome will justify adoption?Connects the technology to time savings, training consistency, documentation quality, deviation reduction, or investigation efficiency.

About SAPU Bioscience and Oncotelic Therapeutics: SAPU Bioscience is a subsidiary of Oncotelic Therapeutics focused on AI-powered solutions for pharmaceutical manufacturing and life sciences operations. SAPU is a member of California Life Sciences.

About TechForce Robotics: TechForce Robotics develops and deploys autonomous mobile robots for commercial and industrial applications. Under the JDA, TechForce and SAPU are exploring how robotics and governed AI interfaces may support regulated pharmaceutical workflows.