Process optimisation: from a problem to a measurable result
An improvement project needs a clear baseline, a defined intervention and comparable results. This turns a general efficiency goal into a practical technical assignment.
Read article ↗Practical technical insights.
Practical guidance on process optimisation, maintenance, automation and manufacturing.
Reviewing control loops: measurement, setpoint and output
A fluctuating process value does not necessarily mean the controller is at fault. A useful review starts with measurement and follows the actual response of the equipment.
Read article ↗Scrap reduction: locate defects within the process
Reducing scrap starts with a clear defect description. Linking defects to process steps prevents corrective action at the wrong point.
Read article ↗Assess energy use alongside production output
Lower total energy consumption means little if output also declined. Assess consumption together with actual production.
Read article ↗Bottleneck resolution: identify the limiting station
A faster individual machine does not automatically increase throughput. First identify the section that actually constrains material flow.
Read article ↗Fault analysis: separate observation from cause
An alarm initially describes a condition. Reliable fault analysis requires the sequence of events and verifiable evidence about the cause.
Read article ↗Continuous improvement: small actions with clear ownership
Continuous improvement relies on specific operational observations. An action log connects suggestions to responsibility and results.
Read article ↗Collecting process data: signals need shared context
Timestamps and measurements alone do not explain production. Equipment state, product and signal definitions make data useful for analysis.
Read article ↗Production ramp-up: resolve outstanding items before shift start
Ramp-up brings together equipment, material preparation and staffing. A shared outstanding-items list makes these interfaces visible.
Read article ↗Reducing setup time: distinguish preparation from downtime
Some setup work can be prepared in advance. Identify which tasks truly require the machine to stop.
Read article ↗Cycle time optimisation: inspect steps, not only averages
Average cycle time can conceal short delays and occasional interruptions. Breaking down the sequence reveals where time actually changes.
Read article ↗Recording downtime causes consistently across shifts
A clear list of downtime causes supports production and maintenance. Too many categories, or ambiguous ones, make later analysis harder.
Read article ↗Testing process changes: agree criteria before trials
A successful test requires more than one trouble-free demonstration. Define acceptance criteria and representative conditions before implementation.
Read article ↗Production sensors: check plausibility before collecting more data
Additional sensor values help only when their meaning is understood. Installation position, signal processing and process state belong in the assessment.
Read article ↗Shift handovers: pass on complete technical information
A useful handover connects equipment status with outstanding work. The next shift starts with the same information as the previous team.
Read article ↗Composite materials: plan joining, loading and repair
A composite material cannot be assessed by weight alone. Processing, joining and later use should form part of material selection.
Read article ↗Aluminium in machinery: balance weight and interfaces
Aluminium can suit machinery components, but selection depends on loading, manufacturing and joining. Assess the complete application.
Read article ↗Material selection: define requirements before choosing names
Material selection starts with component function. Loading, environment and manufacturing together establish the requirements.
Read article ↗Component wear: review material and operating conditions together
A worn component does not automatically indicate an unsuitable material. Contact conditions, alignment and service duration belong in the investigation.
Read article ↗Industry 4.0: start with a specific operational question
Connectivity should solve an operational task. A limited use case helps define data needs, interfaces and responsibilities realistically.
Read article ↗Sustainable equipment operation: consider repairability and consumption
Longer useful life and transparent resource use depend on practical decisions. Maintenance access, spare parts and documented operating states are part of this.
Read article ↗Quality assurance: integrate clear inspection criteria into production
Inspections help when criteria, responsibilities and responses to deviations are clear. An additional check alone does not improve a process.
Read article ↗CAD documentation: assembly needs a clear released revision
A useful model is only part of assembly preparation. Drawings, bills of materials and revisions need to form a shared basis.
Read article ↗Robotics for smaller manufacturers: select a suitable task
A robotics project starts with a recurring task and clear interfaces. Suitability depends on parts, process variation and existing workflow.
Read article ↗Selecting manufacturing methods: connect part, volume and quality
Manufacturing method selection depends on geometry, material and required quality. Volume and later assembly also influence the decision.
Read article ↗Maintenance data analysis: start with existing records
An initial analysis does not always require new software. Existing fault and maintenance records can reveal recurring tasks.
Read article ↗