Automation Fundamentals and Project Justification
What this domain tests
The Automation Fundamentals and Project Justification domain asks you to frame an automation project before any code exists: where the control hierarchy sits, what type of manufacturing problem you are solving, and whether the investment is defensible. Expect questions on the automation pyramid, discrete/batch/continuous classification, ISA-88 and ISA-95 boundaries, lifecycle phases, and financial justification.
Core rules and concepts
- The automation pyramid separates field devices, control, supervisory/HMI, MES, and ERP. Data ownership and latency change at each level; do not put enterprise scheduling logic in a PLC.
- Match the control model to the process: discrete (state/sequence), batch (recipe/phase), continuous (loop/PID). A batch problem specified as continuous logic creates untestable recipes.
- Use ISA-88 for batch object models (recipe, unit, equipment module, phase) and ISA-95 for integration between control and business systems.
- Justify with a baseline and future state. Quantify labor, cycle time, scrap, energy, quality, and compliance cost. Include CAPEX, integration, training, spares, maintenance, and ramp-up.
- Use payback for screening, but NPV/IRR for long-lived assets and risk-adjusted scenarios for uncertainty.
Worked example
A manual packing line uses two operators per shift, three shifts, 250 days/year, loaded labor $38/h. A $320,000 automation cell reduces staffing to one operator and adds $45,000/year maintenance and $20,000 training in year one. Annual labor saving = 2 operators x 8 h x 3 shifts x 250 days x $38 = $456,000. Net annual benefit after maintenance = $411,000. Year-one capex including training = $340,000. Simple payback = 340,000 / 411,000 = about 0.83 years, or about 10 months. Reasoning: use loaded labor, not wage rate; subtract new recurring cost; include one-time training. If ramp-up cuts first-year benefit by 30%, year-one net is $287,700 and payback extends to about 1.18 years. State the assumption.
Traps that cost marks
- Quoting gross labor savings while ignoring maintenance, energy, training, and spare parts.
- Treating simple payback as a complete investment decision.
- Claiming automation improves quality without a measured baseline.
- Confusing the ISA-95 MES layer with the ISA-88 control layer.
- Forgetting lifecycle cost: patches, calibration, cybersecurity, and obsolescence.