EP notes2 by s925457

VIEWS: 27 PAGES: 46

									CC   Page 1 7/6/2012EP notes.
‘




                    ENTERPRISE PLANNING IN BAAN 5
                           CLARK COLVIN
NOTES TAKEN FROM SEVERAL SOURCES.




                                                    1
UP012
An item’s supply can be planned using a combination of master-based and order-based planning. This division is controlled
using the item’s order horizon and planning horizon. Or you can choose one method or the other by adjusting the order horizon.
Planning occurring before the order horizon will be order based, and planning after the order horizon will be master based. As a
rule, a supply plan in a certain plan period exists as long as that period falls
outside the item’s order horizon. When the plan period involved moves within
the order horizon, BaanERP will discard the supply plan involved in the next
planning simulation, because within the order horizon, supply is planned by
means of planned orders.

In a master-plan simulation, BaanERP generates a supply plan to cover the
(forecast and actual) demand, and to meet the target inventory levels specified
in the inventory plan. Moreover, if you use workload control, BaanERP tries to
generate a feasible production plan that meets material and/or capacity
constraints, while taking into account the parameters

Master-based planning receives and uses the following types of demand and
sales data:
DEMAND
Customer-order data from the Sales Control (SLS) module
Sales budgets from the Sales Statistics (SST) module, which can be
converted to a demand forecast in master-based planning
Assembly-part demand forecast from BaanERP Configurator (CF), treated
as special demand in master-based planning

Master-based planning receives and uses the following types of supply data:
SUPPLY
Production-order data from the Shop Floor Control (SFC) module
Purchase-order data from the Purchase Control (PUR) module
Warehousing-order data from Baan Warehousing (WH)

Master-based planning receives information about capacity utilization from:
CAPACITY
The Resource Requirements Planning (RRP) module, which handles order-based
planning
The Shop Floor Control (SFC) module, which handles the execution of
production orders for standars items
The Project Control (PCS) module, which handles the execution of
production orders for project items
Baan Service (TS), which handles the execution of service and maintenance
activities on work centers (resources)

In addition, master-based planning interacts with the following modules in Baan
Enterprise Planning:
Resource Planning Data    (RPD),   which you can use to:
- Maintain plan-item and resource settings
- Initialize master plans
Resource Analysis and Optimization      (RAO),    which you can use to:
- Evaluate the results of planning situations and planning solutions
- Optimize order parameters for production
Plan Aggregation and Transfer    (PAT    ), which you can use to:
- Aggregate planning data to a more general (product family) level
- Disaggregate planning data to a more specific (item) level
- Transfer production plans directly to the SFC module


                                                                                                                                   2
MPS is covered in Baan by Resource Master Planning. Master Based Planning
Process Overview
The master plan is an overall production plan, which contains a company's logistic targets with respect to sales,
production and inventory. In this function, a master plan is created based on a demand plan, created manually or
generated by Demand Management or Supply Chain Planning. Master Planning looks at the critical capacities and
critical materials.


   Master-based planning
     Comparable to traditional MPS
     Planning data recorded in terms of time buckets
     Supply is planned in form of a supply plan
     Critical materials and critical capacity are defined and used for production planning

BaanERP offers several methods for creating a demand forecast and/or extra
demand:
Demand forecasting (and consumption of forecast by actual demand)
The advantage of maintaining an item master plan is that you have access to the following types of master-plan functionality:


Forecast-based inventory planning
Capable-to-Promise (CTP) techniques
Channel planning
This functionality is available over the full planning horizon.
Special demand is maintained in a special session in the DSP module. Here you
can manually enter or modify special demand values, and also record a reason
for each instance of special demand.




                                                                                                                                3
;’

     If the Dependent Demand
     Forecast check box in the Plan
     Item Data
     (cprpd1500m000) session is
     selected, dependent demand
     (resulting from the
     explosion of requirements for
     manufactured or distributed items)
     will also be
     used to consume the demand plan.
     dependent demand (which results
     from the explosion of requirements
     for manufactured or distributed
     items) will be included in the
     historical demand on which the
     forecast generation is based.




                                       4
‘
    n

    If you want the inventory plan to be
    based on the demand forecast, select
    the Forecast Based Generation
    Method check box in the Plan Item
    Data (cprpd1500m000) session, and
    enter a value for the forecast horizon
    in the Forecast Horizon field.
    If you want the inventory plan to be
    based on the safety stock and the
    seasonal patterns defined in the Item
    Ordering Data (tcibd2500m000)
    session, clear the Forecast Based
    Generation Method check box in the
    Plan Item Data (cprpd1500m000)
    session.

‘
            The availability and behavior
            of these FORECAST methods
            are influenced by a plan item’s
            settings for automatic
            updating. You can find these
            settings in the Plan Items
            (cprpd1101s000) details
            session.




‘
‘




                                              5
‘You can create master plans by running the Initialize, Roll and Update Scenario
(cprpd4200m000) session.
FORECASTS
BaanERP offers several methods for creating a demand forecast and/or extra
demand:
Generate a forecast based on historical demand data
‘




Generate a forecast based on sales budgets. Sales budgets are defined in the Sales Statistics (SST) module in Baan
Order Management.

Copy a forecast from another item master plan
Obtain a forecast by disaggregation (from a higher product-family level) or
aggregation (from a lower item level)
Manually enter forecast values. Use the Special Demand by Item
(cpdsp2100m000) session to maintain special demand for an item or channel.

REVIEW DEMAND

