UFC 4-721-11.1
26 Nov 01
4-1.4 Combination In-House A-E Solicitation Development. In many instances it may not be possible
to completely staff the project team with in-house technical specialists either due to workload or
availability of the required expertise.
The integration of a team of technical specialists, some from a
consultant firm, working with the available in-house technical specialists can provide a suitable solution.
In this teaming arrangement it is imperative that the PM focus the team members and orchestrate a
responsibility matrix to ensure that all tasks are being addressed by in-house staff or the consultant staff.
Of particular concern would be the final assembly of the document and the Quality Assurance Checking
to assure completeness and lack of internal conflicts.
4-1.5 Project Delivery Team. The project delivery team is lead by the PM. The team members include
the technical disciplines and interested parties needed to successfully execute the project. Composition
of the team will change as the project progresses through the two phases of the solicitation. At this initial
stage of the project, the project delivery team should include at least the following members:
4-1.5.1
Customer Representative or Customer Project Manager
4-1.5.2
MACOM Representative
4-1.5.3
USACE Project Manager
4-1.5.4
Contracting.
4-1.5.5
Legal.
4-1.5.6
PA/PE supplemented by technical specialists as necessary.
4-1.5.7
Environmental specialist.
4-1.5.8
Construction representatives.
4-1.5.9
Cost Engineer
4-2 SCOPE VERIFICATION.
4-2.1 Scope of Work. The PM should ensure that a complete scope of work is available to the project
team developing the RFP document. The first opportunity to accomplish this is through a thorough review
of the project DD Form 1391, including the back-up data.
4-2.2 Programming. A comparison of the project DD Form 1391 to the topics addressed in Chapter 3 will
provide an outline of things that should have been addressed in the programming of the project.
4-2.3 Clarification. Clarification should be requested from the installation, Army Major Command
(MACOM), USACE Major Subordinate Command (MSC), and HQUSACE if conflicts exist or if data are
omitted from the documentation.
4-3 PROJECT DEFINITION CONFERENCE.
4-3.1 This initial pre-solicitation development conference is normally held at the installation, and is a
directed activity by HQUSACE. The PM schedules the conference with representatives of the user,
MACOM, and USACE. This conference is very important because it establishes the procedures and
responsibilities for all subsequent activities and identifies the roles of the entire project team. The
conference is also the PM's opportunity to ask questions and to satisfy him/herself that the project scope
and constraints are accurately reflected in the project DD Form 1391.
4-3.2 The PM is responsible for explaining to the user the Two Phase Design-Build process and his or
her role as the leader of the PDT. Unless the user has recently participated in a two phase design build
project, he/she may be unaware of the possibilities and restraints imposed by process and the applicable
regulations. This lack of knowledge will cause confusion and frustration, and is best addressed at the
start of the project. If the PM is not sufficiently knowledgeable about the two phase design-build process
he or she shall request support from a local expert from Engineering or Contracting or shall request, fund,
and coordinate support from a sister District or from HQ USACE. It is imperative to the success of the
project that the customer become familiar with the process and the responsibilities they will have during
the entire process.
4-2
Previous Page
