- What "Six Domains" Really Means for C-309
- Domain 1: Programming Analog Instructions
- Domain 2: Troubleshooting Analog I/O
- Domain 3: Program Control Instructions
- Domain 4: Subroutine Instructions
- Domain 5: HMI Objects That Talk to the PLC
- Domain 6: Information, Diagnostic and Alarm Messages
- How the Six Areas Connect
- Delivery Format and What Is Still Unverified
- Sequencing Your Preparation by Domain
- Where These Skills Get Used
- Frequently Asked Questions
- C-309 here means Programmable Controller Systems 2, issued through the Smart Automation Certification Alliance (SACA).
- Six objectives cover analog programming, analog troubleshooting, program control, subroutines, and two HMI areas.
- The six areas come from preparation-curriculum objectives and are unweighted; don't assume official percentage weights.
- Silver is a proctored online written exam; Gold adds an observed hands-on assessment on SACA-approved equipment.
What "Six Domains" Really Means for C-309
Before diving into content, let's be precise about what this guide covers. C-309 on this site refers to Programmable Controller Systems 2, a credential delivered through the Smart Automation Certification Alliance (SACA). If you're still orienting yourself, the articles What Is C-309? and What Does C-309 Stand For? cover the naming and background in more detail.
The six content areas below are drawn from C-309-coded preparation-curriculum objectives published in public college course documents. Four of them (objectives 309.01 through 309.04) appear in a Lake Land College PLC II course information form, and two (309.05 and 309.06) appear in a Lake Land College HMI course information form. These provider documents reproduce credential-coded preparation standards, but they do not establish the latest issuer exam version.
With that framing in place, here is what each objective asks of a candidate, and what hands-on skills sit underneath it.
Domain 1: Program and Operate a PLC Logic Program That Uses Analog Instructions
Programmable Controller Systems 1 typically lives in the world of discrete signals: on or off, true or false. The first C-309 domain pushes you into continuous values, where a sensor reports a range rather than a state. The objective is to program and operate a logic program, which means both writing it and running it against real or simulated process behavior.
Domain 1: Analog Programming
Candidates should be comfortable moving a raw analog signal through a PLC program and turning it into something meaningful for control decisions.
- How an analog input module converts a field signal into an integer value the processor can use
- Scaling raw counts into engineering units (temperature, pressure, level, flow)
- Comparison and math instructions used to trigger actions at setpoints
- Writing values to analog outputs to drive devices such as valves or variable-speed equipment
- Choosing data types and register addresses that keep scaled values accurate
Concepts worth drilling
Scaling is the heart of this domain. A raw value means nothing until you map it to a real-world range, and the arithmetic must be set up so you don't lose resolution or overflow a data register. Practice working scaling problems by hand: given an input range, a raw count range and a measured count, calculate the engineering value. Then practice the reverse for analog outputs.
Equally important is understanding what happens at the edges. What does your program do when a signal reads below its minimum or above its maximum? Candidates who only memorize instruction names tend to struggle with scenario questions that probe exactly these boundary conditions.
Domain 2: Troubleshoot a PLC Program Application That Uses Analog I/O
Where Domain 1 is about building, Domain 2 is about diagnosing. A technician who can write analog logic but can't figure out why a tank level reading is stuck at zero has only half the skill set employers want. This is also where the written exam is most likely to use scenario-style thinking: a symptom is described, and you decide the most probable cause or next step.
Domain 2: Analog Troubleshooting
Think in layers: field device, wiring, module, configuration, then program logic.
- Separating a sensor or wiring fault from a scaling or logic error
- Recognizing the signature of an open loop, a shorted loop, or a miswired transmitter
- Reading live data values in the programming software to confirm what the processor actually sees
- Checking module configuration for input type and range mismatches (for example, a module set for one signal type while the device outputs another)
- Verifying that scaling constants and data addresses match the intended point
A diagnostic habit that pays off
Work from the field inward or the program outward, but be systematic. A common trap in troubleshooting questions is jumping straight to editing logic when the real fault is a configuration setting or a signal-range mismatch. Train yourself to ask "what is the raw value, and does it make sense for the physical condition?" before touching a single rung.
Domain 3: Program and Operate a PLC Logic Program That Uses Program Control Instructions
Program control instructions govern how and when sections of your program execute, rather than simply reading inputs and driving outputs. This domain is where PLC programming starts to feel like structured software design.
Domain 3: Program Control Instructions
Expect to reason about execution order and conditional execution of program sections.
- Instructions that alter the normal top-to-bottom scan, such as jumps and labels
- Master control-style instructions that enable or disable blocks of logic
- How skipped or disabled code affects outputs, timers, and retained states
- Predicting program behavior when a control instruction is true versus false
- Using program control to support modes of operation (manual, automatic, maintenance)
The conceptual challenge here is the interaction between skipped logic and the state of outputs. When a section of code isn't executed, outputs and timers inside it don't update the way they would in a normal scan. Many candidates lose points by assuming a de-energized section behaves the same as a section whose conditions simply evaluate false. Work through small examples on paper, tracing the scan, until the distinction feels automatic.
For a broader sense of how difficult candidates find the instruction-heavy material, see How Hard Is the C-309 Exam?
Domain 4: Program and Operate a PLC Logic Program That Uses Subroutine Instructions
Subroutines let you break a large program into modular, reusable pieces. This domain tests whether you can structure a program so that a main routine calls dedicated routines for specific tasks, and whether you understand how data and control pass between them.
Domain 4: Subroutines
Modular programming is a real-world maintainability skill, not just an exam topic.
- Calling a subroutine from a main routine and returning control
- Passing parameters into and out of a subroutine where the platform supports it
- When to use a subroutine instead of duplicating logic
- Understanding how a subroutine executes only when called, and what that means for the state of its outputs
- Organizing a program into routines by function (for example, analog scaling in one routine, alarm logic in another)
Notice how Domains 3 and 4 overlap conceptually: both control when code runs. A strong study approach is to compare them side by side, noting that jumps skip ahead within a routine while subroutines transfer control to a separate routine and then come back. Candidates who can articulate that difference clearly usually handle both domains well.
Domain 5: Program and Operate an HMI Project That Uses Objects to Interact With a PLC
The last two domains shift from the controller to the operator interface. A human-machine interface (HMI) gives operators a visual way to monitor and command the process. Domain 5 focuses on objects: the buttons, indicators, numeric displays, and other screen elements that read from or write to PLC data.
Domain 5: HMI Objects
The key skill is linking a screen object to the correct PLC tag or address and understanding the direction of data flow.
- Creating screens and placing objects such as pushbuttons, pilot lights, and numeric entry or display fields
- Binding objects to PLC tags so the screen reflects, or changes, controller data
- Distinguishing display-only objects from objects that write values back to the PLC
- Configuring object behavior, such as momentary versus maintained actions
- Testing an HMI project by operating it against a running PLC program
A frequent source of errors is confusing which side "owns" a value. If an operator can type a setpoint on the screen, the PLC logic must be written to use that value, and the HMI object must be configured to write to the right address. Walk through at least one complete loop end to end: PLC variable, HMI object, operator action, PLC response.
Domain 6: Program and Operate an HMI Project That Uses Information, Diagnostic and Alarm Messages
The final domain builds on the previous one by adding messaging. Rather than simply showing values, the HMI communicates conditions to the operator: general information, diagnostic detail for maintenance staff, and alarms that demand attention.
Domain 6: HMI Messages
Know the purpose of each message category and how each is triggered by PLC data.
- Information messages: status notices that tell the operator what the system is doing
- Diagnostic messages: detail that helps a technician locate and understand a fault
- Alarm messages: notifications of abnormal conditions that require a response
- Tying message triggers to PLC bits or values so a message appears when its condition becomes true
- Designing clear, actionable message text rather than vague or cryptic wording
This domain rewards candidates who think like an operator and a maintenance technician at once. A good alarm message states what is wrong and, ideally, hints at where to look. Practice writing short message text for common analog conditions such as high level, low pressure, or sensor out of range, and tie each to the PLC logic that would trigger it.
How the Six Areas Connect
It is tempting to study each domain in isolation, but the real value of this credential is the way the pieces combine in a single working system. Consider one process, such as maintaining a tank level:
- An analog level transmitter feeds the PLC, and you scale the raw value (Domain 1).
- The level reading is unexpectedly flat, so you check wiring, module configuration and scaling (Domain 2).
- Control logic runs only in automatic mode, using program control instructions (Domain 3).
- The scaling and alarm logic live in dedicated subroutines called from the main routine (Domain 4).
- The operator watches the level and enters a setpoint through HMI objects (Domain 5).
- A low-level alarm and a diagnostic message appear on screen when conditions warrant (Domain 6).
Key Takeaway
Build one small integrated project that touches all six areas. A single tank-level or temperature-control exercise forces you to scale an analog signal, troubleshoot it, structure it with subroutines, and surface it through HMI objects and alarms. It's a far better use of time than memorizing instruction lists in isolation.
Delivery Format and What Is Still Unverified
Honest preparation means knowing what is confirmed and what isn't. Here is the picture as researched on October 14, 2026.
| Topic | What is confirmed | What is not verified |
|---|---|---|
| Issuing body | Smart Automation Certification Alliance (SACA) | Latest exam version details |
| Silver level | Proctored online written exam through the SACA portal at participating centers | Exact question count and time limit |
| Gold level | Requires Silver plus an observed hands-on assessment using SACA-approved equipment | Practical assessment duration as a formal timer |
| Content areas | Six preparation-curriculum objectives (309.01 to 309.06) | Official domain weights and a complete current blueprint |
| Fees | Membership benefits can provide certification access for eligible students and member-company employees | Universal retail exam fee, pass mark, retake and renewal rules |
Because the exact written format isn't verified, avoid relying on any timed simulator that claims precise question counts or timers until you have confirmed the specifics with your center. For details on what we do and don't know about thresholds, see C-309 Passing Score 2026 and C-309 Pass Rate 2026: What the Data Shows. For cost questions, including the distinction between certification access through membership and separate tuition, equipment or local center charges, read C-309 Certification Cost 2026.
On eligibility, college course prerequisites and the C-207/C-208 sequence shown in one example degree pathway are not verified issuer-wide admission requirements. Our C-309 Requirements article explains how to approach this without assuming a prerequisite that may not exist for your situation.
Sequencing Your Preparation by Domain
Rather than a generic weekly template, order your study by dependency: later domains assume you're fluent in earlier ones. A suggested progression looks like this.
Analog fundamentals (Domains 1 and 2)
- Master scaling math for both inputs and outputs
- Practice reading live raw values and spotting range mismatches
- Do fault-finding exercises that separate wiring, configuration and logic causes
Program structure (Domains 3 and 4)
- Trace the scan on paper for jump and master-control style instructions
- Build a small program split into a main routine and called subroutines
- Compare skipped logic to logic that simply evaluates false
Operator interface (Domains 5 and 6)
- Bind HMI objects to PLC tags and confirm data direction
- Write information, diagnostic and alarm messages tied to PLC conditions
- Run the whole system end to end as an integrated project
Analog comes first because both programming and troubleshooting depend on it, and because the HMI messages in Domain 6 usually report analog conditions. For a fuller preparation framework, our C-309 Study Guide goes deeper, and the C-309 Cheat Sheet condenses the must-know facts for a last-minute review. When you're ready to test yourself on scenario-style questions across all six areas, try the C-309 practice tests.
Where These Skills Get Used
The six domains map directly onto day-to-day work in industrial maintenance and controls. Technicians who can scale analog signals, troubleshoot instrumentation, structure PLC programs, and build operator screens with meaningful alarms are valuable in manufacturing plants, process facilities, and automation integrators. The same people are often the ones called when a line goes down, because they can move between the controller, the field device and the operator screen.
We deliberately avoid quoting salary figures or job-count statistics here, since none are verified for this credential. For a qualitative look at the roles and employers that value these skills, see C-309 Jobs, and for return-on-investment considerations, Is the C-309 Certification Worth It?
If you want to practice applying these skills the way the exam frames them, work through the question sets at C-309 Exam Prep, focusing on the scenario-based items in Domains 2 and 6 first, since those reward diagnostic reasoning over memorization.
Frequently Asked Questions
No weights are verified. The six areas come from unweighted preparation-curriculum objectives in public college course documents, not from a published issuer blueprint with percentages. Plan to study all six rather than concentrating on one.
Domains 5 and 6. Domain 5 covers HMI projects that use objects to interact with a PLC, and Domain 6 covers HMI projects that use information, diagnostic and alarm messages. Domains 1 through 4 focus on PLC programming and troubleshooting.
Both, depending on level. Silver is a proctored online written exam through the SACA portal at participating centers. Gold requires Silver plus an observed hands-on assessment using SACA-approved equipment.
The exact written question count and time limit were not verified. Course hours and practical assessment time shouldn't be mistaken for a written-exam timer. Confirm specifics with your testing center before scheduling, and see our C-309 Exam Dates guide for scheduling context.
Some SACA announcements and an occupational database record describe Ethernet communications. That conflicts with the analog, PLC and HMI scope in the preparation objectives reviewed for this guide, so we flag the discrepancy rather than blending the two. Verify the current scope with SACA before finalizing your study plan.