Website Upgrade Incoming - we're working on a new look (and speed!) standby while we finalise the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Scheduling in P3e/c

6 replies [Last post]
Wed, 2004-07-28 07:44
Lloyd Young
User offline. Last seen 9 years 9 weeks ago. Offline
Joined: 19 Jan 2004
Posts: 26
Groups: None
when scheduling in P3e/c it seems that i have to follow this process in order for all users to see updates.

1. F10 Commit Changes to database MUST be carried out on each individuals PC.
2. F9 Schedule can then be performed on any one PC. (Once the schedule is complete, all other users must be informed so the following can be carried out).
3. F5. After Schedule, to ensure that data on screen shows correct information everyone Should Refresh the data , this is achieved by pressing F5.(can be done at the same time by everyone)

The whole process can take upto 15mins,

Is this something that other users of P3e/c seen before?
Top

Replies

Wed, 2004-08-04 18:58
#1
Alex Wong
User offline. Last seen 11 years 35 weeks ago. Offline
Joined: 12 Feb 2003
Posts: 874
Groups: TILOS
If you dont want to committ changes everytime you update the schedule is to establish a updating cycle. Ie
Every Friday is a schedule update date. (Everyone update their own progress and change the data date)
Every Monday is a scheudle review date. (Everyone review all the schedule interlink and discuss if any critical issue arise)

That way you will not have a problem when someone changing the progress of an interlink activity when you update your acitivities. So you don’t need to constantly pressing F5 and F10. At the same time you 100% sure that come Monday the entire schedule is updated.
Top
Wed, 2004-08-04 10:53
#2
Forum Guest
User offline. Last seen 17 weeks 5 days ago. Offline
Joined: 28 Jan 2009
Posts: 2
Groups: None
Commit is an oracle command that simply saves/writes new/altered data into the database
Top
Thu, 2004-07-29 04:34
#3
Lloyd Young
User offline. Last seen 9 years 9 weeks ago. Offline
Joined: 19 Jan 2004
Posts: 26
Groups: None
Thank you Alex,

The reason we do not have a centralised scheduler is we have some 46,000 tasks which would take one scheduler a considerable amount of time.

Have you haerd of this Commit Changes before?

It seems that for any updating to show on all the users Desktop we have to go through the process as formentioned.

Top
Wed, 2004-07-28 21:23
#4
MK TSE
User offline. Last seen 4 years 25 weeks ago. Offline
Joined: 27 Feb 2002
Posts: 550
Groups: None
btw, is it help to shorten the screen refresh time interval? Not sure any setting on this one.
Top
Wed, 2004-07-28 21:21
#5
MK TSE
User offline. Last seen 4 years 25 weeks ago. Offline
Joined: 27 Feb 2002
Posts: 550
Groups: None
I agree Alex’s proposed. Although I’m working on P3 with user more than 20, each responsible on his own sub-project.
When I schedule at master level, I inform all parties to close their opened sub-projects and re-open after I schedule.
Top
Wed, 2004-07-28 19:41
#6
Alex Wong
User offline. Last seen 11 years 35 weeks ago. Offline
Joined: 12 Feb 2003
Posts: 874
Groups: TILOS
Scheduling in P3e/c you need to breakdown into projects, when the projects is just too big to handle, ie too many users need to access to the system you should create a EPS with the project ID where inidividual can excusive access to their project while update happens. Remember P3e/c is a real time database, and with data base when you editing the record you actually lock the record of the field in the database table.

Once you splite the projects into responsibility, you can then access to the schedule directly and don’t need to press F10 or F5 anymore.

It seems that the project you discribe do not have any centralised scheduler to handle the update. ie all the project engineers updating the schedule.

The best way to handle this situations is remember when you are updating the schedule you are updating part of the time line. To syn the update you better draw a process diagram and schedule everyone have to update their schedule by certain time of the month before reporting. That way you can ensure the report produce is all updated. Otherwise you may print a report while someone is doing the update. However, this is only for reporting, for daily operation it will not stop anyone update the schedule at any time of the date. The only thing is you a updating and reviewing a snap shot (time) of the schedule instead of syn time version (like end of the month report) of the schedule. (Hope you understand) And that is part of the deal if you using a database in a multi-users enviornment.

Same if you are using P3.

Regards

Alex
Top