Controls & Response · working title

Explore controls.
Understand system response.

Model, compare and document how systems respond to control changes and disturbances.

The development study catalogue includes electrical power, battery and mission energy; hydraulic, fuel-feed and coolant circuits; actuator and motor response; and pressure and ventilation. Each model has a bounded scope and assumptions; independent validation remains necessary.

Explore mission power and system-response demo studies, connect drawings to your study and keep comparisons and supporting evidence together.

Development previews · Availability under review

Start with an available application

Explore controls in context.

Start with a mission-power question: how do changing power demands affect battery response and the reserve marker? Relate the study to mechanical configurations and electrical signals while keeping assumptions and evidence visible.

01 / Analysis

Mission power & energy

Compare baseline and proposed battery packs across takeoff, climb and cruise demand. Inspect energy use, voltage sag and the reserve marker.

See a mission-power workflow →
02 / Mechanical

Drawings & configuration

Register drawing and model revisions, compare baseline and proposed details, and connect supporting files to a test plan.

See a mechanical workflow →
03 / Electrical

Signals & change records

Organise schematic references, I/O and scaling details, then document expected results and observed verification evidence.

See an electrical workflow →
A practical example

Make the next question easier to answer.

These demo studies show how the workflow connects a technical question, analysis and supporting evidence. Sample data illustrates the process; measured results belong in the verification record.

Mission power: from takeoff to reserve

Start: choose the Battery & mission energy study in the local CR application. Set the takeoff, climb, cruise, approach and contingency-demand phases, with a duration and pack-terminal power demand for each.

Choose a case: mission energy and reserve, power peak and voltage sag, or temperature and available power.
Explore: compare baseline and proposed packs against the same mission demand. Inspect delivered and unmet power, state of charge, the reserve marker, voltage sag and temperature under the entered assumptions.

Retain: save the portable study, export trace data and keep the comparison report with the proposed verification plan. Distinguish synthetic model output from measured evidence.

This simplified development model uses synthetic defaults and prescribed power demand. It does not predict qualified aircraft endurance, establish battery operating limits or calculate a regulatory reserve. Independent validation is required; the website illustrates the workflow and does not run the analysis engine.

Mechanical: keep a drawing change tied to its evidence

Start: register an example chamber drawing, document number, revision A and related equipment.

Explore: describe revision B, compare configuration details and select a compatible desktop viewer for the file format.

Retain: link the source attachment or file location, expected test result and observed evidence. Preserve the earlier register when starting a new study revision.

Desktop viewers install separately. CAD files open in the chosen application; a file reference does not provide automatic CAD integration.

Electrical: trace a signal-scaling change through review

Start: identify the schematic revision, signal tag, I/O channel and entered raw and engineering ranges.

Explore: compare the proposed range with the baseline and inspect the calculated linear relationship.

Retain: record the verification criteria and supporting observations. Keep recorded external actions separate from a tool-generated calculation.

A scaling comparison is not calibration, wiring verification or authorization to change equipment.

Your supporting tools

Work with the files you already have.

Common drawing and model formats are the starting point: DWG, DXF, STEP and PDF, with discipline-specific files added as needed.

The development workflow works with common desktop tools by keeping file references, attached originals and supporting evidence connected to your study. Choose a compatible viewer for the file format, operating system and drawing dependencies.

Drawings & modelsDWG TrueView, FreeCAD and LibreCAD are candidates for local evaluation.
Electrical & simulationQElectroTech, LTspice, KiCad and OpenDSS cover different diagram and simulation needs.
Reports & handoffsPortable study files and reports retain context for later review.

Third-party tools are separate products. Compatibility and the Dell installation test remain part of evaluation.

Plans & availability

Explore first. Define the right scope next.

A standalone CR subscription and an Engineering Suite subscription are planned. The Suite is intended to include AEW and CR, with PD at no additional charge. Pricing, plan details and availability will follow validation and release review.

This preview does not offer subscriptions, payment collection or a public software download.

Ask about the tools
Questions before getting started

Clear expectations from the beginning.

Can I use these tools outside aviation?

The workflows are being developed for general engineering analysis and technical records. Suitability still depends on the application, inputs and qualified review.

Will my drawings be uploaded automatically?

The current desktop previews keep study files local. A drawing location is a reference, and attachments are retained in the exported study. No cloud CAD upload is performed automatically.

Can the tools control equipment or approve a change?

These workflows support analysis and documentation. They do not grant engineering approval, operate equipment or replace an applicable authorized process.

Are shared workspaces and subscriptions available?

Customer accounts, subscription billing and shared team workspaces are not available through this preview. Their scope and implementation remain under review.

Tools support documentation and analysis. They do not constitute engineering certification, maintenance approval, airworthiness determination or return-to-service authority. Qualified personnel and independent verification remain necessary.