Skip to main content

bpas_revamp

Beas Feature 01 · 5 Core Concepts

5 Core Concepts of Production Planning in Beas Manufacturing

The thinking behind a schedule people trust.

Software does not fix planning on its own. These five ideas are what make finite capacity planning in Beas APS work on a real shop floor. Each one starts from a problem every plant head will recognise, explains the idea in about a hundred words, and compares it to something from everyday life.

The Five Concepts

From capacity to closed-loop planning

The first three are about how a schedule is built. The last two are about keeping it right once the shift starts.
  1. Concept 01 · Plan to what the plant can do, not to what was ordered

    Finite Capacity Planning

    The shop-floor problem it solves

    Plans promise more machine hours than the plant has, so the shortfall turns up later as late orders and weekend overtime.

    The concept explained

    A plan is a promise about time. Planning without limits schedules every order on the date it is wanted and leaves the floor to sort out the clash. Finite planning starts from the hours each resource actually has, according to its shift schedule and resource calendar. When a resource's hours are full, the next operation is dispatched to the next free time, and the work order's finish date moves with it. The plan looks less flattering, but it is true: every date on it is one the machines can meet, and overloads show up as later dates, days ahead, not as surprises on dispatch day.

    Everyday analogy

    A family car has five seats. You can promise a lift to seven relatives, but only five will fit. Finite planning tells the other two now that they are on the second trip, instead of at the door.

    Where it lives in Beas

    Each resource has a “Consider resource limits” setting. Changing it needs the Beas APS licence, the licence that adds finite capacity planning. With the calculation's capacity-limit setting enabled, such a resource is never dispatched above 100%, apart from exceptions such as manual APS fixes.

    Finite capacity planningLeft: without limits, Tuesday is booked at 150 percent of capacity. Right: with Consider resource limits, the extra work moves to Wednesday and Thursday, the next free time.Without limitsTuesday booked at 150%MonTueWedThuFriCapacityConsider resource limitsExtra work moves to free timeMonTueWedThuFriCapacity
    Without limits, Tuesday is overbooked. With Consider resource limits, the extra work moves to the next free time.
  2. Concept 02 · One resource decides the output of the whole plant

    The Bottleneck Sets the Pace

    The shop-floor problem it solves

    Everyone works hard on every machine, yet output does not rise, because one overloaded resource limits everything behind it.

    The concept explained

    In every plant, one resource has the least spare capacity for the load placed on it. What that resource can produce is what the plant can ship. An hour lost there is an hour lost for the whole factory; an hour saved on a machine with spare capacity changes nothing. Good planning therefore finds that resource first, plans it with the most care, keeps material ready in front of it, and moves suitable work to alternative resources. Everything else is planned around it. As the product mix changes, the overloaded resource can change too, so it is worth checking every week.

    Everyday analogy

    A toll plaza on a highway. Widening the road before and after it does not move more cars per hour; only opening more booths at the plaza does.

    Where it lives in Beas

    The Graphic Utilization Display shows capacity against workload per resource by day, week or month, with overloaded days in red. MRP2 shows workload against capacity per MRP scenario. Alternative resources with Optimization enabled let APS pick a more adequate resource (APS licence).

    The bottleneck sets the paceIllustrative line of four resources: turning 140, milling 80, deburring 150 and inspection 160 parts per shift. Milling has the least spare capacity, so the plant ships 80 per shift.Illustrative: parts per shiftTurning140per shiftMilling80per shiftDeburring150per shiftInspection160per shiftLeast spare capacityThe plant ships 80per shift, not 140
    Illustrative figures: the plant ships what its most loaded resource can make.
  3. Concept 03 · Start each job as late as it can still finish on time

    Schedule Backwards from the Delivery Date

    The shop-floor problem it solves

    Jobs start as soon as material arrives, tying up cash in WIP, while urgent orders wait for machines busy with work not due for weeks.

    The concept explained

    Starting early feels safe, but it costs money. Raw material is consumed, WIP piles up between machines, and capacity is spent on orders nobody needs yet. Backward scheduling starts from the delivery date and places each operation as late as it can run while still finishing on time, allowing for the idle time and overlap set between operations. Material is bought and capacity used only when needed, which keeps floor space and working capital free for urgent work. Forward scheduling is the companion: it starts from the start date to find the earliest possible finish, which is how a planner answers a new enquiry honestly.

    Everyday analogy

    Hot chapatis for guests arriving at 8. You roll and cook them at 7.45, not at 5, when they would be cold and the stove would have been busy for nothing.

    Where it lives in Beas

    APS calculation types run the schedule. Backward Dispatch dispatches to the latest possible date, taking time reservations into account, and is meant for buying material as late as possible. Dispatch forward calculates on a resource-optimised basis from the start date. Idle Time and Overlap Limit are set on each routing position.

    Scheduling backwards from the delivery dateTop row: Dispatch forward runs operations 10, 20 and 30 from the start date and finishes early, so work in progress waits. Bottom row: Backward Dispatch places the same operations as late as possible so they finish on the delivery date, leaving capacity free for urgent work.Dispatch forwardFinished early: WIP waitsOp 10Op 20Op 30Backward DispatchCapacity free for urgent workOp 10Op 20Op 30Start dateDelivery date
    Dispatch forward finishes early and leaves WIP waiting. Backward Dispatch finishes on the delivery date.
  4. Concept 04 · Accurate times and calendars come before clever scheduling

    The Schedule Is Only as Good as the Master Data

    The shop-floor problem it solves

    The plan says a job takes six hours, the floor takes ten, and after a few weeks nobody trusts the schedule.

    The concept explained

    A scheduling engine does arithmetic on master data. If the routing names the wrong resource, uses a setup time that ignores tool changes, or a time per unit from a drawing made five years ago, the plan will be precisely wrong. The same is true of shift schedules that miss festival holidays or planned maintenance. Accurate routings, realistic times, correct calendars and defined alternative resources are the foundation, not an afterthought. The fastest way to correct them is to compare planned times with the times operators actually report, and update the routing wherever the gap is consistent.

    Everyday analogy

    Navigation with an old map. The app calculates the route perfectly, and you still arrive late because the flyover it chose has been closed for a year.

    Where it lives in Beas

    Routing positions hold the resource, Setup time, Mach+Labor Time/unit, Idle Time and Overlap Limit. Post-calculation per work order compares accrued with planned cost, and the times reported at Beas terminals are the actuals behind it.

    The schedule is only as good as the master dataRouting positions with resource, setup time and machine and labour time per unit, shift schedules and resource calendars, and alternative resources feed the APS calculation, which produces a schedule the floor can meet. When reported times differ from planned times, for example 6 hours planned against 10 reported, the routing is corrected.Routing positionResource · Setup time ·Mach+Labor Time/unitShift scheduleand resourcecalendarAlternativeresourcesAPScalculationScheduledates the floorcan meetPlanned 6 h · reported 10 h at the terminalCorrect the routing where the gap repeats
    Correct routings and calendars in, a schedule the floor can meet out. Reported times show where to correct the routing.
  5. Concept 05 · A plan that learns from the floor every shift

    Plan, Execute, Feed Back

    The shop-floor problem it solves

    The plan made on Monday morning is already wrong by Monday evening, because breakdowns, rejections and rush orders never reach it.

    The concept explained

    No plan survives the shift intact. Machines stop, a batch fails inspection, an OEM pulls a schedule forward. Planning only works as a closed loop. Work is planned in APS; operators report start, interruption, completion, finished goods and scrap against each operation as they work; and the planner recalculates from the real position, not from the morning's assumption. Over the weeks, the same reports show where standard times are wrong. A plan that is corrected from the floor every shift is worth far more than a perfect plan made once a week.

    Everyday analogy

    A cricket captain sets the field before the over, then moves fielders ball by ball as he sees how the batsman is actually playing. The team-meeting plan is only the starting point.

    Where it lives in Beas

    Operators report at Beas terminals (Terminal Production Data Collection licence, BEAS_TERMINAL_PDC). When APS runs Dispatch forward, work orders that are logged in (started) are fixed, and the Catch Up calculation moves time reservations from the past into the future.

    BPAS Exclusive Enhancement · misBoost Planned against made, every morning: Production & Planning boosters built from your Beas and SAP Business One data, sent on autopilot.
    The closed planning loopFour steps in a circle: plan in APS within resource limits, work at the machine, report at the terminal, recalculate from what happened. Corrected standard times feed back into the next plan.Every shiftthe plan learnsfrom the floor1Plan in APSWithin resource limits2WorkAt the machine3ReportAt the terminal4RecalculateFrom what happenedStandard timescorrected
    Plan, work, report, recalculate: every shift.
Quick Self-Check

Five questions for your next planning meeting

One question per concept. Ask them of your planner, plant head and sales head together, and compare the answers.
Two or more "no" answers usually means the plan is costing you overtime, freight and missed dates.
Ask the five questions together, and compare the answers.
  1. Are our delivery dates based on current machine load? Concept 01 · Finite capacity planning
  2. Can we name this week's bottleneck, and the orders behind it? Concept 02 · The bottleneck sets the pace
  3. Do jobs start when they need to, not just when material arrives? Concept 03 · Schedule backwards from the delivery date
  4. Do our setup times and times per unit match what the floor actually takes? Concept 04 · The schedule is only as good as the master data
  5. Does the plan update during the shift, from what the floor reports? Concept 05 · Plan, execute, feed back
Go Deeper

More on Production Planning

Test these five ideas on your own plant

In a BPAS gap review we look at your SAP B1 data, your routings and your shift pattern, and show you which of the five concepts is costing you most today.