Professional Documents
Culture Documents
Citation
EXPORT
James J. O'Brien, P.E., PMP, CVS; Fredric L. Plotnick, Ph.D., Esq., P.E.: CPM in
Construction Management, Eighth Edition. ABOUT THE AUTHORS, Chapter (McGraw-
Hill Professional, 2016, 2010, 2006, 1999, 1993, 1984, 1971, 1965),
AccessEngineering
Customer Privacy Notice. Any use is subject to the Terms of Use, Privacy Notice and
copyright information.
For further information about this site, contact us.
This product incorporates part of the open source Protégé system. Protégé is
available at https://protege.stanford.edu//
Acknowledgments
C. Acknowledgments
The writing of this 8th edition has involved the assistance of numerous
individuals who have provided technical advice on the computer software
products discussed, feedback from the field for the case studies discussed,
editorial review to combine the writing styles of the two authors into one
more readable style, and moral support throughout the process of writing
and rewriting and editing and proofreading and publishing. Special
recognition is accorded the following individuals:
The many volunteers and members of AACEi and former PMICOS who have
contributed content and constructive criticism
Jim and Fred dedicate this 8th edition to the memory of:
Citation
EXPORT
James J. O'Brien, P.E., PMP, CVS; Fredric L. Plotnick, Ph.D., Esq., P.E.: CPM in
Construction Management, Eighth Edition. Acknowledgments, Chapter (McGraw-Hill
Professional, 2016, 2010, 2006, 1999, 1993, 1984, 1971, 1965), AccessEngineering
Customer Privacy Notice. Any use is subject to the Terms of Use, Privacy Notice and
copyright information.
For further information about this site, contact us.
This product incorporates part of the open source Protégé system. Protégé is
available at https://protege.stanford.edu//
Introduction to Logic Based Planning and
Scheduling
This introduction discusses some factors that make the case for why
planning and scheduling are best performed by the critical path method
(CPM). It covers some of the history behind the development of CPM planning
and scheduling and relays some thoughts on where the process may go in
the future. The interplay between the theory of mathematics that underlies
the methodology and the modifications needed to make the methodology
more practical is a theme that is woven throughout the text. The reader will
see that it is the scheduler who must balance these two ideals, mathematics
and engineering, to provide a useful and user-friendly tool to the users of
CPM in construction management, manufacturing, and software design, and
to other users of projects that must be finished on time and within budget.
Even at this simple level, not all is what it seems to be. If you are in a hurry,
you might begin eating a portion of your breakfast while still cooking the
rest. If your dry cleaner is open only from 10:00 A.M. to 6:00 P.M. and if your
car is very low on gas, you may have to refuel on your way to work, pick up
your dry cleaning at lunch, and buy milk on the way home from work. If you
have a foot or leg injury, you may need to put on your left shoe first.
If you want to schedule the tasks of two or more persons or the work flow of
two or more machines (even if both are under the supervision of one person),
the process becomes much more complex.
Even the terminology can be misleading. CPM was once noted as a tool in the
process of planning and scheduling. First we must plan, then we can use the
computer to perform the rote calculations (that we understand and could
perform ourselves, given time) to generate the schedule, and finally we must
read the output with a knowledge of the assumptions and tolerances
involved. Today, however, we can purchase software that includes a wizard to
simplify or ignore the need for planning, perform the calculations while
allowing user overrides to generate the features and benefits or "how to use"
your new result, and provide killer report and graphics applications to
display the schedule results.
It is the purpose of this text to teach carpentry and not merely the features
and benefits of software programs or how to use your new power saw. It is
the purpose of this text to teach the process of planning and scheduling by
means of the critical path method of analysis. We can best start by reviewing
how this field of mathematics and engineering was developed.
CPM was developed specifically for the planning of construction. The choice
was fortuitous, since construction accounts for more than 10 percent of the
annual gross national product. Almost every activity and person is affected to
some degree by new construction or the need for it. Most projects are
started well after the need has been established, seeming to follow the
whimsy, "If I'd wanted it tomorrow, I'd have asked for it tomorrow."
One of the keys to the success of CPM is that it utilizes the planner's
knowledge, experience, and instincts in a logical way first to plan and then to
schedule. CPM can save time through better planning, and in construction,
time is money.
The Egyptians and Romans worked construction miracles in their day, and
surviving ruins attest to the brilliance of their architecture, but little is
known of their construction planning and scheduling. Other historical project
managers include Noah, Solomon, and the unknown architect who designed
the tower of Babel. Again, history records much about the construction
details but little about the methods of control.
Many of us make lists of things to do (i.e., a to-do list). Those who are well
organized may make the list in a logical order, for example, a shopping list
based upon the layout of a store or supermarket. Perhaps a fanatic for
organization may first make a list of activities (or, from our example, items to
be purchased) and then copy it a second time to the preferred order in which
it is to be performed. The use of word processing or organizing software
adds a modern wrinkle to this age-old method of planning and scheduling.
However, there are no rules widely published to guide the development of to-
do lists.
If the bar graph is so well suited to construction activity, why look for another
planning aid? Because the bar graph is limited in what information it can
retain. In preparing a bar chart, the scheduler is influenced almost
necessarily by the desired completion dates, often working backward from
the completion dates. The resultant mixture of planning and scheduling is
unfortunately no better than wishful thinking.
When a bar graph is carefully prepared, the scheduler goes through the
same thinking process as the CPM planner. However, the bar graph cannot
show (or record) the interrelations and interdependencies that control the
progress of the project. And at a later date, even the originator is often hard
pressed to explain the plan by using the bar graph.
The general contractor usually prepares the overall construction plan, which
is sensible because the schedules of the other major subcontractors depend
on the general contractor's schedule. Note that in Figures 1.5.1 and 1.5.2 the
general contractor's work is broken down in some detail, with both the
mechanical and electrical work shown as continuous lines that start early
and end late. In conformance with the bar graph "schedule," the general
contractor will then often push the subcontractors to staff the project as
early as possible with as many mechanics as possible. Conversely, the
subcontractors want to come on the project as late as possible with as few
mechanics as possible. The result is that the general contractor will often
complain that the subcontractors are delaying the project through lack of
interest. At the same time, the subcontractors will often complain that the
general contractor is not turning work areas over to them, forcing them to
pull out all the stops to save the schedule.
As in most things, the truth lies somewhere between the extremes. CPM
offers the means to resolve these differences with specific information rather
than generalities. The bar chart often suffers from a morning glory complex:
it blooms early in the project but is nowhere to be found later on. We can
suppose some general reasons for this disappearing act. Prior to the
construction phase, the architect, the engineer, the owner, or all three are
trying to visualize the project schedule in order to set realistic completion
dates. Most contracts will require the submission of a schedule in bar graph
form soon after a contract is awarded. Once the project begins to take shape,
however, this early bar chart becomes as useful as last year's calendar
because it does not lend itself to planning revisions.
Although progress can be plotted directly on the schedule bar chart, the S
curve has become popular for measuring progress. The usual S curve
consists of two plots (Figure 1.5.3): the scheduled dollar expenditures versus
time and actual expenditures versus time. Similar S curves can be prepared
for labor hours, equipment and material acquisitions, concrete yardage, and
so on. Though this presentation can be interesting, it does not provide a true
indication of project completion. For instance, a low-value critical activity
could delay the project completion far out of proportion to its value.
Figure 1.5.3. Typical S curve.
Misuse of bar charts does not prove that they should be discarded. To throw
out bar charts is like throwing out the baby with the bathwater.
In early 1957, the UNIVAC Applications Research Center, under the direction
of Dr. John W. Mauchly, joined the effort with James E. Kelley, Jr., of Remington
Rand (UNIVAC) and Morgan Walker of DuPont in direct charge in Newark,
Delaware. The original conceptual work was revised, and the resulting
routines became the basic CPM. It is interesting that no fundamental
changes in this first work have been made. [3]
In December 1957, a test group was set up to apply the new technique (then
called the Kelley–Walker method). The test team (made up of six engineers,
two area engineers, a process engineer, and an estimator) and a normal
scheduling group were assigned to plan the construction of a $10 million
chemical plant in Louisville, Kentucky.
The network diagram for the project was restricted to include only the
construction steps. The project was analyzed beginning with the completion
of its preliminary design. The entire project was subdivided into major areas
of scope, and each of the areas was analyzed and broken down into the
individual work activities. These activities were diagrammed into a network
of more than 800 activities, 400 of which represented construction activities
and 150 of which were design or material deliveries.
The ability of the first team was such that a larger-capacity computer
program had to be developed for support. By March 1958, the first part of
the network scheduling was complete. At that time, a change in corporate
outlook, plus certain design changes, caused a 40 percent change in the plan
of the project. Both planning groups were authorized to modify the plan and
recompute schedules. The revisions, which took place during April 1958,
required only about 10 percent of the original effort by the CPM test team,
substantially better than the normal scheduling group.
The initial test scheduling was considered successful in all respects. In July
1958, a second project, valued at $20 million, was selected for test
scheduling. It also was successfully scheduled. Since the first two projects
were of such duration that the complete validity of the system could not be
established, a shorter project, also at DuPont in Louisville, was selected for
scheduling.
The third project was a shutdown and overhaul operation involving neoprene,
and one of the materials in the process was self-detonating, so little or no
maintenance was possible during downtime. Although the particular
maintenance effort had been done many times, it was considered to be a
difficult test of the CPM approach.
In the first CPM plan, the average shutdown time for the turnaround was cut
from 125 to 93 hours, and in later CPM applications, it was further cut to 78
hours. The resultant time reduction of almost 40 percent far exceeded any
expectations. [4]
The Polaris fleet ballistic missile (FBM) system was initiated in early 1957. To
manage the program, a Special Projects Office (SPO) was established under
the direction of then Rear Admiral (later Vice Admiral) William Raborn, Jr..
The SPO is generally credited with having developed the PERT system.
One of the key people involved in the development of PERT was Willard Fazar,
who noted that the various management tools available for managing the
Polaris program did not provide certain information essential to effective
program evaluation. In particular, they did not furnish the following:
The search for a better management system continued throughout the fall of
1957. At that time, the Navy was cognizant of the development of CPM at
DuPont. In January 1958, the SPO initiated a special study to determine
whether computers could be used in planning and controlling the Polaris
program, and on January 27, 1958, the SPO directed a group to undertake the
task of formulating the PERT technique. [5]
The goal of the group was to determine whether improved planning and
evaluating research and development work methods could be devised to
apply to the Polaris program, which involved 250 prime contractors and more
than 9000 subcontractors.
The key difference between CPM and PERT is that one identifies activities of
finite and reasonably estimated duration while the other identifies events of
zero duration separated by "some form of activity," only loosely understood to
be performed within a range of possible durations. The range of durations in
PERT varies from an optimistic estimate (or shortest time until the next event
will occur) to a most likely estimate to a pessimistic estimate. This dichotomy
was understandable since the duration of an activity, relating to a known
quantity of work, was fairly capable of estimation; the duration between
events, based upon a scope only vaguely understood, was much more a
guesstimate.
The theory behind the PERT method was based upon the interplay between
these estimates of duration and the statistical likelihood of a project
outcome, as the actual duration experienced may fluctuate among the three.
However, the early computers of the 1950s and even the 1960s did not have
the necessary speed or memory to fully utilize the theory, and the three
estimates were usually combined into one (often by separate calculation by
hand alongside the computer ) using the formula
where O = optimistic
M = most likely
P = pessimistic
An IBM brochure credited the H. B. Zachry Company of San Antonio with the
development of the precedence form of CPM. In cooperation with IBM, Zachry
developed computer programs that could handle precedence network
computations on the IBM 1130 and IBM 360. This was particularly significant
because in 1964, C. R. Phillips and J. J. Moder indicated the availability of only
1 computerized approach to precedence networks versus 60 for CPM and
PERT. Creation of an alternate format for preparing CPM networks required
new naming conventions to distinguish between the two. The form for
traditional CPM networks was originally termed the AOA or "activity on
arrow" variant of CPM. The form for new-style precedence networks was
originally termed the AON or "activity on node" variant of CPM. In the AON
variant, the activity description is shown in a box (or node) with the
sequence, or flow, shown by interconnecting lines. In most cases, arrowheads
are not used, although this leaves greater opportunity for ambiguous
network situations.
Because the terms "AOA" and "AON" are similar, and possibly because a box
only represents a node to a mathematician, AOA became known as the arrow
diagramming method (ADM), and AON became known as PDM. Often,
specifications copied from older specifications may refer to the CPM being
prepared in the AOA or AON method. A sad reflection upon the care in which
such engineering documents are written is that it is not unusual for a
specification to require the CPM to be prepared using the AOA methodology
and to run the schedule on the latest version of Primavera software (which
supports only PDM).
Many users prefer the PDM format, claiming the PDM diagram is "cleaner"
and therefore easier to follow. The simplifying factor results from the fact
that "redundant" restraints are not required in PDM (as they are in CPM) to
create unique activity numbers (i.e., when activities span between the same
two events).
CPM and PERT are based upon mathematics, and professors of mathematics
were quick to note many of the new insights opened up by this new branch
of mathematics. If an estimate of duration is merely an estimate and subject
to a level of uncertainty, then what might happen if randomly some of the
durations were raised and others lowered? If two or more paths of the logic
network were fairly close, this modification may well shift the critical path
and overall duration of the project. CPM provides a set date upon which a
project is expected to be completed. What is the probability of the project
finishing on that date, on an earlier date, or on a later date? If each of the
durations of activities (in CPM) or between events (in PERT) were randomly
chosen from the optimistic, most likely, and pessimistic durations, we would
get one value for an end date. If we repeat this process 100 or 1000 times, we
get probabilities of completion over a range of dates.
The mathematics behind neither CPM nor PERT permits boolean •OR• logic.
If an activity in logic network A is followed by two other activities B and C, it
is assumed that both can start upon the completion of A. It is also assumed
that B can start independently of C and vice versa, either starting before the
other or both starting at once. In the real world this is not always true;
sometimes you can start B or C but only one at a time (the boolean •OR•).
Sometimes you can perform B and C only if both are performed concurrently.
Sometimes the choice of which can be performed first is subject to the status
(started or completed) of a fourth activity D. And sometimes the choice of
successor is based upon a test: pass and go down one path, fail and go down
the other path. In the case of a failed test, the logic network can even loop
around to retake the test after corrective measures have been made. None of
these possibilities are supported by the mathematics of CPM or PERT.
However, many of these possibilities are supported by mathematical models
envisioned in the 1950s through today and more recently supported (at least
in part) by modern software programs generically noted as GERT programs.
As PERT was the acronym for Performance Evaluation and Review Technique,
GERT became the acronym for Generalized Evaluation and Review Technique.
As of the turn of the millennium, PDM supplanted ADM in the majority of the
scheduling world. And yet, numerous serious practitioners noted flaws in the
implementation of PDM, and many bemoaned the loss of rigor of the ADM
system. A common thread to many of these concerns was that commercial
software tended to focus upon information relating to individual activities
and groups of activities while, relatively speaking, ignoring the restraints
and relationships between activities that had been the hallmark of the
original ADM and PERT methodologies.
The issue was raised to a head in a cover story entitled "Off the Critical Path,"
published in Engineering News Record (ENR), May 28, 2003. In one of the
letters to the editor, written in the aftermath of the article, Jim Kelley (one of
the founders of CPM, as discussed in Chapter 1) wrote:
The 6th edition of this text, largely as a response to this challenge, posited a
new system that addressed many of these concerns. Since the focus of the
majority of these embellishments is related to the relationships between
activities, this is called the relationship diagramming method (RDM) and
meant to be the next level of evolution of ADM to PDM and now RDM.
The fully integrated system that has been developed to support RDM is made
available for general dissemination. In an effort to avoid the balkanization of
many different implementations of PDM (resulting in the same input data
yielding differing results based upon which software is used), an evolving
standard has been established, and developers may choose to have
implementations-determined compliance via a certification mark RDCPM
(further details are available at www.RDCPM.com).
The key aspects of the RDM system are a restoration of identifying events (or
points in time) that were represented by the nodes in ADM (and were the
mathematical basis for its rigor), a better definition of the bases of duration
input, and the ability to record both explicit data and metadata on the
restraints between activities. This is not in any manner revolutionary; rather
the process is a natural evolution from the Gantt chart to ADM to the PDM
process. Recalling that CPM is but a mechanized means to re-create (and
hopefully supplement) the preparation of a bar chart mostly by recording
(some of) the reasons for arranging the activities (or bars) in a specific order,
RDM merely attempts to collect and record more of the thought processes of
that manual effort.
The recording of events (points in time) is not limited to that of ADM, at the
start and finish of each activity, but is expanded to events within an activity.
The restoration of these event nodes permits the software to more accurately
model the thought processes of the preparer of a bar chart. An overlap of
two activities, as in PDM, may be accomplished either by a start-to-start
restraint measuring time from the calculated or reported actual start of an
activity or by a progressed-to-start restraint emanating from an event (point
in time) when a specified portion (or percentage) of an activity has been
completed. Similarly, the event (point in time) representing when some
(defined) portion of an activity cannot continue prior to the completion of
another activity may be represented by a finish-to-remainder restraint, to be
compared to the generic finish-to-finish restraint.
It should be stressed that RDM is not merely a return to, or a form of, ADM.
Although an activity may be bounded by an i node and j node (and have one
or more k nodes embedded within), activities are connected solely by
restraints and the j node of one activity may never be the i node of another.
Some of the additional functionalities that may follow the recording of this
known but previously discarded data in this new format include these:
Identify the rationale or reason for each restraint, by both a code and a
description thereof. A physical restraint (erect the walls before the roof) is
the most obvious example. Other types of restraint are resources including
crew, equipment, reusable forms, and others, which are already part of the
thinking of the team preparing the CPM. However, by expanding the
recording of assumptions behind the plan used to prepare the schedule,
additional power may be gained, such as (1) automated guarantees that
each activity in the network is preceded by a physical restraint; (2)
permitting "what if" analyses of the impact of limiting or not limiting crews
by various craft, reusable forms, or other specific resources; (3) sorting
and selecting by reason for relationship; and (4) providing an automated
guide to areas of possible corrective action when various events threaten
to delay or disrupt timely completion of a project.
Expand, sort, and select capabilities to the text of the activity description
and various activity codes of the predecessors and successors of an
activity. For example, a selection may highlight each instance where work
by the mechanical subcontractor is immediately followed by work by the
electrical subcontractor.
Provide the same level of control over lag durations (between activities) as
is (1) provided for activities, such as choice of calendar and (2) range of
duration, for those systems that support PERT and SPERT style of
calculations.
Expand the algorithms used to handle situations where actual
performance bypasses the planned logic and where work is performed out
of sequence. The current choice "retained logic" assumes an activity
started out of sequence to be suspended until its predecessors are 100
percent complete. The current choice "progress override " that assumes
that once an activity is started out of sequence, the violated predecessor
logic is no longer important. A third and new choice may be a "modified
progress override" that assumes that the activity started out of sequence
may continue to zero remaining duration, but that successors thereof may
not start until its predecessors are complete. The choice of algorithm
should further be expanded from a projectwide decision to one that may be
set by type of restraint ("retained logic" for "physical " restraints, "modified
progress override" for "resource" restraints) or even on a restraint-by-
restraint setting by the scheduler.
Expand the types of duration to include a trend duration (TD) based upon
an adjustably damped comparison between original and actual durations
classified by similar work scopes. A separate SPERT-style calculation could
then be run based upon both the original and trend durations.
Many other academic users and practitioners of CPM have suggested similar
and other extensions to CPM. Many variants of CPM and extensions thereto
exist in university computers. Eventually one of the established software
vendors or a new entrant will make such extensions commercially available,
and if they are successful, all other vendors will rush to copy the new
algorithms. Thus, just as PDM replaced ADM and has become the primary
method used in the construction industry today, so too will RDM or some
other diagramming method become the standard of tomorrow. That
notwithstanding, the basic rules of planning and scheduling are immutable,
and it is the hope of the authors that all users of CPM will understand and
appreciate the basics, whichever conventions and/or software is used.
1.12. Summary
The concept of scientific scheduling is barely a century old. The to-do list was
supplanted by the Gantt chart only in 1910. The concept of CPM, replacing
intuition and brute-force arranging and rearranging of bars with a fixed
mathematical algorithm (which could then be performed by a computer), was
introduced in 1956. Implementation of CPM was then—and always will be
—limited to the capabilities of the most current computer hardware and
operating systems. In 1956, this required the rules of (what is now called)
ADM, the arrow diagramming method. Concurrently developed was the PERT
or Project Evaluation Review Technique method. By 1964, improvements in
computer hardware (giving us random access memory, or RAM) permitted
machine calculation of PDM, the precedence diagramming method, which had
been initially developed as not capable of computer solution. A "flaw" of the
concept and implementation was to drop the use of event nodes representing
discrete points in time. This flaw was addressed in 2004 with the
development of RDM, the relationship diagramming method. While some
elements of RDM have been incorporated into Primavera Pertmaster (now
marketed as Oracle Primavera Risk Analysis, or PRA) versions 8.2 through
8.6, full implementation has not yet been provided in a commercially available
software product.
[5]D. G. Malcolm et al., "A Network Flow Computation for Project Cost Curves,"
Rand Paper P-1947, Rand Corporation, March 1960; D. G. Malcolm, J. H.
Roseboom, C. E. Clark, and W. Fazar, "Applications of a Technique for
Research and Development Program Evaluation," Operations Research , vol.
7, no. 5, pp. 646–699, 1959; and W. Fazar, "The Origin of PERT," The
Controller , vol. 30, pp. 598ff., December 1962.
Citation
EXPORT
James J. O'Brien, P.E., PMP, CVS; Fredric L. Plotnick, Ph.D., Esq., P.E.: CPM in
Construction Management, Eighth Edition. Introduction to Logic Based Planning and
Scheduling, Chapter (McGraw-Hill Professional, 2016, 2010, 2006, 1999, 1993,
1984, 1971, 1965), AccessEngineering
Customer Privacy Notice. Any use is subject to the Terms of Use, Privacy Notice and
copyright information.
For further information about this site, contact us.
This product incorporates part of the open source Protégé system. Protégé is
available at https://protege.stanford.edu//
The Pure Logic Diagram
Each arrow represents one activity in the project. The tail of the arrow
represents the starting point of the activity, and the head represents the
completion. The arrow is not a vector and it is not drawn to scale. It can be
curved or bent as required; however, it cannot be interrupted because it is a
separate entity.
As depicted in Figure 2.1.1, the arrow format also conveys logic to the next
activity, while a box must be preceded and succeeded by one or more arrows.
In practice, some practitioners may desire to contain descriptions of activities
(and associated data such as duration and related codes such as resources,
location, etc.) within a box, even if building the network with "arrows," and
some building with boxes may squeeze in an extra activity with a description
printed above an arrow between boxes.
The arrows or boxes are arranged to show the plan, or logical sequence, in
which the activities of a project are to be accomplished. This is done by
answering two questions with each activity:
Rotate tires
Lubricate
Change oil
Wax and polish
Drain antifreeze
In this example, a decision is required before any arrows can be drawn. The
mechanic must decide whether to do the hoist work first or last. Assume that
the mechanic decides to do the hoist work first. Accordingly, the first arrow
will be
Following this are all of the arrows that could logically follow hoisting the car.
From the work list, they are rotate tires, lubricate, and change oil.
When the activity, lower car, is added, note that the general work list is not
broken down into enough detail to show the mechanic's work plan. Adding
this activity after the hoist work:
What does this really say? It says that the activities cannot start until the
hoist is raised and must finish before the hoist is lowered. Something is
missing, however. The activity, rotate tires, indicates that the mechanic must
get the spare tire out while the car is on the hoist. That is not logical, and it
certainly is not what the mechanic might be expected to do. Also, it is usual
practice for the mechanic to loosen the tire lug nuts before raising the
wheels clear of the ground.
This part of the network then becomes
For lubricate, the first network indicates that oiling and checking items
under the hood (battery, alternator, radiator, brake fluid, etc.) must be done
while the car is up on the hoist. To do this, the mechanic would need stilts or
a ladder.
Similarly,
Combining the portions of the network and adding the two activities not
previously shown, drain antifreeze and polish and wax car, the arrow diagram
representing this everyday operation is as shown in Figure 2.2.1.
Another random document with
no related content on Scribd:
DANCE ON STILTS AT THE GIRLS’ UNYAGO, NIUCHI
I see increasing reason to believe that the view formed some time
back as to the origin of the Makonde bush is the correct one. I have
no doubt that it is not a natural product, but the result of human
occupation. Those parts of the high country where man—as a very
slight amount of practice enables the eye to perceive at once—has not
yet penetrated with axe and hoe, are still occupied by a splendid
timber forest quite able to sustain a comparison with our mixed
forests in Germany. But wherever man has once built his hut or tilled
his field, this horrible bush springs up. Every phase of this process
may be seen in the course of a couple of hours’ walk along the main
road. From the bush to right or left, one hears the sound of the axe—
not from one spot only, but from several directions at once. A few
steps further on, we can see what is taking place. The brush has been
cut down and piled up in heaps to the height of a yard or more,
between which the trunks of the large trees stand up like the last
pillars of a magnificent ruined building. These, too, present a
melancholy spectacle: the destructive Makonde have ringed them—
cut a broad strip of bark all round to ensure their dying off—and also
piled up pyramids of brush round them. Father and son, mother and
son-in-law, are chopping away perseveringly in the background—too
busy, almost, to look round at the white stranger, who usually excites
so much interest. If you pass by the same place a week later, the piles
of brushwood have disappeared and a thick layer of ashes has taken
the place of the green forest. The large trees stretch their
smouldering trunks and branches in dumb accusation to heaven—if
they have not already fallen and been more or less reduced to ashes,
perhaps only showing as a white stripe on the dark ground.
This work of destruction is carried out by the Makonde alike on the
virgin forest and on the bush which has sprung up on sites already
cultivated and deserted. In the second case they are saved the trouble
of burning the large trees, these being entirely absent in the
secondary bush.
After burning this piece of forest ground and loosening it with the
hoe, the native sows his corn and plants his vegetables. All over the
country, he goes in for bed-culture, which requires, and, in fact,
receives, the most careful attention. Weeds are nowhere tolerated in
the south of German East Africa. The crops may fail on the plains,
where droughts are frequent, but never on the plateau with its
abundant rains and heavy dews. Its fortunate inhabitants even have
the satisfaction of seeing the proud Wayao and Wamakua working
for them as labourers, driven by hunger to serve where they were
accustomed to rule.
But the light, sandy soil is soon exhausted, and would yield no
harvest the second year if cultivated twice running. This fact has
been familiar to the native for ages; consequently he provides in
time, and, while his crop is growing, prepares the next plot with axe
and firebrand. Next year he plants this with his various crops and
lets the first piece lie fallow. For a short time it remains waste and
desolate; then nature steps in to repair the destruction wrought by
man; a thousand new growths spring out of the exhausted soil, and
even the old stumps put forth fresh shoots. Next year the new growth
is up to one’s knees, and in a few years more it is that terrible,
impenetrable bush, which maintains its position till the black
occupier of the land has made the round of all the available sites and
come back to his starting point.
The Makonde are, body and soul, so to speak, one with this bush.
According to my Yao informants, indeed, their name means nothing
else but “bush people.” Their own tradition says that they have been
settled up here for a very long time, but to my surprise they laid great
stress on an original immigration. Their old homes were in the
south-east, near Mikindani and the mouth of the Rovuma, whence
their peaceful forefathers were driven by the continual raids of the
Sakalavas from Madagascar and the warlike Shirazis[47] of the coast,
to take refuge on the almost inaccessible plateau. I have studied
African ethnology for twenty years, but the fact that changes of
population in this apparently quiet and peaceable corner of the earth
could have been occasioned by outside enterprises taking place on
the high seas, was completely new to me. It is, no doubt, however,
correct.
The charming tribal legend of the Makonde—besides informing us
of other interesting matters—explains why they have to live in the
thickest of the bush and a long way from the edge of the plateau,
instead of making their permanent homes beside the purling brooks
and springs of the low country.
“The place where the tribe originated is Mahuta, on the southern
side of the plateau towards the Rovuma, where of old time there was
nothing but thick bush. Out of this bush came a man who never
washed himself or shaved his head, and who ate and drank but little.
He went out and made a human figure from the wood of a tree
growing in the open country, which he took home to his abode in the
bush and there set it upright. In the night this image came to life and
was a woman. The man and woman went down together to the
Rovuma to wash themselves. Here the woman gave birth to a still-
born child. They left that place and passed over the high land into the
valley of the Mbemkuru, where the woman had another child, which
was also born dead. Then they returned to the high bush country of
Mahuta, where the third child was born, which lived and grew up. In
course of time, the couple had many more children, and called
themselves Wamatanda. These were the ancestral stock of the
Makonde, also called Wamakonde,[48] i.e., aborigines. Their
forefather, the man from the bush, gave his children the command to
bury their dead upright, in memory of the mother of their race who
was cut out of wood and awoke to life when standing upright. He also
warned them against settling in the valleys and near large streams,
for sickness and death dwelt there. They were to make it a rule to
have their huts at least an hour’s walk from the nearest watering-
place; then their children would thrive and escape illness.”
The explanation of the name Makonde given by my informants is
somewhat different from that contained in the above legend, which I
extract from a little book (small, but packed with information), by
Pater Adams, entitled Lindi und sein Hinterland. Otherwise, my
results agree exactly with the statements of the legend. Washing?
Hapana—there is no such thing. Why should they do so? As it is, the
supply of water scarcely suffices for cooking and drinking; other
people do not wash, so why should the Makonde distinguish himself
by such needless eccentricity? As for shaving the head, the short,
woolly crop scarcely needs it,[49] so the second ancestral precept is
likewise easy enough to follow. Beyond this, however, there is
nothing ridiculous in the ancestor’s advice. I have obtained from
various local artists a fairly large number of figures carved in wood,
ranging from fifteen to twenty-three inches in height, and
representing women belonging to the great group of the Mavia,
Makonde, and Matambwe tribes. The carving is remarkably well
done and renders the female type with great accuracy, especially the
keloid ornamentation, to be described later on. As to the object and
meaning of their works the sculptors either could or (more probably)
would tell me nothing, and I was forced to content myself with the
scanty information vouchsafed by one man, who said that the figures
were merely intended to represent the nembo—the artificial
deformations of pelele, ear-discs, and keloids. The legend recorded
by Pater Adams places these figures in a new light. They must surely
be more than mere dolls; and we may even venture to assume that
they are—though the majority of present-day Makonde are probably
unaware of the fact—representations of the tribal ancestress.
The references in the legend to the descent from Mahuta to the
Rovuma, and to a journey across the highlands into the Mbekuru
valley, undoubtedly indicate the previous history of the tribe, the
travels of the ancestral pair typifying the migrations of their
descendants. The descent to the neighbouring Rovuma valley, with
its extraordinary fertility and great abundance of game, is intelligible
at a glance—but the crossing of the Lukuledi depression, the ascent
to the Rondo Plateau and the descent to the Mbemkuru, also lie
within the bounds of probability, for all these districts have exactly
the same character as the extreme south. Now, however, comes a
point of especial interest for our bacteriological age. The primitive
Makonde did not enjoy their lives in the marshy river-valleys.
Disease raged among them, and many died. It was only after they
had returned to their original home near Mahuta, that the health
conditions of these people improved. We are very apt to think of the
African as a stupid person whose ignorance of nature is only equalled
by his fear of it, and who looks on all mishaps as caused by evil
spirits and malignant natural powers. It is much more correct to
assume in this case that the people very early learnt to distinguish
districts infested with malaria from those where it is absent.
This knowledge is crystallized in the
ancestral warning against settling in the
valleys and near the great waters, the
dwelling-places of disease and death. At the
same time, for security against the hostile
Mavia south of the Rovuma, it was enacted
that every settlement must be not less than a
certain distance from the southern edge of the
plateau. Such in fact is their mode of life at the
present day. It is not such a bad one, and
certainly they are both safer and more
comfortable than the Makua, the recent
intruders from the south, who have made USUAL METHOD OF
good their footing on the western edge of the CLOSING HUT-DOOR
plateau, extending over a fairly wide belt of
country. Neither Makua nor Makonde show in their dwellings
anything of the size and comeliness of the Yao houses in the plain,
especially at Masasi, Chingulungulu and Zuza’s. Jumbe Chauro, a
Makonde hamlet not far from Newala, on the road to Mahuta, is the
most important settlement of the tribe I have yet seen, and has fairly
spacious huts. But how slovenly is their construction compared with
the palatial residences of the elephant-hunters living in the plain.
The roofs are still more untidy than in the general run of huts during
the dry season, the walls show here and there the scanty beginnings
or the lamentable remains of the mud plastering, and the interior is a
veritable dog-kennel; dirt, dust and disorder everywhere. A few huts
only show any attempt at division into rooms, and this consists
merely of very roughly-made bamboo partitions. In one point alone
have I noticed any indication of progress—in the method of fastening
the door. Houses all over the south are secured in a simple but
ingenious manner. The door consists of a set of stout pieces of wood
or bamboo, tied with bark-string to two cross-pieces, and moving in
two grooves round one of the door-posts, so as to open inwards. If
the owner wishes to leave home, he takes two logs as thick as a man’s
upper arm and about a yard long. One of these is placed obliquely
against the middle of the door from the inside, so as to form an angle
of from 60° to 75° with the ground. He then places the second piece
horizontally across the first, pressing it downward with all his might.
It is kept in place by two strong posts planted in the ground a few
inches inside the door. This fastening is absolutely safe, but of course
cannot be applied to both doors at once, otherwise how could the
owner leave or enter his house? I have not yet succeeded in finding
out how the back door is fastened.