M45 is an AI workspace for safety-critical engineering. It investigates what you need to know, check, and do before making an informed engineering decision.
You
We want to show the crew when the hoist cable is moving. Can we use the HOIST MOTION signal for that? What do we need to check?
M45
The interface document says this signal reports a motor command, not measured cable movement. That finding guides the next checks: what the crew can infer while the hoist stops, and which feedback and verification are needed.
Rescue hoist · Crew display
Change impact assessment
Change impact assessment
Rescue hoist · Crew display
Using the hoist’s motor-command signal as a cable-movement indication.
Engineering question
Not on its own. HOIST MOTION shows that the controller is asking the motor to run. It does not measure whether the cable is moving.
Why this matters
If the indication goes off, the crew might assume the cable has stopped. This signal alone cannot confirm that.
Work to resolve
Establish what the display should tell the crew, which feedback can support it, and how to verify it, including while the hoist is stopping.
From the interface document · ICD-RH-208 · Rev C · §2
“Indicates that the controller is commanding the motor in either direction. It does not measure cable speed.”
Definition of the HOIST MOTION signal
Examine the indication while the hoist starts, runs, and stops, and identify the evidence needed to distinguish commanded motion from observed cable movement.
Assessment continues below
You can build something that works really well. Then someone asks, ‘Did you also consider what happens when…?’ And you realize you hadn’t considered that at all.
The certification authority wants to know, 'How have you done that? Why have you traded off this thing for that thing? Why have you made that decision?' But tracking down this evidence is actually very difficult.
Before you commit, you need to understand what your decision could affect and what work it would create. Finding those answers requires extensive investigation across documents, teams, and disciplines.
Changing one part can create unexpected work elsewhere.
Work has to be redone because people didn’t know what needed to be checked, updated, or communicated.
Regulatory updates and field reports take work to assess, even when no change is needed.
Teams put good ideas aside because they cannot work out what getting them approved would take.
Cost to correct by stage
The later an issue is found, the more work has to be redone.
M45 connects system intent, requirements, design decisions, and evidence across your existing sources to investigate what your task requires.
M45 examines what a decision, change, or new information could affect across requirements, interfaces, operating procedures, and verification evidence. See what needs review and why, with links to the supporting sources and questions that remain unresolved.
See product detailsM45 compares what you want to achieve with what you already have, your procedures, and applicable requirements. It identifies the work and evidence still needed, so you can decide how to proceed and involve the right people early.
See product detailsM45 helps your team understand how hardware, software, and people work together to achieve your system’s purpose. Use that shared understanding to clarify responsibilities, examine interactions, and evaluate design decisions.
See product detailsKeep your existing tools and systems of record. M45 works across them.
Explore the productWe’re currently working with a small group of early partners and customers to apply M45 to real engineering work and shape the product around their needs.
Let’s talk