Whole Building Design Guide



Design-Build Processes SCRIPT v3Slide 01Welcome to the Design-Build Processes Training Module which is the third training session within the NAVFAC Design-Build (DB) Training Series. This Design-Build training series consists of training modules that provide an understanding of the latest Design-Build policies and processes and an explanation of the tools and documents available to help our NAVFAC personnel and Design-Build Teams accomplish their jobs.Slide 02The training modules provide Project Manager and Designers with the details for the DB processes, explanation of the level of design required, the unique post-award processes as well as roles and responsibilities. The goal of the training series is to prepare you to leverage DB to its fullest advantage. There are five modules:Introduction to Design-BuildStandard RFP Template Design-Build Processes Small Project Template D-B Master Management Training for Criteria ManagersA training series to provide NAVFAC Construction Managers with basic and fundamental information required to effectively manage NAVFAC Construction Contracts is available. These training modules can be found in the Total Workforce Management System (TWMS). Select Online Training & Notices then Available Training. Scroll down to the course titles that begin with NAVFAC CI. The modules that deal specifically with DB are the Design-Build Post Award Process and Post Award Kickoff Meeting (PAK) modules. Slide 03This course is approximately 50 minutes long.There are Knowledge Checks throughout the course to test your comprehension.Each page of this course contains a navigation bar across the bottomThe course will not move to the next page automatically – Use these buttons to move within the courseClick the play or pause button to play or pause the courseClick the back button to review the previous pageClick the forward button to advance to the next pageClick and drag the progress indicator to move the course forward or backwardClick the audio button to turn the audio on or offClick the exit button to close the course windowClick the arrows at the top-left corner to open or close the table of contentsSlide 04These are the topics and learning objectives for this training module:First, to know the Common Objectives and the differences of the 4 NAVFAC Design-Build ProcessesLearn about the NAVFAC Business Management System, or BMSUnderstand the NAVFAC personnel Roles and Responsibilities as outlined in the BMSGet familiar with the Characteristics of the 4 NAVFAC Design-Build ProcessesAnd finally, know the Post-Award ProcessesSlide 05NAVFAC has four basic Design-Build Processes used to develop an RFP and procure a Design-Build Construction contract. All four have a specific purpose. To efficiently execute a project which of these processes to choose depends on the size and complexity of the project and the risk acceptance level. The four processes are:The Standard Design-Build Process, which can be used for all NAVFAC projects. This process is typically used in larger stand-alone contracts. The Standard Process is divided into two delivery methods; in-house and AE. All the other processes include process steps for both In-House and AE project deliveryThe second process is the Multiple Award Construction Contract, or “MACC” Process. It is used for task orders executed under a MACC Contract. The next process: Sole Source Negotiated Scope Design-Build Process is used for non-competitive contracts. And finally, we haveThe Small Project Design-Build Process, which is used for small, low complexity projects.It is important to note that these processes have been developed and refined in the last 20 years of NAVFAC performing Design-Build projects. These processes have been shown to yield successful projects when the steps are followed by all team members and accompanied by open communication and collaboration. It is critical that the client participates in the preparation of the RFP, the selection process and the post-award meetings. This ensures that the client’s needs will be met by the resulting project; and it gets them engaged in the process and provides an understanding of the design-build project delivery process.We are going to describe each of these design-build delivery processes, but before we do let’s talk about what they have in common and what they don’t.Slide 06One thing in common is that for each of the DB processes, you can find the steps to ensure successful project delivery and much more in NAVFAC’s Business Management System, or “BMS”. The BMS is a system that outlines NAVFAC’s business processes and describes the work performed to deliver NAVFAC products and services. It includes associated resources and identifies roles and responsibilities for NAVFAC personnel. There are several training resources on how to use BMS available on the BMS home page. The BMS system is web-based and is accessible through the NAVFAC portal. The BMS processes are designed to be continually updated so they should be reviewed regularly to determine if any processes have been updated.Slide 07Unlike the NAVFAC Design-Build Master RFP that is housed on the public Whole Building Design Guide website, BMS is internal and is accessed through the NAVFAC Portal Intranet. The steps described in each process explain the responsibilities and actions of NAVFAC personnel only. These processes are not applicable to non-NAVFAC personnel and therefore the BMS is not accessible to the publicThe Capital Improvement Section of BMS addresses several processes. Section B1, titled “Design and Construction”, includes both Design-Bid-Build and Design-Build processes. The Acquisition Section of BMS that addresses the planning, award and administration of design and construction contracts is in BMS Section S-17.Slide 08This list shows the sections of the BMS that cover the Design-Build processes. These sections cover NAVFAC personnel’s roles and responsibilities for successful delivery of a Design-Build project for each process.As mentioned previously, the Standard Design-Build process (under B-1.4) has been sub-divided into an In-house process when the RFP will be developed by in-house staff and an AE process when the RFP will be developed under a contract with an AE firm. B-1.4.1 covers Standard Design-Build with In-House RFP DevelopmentB-1.4.2 covers Standard Design-Build with A/E RFP DevelopmentB-1.4.3 outlines Multiple Award Construction Contract, or MACC Design-Build (for task orders)B-1.4.4 covers processes for Single-Source Negotiated Scope, and B-1.4.5 outlines the Small Project Design-Build Decision ProcessSlide 09Here is an example of the detail in BMS:BMS outlines the role and responsibility of a NAVFAC team member, For each NAVFAC team member, it describes the effort needed and how they should do the work.The BMS conveniently provides links to resource documents and forms needed to complete the various tasks within the process steps. Some of these links provide cross-functional knowledge such as: related BMS processes covering financial management, and acquisition processes that are specific to Design-Build.Slide 10BMS includes a link to a matrix presentation of the roles and responsibilities of NAVFAC personnel in each step of the individual processes. NAVFAC personnel, in their project roles as Project Manager, Design Manager, Construction Manager or Engineering Technicians may be shown as “Leading” a task, indicated with an “L”; “Supporting” a Task, indicated with an “S”, or providing “Input”, which is indicated with an “I”.As seen in the matrix here, the project team includes the PM, CM, Contract Specialist (CS), DM, Project Technical Team, Supported Command, and others as appropriate. The Roles and Responsibilities (R&R) Matrix is provided as a companion to assist in the project delivery process. It should not be used independently of the fully developed processes as outlined in the BMS’s.These processes and associated roles and responsibilities have been developed to ensure successful project delivery and all NAVFAC personnel should be familiar with their expected responsibilities for each process in the Design-Build project approach.Slide 11Before we move on, we should review the general roles of NAVFAC personnel in the Design-Build project delivery process. The Project Manager is the one with overall responsibility for management of the project all the way through closeout. In some of the steps the PM has the lead, in others one of the other NAVFAC team members takes the “Lead” role in support of the PM.The Design Manager, or DM, manages development of the RFP, whether through an in-house team or by an A/E Contract. The DM also coordinates or leads the review effort of the Design-Build Contractor Team’s design. Like the PM, in some of the steps involved with the RFP development, the DM has the lead, in others one of the other NAVFAC technical team members takes the “Lead” role in support of the DM or the PM.The Construction Manager, or CM, shifts into the “Lead” role in support of the PM beginning at contract award through project close-out. The CM has a limited role in the development of the RFP which is the focus of BMS processes 1.4.1, .2, .3, and .4. The processes involving post award will be discussed later in this module. Good communication and cooperation between the PM, DM, CM, and all project team members throughout the lifecycle of the project is critical to a Design-Build project’s success.Slide 12 - Knowledge check #1Slide 13 - Knowledge check #1Slide 14The processes share some common components. All of these processes use the NAVFAC standard 6-part RFP format including utilizing the Uniformat Work Breakdown Structure to define the systems and materials for a design-build project. All of the processes use the same team structure, and they all use performance-based requirements to the fullest extent possible. Slide 15The main differences between the 4 processes is the content in Parts 2, 4, and 5 and the procurement process which varies with the type of contract vehicle being used. All four processes can be used with a Stand-Alone contract. The MACC process is used for task order awards and the Sole Source process is used for contracts that are procured with no competition. The Small Project Process is not tied to a specific procurement method although it rarely used with Stand Alone contracts. As we said before, it is used for small, low complexity projects and therefore is mostly used with MACC and Sole Source contracts.Slide 16This is a simple diagram that defines the phases of a project from left to right and the contract types vertically. The DB Process being describe is also shown vertically. This gives a comparison of the DB processes during the different phases of the project. This is a macro view and does not get into the details.In each step you have to develop the “scope”, budget, and schedule. The scope in this case is “what” we need to build. Developing the scope is typically done as part of the initial kick-off meeting with the full project team in a Charrette, Functional Analysis Concept Development (FACD), or Programming, meeting. This must be done for all projects. The next step is to develop the RFP and this is the step where the processes begin to differ. You learned in Module 2 the content of each of the 6 parts and although all four processes have 6 parts and all processes are performance based, the level of detail in each of those parts varies. This part of the graphic shows how much relative effort the Government has to use to create the RFP. You will see that for Stand Alone contracts the RFP must be fully developed using the Standard DB Process. This process can also be used for MACC Basic Contracts or large MACC task orders and even for large Sole Sources contracts although those are rare.For MACC task orders, you see that the MACC and Small Project processes require effort by the Government especially in Part 3 but because part of the requirements are defined in the Basic MACC contract or by a UFC not as much effort is required as the Standard Process.For Sole Source procurements, there is less effort by the Government because this method relies on the contractor to develop a portion of the design parameters.The third phase is contract procurement. This comparison shows when the contractor is expected to participate in the in the specific design process. In the Standard Process the contractor begins his concentrated design effort during the selection process. In the MACC process and Small Project Process using a MACC procurement the majority of the design effort by the contractor begins after award. In the Sole Source Process and in Small Project Process using a Sole Source procurement design starts during the Design Development phase of the project. You can also compare the level of design effort from the Contractor at contract Award. The Standard Process typically has approximately 5% to 15% design at award, the MACC and Small project have between 0% and 5%, and the Sole Source and Small Project using Sole Source the Contractor will develop enough design to be able to price the project. This will be around 15%.Slide 17The differences in the processes are what make them unique so before we describe each process in more detail, we will review what they all have in common. As we said all the NAVFAC DB Delivery Processes share a common format. Let’s review the 6 parts of a Design-Build RFP.Part one and two are typical to any contract we write:RFP Part 1 How Contractor does business with the NAVFAC and Contract ClausesRFP Part 2 How Contractor does business with NAVFAC Capital Improvements and the location, for example a specific Navy Base.Parts three, four, five and six are logical progression of the information needed to define the project requirements. Many Architects and Engineers are accustomed to converting requirements to real solutions so RFP writers often like to go ahead and make all the choices; however, in design-build it is a little different approach. Remember that the Contractor’s Designer of Record is the designer on the project, and the Designer of Record has the advantage of being able to collaborate with the entire Contractor team. Thus, in order to get the benefits of the Design-Build collaborative team, the RFP writer needs to tell the Contractor what is needed but not how to accomplish it. The RFP should not unnecessarily restrict the Contractor by specifying the exact way to construct the project. By limiting the RFP parameters to WHAT is needed, this should open up the Contractor to proposing innovative solutions.RFP Part 3 – Define the owner/facility requirements using Uniformat Structure for the engineering systems requirementsRFP Part 4 – Define Materials Systems requirements using the Uniformat Structure RFP Part 5 – Define any specific or unique Materials & Systems requirementsRFP Part 6 – Provide Specific site and existing conditions to explain Parts 3 & 4.Slide 18One of the BIGGEST advantages of Design-Build is the Design-Build team and its’ relationship. In Design-Build processes, all participants, including the Design-Build Contractor and his Designer of Record, sit with NAVFAC at the same table as fully functioning and participating members of the Design-Build Project Team. The relationship among all these parties is collaborative to enhance problem-solving, and partnering among all parties is continuous throughout the project delivery process. The operational model should be shaped like the “round table” shown here, where all parties are able to participate in the project delivery process. In this graphic all parties within the Design-Build team are shown – the Contractor-related parties are shown in green, the NAVFAC parties are indicated in blue, and the customer or end user parties are shown in red.Slide 19Now let’s look at the make-up of the NAVFAC project team on a Design-Build project. The project team includes the Project Manager, Design Manager, Construction Manager, Contract Specialist, Project Technical Team, Engineering Technicians, and others as appropriate. The Project Technical Team is comprised of NAVFAC engineers and architects (from all disciplines) who provide technical support for the project.Good communication and cooperation within these NAVFAC project team members, as well as between these team members and the Design-Build Contractor, throughout the lifecycle of the project is critical to project success.Slide 20The Standard, Design-Build Processes are covered in BMS Sections B-1.4.1 and B-1.4.2, depending on whether the RFP is developed in-house or through use of an outside A/E firm. First, it is a very versatile and flexible process, and can be used on any type of project and with any contracting procurement method although it is typically used for large projects with Standalone contracts. As we said, it uses the standard 6-part format from the NAVFAC Design-Build Master RFP website; and utilizes either the standard template or one of the Model RFP’s. The second DB Training Module explains in details the required content of the NAVFAC standard and Model RFPs. The RFP is “scalable”; for example, extra information may be needed in the Part 3 Project Program if it is a large complex project with many features; likewise, the RFP can be scaled down for very straightforward projects with fewer disciplines or trades involved.The standard RFP relies heavily on the UFCs, documents for the project design requirements.The Standard DB, MACC, and Sole Source BMS processes contain the steps required to procure the DB construction contract or task order. The Standard DB Process describes the Two-Phase approach required by the FAR for Standalone DB contracts. Keep in mind however, as we said above, this process is flexible and can be used for standalone, MACC task orders, or Sole Source Contracts. Slide 21The MACC Design-Build Process is covered in BMS Section B-1.4.3. This process can be used for traditional projects as well as for projects deemed “low risk”. “Low risk” projects include non-complex projects with a well-defined scope or prescriptive UFC Criteria such as Bachelors Quarters or Dining Halls.The MACC process is only used where there is a suitable basic MACC contract in place. Typically, basic MACCs are limited by location and task order dollar value. There are however some MACCs that are for specific facilities, for example a MACC for Bachelors Quarters or Dining Halls, RFPs for MACC Task Orders use a scaled down version of the 6-part format from the NAVFAC Design-Build Master RFP. The MACC Process steps are very similar to the standard processes with the exception of Parts 1 and 2 and the task order procurement. In MACC Contracts, the “Base” contract includes Parts 1 and 2, which are the Division 0 and Division 1 sections of the RFP, therefore on follow-on task orders, only the portions of Parts 1 and 2 that are unique to the location or project requirements are included in the task order RFP.The RFP will have a right-sized, well-defined Part 3, Project Program. RFP’s are typically developed using in-house teams within NAVFAC although an outside A/E firm may be used if specific expertise is needed or due to workload and schedule considerations. Slide 22 As mentioned in the previous slides, the MACC RFP Package is typically a scaled-down version of the standard RFP:First, parts 1 and 2 are issued with the MACC Base Contract, so the Parts 1 and 2 of the project task order RFP would only include those requirements specific to the location or project unique requirementsPart 3 may be scaled back from a standard RFP if the requirement has prescriptive UFC Criteria, is not considered a complex design, and /or if the entire MACC Contractor pool has experience with constructing the type of facility to be built.Also, if the project is a common facility type then Part 4 for this project type may also have been included in the Base Contract. This would obviously need to be confirmed before Part 4 is omitted.The next slides go into a more detail on how to edit Parts 1 and 2 for the specific location or unique requirements.Slide 23As mentioned in the prior slides, Part 1 for a MACC Contract is typically scaled back because many of the standard Division 0 sections are included in the MACC’s Base Contract. This will need to be checked to determine what will need to be added for the task order RFP. Information does not need to be repeated in each MACC task order.This slide shows the typical layout of a Part 1 section for a MACC RFP. The sections in yellow are typically in the Base Contract and those in blue will typically be customized for each project task order.Slide 24This slide shows the sections in Part 2 of a MACC RFP. Again, the Base Contract will need to be reviewed to determine what needs to be included in each task order RFP. All of these may need to be included in the task order, or most of these sections may be included in the Base Contract and Part 2 of the task order would only need to include edits to the Sections specific to the task order, such as access road or gate requirements, security access information, etcetera.Slide 25The Sole Source Design-Build Process is covered in BMS Section B-1.4.4. The Sole Source process is typically used on projects less than $4 Million. BMS section S-17.2.17 outlines the acquisition procedures for Sole Source; these thresholds change periodically so this BMS should be reviewed for the latest project value threshold.When selecting the Contractor, make sure their skills and past experience are appropriate for the project.This method allows for open and unlimited discussions with the Contractor prior to award; this is very different from the other Contracting methods in Design-Build.The RFP typically uses the traditional NAVFAC 6-part format; however, the Project Program in Part 3 can be scaled-down, because discussions are held to confirm the scope, andOne important distinction in the Sole Source process is that existing site and project information is collected and provided in the RFP; but for this process, the Government typically does not perform any additional testing. The Contractor, during the proposal phase, will be allowed to further collect information such as topographic survey or geotechnical evaluations required as necessary to develop proposal costs. After award, the Contractor will then perform testing necessary to comply with UFC requirements.Slide 26Looking at additional characteristics of the Sole Source Negotiated process.Through the open discussions and meetings that take place between the client and Contractor in the Sole Source Process, the project scope becomes more refined.If a concept design is not included in the RFP, the Contractor’s proposal will include a concept design, typically to about 15% completion of design, as well as a proposed price. These will be evaluated before award. Any features in the concept design can be discussed during negotiations prior to making any award. Much of the discussions during negotiations will center on confirmation of the scope as required by the Government and the client.Part of the process involves the Government developing a Cost Estimate independent of the Contractor. This will serve as a means of identifying those areas during negotiations that may be causing the differential in the pricing.Remember that the design concept, and the resulting contract award, were based on approximately a 15% design completion. Thus, after the award, the parties continue discussions to work through many of the details involved in refining the project specifics.Slide 27 - Knowledge check #2Slide 28 - Knowledge check #2Slide 29The last of the DB processes is the Small Project Design-Build process. This process uses a different template from the Standard DB Master RFP template. Module 4, the next module in the DB Training series will explain how to use the, Small Project Template. Like the other process, the small project process provides the steps required to develop an RFP for a small project. Why do we have a small project process and a small project template? Good question. NAVFAC does hundreds of projects that are less than $750 and the majority of those are minor renovations or repair, or they are replacement or repair for single system of non-high-tech equipment. These types of small projects are easily done as design-build projects but they don’t require a fully developed RFP or even a scaled down version. So, the small project template was developed. Of course, this process and template are not suitable for all projects. The process takes less time that the developing a full RFP required in the other 4 processes. So why can’t we use it on all projects. Because for most project, the small project template does not have the level of detail a contractor needs to design and build the facility. Remember, the small projects are minor renovations or repairs. The small project process and the associated template is a very scaled down version of the other processes. Determining whether a project is suitable is tricky. The next slide shows a tool that project teams can use to determine if a project is suitable for the Small Project Process. Lastly, the small project template can be used with a variety of contract types. The RFP template is typically used with sole source contracts like 8(a) or on MACC task orders. It is rarely if ever used in a standalone contract. Slide 30This cannot be said too many times; The Small Project Process and RFP Template is not appropriate for all projects. This table shows the Decision Guidance for use of the Small Project Design-Build Process (SPDB). This guidance is contained as a resource within the process and is also posted to the WBDG DB website. The first two columns in the table uses Categories of Work designation and a typical dollar amount to define the projects that are suitable. ECB 2018-04, Categories of Work Classification defines the work categories. Refer to this ECB for more detail on the type of projects in each Category. It is VERY IMPORTANT to understand that not all projects in Category 2 are suitable and that the size and complexity of the project are just and critical in making the determination. Category II projects are typically suitable for use of Small Project Design-Build and these include Single-design discipline projects such as roof replacements, HVAC replacements, small pump houses, utility enclosures and other similar projects. Small Project Design-Build may be suitable for projects that exceed $4 Million, by exception, when the work is straight-forward, and single trade, such as roadwork and roofing. The Small Project Design-Build Process utilizes the Small Project Template which is a simplified RFP version. As mentioned in the previous slide, there is a separate training module dedicated to the characteristics and use of the Small Project RFP Template.Slide 31With this slide we are shifting our focus to the contract procurement steps in the Design-Build processes.There are numerous contract vehicles. There are only a few that we traditionally use for the procurement of Design-Build Contracts. Standalone Contracts – which are contracts awarded after full and open competition.MACC Task Orders – which are awarded based on competition between the contract holders under the Basic MACC Contract, typically three to five contractors. Sole Source Contracts – which are award without competition to a specific contractor who is allowed by the FAR to negotiate directly with the government. Slide 32It is not surprising the most involved procurement for Design-Build Contracts is the Stand-Alone Contract. For the majority of Stand-Alone Design-Build Construction Contracts, FAR 36.3 requires the use of Two-Phase Source Selection Procedures. There are a few exceptions to this requirement. Refer to the FAR or discuss them with your Contracting Officer. The Two-Phase Source Selection process is also used to award the Basic Contract for a MACC.Two-Phase selections use the Tradeoff Analysis for the Best Value Source. The tradeoff analysis allows the Source Selection Board to consider the strengths and weaknesses of a contractor’s proposal and make a determination on what is the best value for the government. In addition to the BMS, CI has developed guidelines along with tools to explain the responsibilities CI has in procurement of a DB contract. The tools include templates for writing the Technical Evaluation report. Slide 33Let’s talk about Best Value Source Selection:There are both “Price” and “Non-Price” Factors. The Price Factor is the bid price the Contractor is submitting for design and construction of the project. The “non-price” factors are commonly referred to as the Technical Factors. CI has developed Mandatory Factors that require the Contractor to submit only that information that the government needs in order to make the selection. NAVFAC does not want to be doing in-depth plan reviews in order to select a Contractor. Keeping the proposal requirements minimal also reduces the Contractor’s expenditures and promotes participation by more Contractors. The “technical factors” to be used for evaluating the qualifications of Proposers in Phase One includes a Technical Approach, Past Performance, and Experience in the type of work required. The Technical Approach is not a detailed design solution. The Proposer is required to submit a narrative description of the design/construction team’s vision for the facility and their organizational structure. The Phase Two evaluation factors include Safety, a Technical Solution, Energy and Sustainably Design approach, and Small Business Utilization. The Proposer’s safety record could be evaluated in Phase I depending on the type of work and location. Details on the Standard Factors and guidelines on how to use them can be found on the CIBL Source Selection Portal page. Slide 34The award of a MACC task order requires only a single phase. MACC contracts can use several different evaluation methods.The Source Selection Board can use a Tradeoff Analysis where the Technical Evaluation teams evaluates the strengths and weaknesses of each technical factor. The Board can use the Best Value Low Price Technically Acceptable or LPTA method. LPTA cannot be used for procurement of stand-alone two-phase DB contracts or for the procurement of a basic MACC contract. In LPTA, the technical evaluation board determines if the contractor’s proposal is acceptable. The task order is then awarded to the contractor within the acceptable range that has proposed the lowest price. LPTA should only be used for DB procurements that have a high level of prescriptive requirements such as facilities where the UFC dictates the majority of the design, like a Child Develop Center. The third method, Price Only source selection should be the first consideration for non-complex MACC Task Orders under $25M. This is only used when there is no need for a technical review. This threshold was raised from $10M to $25 M in the 2017 NDAA. MACC Task orders also have Mandatory Technical Factors which as we explained on the previous slide are so the Contractor is required to submit only that information that the government needs in order to make the selection.Slide 35BMS section S-17.2.17 outlines the acquisition procedures for Sole Source. This Selection Process is more informal than other processes, however selecting the right Contractor is still critical in order to have a successful design-build project. The first thing to do is to coordinate with the Small Business SpecialistOne of the sources for information to identify potential Contractors is the Construction Contractor Register, or the “CCR”; this is a Small Business Administration web-enabled tool that can be searched to locate the Contractors in a particular area; another good source of information is the ROICC office at the Bases in the area – they typically know who the good Contractors are that have worked on their projects; this list of potential Contractors should be maintained somewhere so that it can be referenced for future projects also.To ensure project success it is critical to match the right Contractor with the project. One of the ways to do that is with a capability’s presentation. A Contractor can be brought in and asked what their experience is on design-build, what is their experience on a particular type of project, and who they might collaborate with on a particular type of project. You need to be careful not to identify the specific project when having these discussions. You are simply trying to get an understanding of their capabilities to determine if they are a good fit for the project. This would involve them having the right people, right experience, and right subs to be able to deliver a successful project.The next thing is to validate past performance by first checking the CPARS system for Contractor evaluations. The CPARS system may not have a lot of information on these smaller Contractors, but you also can talk to the ROICC Office where they might have performed projects for previously. This is an informal process but enables NAVFAC to perform due diligence on identifying the right Contractor.The typical considerations on selecting the right Contractor include the past performance of the firm, past experience of their key personnel, and their management approach to projects – one thing to focus on here is that they emphasize working with an integrated and collaborative team, including the design team members.Slide 36In the last few slides, we have discussed the procurement methods used to procure a DB Construction Contract, the remaining slides in this module relate the steps after the contract has been awarded. There are unique processes for this Post Award effort. This table shows the Post-award topics and the sub-sections of BMS section B-1.4.6 that cover these processes specifically for Design-Build. These sections cover NAVFAC personnel’s roles and responsibilities during the post-award design phase, construction phase and all aspects for successful delivery of a Design-Build project.As we mentioned at the beginning of this modules, the NAVFAC Construction manager training series provides additional details on the post award management of a DB construction contract in modules: NAVFAC CI Design-Build Post Award Process and NAVFAC CI (PAK).Slide 37The Post Award Kickoff Meeting Project Kick-off (PAK), after award, sets the stage for project success…The Post-award kick-off meeting is a critical component in that it sets the stage for a truly collaborative teaming arrangement and allows the project team to establish the overall schedule, as well as the design schedule, and also to identify all design submittal packages and the procedures that will be used during the post-award design phase.The Government Technical Team has several roles in the project. First, they are the client’s Supported Commanders technical representative and they provide input to the Contractor’s team. The technical team members often have lessons learned on a particular facility type or for work in a certain region of the country, so they can bring this input to the Contractor team.Second, the Government’s technical team is confirming that the Contractor’s proposed design conforms with the contract; this means that the Government reviewers should be reviewing the design against both the requirements outlined in the Design-Build RFP and the Contractor’s proposal that was used as the basis for the Contract award. They should not assume that this facility type has the same needs as the last project they worked on for this same facility type; again, they must review the Contractor’s design against the requirements spelled out in the RFP and the Contractor’s proposal that was the basis for award.Lastly, the technical team must ensure that any requirements included in the RFP with respect to the design process are being met. Examples of these may include life cycle cost analysis of the building or MEP systems, and also BIM requirements.Slide 38This list shows the general roles of key NAVFAC personnel in the post-award phase. As you can see, the roles of the CM and the PM shift after the Contract award to the Design-Build Contractor. While the PM is still the one with overall responsibility for the project all the way through closeout, at project award, the CM shifts into the “Lead” role managing the construction contract. The post award design management is led by the Design Manager in support of the CM.We can’t say this too much, good communication and cooperation between the Project Manager, Design Manager, Construction Manager, and all project team members throughout the lifecycle of the project is critical to a Design-Build project’s success. The BMS sub-sections within section B-1.4.6, as listed on the prior slide, cover these post-award processes in great detail.Slide 39Similar to the Roles and Responsibilities Matrix for Pre-Award Processes, the matrix for BMS B-1.4.6 covers the roles and responsibilities of NAVFAC personnel in the Post-award processes that are outlined. As a reminder, these processes and associated roles and responsibilities have been developed to ensure successful project delivery and all NAVFAC personnel should be familiar with their expected responsibilities for each process in the Design-Build project approach.Slide 40Slide 41Slide 42Slide 43In this training module we learned about:The Common Objectives and the differences of the 4 NAVFAC Design-Build ProcessesThe NAVFAC Business Management System or BMSThe NAVFAC personnel Roles and Responsibilities as outlined in the BMSCharacteristics of the 4 NAVFAC Design-Build Processes, andThe Post-Award ProcessesSlide 44As we wrap-up today, just a reminder that there are 5 Design-Build training modules in this series. These include:Introduction to Design-BuildStandard RFP TemplateDesign-Build ProcessesSmall Project Design-Build, and Design-Build Master Management Training for Criteria ManagersI encourage you to view all of the modules. This will give you an in-depth understanding of the entire NAVFAC Design-Build Process.Slide 45I hope this training module provided you with a greater understanding of the NAVFAC Design-Build Processes. NAVFAC employees can access the BMS processes from the NAVFAC Portal intranet system under the “eTools”. Should you have any questions please contact the name shown on the screen. Thank you for your time. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download