You can view the results of your demand planning in the Item Master Plan
(cprmp2101m000) session. You can view the results of your demand planning for channels in the Channel
Master Plan (cpdsp5130m000) session or the Channel Periods by Item
(cpdsp5140m000) session.




                                                                                                                     6
                                                                              Master Plan to be
                                                                                                        Diag. Name          MPL002
                                                                                Generated
                                                                                                        Diag. Desc.         Master Planning
                                                                10                                      Diag. Version       HYBRID2a
                                                      Session                                           Diag. Cat.
                                                                                                        Creation Date       08-10-1998
                                                                                                        Modification Date   08-10-1998
                                                       Review Master Plan


                                                      20




                                                                30
                                                            XOR

                                                                                 Yes
                                                             Maintain
                                                            Scenario?

                                                                                       Process 50
                                                            40         No


                                                                                            Maintain Scenario

                                                             70
                                                            XOR
                                                                                       60
                                                                Setup            Yes
                                                                Master
                                                                 Plan?
                                                                                       Process 360
                                                            350
                                                                      No
                                                                                         Set Up Master Plan


                                                                                       370



                                                                380
                                                      Session



                                                       Simulate Master Plan


                                                      390




                                                                680
                                                      Process



                                                       Analyze Master Plan


                                                      690




                                                                710
    Process                                                 XOR
                                                Yes
                                                            Corrective
     Perform Corrective
                                                             Actions
          Actions
                                                            Needed?
                                 730
    740                                                     720
                                                                         No




                                                                700
                                                            OR


                                                            Decide on
                                                            Action(s)
                                                                                                        No Action
                          Actual Scenario
                                                            490



                                Session   620                         Process 600                 650

                                  Transfer Production
                                                                       Move Master Plan to
                                   Plan to Production
                                                                      (Firm) Planned Orders
                                         Orders

                                630                                   610




                                                            JOIN
                                          660                                  670
                                                              (No)
                                                             Actions
                                                            Performed

                                                            640

                                                                              Generated Master
                                                                                    Plan
                                                                590








                                                                                                                                              7


   Order-based planning
     Comparable to traditional MRP
     Planning data recorded on a second by second basis
     Supply is planned in form of planned orders
     All material and capacity are defined and used for production planning




                                                                               8
                                                         Order Plans to be
                                                                                       Diag. Name          MPL003
                                                             Created
                                                                                       Diag. Desc.         Order Planning
                                                                                       Diag. Version       HYBRID2a
                                             10
                                   Session                                             Diag. Cat.
                                                                                       Creation Date       08-10-1998
                                                                                       Modification Date   08-10-1998
                                        Review Order Plan


                                   20




                                             940
                                           XOR


                                            Maintain        Yes
                                           Scenario?

                                                                        960
                                           950                Process
                                                   No


                                                                   Maintain Scenario

                                             30
                                                              970
                                   Session



                                         Simulate Orders


                                   390




                                   Process   400



                                     Analyze Order Plan


                                   470




                                             710
Process                                    XOR

                             Yes           Corrective
  Perform Corrective
                                            Actions
       Actions
                                           Needed?
                       810
820                                        800     No




                                             830

                                           XOR

                                                             Yes
                                           Generate
                                             Tools
                                         Requirements?
                                                                        910
                                           890
                                                   No         Process



                                                                    Generate Tools
                                                                    Requirements

                                             900
                                           XOR
                                                              870
                                             Transfer         No
                                             Planned
                                             Orders?

                                           530
                                                   Yes




                                             930
                                   Process



                                        Transfer Planned
                                             Orders


                                   920



                                                                                                                            9
                                         Created Order Plans
                                            590
CTP/ATP

Master-based planning supports the following types of ATP and CTP:
- ATP
- Component CTP (optional)
- Capacity CTP (optional)
- Cycle CTP (optional)
--Family CTP:
--Channel ATP:

n
To use standard ATP (and any ATP/CTP at all):
- Select the CTP Check for Sales check box in the EP Parameters
(cprpd0100s000) session.
- Set the appropriate CTP time fence in the Plan Item Data
(cprpd1500m000) session.
ATP data is only maintained within the CTP time fence; beyond the CTP
time fence, BaanERP assumes that all customer orders can be accepted
without checking availability.
n
To use component CTP checks, capacity CTP checks, and/or cycle CTP
checks, select the corresponding check boxes in the Plan Item Data
(cprpd1500m000) session.

n
For an item, you can check standard ATP in the item master plan.
n
For a channel, you can check channel ATP in the channel master plan.
n
For a resource, you can check capacity CTP in the resource master plan.
Moreover, the Report Capacity CTP of Items by Resource
(cpdsp4420m000) session provides a report specifying for each item
produced by that resource, what quantity of the item can be produced, based
on the capacity CTP.
n
In the ATP – Handling (tdsls4899m000) session, you can check if a
requested quantity is available (or can be made available) on a requested
date or, if not, when it can be available. You can use the same types of CTP
check that have been selected for the item in the Plan Items
(cprpd1101s000) details session, or disable one or more of these checks.


Baan offers both available-to-promise and capable-to-promise. The capable-to-promise (CTP) quantity of a plan item is the
quantity that the company can deliver to a customer in a certain plan period. The capable-to-promise function is also
called due date quoting. If an item is unavailable, Baan can generate a delivery schedule and can report what created the failure
to deliver on the original requested date. Available-to-promise is the amount of inventory on hand to support an order. This
function is typically used in a make to stock environment. Available to promise (ATP) in Baan is used to determine the
quantity of an item that is expected to be on hand based on the supply of that item.
CTP allows for a component and capacity check to see if components and capacity can be available to increase production to
meet customer demand. Only components and work centers that BaanUser defines as critical will be reviewed. The speed of
the CTP feature is greatly influenced by the number of items and work centers that are defined as critical.


There is a fixed lead time parameter that specifies when on the horizon the planning system will use fixed lead times as opposed
to lead times calculated from the routings. Capacity requirement planning in RRP will only look at items using calculated lead-
time.


                                                                                                                              10
     Fixed lead time horizon - the number of workdays until the date for which BaanERP starts planning orders using a fixed lead
      time. This fixed lead-time is entered in production data for the item. Capacity analysis is not available in RRP when fixed
      lead times are used.
     Order Horizon – the number of working days for which the order based planning procedure generates planned orders
     Planning Horizon – number of working days over which requirements are generated. BaanERP creates no master
      plans or planned orders beyond this horizon.
     Time Fence – the number of working days in the near future that an item’s master plan and an item’s planned orders are
      frozen. Within the time fence BaanERP generates no master plan and no planned orders, unless overridden by the planner.
     Forecast Time Fence – The number of working days in the near future that BaanERP ignores the forecast and
      considers only customer orders. Beyond this point, a combination of actual orders and forecasts is used.
.   Signals can be defined and maintained by planner, including:
 Settings for priority
 Settings for horizon
n
If you set the order horizon to zero, BaanERP will plan all supply through master-based supply planning
If you make the order horizon equal to the planning horizon, BaanERP will plan all supply through order-based supply planning

     Settings for tolerance
     Settings for maximum number of signals

SIGNALS
n
Planning signals are generated during the simulation run,. These signals are
shown in a report after the simulation, but they can also be saved for later
reference. If you want to use signal functionality, you should define the
appropriate settings in the RAO module.


The following categories of signal types can be distinguished:
     Inventory and demand signals - Inventory and demand signals are item signals that refer to a projected inventory
      level or a demand quantity. They indicate that the level or quantity involved is below or above a certain norm level.
     Order signals - Order signals are item signals which refer to the planning and execution of orders
     Resource signals - Resource signals are related to the planning of resources. They warn you when there is a
      utilization or workload problem
     Error signals - Error signals are item signals that indicate errors occurring during a planning run
‘
Plan unit groups are a set of plan items that share the production capacity of certain resources. Plan units are used for workload
control (master based planning).



