Node A1

IDEF0 Diagram Builder

Draw a standards-correct IDEF0 diagram: activities on the diagonal, ICOM arrows on the right sides of the box, six activities maximum. Export SVG or PNG.

What IDEF0 arrows mean

Every arrow role is encoded by which side of the box it touches. Inputs enter the left and are transformed by the activity. Controls enter the top and govern how the activity runs — standards, plans, doctrine. Outputs leave the right. Mechanisms enter the bottom: the people, tools, and systems that perform the activity.

IDEF0 caps each diagram at six activities. When you run out of room, you do not add a seventh box — you decompose: any activity becomes its own child diagram carrying its node number (A2 decomposes into A21, A22, ...). That discipline is the entire reason IDEF0 models stay readable at any scale. In this builder, double-click any box (or use its ▼ button in the activity table) to open its child sheet; the breadcrumb above the canvas tracks where you are in the decomposition, and saving to a .idef0 file captures every sheet at once.

Wondering whether IDEF0 is even the right notation for your problem? Read the guide: IDEF0 vs SysML activity diagrams — which one you actually need.