# 5. Practical Guidance for Everyone

*Read this section regardless of your business model*

### Getting Started Checklists

#### For Design-Outsource Model

**Initial Setup (Do Once):**

* \[ ] **Identify your regular suppliers**
  * List company names and contacts
  * Document machine types (Hundegger, K2, SCM, hand-cut)
  * Note file format requirements (BVX, BVN, BTL)
  * Record typical lead times
* \[ ] **Set up MOS structure in Dietrich's**
  * Define MOS Groups by supplier (-1, -2, -3, etc.)
  * Create package naming convention
  * Document your MOS scheme for team reference
* \[ ] **Configure Dietrich's for each supplier**
  * Set appropriate tool dimensions
  * Configure post-processors
  * Set up item numbers for their materials
  * Create export templates for each
* \[ ] **Establish documentation standards**
  * 2D drawing template (fully dimensioned)
  * Material list format
  * Label content and format
  * File naming conventions
  * Folder organization structure
* \[ ] **Create supplier templates**
  * Fabrication package checklist
  * PO template
  * Delivery coordination form
  * Quality inspection checklist

***

**For Each Project (Repeat):**

* \[ ] **Project initiation**
  * Confirm which suppliers will be used
  * Set up project folders (one per supplier)
  * Initialize MOS groups and packages
* \[ ] **During design**
  * Assign MOS groups as you create components
  * Design for known supplier constraints
  * Verify MOS assignments before outputs
* \[ ] **Generate outputs**
  * Filter by supplier (Display Settings)
  * Export machine files (BVX/BVN/BTL)
  * Generate 2D drawings (PDFs)
  * Create material lists (Excel/CSV)
  * Produce labels
  * Package everything per supplier
* \[ ] **Coordinate with suppliers**
  * Send fabrication packages
  * Request quotes (if needed)
  * Issue purchase orders
  * Confirm delivery dates
  * Track progress (weekly check-ins)
* \[ ] **Quality control**
  * Inspect at delivery against 2D drawings
  * Document any issues immediately
  * Clear responsibility with suppliers
  * Approve for installation once verified

***

#### For Vertical Integration Model

**Integration Readiness Assessment (Before Starting):**

* \[ ] **Document current processes**
  * Map current workflow from design to delivery
  * Identify all work centers
  * Document routing for typical components
  * List all quality control points
* \[ ] **Assess ERP readiness (use Section 7 criteria)**
  * Production volume sufficient? (>100 comp/day)
  * Repetitive production? (>50 similar projects/year)
  * Budget adequate? (>$100K)
  * IT capability exists?
  * Executive committed?
  * Staff willing to learn?
* \[ ] **If not ready for ERP:**
  * Consider MES instead
  * Start with manual exports (Level 1)
  * Focus on process improvement first
  * Re-assess in 12-18 months
* \[ ] **If proceeding with integration:**
  * Select integration level (1, 2, or 3)
  * Define realistic budget (2-3x estimate)
  * Set realistic timeline (12-36 months)
  * Assemble project team
  * Select implementation partner

***

**Initial MOS Setup:**

* \[ ] **Define MOS structure for manufacturing**
  * MOS Groups by work center or process
    * `-1` = Primary CNC (Hundegger)
    * `-2` = Secondary CNC (K2)
    * `-3` = Hand assembly
    * `-4` = Finishing
  * Packages by manufacturing batch
  * Elements for pre-fabricated assemblies
* \[ ] **Configure item numbers**
  * Standardize part numbering
  * Sync with ERP part master
  * Set up material database
* \[ ] **Set up export templates**
  * Material list format for ERP import
  * Include all required fields (MOS data, specs, quantities)
  * Test import into ERP

***

**Manual Integration Phase (Level 1):**

* \[ ] **Test the basic workflow**
  * Design sample project in Dietrich's
  * Assign MOS (groups, packages, elements)
  * Export material list (filtered by package)
  * Import into ERP manually
  * Create work orders in ERP
  * Track through shop floor
  * Document issues and lessons learned
* \[ ] **Refine the process**
  * Identify data quality issues
  * Standardize missing information
  * Create import templates
  * Train staff on workflow
  * Document standard procedures
* \[ ] **Measure baseline**
  * Time required per export/import
  * Error rate
  * Manual effort involved
  * Establish ROI baseline

***

**Batch Integration Phase (Level 2) (TBD)**

***

### Common Mistakes and How to Avoid Them

#### Mistake 1: Not Assigning MOS Early Enough

**The problem:** Designers create components without MOS assignments, planning to "organize it later." When outputs are needed, they spend hours trying to assign everything at once, often making errors or missing components.

**Why it happens:**

* "I'll deal with it later" mentality
* Not understanding MOS importance
* Lack of clear process

**Consequences:**

* Last-minute scrambling
* Errors in supplier assignments
* Components missing from packages
* Wrong machine files to wrong suppliers
* Rework and delays

**How to avoid:**

* **Rule:** Assign MOS as you create components
* Train designers: "No component without MOS"
* Make it part of modeling workflow, not output workflow
* Quick assignment takes 5 seconds, later assignment takes 5 minutes

**Best practice:** When you create a component, immediately ask: "Which supplier makes this?" Assign the MOS group right then.

***

#### Mistake 2: Confusing Packages and Elements

