CONTACTS 
0201 - Corps of Engineers, SFD            415 977 8400 fax 8483
020101 - Mr. Thompson F. Keesling, Architect; Assistant Chief =415 977 8473/8701
020102 - Construction Operations Division   =415 977 8480
0202 - Corps of Engineers, SFD            415 977 8400 fax 8483
020201 - Mr. Max R. Blodgett, II, P.E., L.S.
020202 - Construction Operations Division   =415 977 8480

SUBJECTS
Keesling PM for Richmond, Automated Management in District, Keesling
Project Management Review
Automated Management, Keesling's Assignment
Richmond Project Launch, Construction Launch Planning
Objectives/Requirements, Schedule Launch Project
SDS Captures History to Guide Future
Project Manager, COE, Keesling
Supervision & Admin Cost

2210 -    ..
2211 - Summary/Objective
2212 -
221201 - Follow up ref SDS 15 0000, ref SDS 13 0000.
221202 -
221203 - Reviewed and edited launch schedule for Richmond project.  DE assigned
221204 - Tom this morning to be the PM for Richmond and to develop procedures
221205 - and process for PM in the District.  We discussed project management
221206 - process, including WBS, focusing on construction operations to launch
221207 - a new project, using Richmond as a prototype. Discussed briefly with
221208 - Max the need to support Leonard in meeting schedule targets to prepare
221209 - for start of construction on 970601.
221210 -
221211 -
221212 -
221213 -
221214 -
2213 -
2214 -
2215 - Progress
2216 -
221601 - Tom Assigned PM for Richmond
221602 -
221603 - DE asked Tom to be the Project Manager for Richmond and for another
221604 - project, plus take over management of some kind of training mission,
221605 - seems like it is related to technicial managers.
221606 -
221607 -      [On 970428 someone else is doing this, ref SDS 32 5P4N
221608 -
221609 -
221610 -  ..
221611 - Project Management Implemetation Procedures Project
221612 -
221613 - DE seems to have asked Tom to develop a Project Management process in
221614 - the District to implement COE PM regulations and procedures.  This is
221615 - a research effort that is incorporated into the Richmond spec for
221616 - Luster to support under Task Order 1, ref OF 1 line 260.
221617 -
221618 -      [On 970417 DE raised this in meeting with Luster, ref SDS 27 4588
221619 -
221620 -      [On 970427 creating this position for CSB and Richmond
221621 -      organization and management planning, ref SDS 30 KQ3L
221622 -
221623 -
221624 -
221625 -  ..
221626 - Richmond Launch Schedule Prototype
221627 -
221628 - We reviewed the schedule for launching the Richmond project, ref OF 6
221629 - line 30.  Tom generally agreed with the process.  There were no
221630 - significant changes in the logic precedence or activity durations.  We
221631 - considered extending the task for awarding the AE contract to reflect
221632 - that a lot of work can be accomplished by the AE during that period.
221633 -
221634 - Considered providing detail for the activity "Objectives/Requirements"
221635 - showing review of plans and specs, and an Engineering report drawing
221636 - attention to Con Ops any significant planning and scheduling
221637 - considerations in the plans and specs, e.g., GC to provide project
221638 - office for COE.  GC to provide CPM schedule x days following NTP.
221639 -
221640 - Tom suggests citing PMP, PCA, CCA and RMS as inputs to be considered
221641 - in developig project requirements.  Each of these take time for review
221642 - to develop a comprehensive Construction Management Plan.
221643 -
221644 - Tom will ask Leonard to submit comments and/or questions the first
221645 - part of next week.
221646 -
221647 -      [See follow up with Leonard at ref SDS 24 line 149.]
221648 -
221649 - Tom noted that this schedule scenario for launching Richmond could be
221650 - promulgated as a generic process for launching all construction
221651 - projects in the District.
221652 -
221653 - We discussed the correlation with controlling regulations.  The aim is
221654 - to use descriptions of activities that reflect current regulations and
221655 - a consistent structure vis a vis project management, construction
221656 - management, Construction Contract Administration, per CCA Guide, and a
221657 - term that is new for me that Tom called
221658 -
221659 -                  "Supervision and Administration."
221660 -
221661 - We spent considerable time trying various alternate descriptions to
221662 - reflect the work at succeeding planning phases and for different
221663 - levels of COE management.  Tom did some work on this a number of years
221664 - ago that got set aside due to the other assignments, so this is an
221665 - opportunity to think this through, including the current need to plan
221666 - the start of construction beginning with completion of the plans and
221667 - specs.
221668 -
221669 -      [Added a task for Project Team to develop a deliverable called a
221670 -      Supervision and Administration Plan that would be the field
221671 -      implementation of the Construction Management Plan, per Tom's
221672 -      explanation this morning, ref SDS 21 line 105.]
221673 -
221674 - He retrieved the COE regulation on Project Management that is dated
221675 - 1992.  It does not seem to actually mention Construction Management,
221676 - but the introduction the document indicates a general process of
221677 - developing sponsor agreements, engineering management and then
221678 - construction management.
221679 -
221680 - Tom drew out a schematic of the process that covers "Recon"
221681 - Feasability, PDE, which I think is Planning, Design and Engineering,
221682 - then Construction and then O&M.  Recon is investigating project ideas
221683 - to see if feasability should be performed.
221684 -
221685 - Tom discussed having the AE provide a QC process for its work to
221686 - support QA by Project Engineer, similar to General Contractor who
221687 - provides Quality Control for its work.
221688 -
221689 -      [Added this at ref SDS 22 line 60.]
221690 -
221691 -  ..
221692 - Supervision and Administration is the work by Con Ops to manage the
221693 - contractor in performing the work at the site.  This entails use of
221694 - the Construction Contract Administration (CCA) Guide, which calls for
221695 - an implementation plan, per ref SDS 14 line 145.
221696 -
221697 -
221698 - Tom indicated the cost for Supervision and Administration has averaged
221699 - 6% - 8% of direct cost on prior projects.
221700 -
221701 -      [See follow up where budget reported on Richmond does not reflect
221702 -      these valuations, ref SDS 33 line 291.]
221703 -
221704 - The discussion indicated that the project launch schedule should
221705 - typically be prepared by the CSB, as reflected by putting Leonard's
221706 - name at the top of the Richmond schedule.  Another thought would be
221707 - that the CON OPS Construction Manager might be responsible for the
221708 - initial Construction Management Plan that provides liason between
221709 - Engineering Division and CSB.
221710 -
221711 -
221712 - Lessons Learned
221713 -
221714 - We wound up deciding to make a primary deliverable of the Construction
221715 - Launch Schedule a "Construction Management Plan" (CMP), since this is
221716 - the construction phase of the project. It sets roles, responsibilities
221717 - and procedures to implement the Project Management Plan (PMP) produced
221718 - and maintained earlier in the life cycle. Tom feels it should identify
221719 - relationships between CON OPS, PPMD, Contracting Division, the PCA and
221720 - good management practices based on lessons learned on prior projects,
221721 - which reflects Tom Benero's objective in the meeting on 971001,
221722 - ref SDS 1 line 162.
221723 -
221724 - He listed the following elements:
221725 -
221726 -       Construction Management Plan (CMP)
221727 -
221728 -       •  Organization
221729 -       •  Roles and Responsiblities
221730 -       •  Schedule
221731 -       •  Budget/Funding
221732 -       •  Change Order Control
221733 -       •  RMS
221734 -       •  Procure AE Services
221735 -       •  QA/QC by AE
221736 -       •  Contract Administration
221737 -
221738 -
221739 -   [See implementation at ref SDS 21 line 106.]
221740 -
221741 -
221742 -
221743 -
2218 -

SUBJECTS
WBS

2404 -
240401 -  ..
240402 - WBS Needs to Integrate with COE Accounts
240403 -
240404 - We did not consider WBS in the Richmond launch schedule in detail.
240405 - There were no specific changes or additinos, however I want to revise
240406 - the WBS to make it simpler, and apply the double letter structure.
240407 -
240408 -      [See follow up at ref SDS 20 line 98; final submittal at ref SDS
240409 -      23 line 173.]
240410 -
240411 - I asked if the District has a WBS for the project.  Tom seemed to
240412 - indicate there is a general WBS.  When we returned to his office from
240413 - the conference room after our meeting, he showed a large chart that
240414 - has been taped together and which is the District WBS.  Presumably
240415 - there is a component for project launch activities.
240416 -
240417 - We examined COE's WBS later in Tom's office.  It is a huge document
240418 - comprised of approximately 15 sheets taped together.  There is no
240419 - scope description with the elements.  There does not seem to be room
240420 - in the numbering sequence for adding work packages between existing
240421 - ones.  Tom said he asked about this matter and was told the WBS is
240422 - comprehensive.
240423 -
240424 -    [See follow up developing WBS for Richmond that recognizes these
240425 -    concerns, ref SDS 26 line 104.]
240426 -
240427 -
240428 -
240429 -
2405 -

SUBJECTS
Negotiations, Start to Start Work

2504 -
250401 - No Progress Reported on Luster and COE Contract
250402 -
250403 - Tom has not heard from Monti about setting a meeting with Luster. He
250404 - got the impression that DE is not yet fully acquainted with the
250405 - strengths of Luster.
250406 -
250407 -      [See call received from Ahmet, ref SDS 19 line 71.]
250408 -
250409 -
250410 -
2505 -

SUBJECTS
Richmond Scope of Services, 970225
COE Staffing
Staffing of Project
Management Plan

3407 -
340701 -  ..
340702 - CSB to Submit Organization and RMS Planning Next Week
340703 -
340704 - Followed up work at ref SDS 16 8456.
340705 -
340706 - Tom indicated he spoke to Leonard and they plan to meet toward the end
340707 - of next week to review the update on the information flow chart for
340708 - RMS from the results of the meeting last week with Max, ref SDS 16
340709 - line 187.  This reflects discussions with Leonard yesterday at ref SDS
340710 - 18 line 158.
340711 -
340712 - We did not have time this morning to review the updated CSB
340713 - organization chart that was discussed last week, ref SDS 16 line 187.
340714 -
340715 -      [See review meeting on 970404 where updated CSB organization
340716 -      chart not available, ref SDS 25 line 229; prepared on 970428 ref
340717 -      SDS 31 line 89.]
340718 -
340719 -
340720 -
340721 -  ..
340722 - RMS Flow Chart Not Available in Sacramento
340723 -
340724 - Follow up ref SDS 16 1752.
340725 -
340726 - Tom advised his contact in the Sacramento District called and said
340727 - they do not have a formal Information Flow chart for RMS use, per our
340728 - discussion last week, ref SDS 17 8488.
340729 -
340730 -
340731 -
340732 - Schedule, Management Planning Reviews
340733 -
340734 - Tom will get results of Leonard's review of the initial schedule
340735 - launch.
340736 -
340737 -      [On 970402 Tom is scheduling review meeting. ref SDS 24 7751.]
340738 -
340739 -
340740 - I spoke to Max for about 20 minutes while Tom was reviewing the notes
340741 - of the schedule that clarify scope of various activities.  He glanced
340742 - briefly through the project launch schedule for Richmond.  Max showed
340743 - a staffing "requisition" Leonard has submitted.  Max feels getting
340744 - adequate staff is crucial in order to meet the schedule objectives for
340745 - launching Richmond and the other projects CSB has coming up over the
340746 - next year.
340747 -
340748 -
340749 -
340750 - CSB Needs Organizational Development Support
340751 -
340752 - Max feels further work is needed on assisting Leonard with the staff
340753 - requisition process relative to work descriptions and organization
340754 - structure, which was to be reviewed in the meeting this morning, per
340755 - understandings last week, ref SDS 16 line 187.
340756 -
340757 -      [See meeting on 970404, ref SDS 25 line 216; submission of
340758 -      positions for PE and Inspectors on 970424, ref SDS 29 line 126;
340759 -      and submission of organizaiton charts for CSB and Richmond, ref
340760 -      SDS 31 line 90.]
340761 -
340762 -
340763 -
340764 -
340765 -
340766 -
340767 -
340768 -
340769 -
340770 -
340771 -
340772 -
3408 -