What Is a BOR Annotation in Routing? EDGEBIC Definition

A BOR annotation is a free-text sticky note attached to a step in the graphical routing designer. The BOR, or bill of routing, is the recipe that specifies which work center performs each step and for how long; an annotation is a note pinned to that recipe. It carries the human context a planner or operator needs, a reminder, a caution, a setup tip, and it changes nothing about how the step is scheduled. It is the Post-it stuck to the recipe card.

This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary. For the routing the note attaches to, see what is a bill of routing.

How a BOR Annotation Works

A routing is a graph of steps, each with a work center, times, and sequence. That structure is what the engine reads to build a schedule. An annotation lives alongside that structure as pure documentation: it is text a person pins to a step, and it is invisible to the scheduling calculation.

Because it is documentation and not logic, an annotation is safe to add, edit, or delete at any time. It does not alter the step's work center, its hours, its sequence number, or any of the fields the engine acts on. You never re-run a schedule because you changed a note. The value is entirely in preserving context that would otherwise live only in an experienced operator's memory.

The annotation is attached to the routing step in the graphical designer, so it appears in context next to the operation it describes, and it travels with the routing wherever that routing is used.

A Concrete Example

Everyone on the floor keeps forgetting to preheat the fixture before the milling step, and every so often a part comes out wrong because of it. The knowledge exists, it just lives in one veteran machinist's head.

The planner opens the routing in the graphical designer, selects the milling step, and adds an annotation that reads remember to preheat. The note pins to the step like a Post-it on the recipe card. Now anyone who opens that routing sees the reminder right where it matters, next to the operation it concerns. Nothing about how the milling step schedules changed; the engine still sees the same work center, hours, and sequence. All that changed is that the tribal knowledge is now written down, in context, where the next person will find it.

How EDGEBIC Uses It

A BOR annotation is a documentation feature of the graphical routing designer:

• It attaches to a routing step and displays in the designer next to that step, so context sits with the operation it belongs to.
• The engine ignores it. An annotation carries no scheduling meaning; work center, times, and sequence are untouched, so notes never disturb the plan.
• It travels with the routing. Because the note lives on the routing rather than one scheduled job, it persists wherever the routing is used.

An annotation captures free-text guidance; for the structured, code-driven side of a routing, the routing itself is documented in what is a bill of routing. To pin a note yourself, follow how to add an annotation to the routing diagram.