Sequence control from SCADA in SCADA systems - Time & Space Complexity

Time Complexity: Sequence control from SCADA

O(n)

Understanding Time Complexity

When controlling sequences in SCADA systems, it's important to know how the time to complete tasks grows as the number of steps increases.

We want to understand how the system's work changes when the sequence length changes.

Scenario Under Consideration

Analyze the time complexity of the following sequence control code.

# Control a sequence of steps
for step in sequence_steps:
    if step.condition_met():
        step.execute()
    else:
        break
    wait_for(step.completion_signal)

This code runs through each step in a sequence, checks if conditions are met, executes the step, and waits for it to complete before moving on.

Identify Repeating Operations

Look at what repeats as the sequence runs.

• Primary operation: Looping through each step in the sequence.
• How many times: Once per step, until a condition fails or all steps complete.

How Execution Grows With Input

As the number of steps grows, the time to run the sequence grows roughly the same way.

Input Size (n)	Approx. Operations
10	About 10 step checks and executions
100	About 100 step checks and executions
1000	About 1000 step checks and executions

Pattern observation: The work grows directly with the number of steps, so doubling steps doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the sequence grows in a straight line with the number of steps.

Common Mistake

[X] Wrong: "The sequence control runs in the same time no matter how many steps there are."

[OK] Correct: Each step adds work because the system checks and waits for it, so more steps mean more time.

Interview Connect

Understanding how sequence control scales helps you explain system behavior clearly and shows you can think about efficiency in real tasks.

Self-Check

"What if the code could execute multiple steps at the same time? How would the time complexity change?"