Workload Control
The workload-control planning method is basically a leveling algorithm that levels the production plans of several
items simultaneously. If you want to use workload control, you should group your plan items into
plan units, and set the master-planning engine of these plan units to
workload control. If the production plan in a particular plan period creates an overload of the available production
capacity, BaanERP moves a part of the production plan to an earlier or later period. If the available materials are
insufficient, BaanERP also responds by moving part of the production plan. If you use workload control for certain items,
you can view the performance
indicators for workload control in the Work Load Control Performance
Indicators (cpwlc2520m000) session.
     Step 1: Generate the non-constraint plan
      BaanERP generates a production plan in which capacity and material constraints are ignored. In this plan each
      item is produced exactly when it is needed. This plan is generated in the same way as described for the infinite
      planning method.

     Step 2: Backward planning
      Backward planning starts from the non-constraint production plan and re-plans this production plan by considering
                                                                                                                               11
    any material and capacity constraints. All plan periods are planned one by one, starting from the last period, and
    working backward up to the first plan period. If the production volume cannot be planned completely due to
    material or capacity constraints, part of it is moved to the preceding period. The order in which the items are
    planned in each period has a great influence on the resulting plan. This order can be defined by specifying a
    priority rule in the planning parameters. If the algorithm arrives at the first plan period, and the production volume
    in that period exceeds the capacity or material constraints, the method fails to generate a feasible plan in which all
    desired delivery dates are met.

   Step 3: Forward planning
    The forward planning always results in a feasible plan. However, it is possible that a production volume is delivered
    late. The forward planning step starts at the first period and plans the periods one by one. Production volumes that
    cannot be planned completely due to material or capacity constraints are moved to the next period.
‘


By defining a bill of enterprise, you can print or view the inventory of related logistic companies and warehouses. The is
also a multi-site planning function that will need to be reviewed.




                                                                                                                         12
INVENTORY PLANNING
DSP Demand and Sales Planning
RMP Resource Master Planning
n
If you want the inventory plan to be based on the demand forecast, select
the Forecast Based Generation Method check box in the Plan Item Data
(cprpd1500m000) session, and enter a value for the forecast horizon in the
Forecast Horizon field.
n
If you want the inventory plan to be based on the safety stock and the
seasonal patterns defined in the Item Ordering Data (tcibd2500m000)
session, clear the Forecast Based Generation Method check box in the
Plan Item Data (cprpd1500m000) session.
You can manually enter values or modify values in the inventory plan of the
item master plan. You can view the results of your inventory planning in the Item Master Plan
(cprmp2101m000) session.
The distribution part of the supply plan cannot be entered or modified in the
item master plan. As a rule, the planned distribution orders that are part of the
supply plan are generated by BaanERP.




PRODUCTION PLANNING
You can choose between two different planning engines for master-based
production planning:
n
Infinite planning (planning without material or capacity constraints)
n
Workload control (production planning using material and/or capacity
constraints)

n

View a graphical representation of your item planning in the Chart of
Item/Channel Planning (cprmp2701m000) session.
n

Review your channel planning in the Channel Master Plan
(cpdsp5130m000) session or the Channels Periods by Item
(cpdsp5140m000) session.
n

Review your resource planning in the Resource Master Plan
(cprmp3501m000) session, or view a graphical representation of it in the
Resource Chart (cprmp3701m000) session.
n

Get information on critical requirements for an item in one of the following
sessions:
Critical Material Requirements by Period (cprmp2505m000)
Origin of Critical Material Requirements (cprmp2506m000)
Critical Capacity Requirements by Plan Item (cprmp3570m000)
Origin of Critical Capacity Requirements (cprmp3560m000)
n

Get information on CTP reservations (ATP or capacity CTP quantities that
are reserved as a consequence of a component or capacity CTP check) in
one of the following sessions:
Component CTP Reservations by Plan Period (cprmp5510m000)
Origin of Component CTP Reservations (cprmp5515m000)
Capacity CTP Reservations by Plan Item (cprmp5525m000)
Origin of Capacity CTP Reservations (cprmp5520m000)
n

Review planning signals in the RAO module
n



                                                                                                13
module procedure.
‘
‘
‘




                    14
15
‘

Resource Planning Data
Module Procedure UP013A      US


The Enterprise Modeling Management (EMM) module provides the clusters
of warehouses that you use to define supplying relationships. Use the
companies that are defined in EMM to define the plan sites of a multisite
scenario and the supplying relationships.
n

In the Enterprise Modeler (BRG) module you define enterprise units. If a
logistic company does not use one standard calendar, but several calendars,
you can divide the company into enterprise units, and link a different
calendar to each enterprise unit.
The Resource Master Planning (RMP) module
n

The Demand and Sales Data (DSP) module
n

The Workload Control (WLC) module
n

The Resource Requirements Planning (RRP) module
n

The Cyclic Planning (CLP) module
Read the following documents to learn more about these planning modules:
n

Master-Based Planning (RMP/DSP/WLC) (UP012A US)
n

Order-Based Planning (RRP/CLP) (UP014A US)

A scenario identifies a set of master plans and planned orders for plan items.
A plan unit groups a set of plan items that share the production capacity of
certain resources. Plan units are only used for workload control (a master-based
planning method that takes material and/or capacity constraints into account).
A plan item can also be a product family.
A resource in Baan Enterprise Planning is a work center in Baan
Manufacturing.
Material requirements can be covered by three types of orders:
n

Production orders
n

Purchase orders
n

Distribution orders
Distribution orders model the planned movement of goods between warehouse
locations. Distribution orders are especially suitable for multisite situations.
Classes are used to group items according to one or more features. Classes are used to easily define cycle constraints, which are used in
cyclic planning.




                                                                                                                                        16
Step 1 Define the item segmentation
An administrator must define the item segmentation, before you can use Baan Enterprise Planning.
Currently Baan Enterprise Planning supports the following logical segments:
•     Cluster segment -A group of entities that are not necessarily related to one financial company or logistic
company.In the Baan Enterprise Planning package, clusters are used for groups of non-nettable warehouses,
connected by supplying relationships.
•       Project segment
•       Item-base segment
The item-base segment must correspond to the definition of the cpitem domain.
        •        The cluster segment must correspond to the definition of the tcemm.clus domain.
        •        The project segment must correspond to the definition of the tccprj domain.


Step 2 Define the actual scenario
Step 3 EP Parameters (cprpd0100s000)
Step 4 Performance Parameters (cpcom0100s000)


Simulation results, for example
Master plans and planned orders
Capacity requirements
Material requirements
Utilization of resources
If you select the Rolling Plan check box, the planning horizon and plan period
division is regularly shifted forward in time,

Define the local sites that belong to a multisite scenario in the Plan Sites
(cprpd4140m000) session.

Use the Plan Periods (cprpd4120m000) session to divide the total planning
horizon into a number of plan periods. update the scenarios
by using the Initialize, Roll and Update Scenario (cprpd4200m000) session.
You need to define plan units for workload control only (a master-based
production planning method that takes material and/or capacity constraints into
account). In order-based planning, BaanERP ignores the plan units.

                                                                                                                   17
