Evaluated instances
Outputs come from placed block instances after parameters, variables, formulas, states, and nested references have been evaluated.
Automated BOM generation from evaluated drawing data
LogiDraft is for teams that need BOMs, schedules, and structured outputs to stay tied to evaluated instances, especially when drawings are generated from configurable blocks and changing inputs.
Why BOM drift happens
Manual BOM workflows often trail the drawing. Someone changes geometry, component selection, or an assembly option, then a separate spreadsheet or schedule has to be corrected afterward.
The mismatch risk is practical: the drawing may show one transformer group count, starter selection, or panel configuration while the BOM still reflects a previous variant.
Sample BOM/output table from evaluated instances
BOM-style output is shaped from evaluated data. Rows can expose authored inputs, computed values, selected components, and artifact fields from the placed instances that make up the design.
| Evaluated Instance | Raw Input | Resolved Value | Structured Output Field |
|---|---|---|---|
| Control power block | controlLoadVa = 2300, primaryVoltage = 480 | transformerVa = 3000, primaryFuse = resolved from lookup | Transformer and protection rows for the panel BOM |
| Motor starter block | motorHp = 10, voltage = 480 | FLC, breaker, contactor, and overload range from formulas and lookup tables | Starter component selections exposed as output fields |
| Motor control panel assembly | motorCount = 3, shared control voltage = 24 | Nested starter instances and control power instances resolve in context | Parent and child instance data contribute to a structured panel output |
What LogiDraft output automation is based on
Raw and resolved values
A structured output can expose authored input values, computed resolved values, or both, which helps trace each BOM row back to design logic.
Nested assemblies
Parent assemblies and child blocks can both contribute output data, which matters for motor control panels and other composed systems.
Artifacts and structured outputs
Artifacts are generated output views such as BOM-style tables, schedules, flat exports, or hierarchical data derived from the evaluated model.
Manual spreadsheet sync versus evaluated output
Manual spreadsheet synchronization
A drawing change is made first, then someone updates the BOM spreadsheet, schedule, or notes. The process depends on manual review to catch drift.
Drawing scraping
A finished drawing is inspected after the fact. This may recover visible data, but it does not make the drawing logic and output logic the same source.
Evaluated output in LogiDraft
Outputs read from evaluated block instances. The same parameters, formulas, lookup tables, and nested assemblies that realize the drawing also provide output data.
How a motor starter becomes an output row
1. Instance receives inputs
The placed starter instance receives horsepower, voltage, and option parameters.
2. Logic resolves selections
Lookup-driven logic resolves FLC, breaker, contactor, and overload values.
3. Drawing reads resolved data
Labels, visibility, schematic details, and component geometry can use those values.
4. Artifact exposes fields
The output table can expose the same selected starter data as BOM-style fields.
Output automation resources
Outputs documentation
Learn how outputs are derived from evaluated instances instead of separate reporting layers.
Generate A BOM help guide
Follow the practical flow for shaping evaluated instance data into a filtered parts list.
Motor Control Panel example
See a larger system where starters, protection, control power, and BOM output stay aligned.
Artifacts reference
Look up artifact behavior and output options for structured data.
Questions about this LogiDraft workflow
How does LogiDraft generate BOM data?
LogiDraft generates BOM-style outputs from evaluated block instances. Parameters, formulas, lookup tables, nested blocks, and resolved values determine what the instance represents, and outputs read from that evaluated result.
What is the difference between raw and resolved BOM data?
Raw values show authored inputs or source fields. Resolved values show computed values after formulas, lookups, state selection, and nested evaluation have run. Outputs can expose either view depending on the artifact configuration.
Can nested assemblies contribute to BOM output?
Yes. Parent assemblies and nested child block instances can both contribute meaningful data to outputs, which is useful for motor control panels and other composed systems.
Is LogiDraft scraping a drawing to create the BOM?
No. The intent is to generate structured output from evaluated instance data, not to scrape a finished drawing after the fact. The visible drawing and the output view are both produced from evaluated design data.
Inspect how evaluated data becomes BOM output
Start with the outputs documentation or open the motor control panel example to see nested assemblies, artifacts, and BOM-style rows tied to evaluated instances.