on 06-06-2011 1:06 PM
Hi,
I have an issue with the creation of network
We create transactional network through standard network adn their linkage with materials. The network has lot of activities, some sequences are backward scheduled and some are set for forward scheduling. We also provided constraints for the first and last activity. So the network start date adn end date are fixed. However when the network is created using this standard network, float is getting accumulated activities while we need the float at some other activities.
One of the activities in teh backward scheduling has some successors to it, which are decided by forward scheduling. Here my team say that this is the problem, and say that either the whole NW can be backward scheduled or forward scheduled. Is it correct. Why is the dates incorrect with unnecessary floats (though the sequence is correct)
Yes,
System will schedule Network automatically both forward and backward. Only thing we are doing is defining which schedule should be done first whether backward or forward.
Please select the scheduling method at network header level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abdul,
That exactly is the problem.
In the network header, I cannot restrict to either forward or backward scheduling, because some subnetworks need to beforward scheduled and some backward. In this situation, float is not getting accumulated at the point of intersection of forward and backward scheduling, but at some other points.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.