Skip to main content
Process Step is a work item type that represents a discrete manufacturing or assembly operation within a production workflow. Process Steps form the Level 1 (top level) of the Process FMEA (PFMEA) hierarchy, where failure modes and their root causes are analyzed to ensure product quality and process reliability in automotive manufacturing environments. Process Steps are central to IATF 16949/APQP (Advanced Product Quality Planning) workflows and serve as parent entities for Process Failure Modes and Control Plan Items. They provide the structural foundation for documenting manufacturing processes, identifying failure points, implementing detection and prevention controls, and maintaining traceability to system elements and equipment.

Overview and Purpose

In TestAuto2 — Automotive Safety Solution, Process Steps enable:
  • Process FMEA Analysis: Structure the manufacturing workflow to systematically identify what can go wrong at each production stage
  • Control Plan Development: Link manufacturing processes to quality characteristics and inspection methods
  • Equipment Traceability: Connect process steps to the production equipment (system elements) that execute them
  • Failure Mode Analysis: Serve as the parent entity for Process Failure Modes (Level 2 in the PFMEA hierarchy)
  • ISO 26262 & IATF Integration: Support functional safety requirements by documenting process controls and their effectiveness
A typical example: “Solder Wave Process for Circuit Board Assembly” or “Sensor Housing Injection Molding” are Process Steps that organize manufacturing operations.

Core Properties

NameTypeDefaultDescription
idStringAuto-generatedUnique identifier for the process step (e.g., PS-001, PS-Solder-Wave)
titleStringRequiredHuman-readable name of the manufacturing process step (e.g., “Wave Soldering - PCB Assembly”)
descriptionStringEmptyDetailed description of the process step, including inputs, outputs, and key parameters
statusEnumdraftWorkflow status tracking process maturity (values: draft, inProgress, inReview, pendingApproval, approved, rejected, obsolete)
assignedToUserUnassignedEngineer or process owner responsible for defining and maintaining the process step documentation
priorityEnumnormalPriority level for process improvement actions (values: low, normal, high, critical)
categoryStringEmptyProcess category classification (e.g., “Assembly”, “Molding”, “Testing”, “Soldering”)

Relationship Fields

NameLink RoleTarget TypeCardinalityDescription
processFMEAsassessesProcess Failure Mode0..*Outgoing link: Process Failure Modes analyzed for this process step
controlPlanItemsmonitorsThroughControl Plan Item0..*Outgoing link: Quality characteristics and inspection methods that control this process
systemElementsinvolvesSystem Element0..*Outgoing link: Production equipment, tooling, or manufacturing resources used in this step
processFlowpartOfProcess Flow Document0..1Outgoing link: Parent process flow document that sequences this step
relatedProcessStepsprecedesIn / followsInProcess Step0..*Bidirectional links: Process sequence and dependencies (e.g., Wave Soldering precedes Rework Soldering)

PFMEA Hierarchy Structure

Process Steps occupy Level 1 of the three-level PFMEA hierarchy: diagram When you drill down into a Process Step row in the PFMEA Risksheet, you see all associated Failure Modes (Level 2). Each Failure Mode can have multiple root causes (Level 3), each with its own occurrence, detection, and RPN values. Metrics roll up from Level 3 → Level 2 → Level 1.

Custom Fields for Process Analysis

Field NameTypeEnumerationDescription
processCategoryEnumProcess categories defined in project configClassification of process type (e.g., “Assembly”, “Welding”, “Coating”, “Testing”)
processOwnerUserPerson responsible for process execution and control maintenance
standardOperatingProcedureTextReference to or inline documentation of the SOP governing this process
equipmentIdStringManufacturing equipment ID or asset tag (cross-reference to system element)
cycleTimeFloatNominal cycle time in seconds or minutes for this process step
yieldFloatTypical first-pass yield percentage for this process (baseline for PFMEA severity assignment)
controlMethodologyEnumSPC, 100%_Inspection, Sampling, Visual, AutomatedQuality control approach used to verify process conformance
effectivenessMetricFloatProcess control effectiveness rating (pre- and post-mitigation) as input to PFMEA detection ratings

