Question 1

What specific checks does Patrion perform on PNOZmulti 2 controllers during preventive maintenance?

Accepted Answer

Patrion performs a structured checklist on PNOZmulti 2 devices that includes firmware validation and controlled updates via the PNOZmulti Configurator, verification of project backups, CRC checks of configuration files, inspection of I/O modules and terminal block torque, and battery/RTC condition testing. Engineers execute safety loop tests (E-Stop, STO, guarded gate) to confirm response times and diagnostic coverage meet ISO 13849-1 and IEC 61508 requirements. Network diagnostics for PROFINET/PROFIsafe links and device log harvesting for error counters complete the check. All actions are logged and delivered with a corrective-action plan and configuration snapshots for audit traceability.

Question 2

How often should PSS 4000 systems receive preventive maintenance to remain compliant and reliable?

Accepted Answer

Recommended frequency depends on risk assessment and operating hours, but Patrion typically schedules PSS 4000 preventive maintenance annually for low-risk applications and semi-annually for high-utilization or safety-critical installations. Frequency decisions reference ISO 13849-1 and IEC 61508 lifecycle guidance and consider environmental stressors (dust, vibration, temperature). Interim health checks—network monitoring and log review—are advised quarterly. Maintenance intervals are documented in a safety management plan with metrics (MTTR, fault rate) used to refine inspection cadence.

Question 3

Can Patrion validate that a Pilz system still meets required PL or SIL after maintenance?

Accepted Answer

Yes. Patrion conducts functional verification and validation of safety functions against original design requirements to confirm Performance Level (PL) or Safety Integrity Level (SIL). The process follows ISO 13849-1 and IEC 61508 methodologies: review of the safety requirements specification, re-run of safety-related tests (force-stop, safe-limited speed, STO), diagnostic coverage checks, and proof-testing of redundant channels where applicable. Results, calculations and test records are compiled into a validation report suitable for inclusion in the Safety File.

Question 4

Does the preventive service include network protocol and PROFIsafe diagnostics for Pilz devices?

Accepted Answer

Yes. Patrion’s network diagnostics cover industrial protocols commonly used with Pilz equipment: PROFINET, PROFIsafe, EtherNet/IP, Modbus TCP and OPC UA. Engineers use protocol analyzers and managed switches to inspect packet loss, jitter, topology, and cycle-time compliance. PROFIsafe-specific checks validate safe-channel timing and watchdog behavior. Findings include recommended configuration changes to improve determinism and redundancy. This work is aligned with best practices for network design in IEC/ISA standards, including segregation and cybersecurity considerations per ISA/IEC 62443.

Question 5

How are firmware updates and configuration backups handled to avoid production issues?

Accepted Answer

Patrion follows a staged update workflow: create verified configuration backups (PNOZmulti project files, PSS 4000 program exports), document current firmware and configuration versions, test updates in a lab or virtualized environment where possible, and then apply updates during agreed maintenance windows. Backups are stored with version control and integrity checks; rollback procedures are validated prior to live deployment. For safety systems, engineers ensure that any change is traced in the safety management system and re-validated per IEC 61508 and ISO 13849 before returning the system to operational status.

Question 6

What is included in battery and RTC maintenance for myPNOZ and other Pilz modules?

Accepted Answer

Battery and RTC maintenance includes verifying battery type and expiry per Pilz recommendations, measuring end-of-life voltage and capacity, performing controlled replacement, and validating real-time-clock drift after replacement. Engineers record replacement dates and update configuration backups so timestamp data remains consistent. For modules with non-volatile memory, Patrion verifies integrity post-replacement. Procedures follow manufacturer guidance and are recorded for traceability and compliance with safety lifecycle documentation requirements.

Question 7

How does Patrion implement performance trending and analysis for Pilz safety systems?

Accepted Answer

Patrion collects device logs, error counters, CPU and cycle-time metrics via built-in diagnostics and networked access (OPC UA, Modbus TCP or vendor APIs). Data is aggregated into trending dashboards that highlight fault frequency, communication latency, and I/O failure rates. Engineers analyze trends to identify early degradation, develop preventive interventions and estimate MTBF. Trending outputs can be integrated into a client’s CMMS for automated work-order generation. Analysis adheres to IEC guidance on diagnostic coverage and maintenance planning to support safety and uptime targets.

Question 8

Can preventive maintenance be performed without a full production shutdown on Pilz systems?

Accepted Answer

Often yes, depending on system architecture. Patrion evaluates redundancy, hot-swap capability of I/O modules, and whether the safety controller is in a dual-channel or redundant configuration. For systems with redundant paths (e.g., dual PSS 4000 controllers or segregated safety zones), technicians can sequence maintenance to avoid full shutdown, using lockout/tagout and temporary risk-reduction measures per company procedures and IEC/OSHA requirements. When a shutdown is unavoidable, Patrion coordinates narrow maintenance windows and provides rapid-response crews to minimize downtime.

Platform	Pilz
Service Type	Preventive Maintenance
Key Products	PNOZmulti 2, PSS 4000, myPNOZ

Pilz Preventive Maintenance

What We Deliver

Specifications

Frequently Asked Questions