introducing the relationship diagramming methodintroducing the relationship diagramming method...

Introducing the

Relationship Diagramming MethodVariant of the Critical Path Method of Planning & Scheduling Analysis

Fredric L. Plotnick, Esq., P.E.Engineering & Property Management Consultants, Inc.Benson Manor #117 – 101 Washington Lane – Jenkintown, PA 19046

www.fplotnick.com [email protected] 215-885-3733

http://www.fplotnick.com/

mailto:[email protected]

• RECENT DEVELOPMENTS highlighted in the professional and technical societies and in academia, relating to the field of CPM Planning and Scheduling, have drawn attention to the focus upon information relating to individual and groups of activities and the lack of focus upon the relationships between these activities that was the hallmark of the original ADM and PERT methodologies

Gantt Charts are Easy to Read

But if you want to make even a small change...

...to the duration of one activity ...you have a great deal of work to perform to determine the impact

??

CPM requires you to record the relationships between activities ...

... and allows the computer to recalculate the impact of changes made ...

... reducing the 40%+ rework effort to that of a keystroke

Logic Network Based Methods

• CPM – Critical Path Method– 1956 E. I. du Pont de Nemours Company, Newark DE– and later known as

• ADM = Arrow Diagramming Method – or as AOA = Activity on Arrow• PERT – Program Evaluation Review Technique

– 1958 Special Projects Office of the Navy Bureau of Ordinance – for Research and Development of the Polaris Missile Program– also known as the Program Evaluation Research Task method

• PDM – Precedence Diagramming Method– 1964 IBM implementation for H.B. Zachry Co.– and also known as AON = Activity on Node

http://en.wikipedia.org/wiki/Image:Uss_george_washington.jpg

CPM

http://www.amazon.com/exec/obidos/ASIN/0071344403/qid=957662118/sr=1-2/102-3541701-1708038

ADMK.I.S.S.

ActivityDescriptioni jduration of

activityES EFLS LF__TF

__TF

TE = = TL

PERT

logic onlyEvent #1Description duration

betweeneventsTE

TLTETL__TF

__TF

Event #2Description

PDM?ActivityDescriptioni jduration of

activity

finish-to-startstart-to-start

finish-to-finishstart-to-finish

start-to-startstart-to-finish

finish-to-startfinish-to-finish

durationbetweenactivities

logic only

ES=TEiLS≥TLi__

TF__TF

EF≤TEjLF=TLj

PDM

Activityi jduration ofactivity

ES EFLS LF__TF

__TF






logic only

issues with proper usage of non-traditional restraints

A 10

C 10

SS 5

A

B

B 10 FF 5

need never finish

C may start anytime

C may start before NTPA is not required for project completion

visible open endshidden open ends

PDM


ES EFLS LF__TF

__TF






logic only

issues with continuous versus

interruptible activities

continuous durationinterruptible duration

A 20

B 10

FF5

SS5

A 20

B 10

FF5

SS5

SS5 SS5

PDM


ES EFLS LF__TF

__TF






logic only

issues with an activity based methodology

Drywall 10

Elect 5PS2 FR2

Drywall 10

Elect 5SS2 FF2

Loop Error Detected

activity A to activity B to activity A loopevent 1 to event 2 no loop

PDM


ES EFLS LF__TF

__TF






logic only

A OD=10 3 RD=3

B 10

Seven days completeSeven days passed

SS7 Calculated early start of activity B desired when A is 70% complete

A OD=10 5 RD=5

B 10

Five days completeSeven days passed

SS7 Activity A starts on time but loses two days in first weekCalculated early start of activity B is two days early – when A is 50% complete

issues with measuring from start versus from

partial performance

passage versus progress

PDM







logic only

partial-to-startpartial-to-finish

finish-to-remainderstart-to-remainder

ES=TELS≤TL__

TF

TETL__TF

TETL__TF

EF≤TELF=TL__

TF

“… but what we meant to say …”


PDM