SC/CC and Control Plan Integration

Process Steps connect to Control Plan Items via the monitorsThrough link role. When a Control Plan Item is marked as a Special Characteristic (SC) or Critical Characteristic (CC), it indicates that:
  • SC (Special Characteristic) — This process parameter significantly affects product function or safety and requires documented control plan procedures
  • CC (Critical Characteristic) — This process parameter is critical to safety (per ISO 26262) and requires enhanced control, measurement, and reaction planning
The TestAuto2 Control Plan Risksheet displays Process Steps at Level 1, with associated Characteristics and Control Methods nested below, showing which quality attributes are monitored at each production stage.
A single Process Step may have multiple Control Plan Items. For example, “Wave Soldering” might have control plan items for:
  • Solder temperature (process characteristic)
  • Joint quality (product characteristic)
  • Flux coverage (process characteristic)
  • Lead-free solder composition (material characteristic)

Workflow State Transitions

Process Steps follow the standard seven-state lifecycle workflow:
From StateTo StateConditionAuto-Action
draftinProgressAssignee set
draft / inProgressinReviewPeer review requestedClear approvals
inReviewinProgressRework requested
inReviewpendingApprovalApproval requested
pendingApprovalapprovedAll required signatures collectedMark approvals as final
approved / inReview / pendingApprovalrejectedRejected by approverClear approvals; revert to draft
AnyobsoleteProcess step superseded or retiredMark superseded entity reference
Process Steps should not enter approved state until the associated PFMEA analysis is complete and risk controls (prevention and detection methods) are defined. This ensures traceability between process definition and quality controls.

Relationship to ISO 26262 and IATF 16949

ISO 26262 Integration

Process Steps support ISO 26262-4 (System Design) and Part 9 (Functional Safety Assessment) by:
  • Documenting manufacturing processes that could introduce systematic failures (e.g., solder defects affecting electrical safety)
  • Linking to System Elements (production equipment) to ensure equipment reliability
  • Connecting to Process Failure Modes that chain upstream to Design Failure Modes and System Requirements
  • Enabling closed-loop traceability: Hazard → Safety Goal → System Requirement → Design → Process Failure Analysis

IATF 16949/APQP Alignment

Process Steps are core to APQP (Advanced Product Quality Planning):
  • Phase 1 (Plan & Program Definition): Define manufacturing process steps and operational flow
  • Phase 2 (Product Design & Development Verification): Link design characteristics to process steps via Control Plan Items
  • Phase 3 (Process Design & Development Verification): Execute PFMEA analysis; assign occurrence/detection ratings based on process control effectiveness
  • Phase 4 (Product & Process Validation): Monitor Control Plan Item measurements to validate process capability
  • Phase 5 (Feedback, Assessment & Corrective Action): Drive continuous improvement through PFMEA updates and control plan refinement

Linking to Other Work Item Types

diagram
Target TypeLink RolePurpose
Process FlowpartOfParent process flow diagram; defines sequence and dependencies
System ElementinvolvesProduction equipment, tooling, fixtures, or manufacturing resources
Work InstructionsreferencesExternal SOP, drawing, or procedural documentation
Target TypeLink RolePurpose
Process Failure ModeassessesPFMEA row (Level 2); what can go wrong at this step
Control Plan ItemmonitorsThroughQuality characteristic or inspection method that controls this step
Risk ControlcontrolledByMitigation action that reduces PFMEA severity, occurrence, or detection

PowerSheet Integration: Process Steps Sheet

The Process Steps Sheet PowerSheet provides a two-section view:
  • Left Section (Process Steps): ID, Title, Description, Category, Owner, Cycle Time, Yield
  • Right Section (System Elements): Linked equipment and manufacturing resources via systemElements relationship
