Network Techniques - II.

Size: px

Start display at page:

Download "Network Techniques - II."

Roland McDonald
5 years ago
Views:

1 erformance:lide1.doc Network Techniques - II. CM time - CM time+ : Overlapping, open network and non-broken activity keep being problematic ( chedules for roduction Management?! ) MM time : ( METRA otentials' Method ) Activity-on-node typed, deterministic project model with discrete variables and with abilities of handling manyfold and multiple relations GTM : ( General Model ) Event * -on-node typed deterministic project model with homogeneous relations * Deadline and/or milestone

2 erformance:lide2.doc METRA otentials' Method (MM time ) 196 : B. Roy, France, Appl: Nuclear ower tation ( originally: start potentials only ) Node : Activity ( with no break in performance) ( Event and milestone have duration of ) Edge : Technical-, technological-, or resource management-born quantified relation arameter (weight) : ag-time, duration and time potential ( deterministic variable ) Aim : chedules for production management, modelling technologies, monitoring progression, change management Handling ( time consequences of ) overlapping ( relative in time ), restrictions for resource allocation, technological and spatial limitations, etc.

3 erformance:lide3.doc "Activity-on-node" Activity identificator ( optional ) Early tart [A] Duration Early Finish ate tart Total Float ate Finish "Relation" (min) Deadline/milestone of predecessor (basic) activity ( here: Finish ) Deadline/milestone of successor (related) activity ( here: tart ) F p arameter (lag-time) Type or relation ( Finish-tart minimum ) Arrow indicates direction of relation, while solid line indicates that the parameter is a lower bound (minimum)

4 erformance:lide.doc "Relation" (max) Deadline/milestone of predecessor (base) activity ( here: Finish ) Deadline/milestone of successor (related) activity ( here: tart ) "minus" sign - F p arameter (lag-time) Type of relation ( Finish-tart maximum ) Reversed arrow indicates dirtection of relation, while broken line and "minus" sign indicate that the parameter is an upper bound (maximum) "Hammock/uspended Activity" [tart] [Finish] F

5 erformance:lide5.doc MM - Basic Relations rogression (completion) [%] 1 D p FFp 3 Fp 1 p 2 Fp Transforming Relations FFq Fq Fq q FFp q = p - q = p + D p q = p + D p - Fp q = p + q = p +D p + q = p + D p Fp q = p - D p q = p - D p - q = p - p q = p + - D p q = p - D p q = p +

6 erformance:lide6.doc ingle Relations Fp finish-start minimum p -Fp finish-start maximum p p start-start minimum p -p start-start maximum p FFp finish-finish minimum p -FFp finish-finish maximum p Fp start-finish minimum p -Fp start-finish maximum p uccessor (related) activity can be started at least "p" tu later than predecessor (base) activity is finished uccessor (related) activity should be started at most "p" tu later than predecessor (base) activity is finished uccessor (related) activity can be started at least "p" tu later than predecessor (base) activity is started uccessor (related) activity should be started at most "p" tu later than predecessor (base) activity is started uccessor (related) activity should be finished at least "p" tu later than predecessor (base) activity is finished uccessor (related) activity should be finished at most "p" tu later than predecessor (base) activity is finished uccessor (related) activity should be finished at least "p" tu later than predecessor (base) activity is started uccessor (related) activity should be finished at most "p" tu later than predecessor (base) activity is started Typically in case of strictly limited resources ( usually with parameter of, to assign consecutive processes ) Typically accompanying an Fp relation, in case of sensitive conditions or strict expectations on effective resource usage Typically in case of well synchronized parallel processes, in a large-scale schedule of a project Not typical relation. olely or together with an p relation it can be a useful tool for direct allocation ( time or resource ) Mostly a count-down typed relation for administrative, e.g. handover- or supervisory activities Not typical relation. olely or together with an FFp relation it can be a useful tool for direct allocation ( time or resource ) Theoretic relation, typically with negative parameter and for to replace a -Fp relation ( see: scheduling ) Theoretic relation, being mentioned to complete the list only. It can be used in case of complicated allocations

7 erformance:lide7.doc Most Frequently Used Combined Relations p FFp (min) critical succession -p -FFp } CRp (max) critical succession Fp -Fp strict/forced succession F -F } } immediate succession FF f(ds) f(dp) }-CRp } (min) critical approach (in progression) A lead-time of at least p tu should be provided between the predecessor (base) and successor (related) activity at any rate of completion A lead-time of at most p tu can be accepted between the predecessor (base) and successor (related) activity at any rate of completion uccessor (related) activity must be started exactly p tu after predecessor (base) activity is finished uccessor (related) activity must start immediately after predecessor (base) activity is finished Timing of base and of related activities should provide at least f(dp) tu lead-time between their starts and at least f(ds) tu lead-time between their finishes. ( arameters set as function of activity durations ) Typical relation of technological or resource management-born restrictions ( hardening, drying, consolidation, etc.) independent of durations of activities. Carefully applied it can be a useful tool in case of sensitive conditions. Be careful with it! Applications may result in a misguiding model! Typically used for direct allocation of succeeding activities. Typically used for expensive or most significant resources to provide their continuous usage, application or employment Typical tool for to provide room (manipulation/operation area) for succeeding activities. arameters are set in relation of intensity of performances. -FF f(ds) - f(dp) } (max) critical approach (in progression) chedule of base and related activities is acceptable if it results in at most f(dp) tu lead-time between their starts and at most f(ds) tu lead-time between their finishes. ( arameters set as function of activity durations ) Carefully applied it can be a useful tool for restricting area of manipulation/operation on the construction site. Be careful! Applications may result in a misguiding model!

