frePPLev2.0
open source Production PLanning
  • Home
  • Documentation
    • Getting started
    • Modeling guide
    • User guide
    • Installation guide
    • Developer guide
    • FAQ
  • C++ API

Operationplan

Used to model an existing or planned activity.

When used as input the operationplans represent work-in-progress, in-transit shipments, planned material receipts, frozen manufacturing plans, etc…

In the output plan, the operationplans represent the planned activities in the future. The frozen operationplans from the input data are still present in the plan as well.

The operationplan has two closely related models. A flowplan represents the planned production or consumption of material. A loadplan represents the planned consumption of capacity.
These models are never created directly, but they are automatically managed by the operationplan.

Fields

Field Type Description
operation non-empty string Name of the operation.
This field is required when no identifier is provided.
id unsignedLong Unique identifier of the operationplan.
If left unspecified an identifier will be automatically generated.
This field is required when updating existing instances.
start dateTime Start date.
end dateTime End date.
demand demand Points to the demand being satisfied with this operationplan.
This field is only non-null for the actual delivery operationplans.
quantity double Quantity being planned.
locked boolean A locked operation plan is not allowed to be changed any more by any solver algorithm.
owner operation_plan Points to a parent operationplan.
The default is NULL.
flowplans list of flowplan A list of flowplans owned by this operationplan.
This list is export-only.
See the field buffer.flowplans to see all flowplans of a particular buffer.
loadplans list of loadplan A list of loadplans owned by this operationplan.
This list is export-only.
See the field resource.loadplans to see all loadplans of a particular resource.
unavailable duration Amount of time that the operationplan is interrupted due to the unavailability.
This field is export-only.
motive demand, buffer or resource Planning object that triggered the creation of this operationplan. Usage of this field varies by solver. The information is normally not relevant for end users.
action A
C
AC (default)
R Type of action to be executed:
A: Add an new entity, and report an error if the entity already exists.
C: Change an existing entity, and report an error if the entity doesn’t exist yet.
AC: Change an entity or create a new one if it doesn’t exist yet.
R: Remove an entity, and report an error if the entity doesn’t exist.

Flowplan

Models the material production or consumption associated with an operationplan.

Flowplans are fully controlled by the owning operationplan.

Field Type Description
operationplan operationplan Operationplan owning the flowplan.
flow flow Flow model of which this is a planned instance.
quantity double Size of the material consumption or production.
date date Date of material consumption or production.
onhand double Inventory in the buffer after the execution of this flowplan.

Loadplan

Models the capacity usage associated with an operationplan.

Loadplans are fully controlled by the owning operationplan.

Field Type Description
operationplan operationplan Operationplan owning the loadplan.
load load Load model of which this is a planned instance.
quantity double Size of the resource loading.
startdate date Start of the resource loading.
enddate date End of the resource loading.
setup string Setup of the resource when executing this loadplan.
This can be either the setup required by this particular load, or the setup left by any previous loadplans on the resource.
Example XML structures

Adding an operationplan to represent a planned receipt of material



100
2007-01-10T00:00:00
true

Deleting an operationplan



Example Python code

Adding an operationplan to represent a planned receipt of material
op = frepple.operation(name=”Purchase component A”, action=”C”)
opplan = frepple.operationplan(operation=op,
quantity=100, start=datetime.datetime(2007,1,10), locked=True)
Deleting an operationplan
frepple.operationplan(id=”1020″,action=”R”)
Iterate over operationplans
for i in frepple.operationplans():
print i.operation.name, i.quantity, i.start, i.end
Iterate over flowplans
for i in frepple.operationplans():
for j in i.flowplans:
print i.operation.name, j.quantity, j.date, j.buffer.name
Iterate over loadplans
for i in frepple.operationplans():
for j in i.loadplans:
print i.operation.name, j.quantity, j.resource.name,
j.startdate, j.enddate

    • Getting started
    • 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
      • Extension modules
        • Forecast module
        • REST web service module
        • Linear programming solver module
        • OpenERP connector module
    • User guide
      • Main features
      • Supported browsers
      • Getting around
        • Logging in
        • Logging out
        • Changing password
        • Navigation
          • Menu bar
          • Jump search
          • Context menus
          • Browser bookmarks
        • Filtering data
        • Sorting data
        • Selecting time buckets
        • Exporting data
        • Importing data
        • User preferences
        • User permissions and roles
      • Screens
        • Data input
        • Supply Path / Where Used
        • Comments
        • History – Audit trail
        • Plan analysis
          • 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
        • Execute
      • Batch commands
        • manage.py (manage.exe on Windows)
        • frepple (frepple.exe on Windows)
        • freppleservice.exe (Windows only)
    • Installation guide
      • Windows installer
      • Compiling on Windows
      • Linux binary packages
      • Compiling on Linux
      • Compiling on debian-based linux
      • Compiling on Red Hat based Linux
      • Compiling from the subversion source code repository
      • Running the VMWare virtual machine
      • Other platforms
      • Configuring the user interface
      • Configuring multiple models in the user interface
      • Configuring as a Python extension module
    • FAQ
    • Developer guide
      • Code structure
      • Class diagram
      • Solver
        • Solver features
        • Planning algorithm
          • Top level loop
          • Demand solver
          • Buffer solver
          • Flow solver
          • Load solver
          • Operation solver
          • Resource solver
        • Cluster and level algorithm
      • Extension modules
      • Version control
      • Style guide
      • Portability
      • Security
      • Internationalization
      • Translating the user interface
      • Adding or customizing a report
      • 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
    • License
      • GNU Affero General Public License
      • GNU Free Documentation License
    • Third party add-ons
  • Copyright © 2010-2013 frePPLe bvba