The microfluidic development workflow

From concept to fabrication and measured results

Keep requirements, network design, numerical studies, fabrication files, and laboratory records in one project. Follow the stages below as you develop and refine a chip.

1. Define the concept

Record the application, sample, fluid, flow target, constraints, and success criteria in a saved concept brief. Stage readiness shows what still needs attention.

Editor → Workflow → Concept

2. Build a network

Use Auto design to specify total flow and one to four outlet ratios, or a capillary filling time. The compiler searches a bounded physical route family, sizes channels and checks the resulting graph. Open the accepted design in the editor, or build from templates and reusable components.

Auto design → Requirements → Generate and check → Create design

3. Set physical geometry

Specify channel length, width and height, physical coordinates, port diameter, and pressure boundaries. Keep diagram positions separate from fabrication dimensions. Save revisions and compare changes.

Editor → Properties / History

4. Simulate and visualize

Calculate 1D pressure, flow, velocity, Reynolds number, and residence estimates. Explore graphs and flow animation. The recovered Python filling model supports serial channels and a single binary split, with moving-front animation and portable model inputs.

Editor → Analyze / Filling

5. Compare and refine

Sweep one channel dimension across a bounded range and compare calculated outlet flows. Use the target-flow dimension tuner, inspect applicability, and download comparison data. Trial dimensions do not change your design until you choose to apply a proposal.

Editor → Analyze → Compare channel dimensions

6. Check fabrication geometry

Choose a PDMS, micromilling, or laser laminate process profile. Review channel dimensions, spacing, ports, edge clearance, bonding land, and height layers. Override illustrative rules with your supplier’s actual limits and set the chip boundary and mask polarity.

Editor → Workflow → Fabricate

7. Prepare the fabrication handoff

Preview a flattened mask and download a package with closed polygon SVG masks, closed DXF contours, port locations, a bill of materials, process checklist, and a source manifest. Eligible single-height PDMS designs can also include a checked relief-mold STL.

Editor → Workflow → Fabricate → Download fabrication package

8. Record measured validation

Record fabrication method, leak observations, measured pressure and flow, and channel dimensions. Each saved test captures the design and predicted reference values for comparison, so later edits do not silently change the test’s reference.

Editor → Workflow → Validate

What the results mean

The hydraulic solver is a reduced 1D model for rigid rectangular channels. Its validity checks and assumptions accompany the results. Particle playback illustrates a steady solution; filling animation uses a separate transient capillary model. Mixing, diffusion, reactions, thermal transport, electrokinetics, multiphase CFD, and arbitrary 3D devices require additional validated models.

Manufacturing packages currently support straight/channel paths at one channel height. Fabrication profiles are editable starting points. A passing geometry check does not approve a process, material compatibility, operating pressure, or finished device. Review masks, tolerances, layers, port interfaces, and bonding with your fabricator, then qualify the manufactured device with measurements. The app does not claim ISO certification.

Research behind the workflow

The integrated workflow follows the design-to-build approach described in the 3DuF research. Geometry review covers the cross-sections, spacing, port access, and edge considerations discussed in uFluidix’s fabrication guidance. Process selection also depends on material and fabrication method.

For broader physics, COMSOL’s microfluidics overview describes the coupled models needed beyond this release. ISO 22916 addresses microfluidic interoperability; checking its full requirements is a separate task.