Assign plan items to plan units by entering the plan units in the Master Plan
Unit field in the Plan Items (cprpd1101s000) session.




;
‘’ The phase number of a plan unit specifies the order in which BaanERP plans
plan units and items. In general, the production of a manufactured item is
planned before its materials are planned.

If the Online Phase Number Update check box in the EP
Parameters (cprpd0100s000) session has is, BaanERP updates the phase
numbers automatically whenever the BOM or the BCM changes.

The most important data that you define in the Plan Item Data
(cprpd1500m000) session is:
n

Plan level
n

Plan item type
n

Default warehouse
n

Default supply-source
n

Planning horizon
n

Order horizon
n

Maintain master plan




;
; By generating planned production orders for families, you can carry out
the planning and reserve resources. At the very last moment, you can

                                                                                18
decide which of the subitems you will actually produce.

You can overrule the default supply source by defining a sourcing strategy for
the plan item.




‘
The advantage of maintaining an item master plan is that you have
access to the following types of master-plan functionalities over the full
planning horizon:
n

Demand forecasting (and consumption of forecast by actual demand)
n

Forecast-based inventory-planning
n

Capable-to-promise (CTP) techniques
n

Channel planning
The disadvantage of maintaining an item master-plan is that it has an adverse
effect on system performance.




To work with calendars
In Baan Enterprise Planning, you can use two types of calendars:
n

Planning calendars, defined in the RPD module
n

Central calendars, defined in the CCP module
To define a company calendar by designate a specific
resource as the company-calendar provider, and link a calendar to that resource.

Baan Enterprise Planning applies the following rules when you select a
calendar:
n

To plan at a resource, use the resource calendar.
n

To plan at a work center that is not a resource, use the calendar of the
                                                                                   19
enterprise unit that is linked to the work center is used (see the Departments
(tcemm1524m000) session and the Enterprise Units (tgbrg0530m000)
session).
n

To plan aspects that are not related to a work center (for example, fixed lead
time), use the calendar of the default enterprise-unit of the item (see the
Plan Item Data (cprpd1500m000) session and the Enterprise Units
(tgbrg0530m000) session).
If one of these calendars is not available, Baan Enterprise Planning uses the
company calendar. If no company calendar is available either, a standard
calendar of five working days a week is used, using the basic capacity and basic
number of resource units defined for the resource or the company-calendar
provider.




‘
Calendar by Scenario (cprpd2160m000)
Define the working times and the number of resource units in the Calendar by
Scenario (cprpd2160m000) session.

To define supply-chain data




                                                                                   20
‘ Sourcing Strategies (cprpd7110m000)
Define sourcing strategies in the Sourcing Strategies (cprpd7105m000) session.
The sourcing strategy will determine whether a required item will be
manufactured, purchased, or brought in from a warehouse, possibly from
another site. You can also make combinations of sources, for example 60%
production, 40% purchase.


The supply strategy determines the criteria by which the suppliers are selected. Baan Enterprise Planning uses the supplying
relationships to plan distribution orders.
To set up distribution requirements planning (DRP)




‘


‘ Clustered items exist only in Baan Enterprise Planning. If a distribution order is
transferred to the execution level, it is changed into a warehousing order of
Transfer type (in the case of distribution within a site), or into a purchase order
(in the case of distribution between sites).




                                                                                                                               21
To initialize scenarios

During an update of the item master plan, BaanERP performs the following
actions:
n

Retrieves goods-flow data from the execution level
n

Updates receipts and requirements
n

Generates material and capacity requirements
n

Consumes demand forecast
n

Recomputes projected inventory and ATP
Note


Automatic supply planning
If you choose to use BaanERP to generate a production plan, a purchase plan,
and/or planned distribution orders automatically, you need to run a master-plan
simulation.




                                                                                  22
Order-Based Planning (RRP/CLP)
Module Procedure UP014A   US
n

Resource Requirements Planning (RRP)
n

Cyclic Planning (CLP)




                                       23
BaanERP uses the supplying relations that are
defined between the entities in the distribution chain to plan distribution orders
to move goods between clusters, or between a cluster and a nettable warehouse
(manufacturing warehouse).




You can use a single
cluster for multiple warehouses. However, note that Baan Enterprise Planning
considers warehouses in a cluster as one inventory point. A cluster can contain the following types of
warehouses:
n

Nonnettable warehouses
n

Shop-floor warehouses

Master-based planning
Roughly comparable to traditional MPS planning
Planning data is recorded in terms of time buckets (plan periods)
Supply is planned in the form of a supply plan that contains supply
quantities by plan period
In master-based production planning, only critical materials and critical
resource capacity are taken into account
n

Order-based planning
Roughly comparable to traditional MRP planning
Planning data is recorded on a second-by-second basis
Supply is planned in the form of planned orders
In order-based production planning, all necessary materials and all
necessary resource capacity are taken into account

If BaanERP maintains an item master-plan for an item, it also maintains a
channel master-plan for each channel that is linked to the item.



                                                                                                         24
Information on the resource capacity that is needed to manufacture an item,
defined in the Routing (ROU) module.
n

Resource Planning Data (RPD), which you can use to:
Maintain plan-item and resource settings
Initialize master-plans
n

Resource Master Planning (RMP), which you can use to:
Maintain item master-plans and resource master-plans
Plan supply by means of supply plans (planned supply quantities by
plan period)
n

Resource Analysis and Optimization (RAO), which you can use to:
Evaluate the results of planning situations and planning solutions
Optimize order parameters for production
n

Plan Aggregation and Transfer (PAT), which you can use to:
Aggregate planning data to a more general (product family) level
Transfer planned orders to the execution level of BaanERP


BaanERP will automatically use cyclic planning for an item if the following
conditions are met:
n

Cycles have been defined for the resource at which the item is
manufactured
n

The item involved has been assigned to specific cycles
Note


Planned orders and order statuses
Planned orders in Baan Enterprise Planning can have the following order
statuses:
n

Planned
n

Firm planned
n

Confirmed


As a rule, BaanERP will not plan any new planned orders before the last order
with Firm Planned status (including confirmed planned orders, and actual
orders). In the EP Parameters (cprpd0100s000) session, you can allow BaanERP to
generate orders before the last firm-planned order.
Moreover, if you run an order simulation with the Simulate within Time Fence
check box selected, you can optionally let BaanERP set the status of all planned
orders in the time fence to Confirmed.
to use the Capacity Use by Cycle (cpclp2520m000) session, you must maintain
resource master-plans for the resources involved.




                                                                                   25
