MRGI CONSTRUCT / WORKFLOW FIELD GUIDE
Review a revised desktop stand
Connect a design change to material quantities and stated assumptions before considering a production handoff.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Set the revision
- Start with
- A fictional three-part stand.
- Work through
- Choose the width and height and identify the parameter set.
- Result
- A candidate geometry revision.
- 02
Inspect the assembly
- Start with
- The model and part list.
- Work through
- Separate the parts to inspect their arrangement and quantity.
- Result
- A visual assembly review.
- 03
Evaluate the estimate
- Start with
- The dimensions and fictional material rate.
- Work through
- Recalculate the illustrative quantity and identify excluded costs.
- Result
- An estimate with explicit assumptions.
- 04
Review production readiness
- Start with
- The design, BOM, and targeted checks.
- Work through
- Require appropriate engineering and manufacturing validation before release.
- Result
- A documented decision, not an automatic certification.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| DXF / DWG | Drawing interchange foundation | Unknown entities, units, and round-trip fidelity need acceptance tests. |
| BOM / cost table | Grid handoff | Quantity rules and rate assumptions must be documented. |
| Materials / review records | Surface and Evidence handoffs | Visual material appearance is separate from physical material properties. |
A deliberate cross-app boundary
Use Grid for approved cost inputs, reference Surface materials, and preserve review findings in Evidence.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- The model is assembled from simple boxes, not a validated CAD solid.
- The sample estimate excludes labor, waste, fasteners, tooling, and taxes.
- No structural, tolerance, or manufacturing safety conclusions can be drawn from this scene.
Development status
The source foundation is imported. Parametric BOM integration and manufacturing checks are exploratory. Geometry and file-format fidelity must be validated before production use.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Is the displayed cost a quote?
No. It is a calculation using fictional quantities and a fixed illustrative rate. Real procurement needs verified specifications and supplier pricing.
Does the exploded view validate assembly?
No. It helps inspect the arrangement of simple sample parts. Fit, tolerance, strength, and assembly feasibility require separate engineering work.
Open-source foundation
2D/3D drawing, constraints, DXF/DWG, and scripted commands exist in CADCraft. Validated design-to-BOM workflows are the proposed MRGI investigation. Read the credits and foundation mapping.
Keep exploring Construct.
Return to the product breakdown or try the local interactive example.