- Home
- Blog
- EDGEBIC How-To
- How to Add an Annotation to the Routing Diagram in…
How to Add an Annotation to the Routing Diagram in EDGEBIC
To add an annotation to the routing diagram in EDGEBIC by User Solutions, open the routing in the Designer and click Add annotation on the toolbar. The button drops a free-floating sticky note onto the canvas that you can position anywhere and type into. Right-click a note to edit or delete it. Annotations are documentation only: the scheduler ignores them entirely, so they never touch timing, capacity, or the plan. They exist to carry context for the next planner, such as why a step is shaped the way it is or that a branch is pending a decision.
This recipe covers one specific task: a canvas-level note. For a remark attached to a single operation, see how to add a note to a routing step. For a tour of the visual editor, read EDGEBIC graphical BOR designer tour and how to build a routing as a flow chart.
Before You Start
- The routing open in the Designer. Annotations are a Designer feature and live on the diagram canvas.
- The message you want to record, and a sense of where on the canvas it belongs, since a note is free-floating and you position it yourself.
- A reminder that this is documentation only. If you actually need to change timing or capacity, edit the step's fields instead.
Step by Step
- Open the BOR tab and switch to Designer mode.
- Click Add annotation + on the toolbar. A sticky note appears on the canvas.
- Drag the note to the position you want, for example beside the branch or step it comments on.
- Type your remark into the note.
- To change or remove it later, right-click the note and choose Edit or Delete.
- Click Update to save the routing so the annotation persists with the diagram.
What Changes When You Save
Saving stores the annotation with the routing diagram, so it reappears the next time anyone opens the Designer for that routing, in the same place. Nothing else changes: the scheduler does not read annotations, so no timing, capacity, or date is affected. This is the whole point of the feature. You can add as many notes as you like without any risk to the plan, which makes annotations a safe way to leave context that a step's own fields cannot express, such as a reason, a caveat, or a pending decision.
How to Check It Worked
After saving, the annotation should remain on the canvas at the position you placed it. Reopen the routing in the Designer to confirm it persisted rather than living only in your current session. Run a schedule and confirm the plan is unchanged from before you added the note, which verifies the annotation is documentation only and did not alter anything.
Common Mistakes
- Using an annotation to change the plan. Annotations are ignored by the scheduler. If you need a real delay or a capacity change, edit the step's fields.
- Closing without saving. An unsaved annotation is lost like any other unsaved Designer edit. Click Update before leaving.
- Confusing an annotation with a step note. An annotation floats on the canvas and belongs to no step. A step note is the Description field on one row. Pick the one that matches where the remark belongs.
- Overloading the canvas. Too many notes clutter a large diagram. Keep them short and place them near what they describe.
Related Reading
- How to connect two steps in the routing designer for building the diagram itself.
- How to put a product image on a routing node for another way to make a diagram easier to read.
- EDGEBIC and the EDGEBIC how-to hub for the full recipe set.
An annotation is a small courtesy to the next planner: a sticky note on the routing that carries the context the fields cannot, with zero risk of nudging the schedule, because the engine never reads it.
Expert Q&A: Deep Dive
Q: I want to flag on the routing that we are waiting on a tooling quote before this branch is final. Annotation or step note?
A: Use an annotation. It is a canvas-level remark that does not belong to any single step, which fits a status note about a branch or the whole routing. Click Add annotation, type the reminder, and position it near the affected branch. Because the scheduler ignores it, the note has no effect on timing, so it is purely a message to the next planner. Save the routing to keep it.
Q: Will my annotations survive when another planner opens the routing later?
A: Yes, if you save the routing after adding them. Annotations persist with the diagram, so the next planner who opens the Designer sees the same notes in the same positions. They are documentation that lives with the routing, not a session-only overlay. If you add a note and close without saving, it is lost like any other unsaved edit, so save with Update before leaving the Designer.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