If you have defined a class COLOR with class values RED, BLUE, and GREEN, you can
select all items with class value RED, so that all these items are assigned to the same
cycles.
Note that in top-down or bottom-up item selection, the selection is only
extended to anonymous items (not to project-specific items).
As a rule, BaanERP generates no planned orders within a plan item’s time
fence, and leaves the existing planned orders in the time fence as they are.
Time fence Select the Simulate within Time Fence check box in the Simulate orders
(cprrp1210m000) session or the Simulate Orders (Item) (cprrp1220m000)
session during an order simulation run, so that the time fence is ignored.
If there is no item master-plan, the safety stock (taking into account the
seasonal pattern) determines the required inventory level (see the Item
Ordering Data (tcibd2500m000) session)

(In the case of a project-specific item that is derived
from a standard item, BaanERP will first try to solve the shortages by
transferring anonymous inventory to project inventory.)


Baan Enterprise Planning plans orders backwards, starting from the requirement
date. As a rule, the safety time and the extra lead time are taken into account.
These are defined in the Item Ordering Data (tcibd2500m000) session and the
Plan Item Data (cprpd1500m000) session, respectively. The calculation of the
planned order’s start date and finish date proceeds as follows:
n

For planned production orders, BaanERP uses either a routing or a fixed
lead time. As a rule, the item’s routing is used to plan orders in the near
future, whereas a fixed lead time is used for longer-term planning. (You can
control the choice between routing and fixed lead time by setting the fixed
lead-time horizon in the Plan Items (cprpd1101s000) details session.)

n

Planned Orders (cprrp1500m000)              Planned Inventory Movements by Order (cprrp0511m000)


        Time-Phased Planning Overview (cprrp0520m000)
                                                                                                   26
This session gives a time-phased overview of your order-based planning.
The overview includes forecast and actual demand, planned supply orders,
and scheduled receipts. The level of detail of the information is easily
configurable, and can vary from 28-day periods to the level of individual
orders (including, for example, the order number). Moreover, you can easily
simulate extra demand and/or extra supply, and compute the resulting
inventory levels.
n

Item Master-plan (cprmp2101m000)
If you maintain an item master-plan for the item involved, you can use this
session to get an overall view of your item planning.
Resource planning
You can use the following sessions to review the capacity use of planned
production orders:
n

Capacity Use by Planned Order (cprrp2500m000)
Planned Capacity Use by Resource (Order Planning) (cprrp2501m000)
Resource Master-plan (cprmp3501m000)


CYCLIC PLANNING
Operations by Cycle (cpclp2510m000)
n

Capacity Use by Cycle (cpclp2520m000)
JIT
During an order simulation run, requirements for JIT items are automatically
translated to a purchase schedule in the PUR module, if the following
conditions apply:
n

The simulation is run for the actual scenario
n

The requirement falls within a schedule segment with Immediate, Released,
or Firm requirement type
If the requirement falls within a schedule segment with the Forecast
requirement type, a planned purchase order is generated. Any changes to the
planned order are automatically updated in the corresponding purchase
schedule.
Planned supply of project-specific items
If a project item is planned by means of module planning (in the Project Control
(PCS) module), and you want to use order-based supply planning for this item,
you must maintain an item master-plan for it. This item master-plan is used to
temporarily store the requirements from the module planning.




                                                                                   27
Plan Aggregation and Transfer
Module Procedure UP010A     US
various persons in a company are interested in the same
planning information, but at different levels of abstraction: the planner needs
detailed data for each item, whereas the account manager prefers more general
data by product family, and the executive is especially interested in high-level
overviews of product groups.
Aggregation based on product information (grouping items into product
families), for example:
Aggregate planning data from items to a product family (or from
product families to a higher-level family)
Disaggregate planning data from a product family to items (or lower-level
families)
n

Aggregation based on the business structure (grouping business sites), for
example:
Aggregate planning data from sales offices to head office
Disaggregate planning data from central office to production sites
Disaggregate planning data from production sites to distribution centers
You can (dis)aggregate data between:
n

Items
n

An item and its channels
n

Channels
If an item has a master plan, you can combine the plans and orders of multiple items to make a more general plan by means of
aggregation relationships. This process is called aggregation.
You can divide these general plans over many items by means of disaggregation.
n

Production plans and planned production orders are transferred to the Shop
Floor Control (SFC) module in Baan Manufacturing. You can transfer production plans (from the item master plan) directly to
the shop floor. This means that you do not need to convert them to planned
orders first.
n

Planned purchase orders are transferred to the Purchase Control (PUR)
module in Baan Order Management.
n

Planned distribution orders for distribution within a single site are
transferred to the Inventory Handling (INH) module in Baan Warehousing.
n

Planned distribution orders for distribution between sites are transferred to
the Purchase Control (PUR) module in Baan Order Management.
workload-based order transfer. If you do that,
planned production is transferred to the shop floor only up to the workload
norm ( the amount of work (expressed in hours) waiting to be carried out on
the shop floor) of the resource, or a percentage of that norm.
PAT also uses the following types of data:
n

Plan-item data from the Resource Planning Data (RPD) module
n

Data about aggregation relationships from the Bill of Material (BOM)
module
n

Sales-order data from the Sales Control (SLS) module



                                                                                                                               28
Major types of aggregation
Aggregation based on product information


The Plan Item Type (in the Plan Items (cprpd1101s000) details session) of
the higher item in an aggregation relationship does not necessarily have to
be Family: the item can also be a normal plan item.




clusters are used for groups of non-nettable warehouses, connected by supplying relationships.
The clustered item represents a plan item in a distribution warehouse (nonnettable warehouse).



Another example of aggregation based on business structure is central multisite
planning. If you want to control the planning of your production and
distribution facilities at a central office, you can use aggregation to accumulate
relevant information, and disaggregation to control the division of labor
between sites.
‘
Aggregation Relationships (tibom2510m000) session, you can define such
relationships between (clustered or nonclustered) items, between channels, or
between an item and a channel. For each relationship you must specify:
n

Whether the relationship is meant for aggregation, disaggregation, or both
n

Whether the relationship concerns a particular type of planning data, or all
data
                                                                                                 29
For aggregation or disaggregation of a demand forecast, inventory plan,
production plan, or purchase plan, the target item’s settings for automatic
updating of this forecast or plan must be properly configured. You can edit
these settings in the Plan Items (cprpd1101s000) details session. The
appropriate field should be set to either (Dis)Aggregate or Always Update.

For disaggregation, BaanERP needs planning percentages to determine in what
relative quantities the planning data should be distributed over the various sub-items.
Suppose that the inventory plan of a product family is 10, and you disaggregate this
inventory plan to two sub-items. If for both sub-items the planning percentage is 50, this
means that a quantity of 5 is copied to each item’s inventory plan. Note that the sum of
the planning percentages of the various sub-items does not need to be 100. For
example, if for one of the sub-items the planning percentage is 70 instead of 50, then a
quantity of 7 will be copied to that item’s inventory plan, so that the sum of the target
values (5 + 7) is larger than the source value (10).

