The I/O list is the foundational document of every SCADA project. Everything else — loop sheets, tag databases, alarm philosophies, commissioning checklists — flows from it. Yet most engineers either include too little (leaving gaps that cause rework) or too much (creating a document nobody maintains). This guide covers what belongs in an Ignition I/O list and why each column matters.
Body paragraph text goes here. Use bold for emphasis and inline code for technical terms, tag names, file paths, or commands.
Content under the sub-heading.
Warning label: Callout text goes here. Use for important notes, caveats, or things that commonly go wrong.
Best practice: Green callout text goes here. Use for recommended approaches or tips.
Critical: Red callout text goes here. Use for serious mistakes to avoid or compliance risks.
| Column 1 | Column 2 | Column 3 |
|---|---|---|
| Row 1 Col 1 | Row 1 Col 2 | Row 1 Col 3 |
| Row 2 Col 1 | Row 2 Col 2 | Row 2 Col 3 |
| Row 3 Col 1 | Row 3 Col 2 | Row 3 Col 3 |
# Comment line keyword/value/path another_key = "string value" # inline comment
The PROMEC Documentation Generator automates I/O list creation — import your Ignition gateway CSV export and generate a fully structured, formatted I/O list in minutes. Join the waitlist for early access and 3 months free at launch.
Published by PROMEC Systems · promecsystems.com · Based on Ignition 8.1. Naming recommendations reflect best practices from production SCADA deployments across generation, transmission, and process industries.