HENSYNTH Requirements page: mission targets and caps

Requirements before pretty drawings

The Requirements page copy in HENSYNTH says it plainly: answer feasibility before you treat geometry as final. Span maximum and battery maximum are first-class constraints, not afterthoughts you add once the wing looks right. The form stores twelve numeric targets the compliance table will compare against predictions after Run screening.

The twelve fields

• Range (m) — distance the aircraft must fly on one energy load.
• Endurance (s) — time aloft; convert hours to seconds before entry.
• Cruise speed (m/s) and cruise altitude (m) — the cruise segment the performance model uses.
• Stall speed max (m/s) — cap; landing configuration stall must stay at or below this.
• Takeoff limit (m) and landing limit (m) — longest allowed ground roll plus obstacle clearance bookkeeping.
• Climb rate (m/s) — minimum vertical speed in the screening configuration.
• Payload (kg) — useful load besides empty aircraft.
• Span max (m) — hard cap on wing span, not a target span.
• Battery max (kg) and reserve SOC (fraction) — energy mass cap and unused charge fraction for electric architectures.

Each label has a brass help control (asterisk icon) that opens a modal with purpose text in plain language. Use it when a unit or definition is unfamiliar — the modal is the same intent as the inline help on the run report, scoped to data entry.

Save, feasibility, and HEN-AI

Save requirements writes the form to the project. Is this requirement set physically plausible? calls the feasibility endpoint and shows FEASIBILITY status, most restrictive parameters, and suggested minimum changes when the engine finds an inconsistent set. That check is screening logic, not a guarantee the aircraft you have drawn can meet every row.

Review requirements with HEN-AI seeds the dock with a example mission sentence you can edit in conversation. HEN-AI proposes requirement edits; you still save the form when you accept numbers.

Run screening and the report block

After geometry is saved, use Run screening from the project workspace (Requirements participates in save-before-run). When the analysis returns, the Requirements run report appears below the form: predicted metrics, question-mark help on each metric, compliance table, and optional reasoning findings. Download and mail icons on that panel package PDF, figures, and stored numbers into a zip — conceptual report only.

Handoff to synthesis

Then auto-size aircraft candidates → saves requirements, sets a session handoff flag, and opens the Synthesize page. Feasibility is answered first; the four style cards appear after you run Synthesize candidates. None of that replaces Run screening on an aircraft you already chose — it searches alternate wing loadings and battery fractions that might satisfy the same caps.

In simple words: what this page is for

Enter range, endurance, cruise, field lengths, payload, span cap, and battery limits on the HENSYNTH Requirements page — with feasibility check and handoff to synthesis.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH Requirements page: mission targets and caps keeps the focus on conceptual screening you can explain in review.

Why the topic matters

Engineers lose time when a title sounds clear but the page only sketches the idea. This article expands HENSYNTH Requirements page: mission targets and caps so you can answer three questions without jargon: what is the idea, when do you use it, and how do you check it in a HENDOI product.

Read the sections above for the core definitions. Use the steps below to move from reading into a real project trail you can share with a teammate.

How to apply this in HENDOI

In practice: open HENSYNTH after you sign in, set or confirm geometry, write mission targets on Requirements, Run screening, then read PASS / FAIL with margins. Use Mission, Performance, Trades, Optimize and Reports only after the screening snapshot exists. Numbers come from stored runs — the product does not invent missing values.

If you still need the wing section itself, finish that work in HENFOIL first, then continue the aircraft in HENSYNTH. One HENDOI account covers both. Plans stay Student USD 9, Professional USD 29 and Team USD 89.

What this page will not claim: HENSYNTH is conceptual and preliminary screening. It is not wind-tunnel data, not certification CFD, and not a compliance certificate for an authority. PASS / FAIL means requirement-versus-prediction inside the product.

Checklist before you leave this page

• Can you state the idea of HENSYNTH Requirements page: mission targets and caps in one sentence?
• Do you know which product owns the next action — HENSYNTH or HENFOIL?
• Will every number you keep carry a method label or a stored-run source?
• If you are new here, have you opened Register or Login?

Related reading on this site

• HENSYNTH candidate cards, Use this aircraft, and CAD
• HENSYNTH compliance matrix: PASS, FAIL, and margin
• HENSYNTH download and share technical reports
• HENSYNTH Geometry page: wing, fuselage, and tails
• All HENDOI blog articles
• HENSYNTH product page
• HENFOIL product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now