You can enter the planning percentage manually for each sub-item, in the
Aggregation Relationships (tibom2110s000) details session, or let BaanERP
compute these percentages on the basis of historical demand, by running the
Calculate Planning Percentages (tibom2210m000) session.

You can also use planning percentages for aggregation. In this case, the
planning percentage determines how much of the source value is included in the
target value.
If you aggregate an inventory plan from a sub-item to a product family, and the planning
percentage is 50, this means that 50 % of the inventory plan of the sub-item is copied to
the inventory plan of the family.


Use the Aggregate Channel, Plans & Orders (cppat2210m000) session or the




Disaggregate Channels, Plans & Orders (cppat2220m000) session to
(dis)aggregate planning data.’



                                                                                             30
‘If you want to use the (dis)aggregated data for automatic supply
planning, you can do this by running the Simulate Master Plan
(cprmp1202m000) session.


Aggregate Channel to Item Plans (cpdsp5210m000)
You can use the Aggregate Channel to Item Plans (cpdsp5210m000) session to
aggregate planning data (demand forecast, extra demand, and/or allowed
demand) from the master plans of an item’s channels to the master plan of the
item itself.


Initialize, Roll & Update Scenario session for the family item (with the Update
Goods Flow Data check box selected).
Suppose that aggregation relationships have been defined for aggregating goods-flow
data from various types of bikes to a product family BIKE. If you update the scenario
involved (for BIKE, or for a range of items), BaanERP will read the goods-flow data of the
various bike types, and aggregate this data to the item master plan of BIKE.
Example
goods flow
Goods flow is a collective term for all planned actions that influence the inventory of items, such as customer orders,
quotations, production orders, and inventory adjustments.
Goods-flow data is generally recorded in the ERP system.
When the goods-flow data in Baan Enterprise Planning is updated, this data
is loaded into Baan Enterprise Planning as a basis for the planning.
This includes both the historical and the planned goods flow.
The inventory of the current period is also retrieved from the ERP system, but only the inventory in nettable
warehouses is included.
The orders that Baan Enterprise Planning plans become part of the goods
flow, when they are transferred to the ERP system.
BaanERP generates the goods-flow data for product families by aggregation through the aggregation relationships.

The transfer procedure
n

Workload-based order transfer: transfer planned production volumes only
up to the workload norm (the desired number of hours of work waiting to be
carried out on the shop floor) of the resource, or a percentage of that norm.
You can define a resource’s workload norm in the Resources
(cprpd2500m000) session.
During an order simulation run, requirements for JIT items are directly passed
on to a purchase schedule in the PUR module, if the following conditions apply:
n

The simulation is run for the actual scenario
n

The requirement falls within a schedule segment with requirement type
Immediate, Released, or Firm. If the requirement falls within a schedule segment with requirement type
Forecast, a planned purchase order is generated. Any changes to the planned
order are automatically updated in the corresponding purchase schedule.




                                                                                                                          31
Resource Analysis and Optimization
Module Procedure UP011A    US


RAO helps you to monitor these factors
and decide when you should adjust your planning to avoid problems and/or
optimize performance.
Information that allows you to monitor and analyze the performance of your
planning, and to compare the performance of different planning solutions.
n

A logistic optimization algorithm that determines how often an item should
be produced, and in what quantity, to minimize production costs.
The Demand and Sales Planning (DSP) module, which contains planning
data for channels.


The purpose of these signals is to point out (potential) problems, bottlenecks, or errors in the
planning of an item or resource. each planner can define and maintain a customized set of parameters that
determine:
n

Which types of signals are generated for this planner
n

Under what conditions each type of signal is generated
n

What priority each type of signal gets
Some signals are not directed to a specific planner. For these signals, a
customized set of parameters can be defined as well. In a later stage, the signals can also be updated
without actually rerunning a simulation. mark a signal as accepted, which indicates that you want to
further analyze it. Initialize, Roll, and Update Scenario (cprpd4200m000)
n

Rebuild Resource Planning (cprpd2207m000)
n

Simulate Master Plan (cprmp1202m000)
n

Simulate Master Plan (Item) (cprmp1203m000)
n

Simulate Orders (cprrp1210m000)
n

Simulate Orders (Item) (cprrp1220m000)
The procedure’s results




                                                                                                            32
‘
choose Update in one of the following
sessions:
n

Item Master Plan (cprmp2101m000)
n

Resource Master Plan (cprmp3501m000)
n

Channel Master Plan (cpdsp5130m000)
n

Channel Periods by Item (cpdsp5140m000)
Signals by Resource (cprao1130m000)
Use this session to view the signals that refer to a particular resource. Each
signal comes with additional information, such as a reference date and a
quantity indication.




Performance indicators are computed on the basis of a specific planning
situation. These indicators provide the planner with an overall assessment of the
quality and effectiveness of the specific planning solution involved.
Use the logistic-parameter optimization business procedure to optimize the cost
efficiency of your production resources.




                                                                                    33
                                                        Parameter

    1. Company Calendar Provider

    The resource whose calendar is designated as the company calendar.

    The company calendar is used as the default calendar for master-based planning and for order-based planning.

    The company calendar also determines which days are workdays. This is important for the correct interpretation of
    horizons, time fences, and lead times, which are defined in workdays.

    Note

    If the company calendar has not been defined for the entire planning horizon, BaanERP assumes an empty
    calendar for the rest of the time periods. This can have undesired effects.

    You can use some sessions only if you entered something in this field.

    2. Actual Scenario

    The scenario that contains the operational master plan and/or order planning, as opposed to scenarios used only
    for simulation (what-if analysis).

    The actual scenario is the only scenario from which you can transfer planned orders to the execution level.

    A Capable to Promise (CTP) check is always carried out on the basis of the actual scenario. Likewise, when a
    sales order is recorded, only the ATP of the actual scenario can be updated on-line.

    3.   Efficiency Explosion

    If this check box is selected, BaanERP generates no requirements for a material outside the planning horizon of
    that material.

    This applies to the material explosion of planned production orders and the production plan.



    4. Only Reschedule Total Order Quantity

    If this check box is selected, the order-based planning method generates rescheduling messages for the total order
    quantity of a planned order.

    If this check box is cleared, the order-based planning method can generate rescheduling messages for a part of a
    planned order's order quantity.
    5.0 Planned order before firm/SFC
    If this check box is selected, BaanERP can generate planned orders before firm-planned orders.

    If this check box is cleared, BaanERP sets the planned requirements date of planned orders on or after the planned
    finish date of the last firm-planned order.
‘
‘
‘




                                                                                                                         34
Resource Planning Data /
                            RPD
Configuration / EP
Parameters

Company Calendar Provider   The resource whose calendar is designated as the company calendar.

                            The company calendar is used as the default calendar for master-based
                            planning and for order-based planning.

                            The company calendar also determines which days are workdays. This is
                            important for the correct interpretation of horizons, time fences, and lead
                            times, which are defined in workdays.

                            Note

                            If the company calendar has not been defined for the entire planning
                            horizon, BaanERP assumes an empty calendar for the rest of the time
                            periods. This can have undesired effects.

                            You can use some sessions only if you entered something in this field.