• start B 7 days after A has started• start B when 7 days of A are complete• start B when 70% of A is complete• start B when 35cy of 50cy is excavated

• finish B 4 days after A is finished• finish last 4 days of B after A is finished• finish last 40% of B after A is finished• finish last 20cy of 50cy after A is finished







logic only

partial-to-startpartial-to-finish

finish-to-remainderstart-to-remainder

ES=TELS≤TL__

TF

TETL__TF

TETL__TF

EF≤TELF=TL__

TF

“… but what we wanted to say …”


Notice toProceed0

FoundationExcavation5

North FDNForm6

South FDNForm6

North FDNStrip1

East FDNForm6

East FDNRebar2

East FDNPour1

East FDNStrip1

North FDNPour1

South FDNPour1

West FDNPour1

South FDNStrip1

West FDNStrip1

FoundationBackfill2

FS 2FS 2 FS 2 FS 2

North FDNRebar2

West FDNForm6

South FDNRebar2

West FDNRebar2

Resources

Scheduling Resources is Not CPM

What can we do?• Maths of 50s watered down to 50s computers• PCs provide tools (but not skills) to the masses• More powerful PCs benefit glitz – not maths• GUI and WYSIWYG i/o favors bar charting• Wizards further reduce need for skills• Where is the logic?

Notice toProceed

0

FoundationExcavation

5

North FDNForm

6

North FDNRebar

2

North FDNPour

1

North FDNCure

2

North FDNStrip

1East FDNForm

6

East FDNRebar

2

East FDNPour

1

East FDNCure

2

East FDNStrip

1South FDNForm

6

South FDNRebar

2

South FDNPour

1

South FDNCure

2

South FDNStrip

1West FDNForm

6

West FDNRebar

2

West FDNPour

1

West FDNCure

2

West FDNStrip

1

FoundationBackfill

2

Plan – then Schedule

Notice toProceed0


North FDNForm6

North FDNRebar2

North FDNPour1

North FDNStrip1

East FDNForm6

East FDNRebar2

East FDNPour1

East FDNStrip1

South FDNForm6

South FDNRebar2

South FDNPour1

South FDNStrip1

West FDNForm6

West FDNRebar2

West FDNPour1

West FDNStrip1

FoundationBackfill2

FS 2

FS 2

FS 2

FS 2

Relationship Diagramming Method

Fredric L. Plotnick, Esq., P.E.Engineering & Property Management Consultants, Inc.Benson Manor #117 – 101 Washington Lane – Jenkintown, PA 19046

www.fplotnick.com [email protected] 215-885-3733

RDM

http://www.fplotnick.com/


CPM requires you to record the relationships between activities ... ... and allows the computer to recalculate the impact of changes made ...

... reducing the 40%+ rework effort to that of a keystroke

Relationship Diagramming MethodRDM requires you to record the relationships between activities ...

... and allows the computer to recalculate the impact of changes made ...... reducing the 40%+ rework effort to that of a keystroke

more about


• Four classes of new coding:• The Event Code • The Reason Why Code• The Expanded Lead Lag Code• The Restraint Relationship Code

Event Codes

• Internally record and base calculations upon events• Events are at start, finish and possibly within an activity

i jEvents – External and Internal

Event Codes

1440Main Bldg - Install Roofing

10 1 C R 6 RFA12 S23

CrewRoofers

FS 0 1RF1

2440Garage – Install Roofing

5 1 C R 6 RFA15 S231450Main Bldg – Studs & Drywall

10 1 I M 4 CPS06 S071460Main Bldg – Roof HVAC

4 1 I M 4 SMS23 M14

Physical--

FS 0 1--PhysicalPenetrations at 50%

PS 50%

Building Watertight

2440i

1450i

1460i

1440i01 at 2500 SY of 5000 SY

1440i

• TE – TJL – TL – TV – T50% – T90% • TF – JTF – FF – IF • TA – TACOST

