Use cases

Start with the operating need.

AEMS capabilities are configured around the required movement, failure response, operating environment and assurance objective—not around a one-size-fits-all actuator.

Civil and safety-critical applications

Outcome-led engineering

Define what must happen when conditions change.

The right solution begins with the intended platform response—not simply force, stroke and speed.

AEMS considers the function’s criticality, allowable degraded states, external loads, power availability, information needs and maintenance concept before proposing a product configuration.

Actuation use cases

Planned behaviour at the point of motion.

Each example describes an intended use case. Final suitability and performance would be established through application-specific engineering and verification.

UC–01

Primary flight-control continuity

Maintain controlled movement following a defined internal fault.

Situation: A safety-critical surface cannot rely on an uncontrolled or immediate loss of actuator function.
AEMS response: FT‑EMA configured with local sensing, fault management and defined degraded operating states.
Intended outcome: Continued controlled authority appropriate to the aircraft-level safety assessment.

UC–02

Secondary-axis retention

Hold a predictable position when continued movement is not required.

Situation: A secondary function needs a clear, stable response to a specified loss of drive or control.
AEMS response: FF‑EMA with application-defined position retention and embedded diagnostic information.
Intended outcome: Predictable fail-fixed behaviour with reduced architectural complexity.

UC–03

Controlled back-driving

Permit movement under external load without losing system awareness.

Situation: The host mechanism requires load relief, passive movement or externally driven repositioning.
AEMS response: FB‑EMA configured for the required back-driving behaviour, sensing and interface constraints.
Intended outcome: Controlled mechanical response aligned with the wider system concept.

UC–04

Distributed control mechanisms

Apply the right integrity level across multiple compact axes.

Situation: Advanced aircraft may use multiple aerodynamic or propulsion-control mechanisms with different criticality levels.
AEMS response: A tailored mix of FT‑EMA, FF‑EMA and FB‑EMA configurations using a common product approach.
Intended outcome: Function-specific behaviour without unnecessary product proliferation.

Intelligent assurance use cases

Understand what the platform can still do.

Equipment data becomes more valuable when it is interpreted in the context of the wider operating state.

UC–05

Degradation awareness

Recognise developing issues before they become unexpected interruptions.

AAMA™ combines relevant health and status information to support remaining-capability assessment and proportionate operational decisions.

Relevant capability: AAMA™ + embedded BITE

UC–06

Energy and thermal constraints

Coordinate equipment demand when electrical or thermal margin is limited.

ARMS™ is intended to provide a joined-up view of available resources, constraints and equipment priorities.

Relevant capability: ARMS™

UC–07

Configuration continuity

Keep the platform and ground team aligned after maintenance or replacement.

ATLAS and the support layer preserve relevant configuration, version, interchangeability and maintenance information.

Relevant capability: ATLAS + through-life support

Specialist environments

Actuation where access and intervention are difficult.

Remote, sealed or environmentally demanding systems may need compact electric motion with local diagnostics and reduced routine intervention.

AEMS can assess sealing, materials, lubrication, temperature, pressure, noise and maintenance constraints as part of the application definition. Environmental capability will be claimed only after representative verification.

Engagement pathway

From use case to evidence plan.

01
Define the function
Load, stroke, speed, duty cycle and operating environment.
02
Set the required response
Criticality, allowable degraded states and position behaviour.
03
Tailor the interfaces
Mechanical installation, power, control, communications and data.
04
Build the evidence plan
Analysis, test, environmental verification and assurance objectives.

Your use case

Start with a non-confidential outline.

Tell us what needs to move, how it should respond to faults and which constraints matter most. Detailed information can follow under suitable confidentiality arrangements.

Discuss a use case