Problem

FrePPLe will automatically detect problems and inconsistencies in the plan.

Problem detection can optionally be disabled on entities by setting the field "DETECTPROBLEMS" to false.

Problems are export-only, i.e. you can't read them as input.

Types

Problem Entity	Problem Category	Description
demand	unplanned	No plan exists yet to satisfy this demand.
demand	excess	A demand is planned for more than the requested quantity.
demand	short	A demand is planned for less than the requested quantity.
demand	late	A demand is satisfied later than the accepted tolerance after its due date
demand	early	A demand is planned earlier than the accepted tolerance before its due date.
resource	overload	A resource is being overloaded during a certain period of time.
resource	underload	A resource is loaded below its minimum during a certain period of time.
buffer	material excess	A buffer is carrying too much material during a certain period of time.
buffer	material shortage	A buffer is having a material shortage during a certain period of time.
operationplan	before current	Flagged when an operationplan is being planned in the past, i.e. it starts before the current date of the plan.
operationplan	before fence	Flagged when an operationplan is being planned before its fence date, i.e. it starts 1) before the current date of the plan plus the release fence of the operation and 2) after the current date of the plan.
operationplan	precedence	Flagged when the sequence of two operationplans in a routing isn't respected.
demand or buffer or resource or operation	invalid data	Some data problem prevents this object from being planned.

Field	Type	Description
name	normalizedString	Problem type.
description	normalizedString	Description of the problem.
weight	double	A number expressing the seriousness of the problem.
start	dateTime	Date at which the problem starts.
end	dateTime	Date at which the problem ends.

    for i in frepple.problems():
       print i.entity, i.name, i.description, i.start, i.end, i.weight