• total v exclusive preds / succs• RDM – PDM – ADM – PERT • event descriptions or titles• true milestones

i jEvents – External and Internal

TETLTF

TETLTF

TETLTF

TETLTF

Event Codes

Reason/Why Codes• Record the reason why the restraint exists

– physical – how important – description – resource – crew/craft/equipment/forms/materials/etc.

SS 2 & FF 2Excav 1000 feet - 10 days

Stone 1000 feet - 10 days

Pave 1000 feet - 10 daysSS 2 & FF 2

P – 1st / last 50 feet P – 1st / last 50 feet Open Section of Highway

P – Required

Pave Next Location

R – Move MachineType of restraint – P=physical, R=resource – and reason for restraint and duration between activities

Reason/Why Codes• Record the reason why the restraint exists

– physical – how important – description – resource – crew/craft/equipment/forms/materials/etc.

SS 2 & FF 2Excav 1000 feet - 10 days


Pave 1000 feet - 10 daysSS 2 & FF 2


P – Required

Pave Next Location

R – Move MachineType of restraint – P=physical, R=resource – and reason for restraint and duration between activities

Check for:• physical open ends• duplicative resource logicWhat if:• add crews/equip/forms…?• add falsework/relax code?

Reason/Why Codes• Special reason why codes• resource – leveling

– must suppress (ignore) “R” reason coded restraints for same resource– L coded restraints are deleted each time the leveling routine is run

Reason/Why Codes• Special reason why codes• physical – junior or subordinate support

– calculate latest dates to not delay early start of successor to restraint

Rig & Set

Procure Submit Approve Fabricate Deliver

Pour FdnRebar FdnForm FdnExcavateSurvey P P P P P

P P P PJ = Junior

Junior Late Date & Float Attribute

Legend – Top Line (Green) is Early Dates, Middle Line (Yellow) is Junior Dates, Bottom Line (Purple) is Late Dates

• Reason = J / Why = Junior or Subordinate Support• calculate new attributes JLS, JLF, JTF

Junior Late Date & Float Attribute

Legend – Top Line (Green) is Early Dates, Middle Line (Yellow) is Junior Dates, Bottom Line (Purple) is Late Dates

Distinguish Passage v Progress • Interpretation of Start to Start restraint

– what is meant by start to start?– start Activity B when 3 days have passed since Activity A was started?– or start Activity B when 3 days of Activity A have been performed?

Activity A 10 days

Activity B 15 days

Activity A 10 days

Activity B 15 days

versus3 days 3 days

• Interpretation of Start to Start restraint– what is meant if Lag > OD of Activity A?

• Interpretation of Start to Start restraint– what is meant if Lag < 0 (negative Lag)?

– Activity B can be started only after ... two days before Activity A has started?– Are we modeling what will be observable in the field or just moving bars?

Activity A 10 days

Activity B 15 days

Activity A 10 days

Activity B 15 days

versus

12 days

12 days?

Distinguish Passage v Progress

Activity A 10 days

Activity B 15 days?

Expanded Lead/Lag Codes

use the language of the superintendent• activity “B” may start 7 days after start of activity “A”• activity “B” may start when 7 days of activity “A” complete• activity “B” may start when 70% of activity “A” complete• activity “B” may start when 700 units of activity “A” complete• activity “B” may start when 3 days of activity “A” remain• activity “B” may start when 30% of activity “A” remain• activity “B” may start when 300 units of activity “A” remain

Activity A 10 daysActivity A 1000 CY

Activity B 15 days

??

calc ES or data dateSS 7 1

Act A10 1

Act B

Act C calc ES or actual startBS 7 2

Act A10 1

Act B

Act C

7 days performedPS 7

Act A10 1

Act B

Act C 3 days remainingRS 3

Act A10 1

Act B

Act C

70% performedPS 70%

Act A10 1

Act B

Act C 30% remainingRS 30%

Act A10 1

Act B

Act C

35 yd3 performedPS 35/50

Act A10 1

Act B

