# Oracle Fusion Kanban Card Calculator

> Source: https://netray.co/tools/oracle-fusion-kanban-card-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Size a kanban loop: how many cards or containers you need for a given demand, replenishment time, container quantity and safety factor.

## Category

oracle

## Erp

Oracle Fusion Cloud SCM

## Audience

- Oracle Cloud consultant
- Lean manufacturing engineer
- Production planner

## Tool

**Kind:** calculator

**Inputs:**

#### Average daily demand

**Key:** demand

**Type:** number

**Default:** 480

**Min:** 0

**Step:** 10

**Unit:** units/day

#### Replenishment lead time

**Key:** lt

**Type:** slider

**Default:** 3

**Min:** 0.5

**Max:** 10

**Step:** 0.5

**Unit:** days

**Help:** Time from card release to full container back at the point of use.

#### Safety factor

**Key:** safety

**Type:** number

**Default:** 20

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

**Help:** Buffer for demand and lead time variation.

#### Units per container

**Key:** container

**Type:** number

**Default:** 50

**Min:** 1

**Step:** 5

**Unit:** units

#### Unit cost

**Key:** cost

**Type:** number

**Default:** 8.75

**Min:** 0

**Step:** 0.25

**Unit:** $

**Outputs:**

#### Demand during lead time

**Key:** lt_demand

**Expr:** demand * lt

**Format:** integer

#### Number of kanban cards

**Key:** cards

**Expr:** ceil(lt_demand * (1 + safety / 100) / container)

**Format:** integer

**Primary:** true

**Description:** Always rounded up to whole containers.

#### Total kanban quantity

**Key:** kanban_qty

**Expr:** cards * container

**Format:** integer

**Primary:** true

#### Days of stock in the loop

**Key:** days_stock

**Expr:** kanban_qty / demand

**Format:** decimal

#### Inventory value in the loop

**Key:** loop_value

**Expr:** kanban_qty * cost

**Format:** currency

#### Buffer above lead time demand

**Key:** buffer_units

**Expr:** kanban_qty - lt_demand

**Format:** integer

**Chart:**

#### Kanban cards vs replenishment lead time

**Type:** bar

**X:** lt

**From:** 0.5

**To:** 10

**Steps:** 20

**Series:**

- cards

**Disclaimer:** Classic single-card kanban sizing. Signal kanbans, multi-bin systems and variable demand may need different logic.

## Content

**Intro:** Kanban replenishment in Oracle Fusion Inventory and in lean production lines depends on one design decision: how many cards or containers circulate. Too few causes stockouts, too many hides problems and ties up cash. This calculator sizes the loop from demand, lead time and container quantity.

**Sections:**

#### How to use it

**Body:** Enter average daily demand at the point of use and the full replenishment lead time, from the moment a card is released until the container is refilled and back. Add a safety factor that reflects variation, typically 10% to 30% for stable loops. Enter the container quantity. The calculator returns the number of cards, the total kanban quantity, the days of stock in the loop and its inventory value. Start with a higher safety factor and then remove cards one at a time as the process proves stable.

#### The formula

**Body:** The classic formula is number of kanbans equals demand during lead time times one plus the safety factor, divided by container size, rounded up. Rounding up matters because cards are whole containers. The total kanban quantity is cards times container size, so the real buffer is larger than the safety factor alone when containers are big. This is why small containers make tighter loops: they let you tune the buffer in smaller steps.

**Bullets:**

- Cards = ceil(demand x lead time x (1 + safety) / container size)
- Kanban quantity = cards x container size
- Days of stock = kanban quantity / daily demand

#### Mistakes to avoid

**Body:** Do not use the supplier quoted lead time if the loop includes transport, counting and travel waits; use the observed full cycle. Do not size on average demand if demand has seasonal peaks, since cards are only changed on review. Avoid large containers just because of packaging convenience, as they inflate the loop. Review loops on a regular cycle and reduce cards where they never empty, since that signals excess.

**Cta:** If you want kanban loops reviewed against actual consumption data in your ERP, we can help. It is an optional extra and the tool works without it.

**Faq:**

#### What safety factor should I choose?

**Answer:** Begin at 10% to 30% depending on demand and lead time variation. Stable, short loops can run lower. Unstable suppliers or lumpy demand need more. Lower it gradually as evidence shows the loop is not emptying.

#### Why is the number of cards rounded up?

**Answer:** Because a card represents a whole container. Rounding down would leave the loop short of the required stock, so the formula always rounds up to the next integer.

#### Can I use this for supplier kanban?

**Answer:** Yes, as long as the lead time covers the whole supplier cycle: signal, picking, transport and receiving. Add extra safety for transport variation and for any minimum shipment size the supplier imposes.

#### What does days of stock tell me?

**Answer:** It is the total buffer in the loop expressed in days of demand. If it is much larger than the lead time in days, the loop holds more stock than the replenishment cycle justifies. Reduce cards or container size.

## Search terms

kanban card calculator, number of kanbans formula, oracle fusion kanban replenishment, kanban quantity calculation, kanban container size lead time, lean kanban sizing, kanban safety factor, pull system card count

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json