**The problem:** Users create "packages" for things that should be elements (or vice versa), leading to confusion about what's assembled and what isn't.

**Classic confusion:** "I created a package called 'Wall-Panel-W201' but it won't show up as an assembled unit..." → **Wrong tool.** That should be an Element, not a Package.

**Remember:**

* **Package** = Process grouping (CNC batch, delivery) - NOT assembled
* **Element** = Assembly unit (pre-fab panel) - ARE assembled
* **Use both** when components are machined separately but assembled later

**How to avoid:**

* Review Section 2.4 (Package vs. Element)
* Ask: "Will these components be assembled together?" → Element
* Ask: "Are these grouped for manufacturing/delivery only?" → Package
* When in doubt: most things need BOTH

***

#### Mistake 3: Trying to Integrate Before Processes Are Documented

**The problem:** Companies buy ERP and attempt integration while their processes are still ad-hoc and undocumented. Result: automating chaos.

**Why it happens:**

* "ERP will fix our process problems" (it won't)
* Pressure to "modernize" quickly
* Not understanding ERP requirements

**Consequences:**

* ERP doesn't match actual workflow
* Constant system customization
* Staff confusion and resistance
* Failed implementation
* Wasted investment ($$$)

**How to avoid:**

* **Document processes FIRST, then automate**
* Map current workflow completely
* Identify improvements
* Standardize procedures
* THEN consider systems to support them

**Best practice:** If you can't explain your process clearly on a whiteboard in 30 minutes, you're not ready to automate it.

***

***

### Quick Reference Tables

#### MOS Groups Quick Reference

**Common organization schemes:**

| Scheme                      | MOS Group Values   | Example Use                                     |
| --------------------------- | ------------------ | ----------------------------------------------- |
| **By Supplier**             | -1, -2, -3, -4     | -1=Main CNC, -2=Glulam, -3=Hand-cut, -4=Steel   |
| **By Phase**                | 1, 2, 3, 4         | 1=Foundation, 2=Floor1, 3=Floor2, 4=Roof        |
| **By Component Type**       | 10, 20, 30, 40     | 10=Beams, 20=Columns, 30=Panels, 40=Connections |
| **By Material**             | 100, 200, 300      | 100=Glulam, 200=CLT, 300=Dimensional            |
| **Hybrid (Supplier+Phase)** | -11, -12, -21, -22 | -11=SupplierA-Phase1, -12=SupplierA-Phase2      |

**Tips:**

* Use negative numbers for suppliers (common convention)
* Use positive numbers for phases or types
* Keep numbering scheme simple
* Document your scheme for team reference

***

#### File Format Guide

**CNC Machine File Formats:**

| Format             | Machine Type                     | Notch Width | Complexity                                    | When to Use                                                    |
| ------------------ | -------------------------------- | ----------- | --------------------------------------------- | -------------------------------------------------------------- |
| **BVX**            | Hundegger Robot (newer)          | 30mm        | High - complex joinery, multi-sided machining | Supplier has newer Hundegger equipment with robot capabilities |
| **BVN**            | Hundegger (older), K2 Industries | 40mm        | Medium - standard cuts, simpler joinery       | Supplier has older Hundegger or K2 machines                    |
| **BTL**            | SCM, various other brands        | Varies      | Medium - general purpose cutting              | Supplier has SCM or requests BTL format                        |
| **BTLX**           | Enhanced BTL                     | Varies      | Medium-High - BTL with extended capabilities  | Supplier specifically requests BTLX (rare)                     |
| **None (2D only)** | Hand-cut, specialty work         | N/A         | Variable - manual fabrication                 | Large custom beams, specialty components, traditional methods  |

**Key takeaway:** Know your supplier's machine before you design!

***

***

### Conclusion

**The Core Message:**

Integration success depends on matching your approach to your business model:

**Design-Outsource:** Keep it simple. Good MOS organization, clear documentation (2D drawings), and straightforward tools (spreadsheets, PDFs) are enough. Don't overcomplicate.

**Vertically Integrated:** Integration MAY be justified if volume, repetition, and budget support it. But start simple (manual), prove value, then incrementally add complexity only where it provides clear ROI.

**Universal Truth:** Simple, well-executed processes beat complex, poorly-implemented systems every time.

***

#### The Jens Hackethal Wisdom:

> "I've seen people spend $500K trying to integrate everything with ERP and complex systems. It never works smoothly. We use Dietrich's, PDFs, Excel spreadsheets, and email. Our projects run on time and on budget. The fancy systems just add complexity and problems."

**Start where you are. Use what you have. Do what you can.**

Good MOS organization and clear documentation will take you far. Add complexity only when simple solutions no longer serve you. **Congratulations! You've completed the guide.**

You now have a practical understanding of how to integrate Dietrich's with your manufacturing workflow, whether you outsource fabrication or do it in-house.

**Remember the core principles:**

1. Match your approach to your business model
2. Start simple, add complexity only when justified
3. Good MOS organization is the foundation
4. Clear documentation beats complex systems
5. Measure results, refine incrementally

**Good luck with your integration journey!**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dietrichs.com/tutorials/tutorials-en/creating-from-dietrichs/delivery-journey/design-to-manufacture/5.-practical-guidance-for-everyone.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.