This is a ready-to-use standard operating procedure governing a virtual or remote person-in-plant (PIP) oversight setup, the camera feed, screen-share session, and remote electronic batch record access a virtual PIP relies on. It applies before a virtual or hybrid oversight model is used for any GMP-relevant campaign; it does not replace the Person-in-Plant Program SOP, which governs the PIP role itself. Replace every <<FILL: ...>> placeholder. A filled specimen follows.
Document control header
| Field | Entry |
|---|---|
| Document title | Virtual PIP Oversight Data Integrity SOP |
| Document number | <<FILL: e.g. SOP-QA-0158>> |
| Version | <<FILL>> |
| Effective date | <<FILL>> |
| Supersedes | <<FILL: prior version or "None, initial issue">> |
| Owner | <<FILL: e.g. Head of Quality>> |
| Applies to | <<FILL: every virtual or hybrid PIP oversight assignment at any CDMO>> |
1. Purpose
This SOP defines how a virtual or remote PIP oversight setup is qualified before use and operated during a campaign, so that a camera feed, screen-share session, or remote electronic batch record connection produces trustworthy real-time observation rather than an unverified data stream with no defined retention, access control, or interruption response.
2. Scope
This SOP applies to every virtual and hybrid PIP assignment at every contract manufacturer, covering the video or screen-share feed used for real-time floor observation and any remote read access to an electronic batch record or other GMP system granted to a PIP. It does not cover on-site-only assignments, and it does not grant a PIP write access to any CDMO system under any circumstance.
3. Responsibilities
| Role | Responsibility |
|---|---|
| Sponsor quality unit | Owns this SOP; defines the access, retention, and qualification requirements a virtual oversight platform must meet before use |
| CDMO information technology function or platform vendor | Implements and maintains the feed and access controls; produces the audit trail showing who accessed what and when |
| Person-in-plant (PIP) | Confirms the setup is qualified before the first login of a new campaign; treats a feed interruption as a real event requiring the defined response, not a technical inconvenience to note in passing |
| Sponsor technical operations / manufacturing lead | Selects the virtual or hybrid model per campaign and confirms the qualification record is current before approving it |
4. Definitions
| Term | Definition |
|---|---|
| Virtual oversight | Real-time observation of a manufacturing step through a video or screen-share feed, without the PIP physically present in the room |
| Read-only access | System access that allows viewing an electronic batch record or other GMP record without any ability to create, modify, or delete an entry |
| Feed interruption | Any loss, freeze, or material degradation of the video or screen-share connection during an observed step |
| Qualified setup | A virtual oversight configuration that has passed the verification steps in Section 5.1 before being relied on for a live GMP campaign |
5. Procedure
5.1 Qualifying a virtual oversight setup before first use
- Confirm camera placement and resolution against the specific critical steps the PIP will be verifying for this campaign, a label check or a line-clearance confirmation needs a close, legible view, not a wide angle that merely includes the area. Document the confirmation with a still image or short recording taken during setup.
- Confirm electronic batch record access granted to the PIP is read-only, individually attributed to that PIP’s own login, and scoped to only the records relevant to the campaign. Reject any access request broader than this.
- Confirm the PIP’s remote access itself generates an audit trail entry, showing who accessed which record and when, consistent with the same electronic-record expectation applied to any other GMP system user.
- Load-test the feed under real production network conditions, not an office demonstration, and record the measured latency. Confirm the measured latency is tolerable for the fastest manual step the PIP will be observing; if not, do not proceed with virtual oversight for that step without an on-site fallback.
- Confirm and document the interruption response per Section 5.3 has been reviewed with the CDMO’s floor quality representative before the first batch of the campaign.
- Record the completed qualification in the campaign’s oversight plan before virtual oversight begins. Do not begin a campaign on an unqualified setup regardless of schedule pressure.
5.2 During a virtual oversight session
- Confirm at session start that the feed shows the intended view and that electronic batch record access, if used, functions as expected before the observed step begins.
- Observe against the batch record and campaign plan; document contemporaneously, the same as an on-site assignment, per the Person-in-Plant Program SOP.
- Log out of any remote electronic batch record access at the end of each session; do not leave a live, unattended remote session open between observation periods.
5.3 Responding to a feed interruption
- If the feed drops, freezes, or materially degrades during an observed critical step, immediately contact the CDMO’s floor quality representative to pause the step until the feed is restored, where the process allows a pause.
- Where the step cannot be paused, log the interruption, start time, restoration time, and the specific step affected, as a documented oversight gap in the visit report, independent of whether the step later appears to have gone correctly.
- Never treat an unobserved window as equivalent to an observed one; a batch record showing a step occurred during a feed interruption with no PIP observation is not evidence the PIP verified it.
6. Acceptance criteria
A virtual oversight assignment meets this SOP’s bar when: the setup was qualified per Section 5.1 before the first batch of the campaign; every electronic batch record access granted to the PIP was read-only and individually logged; every feed interruption during an observed step was logged per Section 5.3 rather than passed over silently; and no remote session was left open unattended between observation periods.
7. Records generated
| Record | Retention | Location |
|---|---|---|
| Virtual oversight setup qualification record | <<FILL: matches the associated campaign's oversight plan retention>> | <<FILL: document management system>> |
| Audit trail of PIP remote electronic batch record access | <<FILL: per the electronic system's own retention configuration>> | <<FILL: electronic system's audit trail module>> |
| Feed interruption log entries | <<FILL: matches the associated visit report retention>> | <<FILL>> |
8. References
21 CFR Part 11, Electronic Records; Electronic Signatures. FDA guidance, “Data Integrity and Compliance With Drug CGMP” (December 2018). Person-in-Plant Program SOP.
Confirm the current version of each reference before issue.
9. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL>> | <<FILL>> | Initial issue. |
10. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (Quality Assurance) | <<FILL>> | ||
| Reviewer (Information Technology or platform vendor liaison) | <<FILL>> | ||
| Approver (Head of Quality) | <<FILL>> |
Filled specimen
Extract for Acme Therapeutics’ virtual oversight setup at Beacon Cell Processing for a hybrid-model PIP assignment.
| Field | Entry |
|---|---|
| Document number | SOP-QA-0158, version 1.0 |
| Camera qualification | Fixed camera on the fill suite’s line-clearance station confirmed to resolve label text at 1.5 meters; still image captured 2026-09-20 and filed with the campaign oversight plan |
| Electronic batch record access | Read-only login issued to PIP J. Alvarez, scoped to the current campaign’s batch records only, audit trail confirmed to log each session’s start and end time |
| Latency test | Measured at 1.8 seconds under production network load, accepted as tolerable for the changeover steps observed; fill-pump start, a faster manual action, retained on-site observation instead |
| Interruption event | Feed dropped for six minutes during a planned changeover on batch 2; changeover paused per the agreed response until the feed was restored; logged in the visit report as a documented gap, changeover re-verified against the completed electronic batch record once the feed returned |
Common inspection findings this SOP prevents
- A virtual oversight platform used for a live campaign with no qualification record showing camera placement, access scope, or latency were ever verified.
- PIP electronic batch record access broader than read-only, or shared under a generic login rather than individually attributed.
- A feed interruption during a critical step passed over with no log entry, leaving a batch record that implies observation occurred when it did not.
- A remote session left open and unattended between observation periods, with no record of when access actually started or ended.
How to adapt this SOP
- Set your document number, owner, and applies-to scope in the header.
- Confirm your own electronic batch record system’s access control model actually supports a scoped, read-only, individually attributed login before committing to this procedure.
- Set real retention periods in Section 7 that match your document management and electronic system’s actual configuration.
- Confirm the interruption response in Section 5.3 against your own process’s actual ability to pause a given step; some steps cannot pause, and the SOP should say so explicitly for those cases.