How SIL2 Shapes AWP Electronic Control Selection

Why OEMs Ask About SIL2

The core safety functions of an aerial work platform — platform load limiting, boom levelling, machine stability control and motion limiting — put people in the basket at risk when they fail. Under the EN 280 framework these functions are increasingly designed and validated to functional-safety levels, and European buyers now list SIL2 / PLd evidence as a hard requirement in supplier onboarding. Yet a certified component is only the starting point; how the level translates into sourcing decisions is the real engineering question.

SIL2 and PLd: two complementary scales

IEC 61508’s Safety Integrity Level and EN ISO 13849’s Performance Level are complementary frameworks — the former targets random and systematic failures of safety-related E/E systems, the latter mechanical-safety control loops. In practice SIL2 roughly corresponds to PLd (typically Category 2 / Category 3 architectures), the combination most AWP OEMs specify. Understanding this mapping is how you read what a supplier’s certificate actually covers.

Impact 1: controller level ≠ system level

A component certificate proves the random-failure metric (e.g. PFHd) under rated conditions; the system level also depends on the sensor chain, actuation chain and diagnostic coverage. A SIL2 controller fed by sensors without redundant output cannot deliver a high-integrity safety loop. Ask suppliers for a full-chain safety concept — controller + sensors + safety outputs — not a single certificate.

Impact 2: sensor redundancy and diagnostics

Angle, length and level sensors are the input sources for weighing and levelling. Single-channel sensors without diagnostics cannot support higher safety loops; dual-channel or diagnostic-protected redundant outputs (e.g. PLd redundant inclinometers) are what enter safety-function validation. Mature teams make “redundant output, documented diagnostic coverage” a precondition of sensor selection.

Impact 3: software, calibration and change control

Uncontrolled software versions, parameter calibration and FOTA updates undermine production consistency and certification. Developing on standard platforms such as CODESYS, archiving parameter files per machine model, and running 100% EOL tests with dedicated calibration rigs turn a paper level into a batch-consistent level.

Impact 4: certification timeline vs. production window

Components with certification in progress can serve engineering validation, but production sourcing must verify certificate closure timing and the supplier’s volume track record — delivery records, type-test capability (thermal, rain, vibration) and after-sales calibration say more about delivery certainty than the certificate itself.

A practical checklist

  • Require a full-chain safety concept (controller + sensors + safety outputs)
  • Document sensor redundancy and diagnostic coverage into drawings and tech agreements
  • Match controller certificate scope — temperature, ingress, EMC — to real duty conditions
  • Deliver calibration and EOL schemes together with the hardware
  • Write certification milestones into the contract, aligned with SOP windows

HCT’s HCU201/202 safety controllers (SIL2, CODESYS), TLJ100 / CET12 / HPT1210 sensor families (PLd redundant output) and production-line EOL + calibration systems are volume-proven on a leading AWP OEM’s full machine range. Bring your machine list — we’ll walk the configuration with you.

Request a Sample Evaluation

5-field graded inquiry · 4-working-hour response · proven in volume delivery

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top