RPL vs spreadsheets

Stop rebuilding propulsion assumptions across spreadsheets, CAD, and reports.

Spreadsheets are useful and familiar. RPL Engine Workbench is for the point where spreadsheet-based sizing starts drifting away from geometry, warnings, reports, and review artifacts.

Pain point

Where drift creeps in.

Sizing versions

Multiple files can carry different chamber targets, O/F assumptions, units, or feed boundary assumptions.

CAD handoff

Geometry can be rebuilt manually after the sizing file changes, creating another place for mismatch.

Review reports

Manual report updates can omit warnings, stale assumptions, or the actual solved case basis.

Semester handoff

New team members inherit files without always knowing which assumptions are current.

Connected workflow

One solved case drives the artifacts.

RPL keeps sizing, injector/nozzle workflow context, DXF exports, reports, warnings, and supported Flowfield visuals connected to the same solved case.

Assumption tracking CAD handoff Review-ready reports Local Mac workflow
RPL Engine Workbench report showing solved outputs, assumptions, and warnings
Reports keep solved outputs, assumptions, and warnings visible for review.

Use both well

RPL does not ask you to abandon every spreadsheet.

Keep spreadsheets for side analysis

Use them for quick notes, independent checks, budget tracking, or custom calculations your team already understands.

Use RPL for review artifacts

Use the workbench when sizing, geometry, warnings, reports, and exports need to stay tied together.

Document remaining review work

Keep safety review, test planning, export-control review, and qualified engineering signoff outside the software claim boundary.

Evaluate fit

See whether RPL reduces drift in your review workflow.

Download the built-in trial and test the workflow on an Apple silicon Mac.