Actual Scenario             The scenario that contains the operational master plan and/or order
                            planning, as opposed to scenarios used only for simulation (what-if
                            analysis).

                            The actual scenario is the only scenario from which you can transfer
                            planned orders to the execution level.

                            A Capable to Promise (CTP) check is always carried out on the basis of
                            the actual scenario. Likewise, when a sales order is recorded, only the
                            ATP of the actual scenario can be updated online.

Refresh Rate                The rate in seconds that determines how often an automatic refresh is
                            performed in a session.

                            An automatic refresh retrieves and displays the current data from the
                            database.

                            Note

                            A refresh rate of 0 (zero) means that no refresh is performed.

Default Availability Type   The availability type that is used for resources, which use central
                            calendars.

                            The Copy ERP Calendar to Planning (cprpd2201m000) session uses this
                            availability type to copy calendars from the Central Calendar
                            Management (CCP) module to BAAN Enterprise Planning.

                            Choose an availability type for which the Available check box in the
                            Availability Types (tcccp0501m000) session is selected. The Plan Time
                            Unit field in the Availability Types (tcccp0501m000) session must have
                            the value “Exact Time”.




                                                                                                          35
Online ATP Update             Yes / No

                              If this check box is selected, BaanERP updates the ATP for a plan item
                              online, when a planned or actual inventory transaction is recorded for the
                              plan item.

                              BaanERP updates the ATP over the entire planning horizon, but only in
                              the actual scenario.

Round                         Yes / No

                              If this check box is selected, BAAN Enterprise Planning rounds all
                              displayed values.

                              The unit of a quantity determines how it is rounded. If this check box is
                              cleared, the system performance will be better.

Efficiency Explosion          Yes / No

                              If this check box is selected, BaanERP generates no requirements for a
                              material outside the planning horizon of that material.

                              This applies to the material explosion of planned production orders and
                              the production plan.

                              Note

                              You can still enter customer orders for the material outside the planning
                              horizon.

                              If this check box is cleared, BaanERP generates the requirements for a
                              certain item also outside the planning horizon of that material. This means
                              that demand from higher-level items is visible over the planning horizon of
                              that higher-level item. However, BaanERP plans no orders on the basis of
                              these requirements, because they lie outside the planning horizon.

                              Example

                              A television has a planning horizon of 6 months.

                              The power supply unit of that television has a planning horizon of 2
                              months. The order lead time for televisions is one week.

                              You have planned the production of 200 televisions to be ready five
                              months from now. If the Efficient Explosion check box has been cleared,
                              BaanERP generates the requirements for the required power supply units
                              for those 200 televisions, even if these requirements are outside the
                              planning horizon of power supply units.

Only Reschedule Total Order   Yes / No
Quantity
                              If this check box is selected, the order-based planning method generates
                              rescheduling messages for the total order quantity of a planned order.

                              If this check box is cleared, the order-based planning method can
                              generate rescheduling messages for a part of a planned order's order
                              quantity.




                                                                                                            36
CTP Check for Sales          Yes / No

                             If this check box is selected, BaanERP carries out a capable-to-promise
                             (CTP) check when a sales order for an item is closed.

                             If this check box is cleared, BaanERP does not carry out any CTP check,
                             regardless of the values of CTP-related parameters in the Plan Item Data
                             (cprpd1500m000) session.

Online Phase Number Update   Yes / No
                             If this check box is selected, BaanERP updates the phase numbers of
                             items and plan units immediately when a change occurs in a bill of
                             material (BOM) or bill of critical material (BCM).
                             If you select this check box, the phase numbers of items and plan units
                             are always consistent with the data in the BOM’s and BCM’s (Bill of
                             Critical Material).
Planned Order Before         Yes / No
Firm/SFC
                             If this check box is selected, BaanERP can generate planned orders
                             before firm-planned orders.

                             If this check box is cleared, BaanERP sets the planned requirements date
                             of planned orders on or after the planned finish date of the last firm-
                             planned order.

                             Note

                             Even if you cleared the Planned Order before Firm/SFC check box,
                             BaanERP sometimes puts the planned finish time of a planned order
                             slightly before the planned finish date of the last firm-planned order.
                             Which is caused by the backward planning method.
Performance Parameters       COMMON

Display Time Interval        The amount of time (in seconds) BaanERP waits before displaying new
                             information.
                             Sessions which process large volumes of data usually display some
                             runtime information, which enables you to monitor the session's progress.
                             However, if the screen is refreshed very frequently this may affect system
                             performance.




                                                                                                          37
Unlimited Commits                The size of the set of records that is committed with a single commit-
                                 transaction command.
                                 With this field you can control the commit-transaction behavior of BAAN
                                 Enterprise Planning.
                                 This field has a large influence on the performance of the package.
                                 The main tables for which this performance is important are:
                                 • Item/Channel Master Plan (cprmp300)
                                 • Rough Material Requirements by Period (cprmp130)
                                 • Co-Product Deliveries (cprmp138)
                                 • Rough Capacity Requirements by Plan Period (cprmp120)
                                 Specify a large number (>9999) if BaanERP uses an Oracle database for
                                 the main tables of BAAN Enterprise Planning.
                                 Specify a small number (100) if you have a database that is not able to
                                 handle large sets of records in one commit (for example, bisam).
                                 If this field has the value 0, BaanERP does not carry out any commit-
                                 transaction commands between records: BaanERP only commits
                                 complete and logical sets of records. This can lead to very large
                                 transactions.


Normal Number of BOM Lines       The number of BOM-lines in a typical BOM in your company.
                                 This field determines how much memory BaanERP allocates when
                                 reading BOM-lines from the database. A higher number leads to a better
                                 performance but also to a higher memory demand.

