Image Removed General Notes

...

General Workflow Building

1. When building your workflowWorkflow, make sure you put more space between units Units than what seems necessary at first. It is almost always the case that you will have to revisit sections and add systems later.
2. If you know that you will need a variable Variable in more than one place, it is advisable to create a variable Variable for it.
   1. If the variable Variable is only used within one workflow, use workflow variables Workflow Variables (not project variablesProject Variables)
3. Use Workflow variables Variables to cover large distances between units, to avoid unnecessary cable overlapping.
4. If you find yourself duplicating a system for multiple parts of your projectProject, encapsulate its functionality in a WorkflowUnitSubworkflow (using the Workflow Unit).
   1. When designing a WorkflowUnit Workflow Unit it is important that you expose both in- and out trigger-triggers, since workflow Workflow units will only pass variables Variables to the 'sub-workflow' on Subworkflow on a trigger tick.
   2. When you are done with your main workflowWorkflow, expose the trigger In. trigger outTriggers, and any variables Variables that you deem necessary. (see published ins and outs) - This will allow someone else to reuse your workflow.
   3. Provide necessary information about published input ports Input Ports via an annotation → see published inputs

Image Removed Main Bus Design

It is best practice to layer indistinct systems Vertically, conversely, if two systems are distict from one another they are layered horizontally

...

1. 1. Annotations.

Main Bus Design

Having a well structured Workflow is crucial for larger Projects, as it severely decreases the overhead which is required to fix problems, implement changes and introduce other developers to the Workflow design. There are three "bus design" practices: