Let me comment on some tricky parts.
>>Q9) between start.R1.P1 und start.R2.P1 there must not be a time longer then 48h
Set a the marearly field for resource R2 for this.
This value will be applied for all jobs on that resource, ie not only P1.
>>Q10) work start at 8am. All machines has to undergo setup. Work stop at 5pm. All machines has to undergo setdown before this.
Since your setups seem to be fixed tasks and don't depend on the
switch from product P1 to P2, the setup feature in frePPLe is NOT what
you need.
You'll need to include the setup time as part of the operation time.
Regards,
Johan
2010/12/18 Daniel Studzinski <daniel.s...@gmail.com>:
--
Johan De Taeye
Mob: +32 477 385 362
Skype: jdetaeye
F.P1 should an operation of type "routing". It has 4 sub-operations as steps.
>>* Q7 Stuck. by now I have no clue how to explain my Machine Matrix and Skill Matrix to frePPLe
It's pretty straightforward to model these as loads in the model.
For "R2.P1=M2+(O1,02)" you create 3 records in the "load" table:
- a first one to specify M1.
- a second one to specify O1. Populate the "name" field with some
arbitrary name, set the "search" field to "PRIORITY" and set the
priority to "1"
- a third one to specify O2. Populate the "alternate" field with name
defined in the previous record, set the "search" field to "PRIORITY"
also and set priority to "2". This indicates that O2 is an alternate
of O1, but O1 is the preferred resource.
>>so. 7pm in my Singapore office so I leave it better and look for my lovely wife...
You bet!
Johan
In case you have common subassemblies that are shared across end
items, using seperate items and buffers is indeed required.
> Another point: in the Operation List there is a table were the Setup
> and Setdown time is visible. how to make the Duration and Duration Per
> in this list visible? its a critical numbers for production and a
> overview for debugging is something precious.
I added these fields - missed them...
This will be part of the next release, or you can look at the changes
at http://frepple.svn.sourceforge.net/viewvc/frepple?revision=1389&view=revision
and patch your install.
Regards,
Johan
If you model the availability as resource calendars, an operationplan will
need to fit completely in a day, i.e. needs to start an stop on the same
day.
If you model the availability as an availability calendar on the location
where the operation is located, an operationplan started on day X will be
interrupted at 5pm and automatically continue the next day at 8am.
>>I tried to find a way to put repeatable entries into the calendar but I
cannot find a way. also I can combine only one calender with one resource.
>>in case I have now to put for every one operator a daily calendar entry
this will ends in huge data maintenance. there must be a way around...
You need an entry for each day indeed.
The code is structured to support such repeating entries at some point in
the future, but it's not ready yet.
A single record for each day is not too big of a maintenance headache : you
populate it once every year or so in an excel sheet and can easily upload
the result.
Johan
This is used for the reporting in weekly, monthly, quarterly or yearly
time buckets.
The default content will normally suffice, unless you want to your own
boundaries of the time buckets.
(BTW: this table is reworked in the upcoming 0.9.0 release)
Johan
This is the standard behavior of the Django framework. I found it a
bit counter-intuitive too, but haven't spent time yet in analyzing
and/or fixing it.
> Question 1: in case I put now the items of my real fab into frePPLe,
> how to explain the stations on which the items are currently. how to
> make the day zero?
The currrent work-in-progress needs to be fed into the operationplan
table - with the "locked" field set to true.
You can also feed this table with the part of the previous plan that
is "frozen". Eg workorders that are firmed up in your ERP and sent to
the shop floor for execution should be modeled as locked
operationplans in frePPLe.
> Question 2: fraPPLe provide a nice tool for planing. but how to modify
> the plan in case the machine went down for no reasons 4h ago?
Change the availability of the resource and rerun the plan. This will
recalculate the precise impact of the downtime.
Only the locked/frozen part of the plan will not be touched.
Regards,
FrePPLe recomputes every time without remembering anything from the
previous run.
By copying some of the plan from the output table "out_operationplan"
into the input table "operationplan" you can make it remember. For
plan stability (ie avoid that the plan changes too much from day to
day) this is common practice and a good idea.
This copying from output to input is done standard in frePPLe - you'll
have to run some custom sql to achieve this.
frePPLe supports MySQL, PostgreSQL, Oracle and SQlite databases.
If you don't know which one you're using, you're most likely using the
SQLite database that is bundled with the Windows installer.
You can open the database files (with the extension .sqlite) with a
database frontend such as http://www.sqliteexpert.com/ (excellent and
highly recommended)
It would also possible to execute such SQL statements from a custom
extension of the frePPLe user interface.
Johan
Correct.
>>the way over MySQL and ODBC seems to be easier to me and for the future
more user friendly...
The basic Windows installation using SQLite is NOT suitable for real
multi-user production environments. It's only suitable for a first look,
for training, for small single-user models, etc.
Real production use requires a different configuration with a separate
database and/or web server.
See also http://www.frepple.com/pmwiki/pmwiki.php/Frepple/OverviewDjango
Johan
-----Original Message-----
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com]
On Behalf Of Daniel Studzinski
Sent: Thursday, January 27, 2011 7:50 AM
To: frePPLe users
Subject: Re: a simple production model
If you run the following the command lines, does it work?
mysql --host=localhost --port=3306
mysql --host=localhost --port=3306 --user=root --password=xxx
--database=mysql
If it works, I don't see any reason why it wouldn't work for frePPLe.
If it doesn't, search google to fix that.
Frepple 0.8.1 comes packaged with the "MySQLdb" 1.2.2 driver for Python.
This driver is normally not very sensitive to the version of the MySQL
database or 32-bit/64-bit issues.
Johan
-----Original Message-----
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com]
On Behalf Of Daniel Studzinski
Sent: Monday, January 31, 2011 12:04 PM
To: frePPLe users
Subject: Re: a simple production model
>>my task now is to freeze the operations...
>>a) in "Operation detail report" I cannot click the "locked" field
>>b) how to move the planed operations from "Operation detail report" to "operation plans" (or am I performing here an mistake to do so?)
>>c) and if I have now the tasks in "operation plans" (were I can lock and unlock them) how to edit/delete the task from here (let say production stop)
The results in the “operation detail” report are indeed non-editable. They are recomputed with each planning run, and thus any manual change would be lost with the next run.
They are stored in the database table “out_operationplan”.
The frozen operationplans you refer to in step b) represent the work-in-progress and frozen production plan. These are inputs to the plan.
They are stored in the database table “operationplan”.
There is no out-of-the-box data transfer between those tables.
- In most cases the work-in-progress and the frozen production plan are imported from an external (ERP-)system, and NOT maintained in the frePPLe user interface.
- In case you would want to maintain the frozen plan in frePPLe:
You’ll need an excel export+import that copies a portion of the plan between these tables. Which part of the plan you copy depends on the business.
If the freeze logic is clearly defined, it’s also easy to implement a “freeze plan” button or command that makes this task easier.
Johan
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com] On Behalf Of Daniel Studzinski
Sent: Monday, July 09, 2012 12:54 AM
To: freppl...@googlegroups.com
Subject: Re: a simple production model
model solved.
I see that in the input operationplan table you have not marked the operationplan as locked.
Locked operationplans are left untouched during a planning run.
All others get replanned.
Otherwise, looks ok what you’ve done & should work fine.
Johan
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com] On Behalf Of Daniel Studzinski
Sent: Tuesday, July 10, 2012 12:28 AM
To: freppl...@googlegroups.com
Subject: Re: a simple production model
itchy fingers... I needed to try it out...
>>nice MS Access front-end via ODBC and the life of the planer start to be enjoyable... ;)
More people might be interested in this as well.
Would be nice if this could be added as a re-usable contribution.
Johan
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com] On Behalf Of Daniel Studzinski
Sent: Monday, July 09, 2012 10:23 AM
To: freppl...@googlegroups.com
Subject: Re: a simple production model
in such a case an I need to manipulate the data by SQL... manual export/import would be to time consuming...
More people might be interested in this as well.
Would be nice if this could be added as a re-usable contribution.
I see that in the input operationplan table you have not marked the operationplan as locked.
Locked operationplans are left untouched during a planning run.
All others get replanned.
FrePPLe doesn’t freeze the allocation of supply to demand. The pegging between supply and demand is dynamic and recomputed every time.
E.g. if an order is canceled, any frozen operationplans will be repegged to other open demands.
E.g. if an more urgent demand comes in, supply will be reallocated and yes, this can steal supply away from less urgent demands.
Who gets the first shot at consuming material and capacity is indeed controlled by the priorities.
Johan
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com] On Behalf Of Daniel Studzinski
Sent: Tuesday, July 10, 2012 10:03 AM
To: freppl...@googlegroups.com
Subject: Re: a simple production model
I see that in the input operationplan table you have not marked the operationplan as locked.
Who gets the first shot at consuming material and capacity is indeed controlled by the priorities.
>>works for me... but I need to increase the number of priorities... to around 100...
>>is this an option or I have to dig into the quell code?
Priority is the first criterion for sorting.
When there are multiple demands of the same priority, the due date works as a tie breaker. Earlier due date gets planned first.
You thus need only a different priority for a different *type of* demand or *type of* customer that you want give priority over another.
20 of such priorities should normally suffice.
If not sufficient, you can always remove the option “choices” from line 778 in the file input/models.py:
The priority is then an integer field without predefined limit.
Johan
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com] On Behalf Of Daniel Studzinski
Sent: Tuesday, July 10, 2012 11:14 AM
To: freppl...@googlegroups.com
Subject: Re: a simple production model
Who gets the first shot at consuming material and capacity is indeed controlled by the priorities.
If not sufficient, you can always remove the option “choices” from line 778 in the file input/models.py:
The priority is then an integer field without predefined limit.
Try these steps:
- Check the file bin\custom\freppledb\settings refers correctly to the “postgresql_psycopg2” database engine in the parameter DATABASES. Review also database connection parameters in the same file, and correct if required.
- Verify pgadmin can connect to the database with these parameters.
- If you have multiple frepple installations on the machine, make sure the environment variable FREPPLE_HOME points to the correct folder.
- Run the command to create the database structure. There should be a an error message in case things go wrong.
cd bin
.\manage.exe syncdb
Johan
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com] On Behalf Of Daniel Studzinski
Sent: Wednesday, July 11, 2012 9:27 AM
To: freppl...@googlegroups.com
Subject: Re: a simple production model
I setup a PC. install PostgreSQL. even created a DB "frePPLe". now I wanted to put frePPLe on top with the tables in PostgreSQL. but somhow frePPLe refuse to use this one. it uses iSQLite istead... user name, DB name, Port and passwords are OK, I even repeated this several times...
I must miss something..
>>is there a way to start the solver out of the browser?
Yes, you can.
Use the command line “manage.exe frepple_run” & check the documentation http://www.frepple.com/pmwiki/pmwiki.php/UI/CommandLine
Please post specific questions with appropriate subject…
There are too many people on this list that are NOT interested in following a long mail thread “simple production model”.
A question on “how to run the solver outside browser” is more interesting for others.
Johan
From: freppl...@googlegroups.com [mailto:freppl...@googlegroups.com] On Behalf Of Daniel Studzinski
Sent: Wednesday, July 11, 2012 2:20 PM
To: freppl...@googlegroups.com
Subject: Re: a simple production model
this was fun :)