frePPLeOpen source Production Planning
  • Home
  • Documentation
  • C++ API

6 – Your first plan

Now that your model is ready we will now create a plan and analyze the results.

The model has only a single demand which is due on 5/5. With a plan horizon starting on 1/1, there are no time, material or capacity constraints that are preventing on-time delivery.

  • To create the plan, select “execute” from the “tools” menu. The execution screen will appear, as shown below.
    Select “constrained” plan, ensure all constraints are enabled and hit the “run” button. This will trigger the plan creation. A message will be shown at the top of the screen when the plan is finished.
    You can have a look at the log file of the planning run.

  • The plan generation in the previous step is calculated using a heuristic algorithm.
    The demands are planned one by one in order of priority, and search the supply path for available material and capacity. When material, capacity or time constraints are found, heuristic business rules are used to solve the problem and find a feasible solution.
    More details can be found in the modeling guide.

  • Review demand plan
    A first report shows the planned delivery for the order. Open the “demand list” report, click on the demand name and select the “plan” from the popup menu.
    A Gantt chart shows the delivery plan of the demand, including all operationplans it requires.

  • Review resource plan
    A second report highlights the usage of the resources.
    We can see the loading in three different reports:

    • Selecting resource report from the top menu we get a table with the loading of all resources in each time bucket.
    • When clicking on a specific resource and selecting plan from the pop-up menu, we see a graph displaying the loading of the selected resource.
    • When clicking on a specific resource and selecting plan detail from the pop-up menu, we get a detailed list of all operations with their start date, end date and the capacity they consume.
  • Review inventory plan
    Next, you’ll be interested in the inventory planned for all items.
    We can see the information in three different reports:

    • Selecting inventory report from the top menu we get the inventory per time bucket.
    • When clicking on a specific buffer and selecting plan from the pop-up menu, we see a graph displaying the inventory evolution over time.
    • When clicking on a specific buffer and selecting plan detail from the pop-up menu, we get a detailed list of all consumed and produced material.
  • Review operation plan
    The next reports show all operations that are planned in order to satisfy the demand.
    We can see the information in three different reports:

    • Selecting operation report from the top menu we get the planned quantity of all operations per time bucket.
    • When clicking on a specific operation and selecting plan from the pop-up menu, we see a graph of that resource.
    • When clicking on a specific operation and selecting plan detail from the pop-up menu, we get a detailed list of all operations with their quantity and date.
  • Review problems
    FrePPLe creates alerts to flag infeasabilities and issues in the plan to the planner: capacity shortage, material shortages, late or short orders, etc.
    As you already understood from the above, this plan has no problems: all demand could be fully satisfied in time, respecting all material and capacity constraints. Only 2 warnings are shown about unused excess inventory.

    • Getting started
      • 1 – Introduction
      • 2 – Installation
      • 3 – Entering data
      • 4 – Modelling concepts
      • 5 – Your first model
      • 6 – Your first plan
    • Modeling guide
      • Simplified domain model
      • Detailed domain model
      • Environment variables
      • Python interpreter
      • Global parameters
      • Buffer
      • Calendar
      • Customer
      • Demand
      • Flow
      • Item
      • Load
      • Location
      • Operation
      • Suboperation
      • Operationplan
      • Problem
      • Resource
      • SetupMatrix
      • Skill
      • Resource skill
      • Solver
    • User guide
      • Supported browsers
      • Getting around
        • Logging in
        • Logging out
        • Changing password
        • Navigation
          • Menu bar
          • Jump search
          • Context menus
        • Filtering data
        • Sorting data
        • Selecting time buckets
        • Exporting data
        • Importing data
        • Customizing a screen
        • User preferences
        • User permissions and roles
        • Comments
        • History – Audit trail
      • Data maintenance screens
      • Supply Path / Where Used
      • Plan analysis screens
        • Problem report
        • Constraint report
        • Inventory report
        • Inventory detail report
        • Resource report
        • Resource Gantt report
        • Resource detail report
        • Operation report
        • Operation detail report
        • Demand report
        • Demand detail report
        • Demand Gantt report
        • Forecast report
        • Performance indicator report
      • Execution screen
      • Batch commands
        • frepplectl
        • frepple
        • freppleservice.exe (Windows only)
    • Installation guide
      • Windows installer
      • Compiling on Windows
      • Linux binary packages
      • Compiling on Linux
      • Compiling from the source code repository
      • Running the VMWare virtual machine
      • Other platforms
      • Configuring multiple models in the user interface
      • Configuring as a Python extension module
    • Extension modules
      • Forecast module
      • Order quoting module
      • REST web service module
      • OpenERP connector module
      • Linear programming solver module
    • Technical guide
      • Architecture
      • Source code repository
      • User interface
        • Creating an extension app
        • Translating the user interface
        • Adding or customizing a report
        • Style guide
      • Solver engine
        • Code structure
        • Class diagram
        • Planning algorithm
          • Top level loop
          • Demand solver
          • Buffer solver
          • Flow solver
          • Load solver
          • Operation solver
          • Resource solver
        • Cluster and level algorithm
        • Extension modules
        • Style guide
        • Portability
      • Security
      • Unit tests
        • buffer_procure_1
        • calendar
        • callback
        • cluster
        • constraints_combined_1
        • constraints_combined_2
        • constraints_leadtime_1
        • constraints_material_1
        • constraints_material_2
        • constraints_material_3
        • constraints_material_4
        • constraints_resource_1
        • constraints_resource_2
        • constraints_resource_3
        • constraints_resource_4
        • constraints_resource_5
        • datetime
        • deletion
        • demand_policy
        • flow_alternate_1
        • flow_alternate_2
        • flow_effective
        • forecast_1
        • forecast_2
        • forecast_3
        • forecast_4
        • forecast_5
        • forecast_6
        • jobshop
        • load_alternate
        • load_effective
        • lpsolver_1
        • multithreading
        • name
        • operation_alternate
        • operation_available
        • operation_effective
        • operation_pre_post
        • operation_routing
        • pegging
        • problems
        • python_1
        • python_2
        • python_3
        • safety_stock
        • sample_module
        • scalability_1
        • scalability_2
        • scalability_3
        • setup_1
        • setup_2
        • skill
        • xml
        • xml_remote
    • FAQ
    • License
      • GNU Affero General Public License
      • GNU Free Documentation License
    • Third party add-ons
  • Copyright © 2010-2013 frePPLe bvba