WBDG | WBDG - Whole Building Design Guide



Standard Design-Build Master RFPSlide 1 - Cover SlideWelcome to the Standard Design-Build Master RFP Training Module which is the second 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 DB Teams accomplish their jobsgoals.Slide 2 (inserted new slide)The training modules provide Project Managers and Designers with the details for the DB processes, an explanation of the level of design required, the unique post-award processes as well asand their 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 Design-Build Master 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 also 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 3This course is approximately 50 minutes long.There are Knowledge Checks throughout the course to test your comprehension.(Added a screen shot to slide to better illustrate the navigation)Each page of this course contains a navigation bar across the bottom.The course will not move to the next page automatically – Use these buttons to move within the course.Click the play or pause button to play or pause the course.Click the back button to review the previous pageClick the forward button to go 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 contents. Slide 4These are the topics and learning objectives for this training module:Finding the DB Master Website and navigating itHow to customize the RFP for a specific projectThe layout of the 6-part RFPDescription of the components of each part of the RFPSlide 5The NAVFAC Design-Build Master (NDBM) is an accumulationconsists of documents and tools on the “NAVFAC Design-Build Request for Proposal Website. The Website can be accessed through the Whole Building Design Guide Website at “”Upon landing on the main website, click on the link to “Federal Facility Criteria”Then click on the link to “Navy – NAVFAC”.Slide 6Scroll down to Specifications & Criteria and select “Design-Build Request for Proposal”. Then sSelect “Standard Template” from the list of RFP templates.Slide 7 The Standard template is a collection ofcomposed of individual documents files that can be downloaded and edited for your project.s. The documents files are available in Adobe Acrobat (PDF), Microsoft?Word. , or for Part 2 specs only, in SpecsIntact. There are also excel files associated with Part 3. The documents can be downloaded together as a zipped file or individually. In order to ensure you obtain a complete master, including the excel files, you must download the zip file.Slide 8However, project teams creating an RFP will want to There is the capability to download a “customizable set” of the standard template documents. For example, you couldUsing this tool you can add a company name, work order name, project number, or project name to the headers on the RFP Word documents. ?To go to the customization page click the link “Customizable set”, on the standard template webpage.Slide 9It is VERY IMPORTANT that the information entered on this page is correct and complete. Take the time to gather verify the information needed fromprovided with the NAVFAC Project Manager. Even if the information is stated in the statement of work, run it by the NAVFAC PM for confirmation. This part of the processInitiating this customized set will create headers for all the documents being downloaded. If the information is incorrect or needs to be changed after this part of the processthe initial download, each document file will need to be individually opened, and the headers changed and saved.Slide 10Now that you that you know how to get the documents that make up the NAVFAC Design-Build RFPs, you next need to know how they ar RFP is e organized and what is’s in themeach part.Let’s start with organization. NAVFAC Design-Build RFPs are made up of 6-parts. Part 1 contains the contracting documents and is prepared by the Contracting Officer.Part 2 are the General Requirements also known as “Division 1”Part 3 is the functional Project Program explaining what we want to design and build. Part 4 includes Performance Technical Specifications describing the quality level required.Part 5 includes required Prescriptive Specifications, i.e. Unified Facility Guide Specs (UFGS). Part 6 contains attachments that are needed to support the final design effort. The documents in the DB templates on the website are arranged into Parts 1 through 4 so that the RFP preparer will know what goes where. Part 5 documents are found ? and Part 6 attachments are unique to each project. Slide 11Let’s go into a little more detail on each one of the RFP parts.Part 1 includes the Proposal Forms, and other submittal documents, and general contractual terms and clauses that are traditionally included in CSI Division 0. and are prepared by the Contracting Officer.Part 2 is where you will find the documents that address the administrative, safety, design and construction process, and project closeout instructions for the project. These are the CSI Division 1 specifications.Part 3 is the functional Project Program Statement that says, “This is what we want to receive when the project is completed.” It doesn’t tell the DB Contractor “how” to get there, just what we want to provide to our end user. Contained in the Project Program are project descriptions, room requirements, and Engineering Systems Requirements (ESRs). Part 4 includes Performance Technical Specifications (PTS) which describe the quality level and the standards that must be followed in order to achieve the quality level required. The ESRs and PTSs will be explained on the next slide. Part 5 is where any necessary Prescriptive Specifications should bemust be included in the RFP. This section should be utilized sparingly and judiciously so that we do not dictate the solution, except where it is deemed appropriate due to thenecessary to meet the specific “Navy” or “Marine Corps” requirements and criteriawhich may not be typically designed or constructed in non-DOD facilities.Part 6 is where you put the related information that supports the project, such as surveys, studies, soils reports, environmental documentation, as-builts, etc. Care must be taken to ensure that Part 6 is not used as a place to put “prescriptive” information which cannot be included in Parts 3, 4 or 5. Including prescriptive information in Part 6 circumvents the entire reason for having a 6 Part format which is to facilitate a performance requirement and is counterproductive to the DB Process.Slide 12The main criteria documents within a DB RFP are UFCs, the UFGS’s, ESRs, and the PTS’s. UFCs - Unified Facility Criteria are documents developed to give the architects and engineers the design requirements. For facility projects there are Core UFCs that provide specific criteria for a discipline or system, for example Architecture or Interior Electrical Systems. In addition to the Core UFCs there are facility specific UFCs, for example, Dining facilities.The majority of the UFC’s are unified criteria that apply to all DOD Components. Unified Facility Criteria applies to both Design-Build and Design-Bid-Build. These UFCs are resident on the UFC Webpage of the Whole Building Design Guide Website. The next type of criteria documents are Unified Facility Guide Specifications (UFGS). Most of you recognize this acronym – these are the Prescriptive Guide Specifications that we have used for years in Design-Bid-Build. We utilize UFGS in Part 5 of the RFP in areas where we want to be prescriptive. The criteria that is unique to design-build are Engineering System Requirements, ESRs, and Performance Technical Specifications, PTSs. The ESRs are part of the Project Program in Part 3 of the RFP. ESR’s identify the Engineering engineering Choices choices in the Basis of Design Information; another way to look at the ESR is that they outline the scope parameters for the projectThe PTS’s are included in Part 4 of the RFP. The PTS outline the Quality and Performance of the Materials and Systems and set a minimum standard for the materials and systems. So you make your engineering material and systems choice in the ESRs and describe the minimum quality requirements of those materials and systems in the PTS. Slide 13The NAVFAC DB RFP uses both Uniformat and Masterformat to organize the requirements. MasterFormat is a specification writing standard. It is organized around major divisions of specification subjects. Most Architects and /Engineers are familiar with their MasterFormat 16 Divisions. Masterformat sections (titles and numbering) is are organized around construction products and activities, e.g. Brick, Paint, etc.The UFGS currently go up to Division 48 Electrical Power Generation.Uniformat is a classification system for building elements and is organized around the major systems of a facility, e.g. Foundations, Exterior Enclosures. As you can see at the bottom of slide, Uniformat classification includes all of the components that make up an exterior enclosure. Both have their advantages depending on the type of information we are dealing with. For prescriptive requirements, Masterformat has the advantage. For performance requirements, Uniformat is better suited.Slide 14Within the design-build contract we havethere are two three different types of organization formats and four different kinds of criteria documents. So where does all of this fit into a typical Design-Build Contract?. The Contractual Requirements are created by the Contract Specialist and found in RFP PART 1. These are typically organized by masterformat and contains the proposal forms contractual documents.The General Requirements are found in RFP PART 2 which also use the mMasterformat. These are how the contractor does business with NAVFAC and the Installation. The Owners Requirements are only found in Part 3 which is the Project Program. The Project Program Chapters 1 to 5 are in paragraph format. uses uniformat. Part 3 also contains design requirements.The Design requirements are included in Part 3 Chapter 6 and Part 4. Part 3 Chapter 6 includes the ESRs that describe the engineering choices allowed (the what). Like Part 3Chapter 6, Part 4 uses uniformatUniformat. Part 4 contains the Performance Technical Specification (PTS) which tell the designer minimum standards for the materials and systems (the how). The last Component is the Materials and Systems Requirements. The Materials and Systems Requirements are found both in Part 4 and Part 5. Unlike Part 4, Part 5 uses Masterformat. Part 5 contains the UFGS prescriptive specifications, which are in MasterFormat. Parts 3, 4, and 5 all reference UFCs. Slide 15There is significant interdependence between the UFCs, and the ESRs and the PTSs.The ESR and PTS Sections were created to align with the UFC that describes the design.The UFCs are referenced and cannot be edited. The ESRs and PTSs are edited based on the scope of the facility project. Another way to look at this is:The UFC controls the design requirements of the DB project. The ESRs control the project specific Design Choices and Materials and Systems choices. And the PTS controls the Materials and Systems Quality and Performance. Finally, it is important to understand that when you use a specific PTS you must reference the associated UFC. Additionally, if you use an ESR in Part 3 PTS in Part 4 you must use the associated ESR PTS in Part 34.Slides 16 & 17 (voice) Knowledge CheckSlide 178Now that you have the basics of where to find the DB RFP templates and how the six part format is arranged. It’s time to go into detail on each of the parts. Before we start, let’s look at the home page of the NAVFAC DB Master on the Whole Building Design Guide.There is a link, preparing the RFP, which describes the layout of each one of the parts. The information on the site is a good reference material while the DB RFP is being developed. The link brings us a page outlining the 6 parts and each part has a link that describes the layout in detail. Slide 189Part 1 is created using the Standard Procurement System by the Contract Specialist. The documents in Part 1 are not available on the website. One the website, Part 1 is provided for information only as an example, so you can see what sections are included in Part 1. These sections include the legal clauses as well as instructions on how to develop the Contractor’s proposal. There are separate versions for projects in the United States as opposed to projects in foreign countries.Slide 1920The Order of Precedence clause included in Part 1 is a contractual requirement that must be understood both during the development of the RFP and especially in the post award contract administration. This important clause requirement determines the precedence in case of a conflict within the contract documents. This was previously an NFAS clause, but now theThe NFAS clause is contained in Part 1. Because of its importance, itOrder of Precedence is only included in full text in Part 2, 01 33 10.05 20 Design Submittal procedureProcedures. The contract consists of the solicitation, the approved proposal, and the DB contractor’s final design. If a conflict arises or there is inconsistency within the contract, the Order of Precedence will determine if a change or modification to the contract is required.There are two three parts to the Order of Precedence:Part “a” refers to the order of precedence when there is a conflict between the Contractor’s final design, the Contractor’s proposal, and the RFP Solicitation.Part “b” refers to the order of precedence when the is a conflict within the 6-part RFP. If conflicts occur, the Order of Precedence will be used to determine what part of the RFP is most important.Part “c” clarifies that within Part 3 Section 5.0 Room Requirements provides detailed requirements on a room by room basis that are in addition to the 6.0 ESR section.In preparing the RFP, the design team must strive to avoid conflicts within the various Parts of the RFP. Slide 201Parts 2-6 are prepared by the Technical Team using the Standard Template documents. Part 2 contains Division 1 specification sections covering administrative requirements. Within the individual specifications, bracketed sections are used when project requirements are optional.Many of the specifications in Part 2 are included in Design-Bid-Build contracts. , wWhile others have been tailored specifically to Design-Build. An “05” in the Level 4 of MasterFormat numbering indicates the specification is tailored for “Design-Build”. A “20” in the Level 5 indicates the specification is tailored for the Navy.In the next few slides, we will discuss some of the specific DB specifications.Slide 212Post Award Meetings are defined in RFP Part 2 Section 01 31 19.05 20. Remember the “.05” means the specification is for DB and the “20” means it is tailored for a NAVFAC contract. A DB contract requires design meetings to finalize the design as well as the more traditional post award construction meetings. Post Award Meetings are defined in RFP Part 2. Section 01 31 19.05 20. This section allows the construction and design meetings to be combined. The initial Post Award Kickoff meeting with the entire project team, including NAVFAC, the Client, and Contractor, focuses on initial contract start-up procedures, schedule for design, and final design conceptsThe first meeting is the Post Award Kick-off Meeting, called the “PAK”, which is made up of 4 elements: Contract Administration, Concept Design Presentation/Design Development or Concept Design Workshop (CDW), Partnering, and Scheduling. These four elements may be addressed in a single multi-day meeting or depending on the complexity of the contract requirements, the elements can be addressed in separate meetings. Most often the element that requires additional time and is scheduled separately is the CDW for contracts where the technical design solution was not provided as a part of the proposal or the design solution needs further refinement. After the PAK Meeting there are Design QA Reviews. The Contractor is to meeconducts review meetingst with the government after each Design Submittal. There are also construction related meetings concentrated on Contractor QualityContractor Quality Control and Production, Safety, and, Facility turnover planning meetings (NAVFAC Red Zone ). Depending on the project, an eOMSI Meeting and a Sustainability Documentation Progress Meeting may be required.Slide 223 Post award submittal approval is “tricky” with design build because not all submittals with a “G” designation are indicated for Government approval, with a “G” designation.. For Part 2 “General Requirements” the Government approves items identified with a “G”. This is similar to Invitation for Bid (IFB) contracts where the Government approves items such as insurance, bonds, payments, safety, and QC plans.In Parts 4 and 5, the contractor’s Designer of Record (DOR) approves items identified in Part 4 and “G” items in Part 5. The contractor’s DQC (design quality control) manager certifies all design submittals. The overall QC manager also certifies the design submittal. The QC manager certifies all other submittals. By default in Parts 4 and 5, there are no systems and material the government approves. However, specific section 01 33 00.05 20, Construction submittals Submittals can be modified to require government approval. For example, electrical has a list recommending Government approval of specific systems and materials such as pad mounted transformers, overhead transmission & distribution, and electrical substations. Any systems or materials requiring Government approval must be written into this section. Sections can also be modified to require the contractor to provide surveillance copies to the ernment. This is also included in the Construction Submittals section. If any of the electrical items listed do not require Government approval, the recommendation is to receive surveillance copies. Examples of other submittals that are suited for surveillance include Fire Protection systems, Geotechnical reports, performance verification and acceptance testing and sustainable reporting. Slide 234The Design Submittal Procedures specification describes the design submittal format requirements. The formats described include a Basis of Design Format, Design Calculation Format, Drawing & Specification Format, Sustainable Design Requirements, Design Submittal Packages, Variations, and DD1354 requirements. The durations for the Government Design Reviews are also included in this section. The durations are very important. Completing the QA review and returning the submittal with review comments to the DB Contractor within the time frame specified is very important. Delays by the government that affect the schedule can constitute a contract modification. Review comments must be made in a timely manner and in compliance with the contract schedule.An important item to note is that the “Government Design Review Duration” is not identified for the final design submittal. The contractor can begin construction and ordering materials after DOR seals and signs documents. Review of the final design in a timely manner is critical. The government must review this submittal as quickly as possible. Comments that affect the design and ongoing construction must be clearly an contract requirement. At this point a change in design “choices” is not practical because any change could impact the construction progress. Discuss final design review at the PAK and set the expectations for all project team members. Slide 245Building Information Modeling is required on Design-Build projects when:The project is new construction with value greater than or equal to $1 Million, andMajor renovation projects that exceed 50% of Plant Replacement Value or with project value greater than or equal to $3 Million.The BIM submittal requirements are defined in the Design Submittal Procedures section and in FC 1-300-09N. The BIM submittal requirements include:A BIM Execution PlanDesign ModelVisual Review ReportClash Detection Report, and The Record ModelSlide 256 (may need to come back to this slide)By default there are two design submittals for each submittal packageproject: design development and final. The requirements can be edited to add additional submittals for project specific requirements. Critical Path have only one required submittal - a final design submittal. Critical Path submittals are discussed on the next slide.The Contractor is allowed to “tailor” the design submittals. Drawings may be similar to shop drawings and brand names with model numbers should be used to the maximum extent possible. The drawings must still conform to NAVFAC Standards as required in FC 1-300-09N, such as sheet size, title block, AUTOCAD layering, etc. For the specifications the Contractor may submit manufacturer data and catalog cuts, in a CSI format, in lieu of prescriptive specificationsin addition to UFGS tailored to the project requirement. UFGS are required also, to ensure that the selected products meet government established specifications. For example, if the Contractor submits catalog cuts for the “Standing Seam Roof”, and the documents have enough information to verify that it meets the RFP requirements, the Contractor still must provide a complete UFGS specification for the RFP requirement. doesn’t have to provide specifications for the roof material. Specifications are only required for items the Contractor hasn’t already selected or if specifically required by the contract in Part 4. For example, USGS 16360N. The specifications can be prepared using MS Word or SPECSTINTACT. Documents should not be as detailed as for Invitation for Bid (IFB) contracts. Intent is to have design documents that are “Buildable” and not “Biddable”. Slide 267One advantage of Design-Build is the ability for a contractor to “fast track” .”construction elements that are on the critical path. Fast track is starting the constructionearly purchasing or construction of critical elements prior to a complete design. “Fast Track” is the industry term. “Critical Path” is the NAVFAC term used in Part 2. This that allows the Contractor to start work earlier on certain elements of the project concurrent with design development.The term “Critical Path” was adopted because the construction element (also known as the definable feature of work) must be on the project schedule’s critical path. This restriction is not intended to limit the contractor, but is needed to not burden the government team with numerous submittals if the project schedule would not be impacted.Critical path submittals must be indicated on the Network Analysis Schedule. In addition, the Schedule of Prices or Earned Value Report must include detailed design and construction line items for each fast-tracked/ critical path phase(s), submitted to and accepted by the Contracting Officer during the Post Award Kickoff Meetings and confirmed prior to starting construction work in that phase.Critical path submittals include the same requirements as a final design submittal and they must be signed and sealed by the DOR. Slide 278As we discussed previously, the Order of Precedence clause is included in Part 1. It is also included in full text in PSpec 01 33 10.05 20 Design Submittal Procedures.art 2 because of the importance of this clause. This clause provides the order of precedence when there is ais intended to resolve conflict between the Contractor’s final design, the Contractor’s proposal, and the RFP Solicitation. In addition, the clause this provides the order of precedence when there is a conflict within the 6-part RFP or between specific room requirements and more general requirements in Part 3 Project Program. Let’s review a few case studies involving the first part of the clause because the intent is not as well understood as the second part. The clause states when there are discrepancies between the solicitation, Proposal, and Final Design, the clause states precedence is given to any portions of the “accepted” proposal or final design that exceed the requirements of the solicitation.Case 1: Example: The sSolicitation specifies Type V construction including, stud walls. The a Accepted Proposal shows Type II construction using, CMU walls. Since CMU wallthe accepted proposal with CMU walls exceeds the solicitation requirements, the CMU walls in the proposal govern.Case 2: The “Accepted Proposal” shows stainless steel handrails. The “Final Design” shows galvanized handrails. Since the stainless steel handrails exceed the “Final Design” galvanized, stainless steel shall govern and must be provided.Case 3: The “Final Design” shows stainless steel handrails. The “Accepted Proposal” shows galvanized handrails. Since the stainless steel handrails exceed the “Accepted Proposal” galvanized handrails, stainless steel handrails walls will govern.Slide 289This Spec section 01 45 00.05 20 also defines the requirements of the Contractors Design and Construction Quality Control Program. At a minimum, at least two Quality Control Managers are required as part of the Quality Control Organization. This section defines the responsibilities and qualifications required of the These two are the Quality Control (QC) Manager & and Design Quality Control (DQC) Manager . Qualifications and responsibilities of the QC Manager and DQC Manager as well as any Quality Control Specialists requiredare provided. This section would also include anycoordinates with any Commissioning requirements, which are detailed in 01 91 00.15 Total Building Commissioning . The Quality Control QC Manager administers and maintains the Quality Control Program in accordance with the approved Quality Control Plan.The Design Quality Control (DQC) Manager is subordinate to the QC Manager. The DQC manager must ensures that the design is in conformance with the RFP and also validates and coordinates testing and Government training requirements. Design and Construction Quality Control Plans are required. The contractor must provide a project specific Design Quality Control (DQC Plan ) and Construction Quality Control (CQC) plan, for review and approval. The Contractor cannot perform any design until the DQC Plan is approved and no construction until the CQC Plan is approved.Slide 2930UFC 1-200-01 DoD Building Code (previously named General Building Requirements), with Change 1 provides general building requirements establishes the use of consensus building codes and standards, identifies key core UFC, and identifies unique military criteria. In compliance with the UFC, designs mustshall use the International Building Code (IBC) as the building code for the Department of Defense, except as modified within the UFC 1-200-01 and referenced documents. During the late 1970’s and early 1980’s, a House of Representatives subcommittee looked into ways to reduce the number of structural failures occurring to public facilities. The subcommittee recommended that building codes incorporate mandatory requirements for on-site inspection by structural engineers, and other qualified individuals, during the construction of critical structural components on public facilities. Chapter 17 of the IBC includes fairly specific inspection requirements for different structural building systems, including steel construction, concrete construction, Masonrymasonry, Woodwood, Soil soil considerations, Pile pile and pier foundations, and also for Sprayed sprayed on Fire fire proofing, EIFS, and smoke control systems. UFC 3-301-01 Structural Engineering and UFC 3-310-04 Seismic Design for are referenced in the DoD Building Code for any modifications to these structural special inspection requirements.The requirements in the IBC include the frequency of inspection as well as industry and code references related to the individual inspection requirements. The Contractors Quality Control Plan must include a “Schedule of Special Inspections” prepared by the DOR describing a complete list of materials and work requiring special inspections” and a list of individuals conducting the special inspections.The specific qualifications and certification requirements for the inspectors and testing labs are described in more detail in ASTM E 329, entitled “Standard Specification for Agencies Engaged in Construction Inspection and/or Testing”.this specification.For structures where the structural system is more critical; for exampleexample, buildings in a region of higher seismic activity, or where high winds could occur; there are additional requirements in this section and the IBC.Slide 301The Facilities Electronic Operation & Maintenance Support Information (eOMSI) specification identifies the operation & maintenance support information requirements including any reference information required by UFGS 01 78 23, Operation & Maintenance Data. This section is used in all projects. For larger projects, the contractor Contractor will utilize the Building Information Modelling (BIM) to create the Facility Data Matrix and Workbook.The specification should be scaled down for Small Projects. Adding tech note for what submittals are required when only OMSI Part III is required. We always will get Product Data as a minimum.Depending on the project, per the Design and Construction Quality Control specification section, the DQC may be required to provide government personnel the necessary comprehensive training to operate the facility. Training would be for items such as the HVAC systems. Submittal requirements are identified: Preliminary is due at 50% construction complete; 100% is submitted 30 days prior to BOD, and Final 90 days after BOD. These dates are important because OMSI submittals must be available for the personnel to maintain and operate the facility after occupancy.Slide 312This guide specification covers Total Building Commissioning requirements for new construction and major renovations. Ensure any other technical specifications that reference commissioning are coordinated with this specification section.Coordination with any Third Party Certification for sustainability and the QC program is also required.Slide 323This guide specification covers the requirements for providing sustainability documentation for Guiding Principles Validation (GPV), and Third Party Certification (TPC). Some projects will require both GPV and TPC for sustainability if required by the scope of work.Guiding Principles Validation (GPV) is equivalent to meeting the requirements of UFC 1-200-02 "HIGH PERFORMANCE AND SUSTANINABLE BUILDING REQUIREMENTS." All projects must meet the requirements of UFC 1-200-02.This section helps to identify those “S” submittals that will be required to include in the Sustainability Notebook as provided at project closeout.A preliminary HPSB Checklist must be included as Attachment 1 at the end of the UFGS.Slide 34 & 35Knowledge CheckSlide 36Part 3 provides the functional project requirements. This is the heart of the RFP and describes what the user of the facility needs and what NAVFAC wants to receive in the completed project. RFP Part 3 is divided into six chapters. RFP Part 3, Chapters 1-3 are in paragraph format describing design and site requirements; Chapters 4 and 5 are mostly tabular descriptions of the building and each room or space within the building; and Chapter 6 describes the engineering choices that are made by the RFP editor. Chapter 6 utilizes the Uniformat/ Work breakdown Structure to allow systems descriptions of the facility and parallel the information structure and requirements of RFP Part 4.The majority of the information for this PART is obtained during the FACD/Functional Analysis Concept Development (FACD) charettecharrette. The chapters are set-up such that more detailed requirements are stated as you go from Chapter 1 to Chapter 6. For example, Chapter 1 may identify a 10,000 square feet facility. Chapter 4, Building Requirements would identify the spaces/rooms for the 10,000 square foot facility. Chapter 65, Engineering SystemsRoom Requirements would identifiesy requirements like the temperature and lighting requirements for the spaces/rooms. Chapter 6 Engineering Systems Requirements provides system and product selection requirements.Slide 37The information in Chapters 1 & is provided in a “Paragraph” format. These chapters address items such as the user’s mission, staffing, hours of operation, historic and economic considerations, future expansion, etc. A lot of the data can be obtained from the 1391 document. Slide 38The information in Chapter 3, Site Analysis is also is provided in “Paragraph” format. In addition, the chapter contains graphics and photos. This chapter addresses items such as traffic circulation, utilities, wetlands, site drainage, topography, demolition, AT/FPAnti-terrorism, ADAAccessibility, etc.and any other site requirements.Slide 39Part 3, Chapter 4, Building Requirements information is provided in “Paragraph” and “Table” formats. This chapter addresses spaces required for the facility such as conference rooms, offices, toilets, SCIF’s, equipment rooms, etc. Any special dimensions such as 10 foot ceiling heights for certain spaces or rooms would also be covered in this chapter. This chapter and the next chapter, Chapter 5, are only used when the size of the rooms must be identified. For example these two chapters will generally not be used for airfield, wharfs, piers, or utility projects.For buildings where the size of the room is essential, it is EXTREMELY IMPORTANT that ALL rooms are identified (including utility rooms) and the Net to Gross Factor is verified. The Net to Gross Factors used by Planning Departments are around 1.10 or 1.15 and are most often inadequate. To validate the Net to Gross Factor a conceptual floor plan should be created. Mechanical, Electrical, and Communications rooms must be identified, and sufficient space must be allowed. Developing the conceptual floor plan is the only way to provide “proof of concept” and an accurate Net to Gross Factor. The conceptual floor does not need to be included in the RFP. The DD1391 is the initial source of this space program information and the RFP requirements of this chapter must be consistent with the DD1391.Slide 40Part 3, Chapter 5, Room Requirements information is provided in “Table” format. This chapter addresses detailed room requirements such as wall, floor, & ceiling finishes, acoustics, special lighting, power requirements, communication (telephone and computer) requirements, doors, windows, cabinets, etc and other features by the corresponding Uniformat Section reference. Space characteristics including functional adjacencies, special dimensions, acoustics, access, occupants, and any other special requirements are also included. Again, it is EXTREMELY IMPORTANT that all rooms be identified to ensure that adequate spaces are provided.Any Room Requirements not identified in the RFP could become the subject of a change order during the Post Award phase. A Concept Floor Plan is HIGHLY RECOMMENDED to ensure “proof of concept”.Slide 41Part 3, Chapter 6, provides the Engineering Systems Requirements information in “Paragraph” format using the Uniformat classification system for building elements which is organized around the major systems of a facility. This chapter addresses in general terms the facility elements that correspond to the PTSs in Part 4. To take full advantage of the DB contract, it is IMPORTANT to avoid making choices in Part 3 that limit the contractor’s ability to select alternative systems. Only limit choices if a single solution is mandated by the project or no other alternative will work. In developing this part of the Project Program, the designers must avoid duplication with Part 4,. As as well as avoiding duplication between this chapter and Chapter 5 “Room Requirements”. Duplication of information can lead to potential conflicts. These conflicts are not always adequately resolved using the Order of Precedence.Slide 42This graphic indicates the PTS and ESR sections that could be used. These are identified using the Uniformat Level 2 numbering. The colors you see relate to the different Architectural/Engineering Disciplines. Structural uses – BrownArchitectural - GreenMechanical – BlueFire Protection – OrangeElectrical – YellowEnvironmental – Bright GreenCivil – Teal GreenPlease notice that several PTS/ESR sections are all one color but many PTS sections have more than one color This is because most PTS/ESR section have more than one discipline involved.Because the PTS are written around systems, they are not solely related to one Architectural/Engineering DisciplineThe top cover sheet of these PTS sections indicates the typical lead. The back-up color represents the other disciplines that routinely have input into the PTS Section.For sections that have other disciplines involved, the lead becomes a coordinator and obtains information from other disciplinesYour organization may vary the lead for these PTS/ESR sections depending on resourcesPlease notice that there is a Z10. This PTS Section needs to go into every project. This section holds all of the Repetitive requirements from all of the other PTS Sections.Slide 43Part 4 of the RFP is the Performance Technical Specifications – these describe the performance and level of quality of the materials and systems of the facility. Part 4 utilizes the Uniformat/ Work Breakdown Structure. As we said on the previous slide, the PTSs corresponds to Part 3, Chapter 6, Engineering Systems via UNIFORMAT numbering. If there are 16 Engineering Systems identified in Part 3 Chapter 6, then the corresponding 16 PTSs must be specified in Part 4. to allow systems performance requirements to be used.Slide 44What is a Performance Technical Specification? A Performance Technical SpecificatioPTSns allows the DB Contractor to use their expertise and creativity to develop their most cost-effective solution. The editor needs to state the required end results without stating the method for achieving the end result. The PTS identifies design criteria, verification requirements, and performance and quality requirements of products. For examples, the PTS may specify that a window must meet AT/FPAnti-Terrorism requirements, 175 mph wind load, not leak, and last at least 15 years. For verification, you would require in the PTS for the Contractor to submit structural calculations showing that window framing and anchoring system meets AT/FPAnti-Terrorism requremetns, 175 mph wind load, and require manufacturer’s catalog cuts and test reports that it will not leak at 175 mph wind. Manufacturer’s warranty would also be required for the 15 year warranty. Unlike Unified Facilities Government Guide Specifications (UFGS), the Performance Technical Specifications were developed for the NAVFAC Design-Build RFP. Currently, they are not unified documents although there are on-going efforts by Tri-Service to unify the DB documents. Slide 45Lets review the layout of a PTS. This is a partial Table of Contents for the HVAC PTS. This Table of Contents is typical for other PTS sections. If this was the A10 FOUNDATION PTS, then paragraph 1.2 would be Structural Design Guidance instead of Mechanical Design Guidance. The General Section covers the “design and compliance criteria” and the “design and construction submittal requirements.” The remainder of the specification covers the “Performance & Quality” of the products, materials, and equipment for the project. Above the line is all the Performance Verification and Acceptance Testing in one location.Slide 46This is the Government “Design Criteria” you would find in the D30 HVAC PTS. If this was the A10 FOUNDATION PTS, you would see structural engineering UFCs and UFGSs identified. Throughout the PTS there would also be references to industry standards such as International Mechanical Code, NFPA, ASME, ASTM, etc.Slide 47These are the typical statements for “Design & Construction” submittals you would see in a PTS. The only difference would be for “Design Submittals” you would see a different UFC referenced based on the design discipline involved. For example, for the Electrical PTS D40, you would see UFC 3-501-01 “ Electrical Engineering”.These are examples of what we referred to as “Above the line design criteria and construction requirements” from a few slides back.Slide 48This is an example of the “Performance & Quality” specified in a PTS. These specifications reference industry standards (such as International Mechanical Code, NFPA, ASME, & ASTM) and testing requirements (for example, NFPA 31 – Standard for the Installation of Oil-Burning Equipment) for compliance. Slide 49 (Delete this slide in its entirety) no slide 49The PTSs listed have UFGS identified within their section that the DOR must use when preparing the design documents. NAVFAC technical discipline experts determined that there were not commercial criteria available so these UFGS’s must be used by the DOR in preparing the specifications. UFGSs are only required if the Contractor hasn’t already selected the item. Z-10 is a section that was created to include the “general requirements” that were common to all of the PTSs. Z-10 applies to all PTSs. Slide 50 (delete this slide)This is an example of the wording included in a PTS that requires the DOR to use certain UFGSs. In this example, the DOR has to use Section 26 11 16 “Secondary Unit Substation”, Section 26 23 00 “Low-Voltage Switchgear, and Section 26 24 13 “Switchboards” for the project.Slide 51Part 5, Prescriptive Specifications include Unified Facilities Guide Specifications (UFGS) only when it is not feasible to prepare a performance specification. These sections would be edited by the RFP Preparer and included in the RFP. The intent is to have zero or minimal prescriptive UFGSs in an RFPspecifications only when necessary for the RFP. The number and type used will vary based on the project .requirements. Slide 52Part 6, Attachments include information that may help the DB Contractor in preparing the design documents. Attachments include items such as Permits Record of Decision (PROD) forms, geotechnical reports, site surveys, as-built drawings, and concept drawings. We need to be careful when including attachments. Also included in Part 6 is a Performance Assessment Plan (PAP). The PAP is a tool to assist in managing and evaluating the Contractor’s team on their performance throughout the contract to provide an objective CPARS rating. There is no order of precedence among the attachments, other than the Concept Drawings. If the soils report is included in the RFP, the report’s recommendations should be included in the RFP.Slide 53, 54 & 55Knowledge CheckSlide 56In this training module we learned about. Finding the D-B Master Website and how to Navigate within the siteHow to customize the RFP for a specific projectThe layout of the 6-part RFPDescription of the components of each part of the RFPSlide 57As we wrap-up today, just a reminder that there are 5 Design-Build training modules in this series. These include:Introduction to Design-BuildStandard Design-Build Master RFP TemplateDesign-Build ProcessesSmall Project Design-Build, and D-B Master Management Training for Criteria ManagersI encourage you to view all of thethe first four modules. This will give you an in-depth understanding of the entire NAVFAC Design-Build Process.The last module is targeted to NAVFAC criteria managers.Slide 58This concludes the training on the Standand Design-Build Master RFP. I hope this training module provided you with a greater understanding of the NAVFAC 6-Part Standard Design-Build Template. Here is a resource link to the Navy Design-Build Master RFP documents on the Whole Building Design Guide website. 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