A pharmaceutical facility monitoring system combines sensors, sample transport, vacuum and power infrastructure, communications, server, database, alarm logic, reports and quality procedures. A screen showing online sensors proves only a small part of intended operation. QA, Engineering and IT must be able to explain how the system is configured, where the original records reside and what happens when a component fails.

The handover package should include the approved URS, scope boundaries, architecture, traceability, sensor and location lists, calibration status, software and firmware versions, configuration baseline, recipes, limits, reports, user roles, data retention, backup, restore, qualification, procedures, training, spares and support contacts. Assumptions and exclusions should be visible.

A disconnected sensor must not appear as a clean zero result. The site should challenge sensor loss, communication failure, vacuum failure, alert and action thresholds, delay, latching, acknowledgement, notification and return-to-normal behavior. Each test should verify the user display, timestamp, stored event and report output.

Time synchronization is essential for investigations. FMS, BMS, production equipment, servers and batch records must support a reliable event sequence. The project should define the time source, timezone, access to time settings and behavior if synchronization is lost.

A successful backup job is not the same as a successful recovery. Restore testing should demonstrate that database records, metadata, audit trails, configuration, users and report definitions can be recovered consistently. Approved recovery time and recovery point objectives should match system criticality and site infrastructure.

Role testing should attempt unauthorized changes to limits, recipes, records and administration. Valid changes should retain identity, timestamp, previous and new values and required rationale. Privileged access needs controlled ownership rather than broad distribution of a shared administrator password.

QA owns intended-use acceptance and quality-system integration; Engineering owns physical instrumentation and maintenance; IT owns infrastructure, access, backup and security; Production owns routine response and process context. Supplier responsibilities must be defined by deliverable and SLA. Open deviations and defects require an explicit risk decision before release.

Particle Measuring Systems describes PharmaceuticalNet Pro as modular environmental monitoring software with configurable components, while official demonstrations include sensor visualization, alarm limits and delays, recipe control, users, backup and archive. Exact functions depend on purchased version, license and configuration. SAO NAM supports PMS Life Science FMS projects in Vietnam within the authorized project and service scope.

The first weeks after go-live should include enhanced review of alarms, communication losses, user errors, cancelled samples, backup jobs and report behavior. Project accounts should be closed or converted to controlled support access. The as-built baseline, approved procedures and training records must match the released system rather than an earlier design snapshot. A defined hypercare period with escalation contacts helps the site resolve defects without bypassing change control. The handover is complete when routine owners can operate, review, recover and support the system using approved records, and when residual project actions have documented owners, due dates and quality decisions.