Act C 15 yd3 remainingRS 15/50

Act A10 1

Act B

Act C

• Record “what was said” – not translation – of restraint– 7 days after calculated start of remaining scope of work of “A”– 7 days after reported actual start of “A”– 7 (of 10) days completed – 70% completed – 35cy (of 50cy) completed– 3 (of 10) days remaining – 30% remaining – 15cy (of 50%) remaining

Start-to-Start Restraints

Record rule for out-of-sequence continued progress

ES or data dateSS 7 1

Act A10 1

Act B5 1

Act C8 2

ES or actual startBS 7 2

Act A10 1

Act B5 1

Act C8 2

Record rule for out-of-sequence continued progress

ES or actual startBS 7

Act C Act D

Act E

Act BAct A1001MAY06 12MAY06

10 515MAY06

10 715MAY06 EF=30MAY06

or 06JUN06?

10ES=24MAY06or 07JUN06?

10ES=31MAY06or 07JUN06?

Data Date = 22MAY06Activity C subject to Progress Override – BS restraint is Actual StartActivity C subject to Retained Logic – SS restraint is Early Start

Act C Act D

ES or actual finishEF 7 Act E

Act BAct A1001MAY06 12MAY06

10 515MAY06

10ES=22MAY06or 29MAY06?

12 115MAY06EF=29MAY06or 05JUN06?

Data Date = 22MAY06Activity D subject to Progress Override – EF restraint is Actual FinishActivity D subject to Retained Logic – FF restraint is Early Finish

10 15MAY06 18MAY06

• Interpretation of Finish to Finish restraint– what is meant by finish to finish?– complete Activity B when 2 days have passed since Activity A was completed

– one second after the two day hiatus?– but we didn’t say which portion of Activity B could not finish until that time!

– by the way -- can we split Activity B into two sections?– or should the start be also delayed to assure a continuous effort?– note a continuous effort or contiguous portions of an activity are the default in P3

Activity B 10-2 days

Activity A 15 days

2 days

2 days


Activity A 15 days

4 days

2 days



Activity A 15 days

2 days

2 days

Finish-to-Finish Restraints• similar issue of FF v EF restraint• if predecessor to “A” not finished

but A is finished, do we count from the calculated early finish or reported actual finish of “A”

• note need to choose calendar for FF and EF restraints

• FR and FP restraints are linked to calendar of activity “C”

• FF matches retained logic of “C”• EF matches P or M logic override

7 days remaining of CFR 7

Act A Act B

Act C12 1 I M

5 days performed of CFP 5

Act A Act B

Act C12 1 I M

EF or data dateFF 7 2

Act A Act B

Act C12 1 C R

EF or actual finishEF 7 2

Act A Act B

Act C12 1 I M

• Interpretation of Finish to Start restraint– what is meant by finish to start?– what is meant by start Activity B when Activity A is complete?– what is meant by start Activity B 7 days after Activity A is complete?– what is meant if Lag > OD of Activity A or OD of Activity B?

– what is meant if Lag < 0 (negative Lag)?– what part of Activity A is not yet complete?– what part of Activity A is complete?– – what happens if A is never completed?– – do we have another hidden open end?

– what would be meant by FS-12?

Activity A 10 days Activity B 15 days7 days

Activity A 10 days Activity B 15 daysActivity A+ 7 days


Activity A 10 days

Activity B 15 daysSS+7 FS-3

i j

i j

SS2 PS2 FR3 FF3

RD CPM™

Compliance Certified

Relationship Diagramming Critical Path Method

Recap – SS – PS – FR – FF

2 of 10 days

15 days 3

• SF – Start-to-Finish optionally supporting a “passage of time” style lag of any duration– While this restraint is generally used merely to “move the bars on the screen,”

it occasionally may be used to represent the relationship between the two activities to the best knowledge of the project manager

• A “progress of performance” style of lag is not easily supported – such would require two lags to represent – the portion of work performed of the predecessor activity – prior to – completion of work of the successor activity– Possible Lead/Lag codes where two lags are provided may include

