Re: [Planner] Some issues




Actually this prob can and must be bypassed - professional schedulars use a spreadsheet, a word processor (emacs), or a database to create batch entrys - the practice of 'fragnetting' involves templating common work activities and entering them either programatically or modifying them with some kind of search and replace to fit specific projects. if you use Means a fragnetting scheme can be implemented around the wbs and the crew data in the book. Those 'other' programs allow cutting and pasting of groups of activities - what programming that takes boggles the mind. For a specific example if you have a building with 6 identical floors - you schedule one then paste it into your spreadsheet, copy it 4 times, global replace the floor identification, fill the activity numbers, and paste back the five floors. Another tip - allow all calcs and saves to be switched off during data entry (with an on-screen warning).
Yes, or something along those lines. But in addition to batch entry, there is the issue of massaging a living project. I did not expect to see performance issues with just a 100 task sample. That worries me. Even more so when it's been speculated the cause might be quite non-deterministic. I hope this will be addressed in some way.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]