8 erformance:lide8.doc roviding Technological Break 1 rogression [%] D p FFp CRp p rogression [%] D p FFp 1 CRp p

9 erformance:lide9.doc roviding Manipulation Area rogression [m] D p FF l l l l D p rogr.[m] D p FF l l l l D p

10 erformance:lide1.doc ensitive Conditions rogression [%] rogression [%] D p -FFp D p -FFp 1 1 -CRp -CRp -p -p Restricting Manipulation Area rogression [m] D p -FF l l rogr.[m] -FF l D p l l - l D p l - l D p

11 erformance:lide11.doc Restrictions on Duration rogression [%] -D max 1 j j i D min Virtual Deceleration / aradox / rogression [unit] D n = D - d n 1 d

12 erformance:lide12.doc MM Network roblem: eft Abutment eft ier Right ier Right Abutment ite reparation iling F -F F F F F Foundations F F5 F5 F F5 F5 F Walls & iers F F2 F2 F2 F2 F2 F2 Beams & labs F F F F F F F Road tructures + Finishes

13 erformance:lide13.doc Behavior/Type of (Critical) Activities A B + C 7 7 F F A 1 A 2 B 1 B 2 C 1 C A B /F C A 1 A 2 B 1 B 2 C 1 C A B - C FF A 1 A 2 B 1 B 2 C 1 C

14 erformance:lide1.doc General Model (GTM) 1997 : Hungary, Z. A. Vattai, Multi-project management (MÁV) Node : Event ( a specific moment in time ) ( start, finish, milestone, deadline ) Edge : Relation/comparision/restriction assignment ( process, activity, idle-time, lag-time, etc. as technical interpretation ) arameter (weight) : Restriction parameter, lower bound value, time-potential ( deterministic variable ) Aim : Releasing restrictions of traditional scheduling techniques (ERT,CM,MM), to develop flexible technological models and stabil logical structures for projects of typified (logical/technological) elements

15 erformance:lide15.doc Homogenizing relations p i i t ij p j - p i t ij p j j p i i p j - p i t ij / ( 1) τ ij π i π j - t ij p j j p j - p i = t ij τ ij π j π i τ ij p i i t ij - t ij p j j

16 erformance:lide16.doc MM time fi GTM roblem A B C FF F D E F F F2 F1 FF A A B1 B2 C1 C D D2 3 5 E E2 F1 F A1 A2 B1 B2 C1 C2 D1 D2 E1 E2 F1 F2 A A2-7 9 B B C1 2 C2-2 2 D1 3 D E1 5 E2-9 1 F F2-1 2 π max π min

17 erformance:lide17.doc FOUR "MAGIC QUETION" from network techniques 1., Duration of an activity having no float in an activity-on-arrow typed project model get increased by δ. What will be its effect on the overall execution time of the project? 2., Duration of an activity having no float in an activity-on-arrow typed project model get decreased by δ. What will be its effect on the overall execution time of the project? 3., Duration of an activity having no float in an activity-on-node typed project model get increased by δ. What will be its effect on the overall execution time of the project?., Can emerge any situation when an activity having no float simultaneously behaves as "positive-", "negative", "start-", and "endcritical"?

4. Network Calculations

Construction Project Management (CE 110401346) 4. Network Calculations Dr. Khaled Hyari Department of Civil Engineering Hashemite University Calculations On a Precedence Network I Early Activity Start