• PR – Progressed-to-Remaining• PP – Progressed-to-Progressed• RR – Remaining-to-Remaining• RP – Remaining-to-Progressed

– The complexity and additional data entry of two lags one measuring work on the predecessor and one measuring work on the successor required for the above codes may make such impractical.

– In the event that a SF restraint is used because a “progress” style restraint is not supported details of the restraint may be noted in the restraint description field.

RD CPM™



7 days performed5 days remainingFS 12 versus PR 7 5

note start of B unimpeded

Activity A 10 days

Activity B 15 days

• CT – Contiguous– representing a Finish-to-Start restraint – where the preceding activity may not start until – a contiguous and continuous flow of work may occur – from the start of the predecessor to the finish of the successor

• The lag portion of this Lead/Lag code – represents the longest “weekend” permitted between activities

• The use of this restraint code will be similar to – assigning a Zero Free Float constraint to the predecessor– affecting the successor activity of THIS restraint only

RD CPM™



Activity A Activity B

• CC – Concurrent – representing the two activities must be performed in lock-step– this is more than saying two activities joined with SS+FF or PS+FR

RD CPM™



• CC – Concurrent – representing the two activities must be performed in lock-step– this is more than saying two activities joined with SS+FF or PS+FR

• Examples include:– erecting a MSE wall and backfilling during placement– pouring a concrete slab with embedded electrical conduit – coordination of surgeon and anesthesiologist during an operation– in each instance possibly being performed by separate subcontractors

but under the daily control of only one individual

– the proper logical means to depict the combination is by only one activity, however the needs for separate rollups by subcontractors and the general desire for such a splitting of this ONE activity indicate a need for this type of restraint code

RD CPM™



• DS – Duplicate SS+FF restraints sharing the same lag duration– the MSCS program of the 1960s and 1970s included a popular “Z” code = combination of SS+FF– indicates that the early (but not necessarily the late) start of the two activities would start together

or that the two activities (if having the same duration) would be staggered– note predecessor and successor activities should have the same duration and calendar

An error code should be generated for violations.

• DP – Duplicate PS+FR restraints sharing the same lag duration– Similar to the DS restraint, except the successor activity will be calculated to start after the

remaining duration of the predecessor has been reduced by Lag units of time.

• DR – Duplicate RS+FP restraints sharing the same lag duration– Similar to the DS restraint, except the successor activity will be calculated to start when the

remaining duration of the predecessor has been reduced to Lag units of time.

RD CPM™




• Four classes of new coding:• The Event Code• The Reason Why Code• The Expanded Lead Lag Code• The Restraint Relationship Code

Relationship Codes• Restraint v Relationship Codes• resource codes – user defined activity codes

• Calculation “on the fly?”• conduit – cable – connections – energize • rig pump – pipe to pump – run wire to pump

• Highlight the Handoff• mechanical to electrical subcontractor• crew movement between job area locations• is there a handoff or demob/remob duration?

event codes & text reason/why codes & textexpanded lead/lag codes relationship codes

Put it all together …


10 1 C R 6 RFA12 S23

CrewRoofers

FS 2 1RF1




4 1 I M 4 SMS23 M14

Physical--

FS 0 1--

PhysicalPenetrations at 50%

PS 50%

2440i

1450i

1460i

Building Watertight

1440i01 at 2500 SY of 5000 SY

1440i

Beyond RDM• standardized symbols and nomenclature • record for each activity if continuous / interruptible• record for each activity rules for out-of-sequence progress• risk and Monte Carlo• trend durations• GERT and non-inclusive logic• multiple leveling priority schemes• distributed scheduling

• RDM – Relationship Diagramming Method• RDCPM™ – Relationship Diagramming Critical Path Method

RD CPM™


Event #1 Activity #1 – 10 days50%

Event #2 Activity #2 – 12 days

Event #3 Activity #3 – 8 days