Multiplier 2-D Calendar Arrays   Before BAAN Enterprise Planning carries out a simulation, it loads the
                                 resource calendar into internal memory. BaanERP uses a 2-dimensional
                                 array to store the calendar.
                                 The Multiplier 2-D Calendar Arrays field determines the size of the time-
                                 dimension of the array.
                                 The size of the array is determined as follows:
                                  AS = M x MY, where AS = size of the array
                                 M = value of the Multiplier 2-D Calendar Arrays field
                                 MY = minimum array size for a one-year calendar
                                 The minimum array size for a one-year calendar suffices to store a
                                 calendar of one year, having only one working period per day. If you
                                 simulate a scenario and the multiplier is too small, BaanERP displays an
                                 error message.
                                 Allowed values
                                 Enter a value greater than zero.
                                 How to determine a suitable value
                                 1. Calculate the minimum value by using the following formula:
                                  LPV = WP x ND/365, where LPV = the lowest possible value
                                 WP = the maximum number of working periods per day
                                 ND = the number of days in the longest scenario
                                 2. Enter a value which is somewhat larger than LPV.
                                 Note
                                 A high value of the multiplier has a negative influence on memory usage.




                                                                                                             38
      Work Load Control (Per
WLC
      Scenario, -Plan Level and
      Plan Unit)
      Backward Planning           If this check box is selected, the system will plan the production plan in a
                                  backward pass.

      Forward Planning            If this check box is selected, the system will plan the production plan in a
                                  forward pass.

      Backward Plan Rule          This field determines how the items are selected in a backward planning
                                  step, if not all plan items can be planned within a plan period. This rule
                                  can be refined with other parameters.
                                  Possible Values:
                                  Production Volume
                                  The plan items with the highest production volume are planned first. The
                                  production volume is the quantity to be produced in a plan period.
                                  Volume Moved
                                  The plan items with the highest volume to be moved are planned first.
                                  The volume moved is the production volume that has been moved to the
                                  plan period under consideration.
                                  Number of Periods Moved
                                  The plan items for which the production volumes have been moved the
                                  highest number of times are planned first.
                                  Volume and Periods Moved
                                  For each plan item the volume moved and the number of periods moved
                                  are multiplied. The plan items for which this multiplication gives the
                                  highest values are planned first.
                                  This field determines how the items are selected in a forward planning
      Forward Plan Rule
                                  step, if not all plan items can be planned within a plan period. This rule
                                  can be refined with other parameters.
                                   Possible Values:
                                  Production Volume
                                  The plan items with the highest production volume are planned first. The
                                  production volume is the quantity to be produced in a plan period.


                                  Volume Moved
                                  The plan items with the highest volume to be moved are planned first.
                                  The volume moved is the production volume that has been moved to the
                                  plan period under consideration.


                                  Number of Periods Moved
                                  The plan items for which the production volumes have been moved the
                                  highest number of times are planned first.


                                  Volume and Periods Moved
                                  For each plan item the volume moved and the number of periods moved
                                  are multiplied. The plan items for which this multiplication gives the
                                  highest values are planned first.
                                  If this check box is selected, the material costs of an item are taken into
      Consider Material Costs
                                  account in the item
                                  priority.

                                                                                                                 39
                             If this check box is selected, the production costs of an item are taken into
Consider Production Costs
                             account in the item priority.
Consider Item Priority       Determines if the item priority must be considered in the planning.
                             The item priorities are defined in the Plan Item Data (cprpd1500m000)
                             session, and range from Lowest to Highest.


                             Yes
                             The priority of an item is considered in the workload control planning,
                             together with the rules specified in the Backward Plan Rule field and the
                             Forward Planning Rule field.


                             No
                             The item priority is not taken into account in the planning.


                             Only
                             The items will be planned in order of highest item priority. The values of
                             the Backward Plan Rule and Forward Planning Rule fields will not be
                             used.

Capacity Consumption Based   This field determines how the capacity is consumed when the production
On                           plan is planned.
                             Possible Values:
                             Total Capacity
                             The capacity requirements of a production quantity is spread over the
                             relevant periods based on the total capacity of these periods. In other
                             words, the capacity requirements in a period are proportional to the total
                             capacity in that period.


                             Free Capacity
                             The capacity requirements of a production volume are spread over the
                             relevant periods by leveling the capacity use. This means that in every
                             period, the ratio of free capacity and total capacity is leveled as much as
                             possible.




                                                                                                             40
Starting Point WLC             Determines the starting point for the simulation.
                               Possible Values:
                               Infinite Plan
                               An infinite plan is generated as input for the rest of the simulation.


                               Current Master Plan
                               The current master plan, generated in the Simulate Master Plan
                               (cprmp1202m000) session, is the input for the rest of the simulation.
                               BaanERP will leave the purchase plan and the planned distribution orders
                               unchanged.
                               Note
                               If you select Current Master Plan, you will probably need less iterations to
                               reach an optimum situation.
                               This is especially true, when only small changes have been made to the
                               master plan.
                               In this way, you can enter a lower value in the Number of Iterations field
                               in the Simulate Master Plan (cprmp1202m000) session, and achieve a
                               faster simulation.
                               Allowed values
                               The first time you simulate a plan unit, this field must have the value
                               Infinite Plan .
Performance Indicators (Per
Scenario, -Plan Level and
Plan Unit)
Backward – Average             The total moved volume or value in the backward planning divided by the
Volume/Value Moved             number of moved production volumes.

Backward – Average Number      The average number of periods a production volume was moved in the
of Periods Moved               backward planning.
                               This is the total number of moved periods divided by the number of
                               moved production volumes.

Backward – Total               The total volume or value in the backward planning that has moved to a
Volume/Value Moved             period other than the original period. This is the total volume or value that
                               could not be planned according to the ideal plan.

Backward – Unplanned           The total volume or value that could not be planned in the backward
Volume/Value                   planning due to capacity constraints or material constraints. If the value of
                               this field is greater than zero, the desired delivery dates cannot be met.
                               The total moved volume or value in the forward planning divided by the
Forward – Average
                               number of moved production volumes.
Volume/Value Moved

Forward – Average Number of    The average number of periods a production volume was moved in the
Periods Moved                  forward planning.
                               This is the total number of moved periods divided by the number of
                               moved production volumes.

Forward – Total Volume/Value   The total volume or value in the forward planning which has moved to a
Moved                          period other than the original period.
                               This is the total volume or value that could not be planned during the
                               preceding backward planning pass.




                                                                                                               41
        Forward – Unplanned              The total volume or value that could not be planned in the forward
        Volume/Value                     planning due to capacity or material constraints.
                                         If the Unplanned volume/value field is greater than zero, not all items can
                                         be produced within the simulated periods, because of capacity constraints
                                         and material constraints.

ATP Available to Promise
BOM Bill of Material
CLP CYCLIC PLANNING
CTP Capable to Promise
CF Baan Configurator
CPR Cost Accounting
DRP distribution requirements planning
DSP Demand and Sales Planning
IBD Item Base Data
IPD Item Production Data
ISA Item Data Sales
MPS Master Production Scheduling
MRP Material Requirements Planning
PAT Plan Aggregation and Transfer
PCS Project Control
PUR Purchase Control
RAO Resource Analysis and Optimization
RMP Resource Master Planning
ROU Routing
RPD Resource Planning Data
RRP Resource Requirements Planning
SFC Shop Floor Control
SLS Sales Control
SST Sales Statistics
TS Baan Service
WH Baan Warehousing
WLC Work Load Control



‘




                                                                                                                       42
‘




‘
‘
‘
‘
‘




‘
‘
‘
    43
‘




‘
‘




    44
45
BAAN 4 NOTES ON PLANNING




                           46

								
To top