# Process Steps Sheet - Simplified Structure
source:
  entityType: ProcessStep
  
columnGroups:
  - name: "Process Steps"
    columns:
      - id          [collapsed focus]
      - title       [bold ascending sort]
      - description
      - category
      - processOwner
      - cycleTime
      - yield
  
  - name: "Equipment Involved"
    expansion:
      relationship: systemElements
      columns:
        - id
        - title
        - equipmentType
Users navigate this sheet to:
  • Verify all process steps are documented and assigned
  • Trace equipment involvement across the production workflow
  • Ensure process steps are linked to correct System Elements (no orphaned steps or equipment)

Risksheet Column Integration: PFMEA Level 1

Process Steps appear as Level 1 rows in the Process FMEA Risksheet:
Column GroupColumnsNotes
Process IdentificationProcess Step ID, Title, Description, CategoryLevel 1 row headers; collapsible to title
Failure ModesFM Count, Associated Failure ModesDrill-down to Level 2
Controls & StatusPrevention Controls Summary, Detection Controls SummaryAggregate from Level 2-3
RPN / Action PriorityRPN Range, Highest AP (H/M/L)Aggregated metrics
EquipmentLinked System ElementsQuick reference to production resources
When a Process Step row is expanded:
  1. Level 2 (Failure Modes) appear indented below, showing what can go wrong
  2. Each Failure Mode (Level 2) can be further expanded to show Level 3 root causes
  3. Individual cause rows show Severity, Occurrence, Detection, RPN, and pre/post-mitigation values
  4. Control methods (prevention and detection) are documented per cause

Example: Sensor Housing Injection Molding Process

PS-003: Injection Molding - Sensor Housing Assembly
PropertyValue
StatusApproved
OwnerManufacturing Engineer (Bob Smith)
EquipmentInjection Molding Machine XYZ-2000
Cycle Time45 seconds
Yield96.5%
Control Plan Items (monitorsThrough):
  • CP-001: Mold Temperature (Process Char) — Target: 85+/-5 C
  • CP-002: Injection Pressure (Process Char) — Target: 1200+/-50 bar
  • CP-003: Wall Thickness (Product Char - SC) — Target: 2.5+/-0.2 mm
  • CP-004: Surface Finish (Product Char) — Target: Ra 1.6 um max
PFMEA Failure Modes (assesses):
  • FM-1: Incomplete Fill (short shot) — O:4, D:5, AP:H
  • FM-2: Surface Voids/Porosity — O:3, D:3, AP:H
  • FM-3: Flash at Parting Line — O:2, D:2, AP:M
  • FM-4: Warping/Dimensional Variation — O:5, D:4, AP:H
System Elements (involves):
  • Injection Molding Machine XYZ-2000
  • Mold Cavity Assembly
  • Hopper & Drying System

Creating and Managing Process Steps

Typical Workflow

  1. Define — Create a Process Step work item with title, description, and process category
  2. Assign Ownership — Set processOwner and assignedTo fields
  3. Link Equipment — Use systemElements relationship to link to production equipment
  4. Execute PFMEA — Create Process Failure Modes (Level 2) linked via assesses relationship
  5. Define Controls — Link Control Plan Items via monitorsThrough relationship
  6. Approve — Route through review/approval workflow; transition to approved state
  7. Monitor — Track Control Plan Item measurements and update effectiveness ratings

Best Practices

Each Process Step should represent one distinct manufacturing operation. Avoid combining multiple operations into a single step (e.g., separate “Soldering” from “Rework Soldering” or “Inspection”). Finer granularity enables more precise failure mode identification.
Always link Process Steps to the actual production equipment (System Elements). This enables supply chain risk assessment (e.g., “Which processes depend on Equipment X?”) and supports production audit trails.
All Control Plan Items linked to a Process Step must have defined Target Values, Tolerances, and Reaction Plans before the Process Step is approved. Missing or incomplete control specifications can delay quality certification.

References

For related documentation, see: