Pipeline SCADA Telemetry Commissioning Checklist

Role: Principal SCADA Systems Integration Engineer specializing in pipeline instrumentation and midstream monitoring.

Context

• Operating Enterprise: {{utility_operator}}
• Physical Corridor: {{pipeline_corridor}}
• Industrial Protocol: {{communication_protocol}}
• Instrumentation Types: {{telemetry_point_types}}
• Maximum Acceptable Latency: {{alarm_latency_limit}}
• Historian Reference: {{historian_tag_database}}

Task

Produce a rigorous field-to-control-room commissioning checklist that validates signal integrity, zero-span calibration, communication failover, and telemetry tag accuracy for field sensors along the designated pipeline.

Method

1. Inspect physical loop wiring and power supplies for {{telemetry_point_types}} along {{pipeline_corridor}}.
2. Verify local transmitter analog output against simulated 4-20mA calibration signals (0%, 50%, 100%).
3. Confirm register mapping and scaling factors between local RTU registers and {{communication_protocol}}.
4. Perform an end-to-end ring check comparing field multimeter readings directly with {{historian_tag_database}} displays.
5. Test safety threshold alarms (Low, Low-Low, High, High-High) to ensure notification within {{alarm_latency_limit}}.
6. Simulate communication failure on the primary link to ensure seamless secondary circuit failover.
7. Document baseline deadband settings and rate-of-change filters.

Constraints

• Each task item MUST specify the responsible role (Field Tech vs. SCADA Console Engineer).
• MUST NOT permit sign-off if analog readings deviate by more than 0.25% from simulated scale values.
• Use standard industrial verification syntax with [ ] checklist boxes.
• Limit total checklist items to between 15 and 20 discrete items across all sections.

Output format

• Section A: Physical Loop & Power Quality Verification (4 checklist items)
• Section B: Calibration & Signal Range Verification (4 checklist items)
• Section C: Protocol & Historian Tag Ring Checks (4 checklist items)
• Section D: Alarm Logic & Communication Redundancy Tests (4 checklist items)
• Sign-off block: Dual-signature verification table

Self-review

• Does the checklist mandate verification against {{historian_tag_database}} for each point?
• Are alarm response times checked explicitly against {{alarm_latency_limit}}?
• Does the method test primary and backup paths over {{communication_protocol}}?