Logic #1

Logic #2

Start @ 50%

Event #4 Activity #4 – 10 daysLogic #3

Start after 5 days

SS 2 & FF 2

Excav 1000 feet - 10 days


Pave 1000 feet - 10 days

SS 2 & FF 2


P – Required

Pave Next Location

R – Move Machine


10 1 C R 6 RFA12 S23

CrewRoofers

FS 0 1RF1




4 1 I M 4 SMS23 M14

Physical--

FS 0 1--PhysicalPenetrations at 50%

PS 50%

Building Watertight

2440i

1450i

1460i

1440i01 at 2500 SY of 5000 SY

1440i

Continuous or Interruptible?

• if continuous – delays start of activity until all xF restraints complete• if interruptible – by how much and how often?• see P3 resource leveling dialog box – splitting• number of segments – relate to number of SS or FF restraints• minimum segment duration – relate to SS or FF lags

8 10 15 I M

PS 20%

PS 6

FR 3

FS 7 7 10 M

SS 2 3 7 M

PS 7

FF 1 2 5 R

Activityi jdurationES EFLS LF__TF

__TF

• ESstart = DD = Day 20• EF = ES + Dur• ES = latest EFpredecessors

• LFfinish = EFfinish

• LS = LF - Dur• LF = earliest LSsuccessors

• TF = LS - ES • TF = LF - EF

A B C D

E F

108

5 10 10

7107

20 28 35 45

28 35

35

28 33

35 42

554535

1 2 3

4

5 6

Out-of-Sequence Continued ProgressRetained Logic

Retained Logic vProgress Override

Activity 2-4, “E,” cannot continue until Activity 1-2, “A,” is complete


__TF





A B C D

E F

108

5 10 10

7107

20 28 33 43

20 27

27

28 33

27 34

534327

1 2 3

4

5 6

Out-of-Sequence Continued ProgressProgress Override

Retained Logic vProgress Override

Activity 2-4, “E,” has started and may continue without regard to Activity 1-2

Out-of-Sequence Continued ProgressModified Progress Override™


__TF





A B C D

E F

108

5 10 10

7107

20 28 33 43

20 28

28

28 33

28 35

534328

1 2 3

4

5 6

Activity 2-4, “E,” cannot be completeuntil Activity 1-2, “A,” is complete

Retained Logic vProgress Override- A Third Way? -

Risk and Monte Carlo Simulation

A 10±2

B 10±2

C 10±2

D 10±2

A 10±2B 10±2C 10±2D 10±2≈ 40

Project Duration ≈ 31⅔

LATEST DATE 5 JUN 6 EXPECTED DATE 31 MAY 6 EARLIEST DATE 26 MAY 6 TARGET DATE 30 MAY 06

Plot Date 10FEB06 (c) Primavera Systems, Inc.

MONTE CARLO TEST #2Title

Finish Date of Project

MC02MPRJ.MC Sheet 1 of 1

Date Revision Checked Approved

0

10

20

30

40

50

60

70

80

90

100

%

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

%

26 27 28 29 30 31 32 33 34 35 36DAY

Estimating Scheduling

Excerpt from page 142 of CPM in Construction Management

• for ACTIVITIES –– optimistic, most likely, pessimistic estimate of duration– bell shape, triangular, other distributions

• for progress style RESTRAINTS –– based upon reference activity

• for passage style RESTRAINTS –– optimistic, most likely, pessimistic estimate of duration– bell shape, triangular, other distributions


• default -15%/+20%, default by group, individual by activity

• for ACTIVITIES –– based upon any common resource– based upon any user defined activity code


• for passage style RESTRAINTS –– based upon any common resource– based upon any user defined restraint code


Trend Durations• for ACTIVITIES –

– based upon any common resource– based upon any user defined activity code


• for passage style RESTRAINTS –– based upon any common resource– based upon any user defined restraint code

Notice toProceed

Foundation Excavated

FoundationsPoured

