Reference Manual · Publication PROCES-RM013 · Rockwell Automation

PlantPAx Process Objects Logic Reference

Logic-level companion to the PlantPAx Process Objects Library — documents the internal ladder logic and structured text inside every P_ Add-On Instruction (AOI). Where PROCES-RM002 is the user-facing reference (input/output parameters, faceplate operation, command-source arbitration), PROCES-RM013 is the implementation reference: the actual ladder rungs and ST routines that sit between each AOI's public interface and the wrapped raw Logix instruction. Audience is engineers who need to audit, troubleshoot, customize, or recreate AOI behavior — for SIL / safety review, site-specific extensions, or migration to a custom framework. Covers the full library: analog I/O AOIs, discrete I/O AOIs, motor and valve AOIs, P_PIDE PID wrapper, dosing and sequencing AOIs, interlocks and permissives, command-source arbitration, alarm framework integration, and the diagnostic / runtime tracking blocks.

Download PDF
PROCES-RM013 Publication
436 Pages
All P_ AOIs Coverage
PROCES-RM002 Companion to

Document Preview

Open the full PDF in a new tab  · Publication PROCES-RM013

Catalog Number Format

How to read an Allen-Bradley PROCES catalog number. Each position encodes a specific configuration attribute.

Position
Meaning
Example
PROCES-RM013
Rockwell publication number — Reference Manual for the Process Objects logic-level reference
PROCES-RM013 (current revision)

Document Contents

Full PDF covers the following topics in detail:

  • Internal ladder + structured-text source listing for every P_ AOI in the library
  • Cross-reference between AOI public interface (PROCES-RM002) and the wrapped raw Logix instruction
  • Command-source arbitration logic implementation (Operator / Program / External / Maintenance / Override / Out of Service handling)
  • Alarm-framework integration patterns: how each AOI emits to FactoryTalk Alarms & Events
  • Interlock and permissive evaluation logic across the library
  • Audit-trail documentation suitable for SIL or compliance review
  • Customization touchpoints: where to add site-specific extensions without breaking the AOI signature
  • Faceplate-to-AOI binding patterns for FactoryTalk View SE and ME runtime

Frequently Asked Questions

When do I need PROCES-RM013 instead of PROCES-RM002?
PROCES-RM002 is the user-facing reference — input/output parameters, faceplate behavior, command-source operation. Use it when wiring AOIs into a project. PROCES-RM013 is the logic-level reference — the actual ladder/ST that sits inside each AOI between the public interface and the wrapped raw instruction. Use it when you need to troubleshoot unexpected AOI behavior, customize an AOI for a non-standard application, audit the implementation for a SIL review, or document the system for compliance.
Can I modify the AOIs documented in this reference?
Yes — in Studio 5000 the AOI source is editable. Standard practice for any modification is to copy the stock AOI to a new revision (e.g. P_PIDE_v3_06_SiteCustom) so future library updates from Rockwell do not overwrite local customizations. The logic-level detail in PROCES-RM013 is what you reference when planning the modification — the internal logic shows where to safely insert additional rungs without breaking the AOI's public interface or command-source arbitration.
Is the documented logic the same across all PlantPAx Library versions?
No. Each PlantPAx Library release ships with a corresponding PROCES-RM013 revision, and the internal logic of an AOI may change between versions (additions, bug fixes, performance improvements). Always reference the PROCES-RM013 revision that matches your installed PlantPAx Library version — check the AOI revision string in Studio 5000 against the manual's revision history.
Does this manual document SIL safety logic?
No. The P_ AOI library covered here is for general process control, not safety-rated control. Safety AOIs and the underlying GuardLogix safety logic are documented separately. PROCES-RM013 can be useful for general SIL audit by showing the deterministic logic flow inside non-safety AOIs, but it is not itself a safety-certified document.

Disclaimer