FoundationsBackfilled

3 5 10 1 2 3Select FillCompacted

1 2 4 1 1 2Compaction

Test

PASS

FAIL

0 0 0

1 2 5

• GERT .or. statement– when Activity A is complete, B .or. C .or. D may start– choosing probability of B, C or D -- random numbers– choosing probability of duration

• PERT -- Optimistic, Most likely, Pessimistic• extra rock -- Zero to 60 days duration

• GERT .if. statement– if Activity A is complete when B is complete start C, otherwise start D

• what other conditions might trigger a decision of which task goes first?

GERT – Non-Inclusive Logic

multiple leveling priority schemes• no solution to NP Complete problems• trial and error – tedium – rerun for each update

Bestof

Breed

one severalall

Reason = L1 L2 L3 L4 L5

NP CompleteProblem SolutionPatent Pending

Distributed Scheduling™• Issues with hierarchical reporting of projects

Owner

Contractor

Subcontractor

Distributed Scheduling™

•activity ID•activity description•resources assigned•resources used TD•early start / finish•late start / finish•sched start / finish

•bid to contractor•subcontractor estimate•bid from sub-subs•cost to date•billed to contractor

•bid to owner•contractor estimate•bid from subcontractor•cost to date•billed to owner

•commitment by financier•engineer’s estimate•bid from contractor•cost to date•paid to contractor

My Project

Owner

Contractor

Subcontractor

Multi-HierarchicalReporting Methodology

Patent Pending

Conclusion

Notice toProceed

0

FoundationExcavation

5

North FDNForm

6

North FDNRebar

2

North FDNPour

1

North FDNCure

2

North FDNStrip

1East FDNForm

6

East FDNRebar

2

East FDNPour

1

East FDNCure

2

East FDNStrip

1South FDNForm

6

South FDNRebar

2

South FDNPour

1

South FDNCure

2

South FDNStrip

1West FDNForm

6

West FDNRebar

2

West FDNPour

1

West FDNCure

2

West FDNStrip

1

FoundationBackfill

2

Notice toProceed0


North FDNForm6

North FDNRebar2

North FDNPour1

North FDNStrip1

East FDNForm6

East FDNRebar2

East FDNPour1

East FDNStrip1

South FDNForm6

South FDNRebar2

South FDNPour1

South FDNStrip1

West FDNForm6

West FDNRebar2

West FDNPour1

West FDNStrip1

FoundationBackfill2

FS 2

FS 2

FS 2

FS 2

Notice toProceed0 0 0

FoundationExcavation3 5 10

North FDNForm5 6 8

North FDNRebar1 2 3

North FDNPour1 1 2

North FDNCureFS 2 2 2

North FDNStrip1 1 1

East FDNForm5 6 8

East FDNRebar1 2 3

East FDNPour1 1 2

East FDNCureFS 2 2 2

East FDNStrip1 1 1

South FDNForm5 6 8

South FDNRebar1 2 3

South FDNPour1 1 2

South FDNCureFS 2 2 2

South FDNStrip1 1 1

West FDNForm5 6 8

West FDNRebar1 2 3

West FDNPour1 1 2

West FDNCureFS 2 2 2

West FDNStrip1 1 1

FoundationBackfill1 2 3

Physical

Physical

PhysicalPhysical

Physical

Physical

CP Crew

CP Crew

CP Crew

Rod Crew

Rod Crew

Rod Crew

Conc Crew

Conc Crew

Conc Crew

Labor Crew

Labor Crew

Labor Crew

Forms #1

Forms #2

ADM

PDM

RDM

performance of projects is measured by activitiesperformance of projects is driven by relationships™

RD CPM™


Questions?Questions?

send further questions to:Fredric L. Plotnick, Esq., P.E.

Benson Manor - Suite #117Jenkintown, PA 19046

[email protected]

or go towww.rdcpm.com

RD CPM™



introducing the relationship diagramming methodintroducing the relationship diagramming method...

Documents