| NODIS Library | Program Management(8000s) | Search |

NASA Ball NASA
Procedural
Requirements
NPR 8820.2H
Effective Date: September 27, 2022
Expiration Date: September 27, 2027
COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES
Printable Format (PDF)

Subject: Facility Project Requirements (FPR) (Updated w/Change 1)

Responsible Office: Office of Strategic Infrastructure


| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | Chapter7 | ApppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | ALL |

Chapter 3. Design

3.1 Design Coordination

3.1.1 General. Guidance for final designs can be found in NASA-STD-10002, NASA Facility Design Standard.

3.1.2 FPM Responsibilities. The FPM shall keep the Facility Project Team, the FRED EPM (if applicable), the FRED CoF Program Officer, the CNM, and the Center CRM, apprised of all changes or proposed changes in project requirements.

3.1.3 Program-Direct CoF Projects. For Program-Direct CoF Space Flight and/or R&D projects, the FPM shall coordinate the final design effort with the sponsoring Mission Directorate POCs.

3.2 Procurement of Architectural-Engineering (A-E) Services

3.2.1 General. Whenever commercial A-E services are required, the FPM and the Center Procurement Office's assigned CO shall acquire those services in accordance with the FAR Part 36 and NFS.

3.2.2 A-E Contractor Selection Criteria. A-E contractor selection is subject to the criteria under Selection of Architects and Engineers, 40 U.S.C § 11 (Brooks Act).

3.2.3 Regional A-E Contracts. In lieu of procuring A-E services, FPMs will use NASA's regionally established A-E Contracts as much as possible for providing the required facility project services in accordance with Architect-Engineering Services Not Associated with Environmental Remediation, NFS A-102.14. If it is necessary to deviate from NFS A-102.14, the FPM will work with the Center CO to submit a request for permission for such a deviation. If granted, the request for deviation would ultimately be approved by the NASA Associate Administrator for Procurement. Only after the deviation has been approved can quotes, bids, or proposals be requested from potential contractors.

3.3 Public Release

3.3.1 The FPM and Facility Project Team members will ensure that public disclosure of CoF project information (including subprojects and/or work packages) occur only after release by the appropriate committees of Congress. Facility project design documents prior to their planned construction FY of execution are sensitive, and the FPM ensures that all parties connected with project development are aware of this sensitivity. Design packages used for acquisition do not include any information classified as "for official use only," secret, or top secret.

3.3.2 Any information deemed Controlled Unclassified Information (CUI) will be handled by the FPM and Facility Project Team members per NPR 2810.1, Security of IT.

3.4 Management of Preliminary Engineering Report (PER)

3.4.1 PER Purpose. If special studies are not sufficient to identify the necessary content for a Facilities Requirements Document (FRD), the FPM should advocate for the development of a PER. This is especially applicable for projects of complex technical content, implementation, schedule, or geographic constraints. The goal of a PER is to study options, identify the optimal project approach, clarify design

requirements, clarify operational requirements, identify environmental issues, and establish a high-level cost estimate for the project design, implementation, and activation phases. If the project may cause adverse effects to cultural resources, the PER should include an analysis of alternatives considered to avoid these effects. Other deliverables from a PER can include the following:

a. Documentation and analysis of field visits required to verify existing conditions (e.g., review of existing record drawings, photographs).

b. Market research of potential vendors to ascertain capabilities necessary to meet project objectives.

c. A 15 percent conceptual design including the development of basic site/floor plans, piping & instrumentation diagrams (P&IDs), general equipment layouts and existing facility/utility modifications. This could include a preliminary specification table of contents.

d. Functional Requirements Document or a Performance Specification for a design-build project per Section 2.2.5.4.

e. Preliminary business case, per the NASA Business Case Guide for Real Property and Facilities Project Investments, including a review of the status quo (including current maintenance and repair costs) and the associated costs based on the required modifications and a study of alternatives.

f. Preliminary project risk assessment including studies of the reuse of existing assets, impacts of unplanned outages, etc.

g. A preliminary FPMP per Section 2.2.7.

h. Site analysis, including soil borings to determine geotechnical characteristics and/or identification of hazardous soils.

i. A preliminary construction schedule identifying major milestones.

3.4.2 PER Funding. Funding for a PER is determined by the facility project type.

3.4.2.1 Institutional CoF Project. If a PER is required for an Institutional CoF Project, the FPM should advocate to the FRED for FP&D funding in advance of the request for Final Design funding.

3.4.2.2 Program-Direct CoF Project. If a PER is required for a Program-Direct CoF Project, the FPM should advocate for funding from the sponsoring Mission Directorate in advance of the request for Final Design funding.

3.4.3 Cost for a PER. Typically, the cost of a PER should not exceed two percent of the initially assumed project AFPCE.

3.4.4 PER Format. The FPM will ensure that the SOW for a PER includes provisions for developing project requirements, scope of work, justification, alternatives considered, method for selecting proposed option, final design estimate for the proposed option, engineering budget for construction of the proposed option, and appendices to include sketches (e.g., floor plan, elevations, piping &

instrumentation diagrams, one-line electrical diagrams) engineering analyses, catalog cuts, or other descriptive materials.

3.4.5 PDRI Requirements. The FPM and the Facilities Project Team shall perform a PDRI exercise immediately upon the completion of the PER (refer to Chapter 2, Section 2.2.6.4, Project Definition Rating Index - PDRI). This does not eliminate the need for the required PDRI at the 30 percent final design milestone. All stakeholders including facility occupants and users, POCs for facility systems, facility/building managers, and Center Institutional Safety Discipline Leads should participate in the PDRI exercise.

3.5 Management of Final Design Phase

3.5.1 Final Design Funding. Funding for a final design (including project-specific environmental and cultural resource compliance) is determined by the facility project type.

3.5.1.1 Institutional CoF Project. If a final design is required for an Institutional CoF Project, the FPM should advocate to the FRED for FP&D funding no later than two years prior to the year of execution.

3.5.1.2 Program-Direct CoF Project. If a final design is required for a Program-Direct CoF Project, the FPM should advocate for funding from the sponsoring Mission Directorate no later than two years prior to the year of execution. This funding should be recorded on a NF-1878 issued by the FRED Resource Analyst.

3.5.2 Final Design Funding Obligation. NASA's policy is to award final design contracts for Facility Projects early in the FY for which the design funding is appropriated. The FPM shall plan and manage the procurement of final design services to achieve the goal of obligating 85 percent of all approved design funding by the end of the FY (assuming that the remaining 15 percent of unobligated funding is required for Contingency and Other Burden Costs). Contract obligation planning will include time for the preparation, submission, and approval of the NF-1739, which establishes the proper accounting treatment of the design funding. Completing the NF-1739 process and establishing the proper accounting treatment by the OCFO needs to occur prior to procuring the final design services.

3.5.3 Designing in Accordance with Project Budget. For all Facility Projects, the FPM shall include a statement in the A-E SOW indicating that the design entity is responsible for designing the project in accordance with the estimated cost of construction provided by the Government. For all CoF projects, the SOW should specify that at the 60 percent design completion milestone, the A-E design entity will notify the FPM, the CO, and the FRED EPM (if applicable) in writing if the estimated cost of construction is not adequate to cover the requirements included in the SOW. Refer to Section 3.6.1.3 for alternatives.

3.5.4 Final Design Cost Limitation. Final design cost proposals received from an A-E firm are subject to 48 CFR § 836.606-71 - Application of six percent Architect-Engineer Fee Limitation. Additional funding beyond the six percent limitation is typically required for A-E contract personnel field investigation and record drawing review, cost estimating, special analyses, construction implementation plans, and other services not addressed in the CFR.

3.5.5 Final Design Guidance. The FPM is encouraged to use NASA STD-10002, NASA Facility Design Standard as a reference during the facility project final design phase.

3.5.6 BIM Requirement. BIM is required for all Discrete level new construction and major modification projects. Depending on the project delivery approach (Design-Bid-Build or Design-Build), the FPM should incorporate applicable information from NASA-STD-10001 into the final design statement of work.

a. The FPM should clearly identify the scope of BIM requirements within the Final Design SOW.

b. For design-bid-build delivery, refer to the guideline documents NASA BIM Scope of Service and Requirements for Architects and Engineers and NASA BIM Scope of Services and Requirements for Construction Contractor in a Design-Bid-Build Process.

3.5.7 Final Design SOW, Design-Bid-Build Project. The FPM shall develop an SOW such that the A-E contractor can provide a firm fixed-price cost to provide the design required services. A typical format for a final design SOW is as follows:

3.5.7.1 Part 1 General. This section should provide a high-level overview of the project and some basic A-E requirements.

a. Description. Provide an overview of the project location, scope, purpose, the Government's budget, a statement regarding the need to design in accordance with the defined budget (see Section 3.5.4), and a schedule for delivery of the final design services.

b. General Requirements. Provide a comprehensive description of the A-E services required including field visits and verification of existing conditions, the use of BIM, required calculations and analyses (refer to NASA-STD-8719.11), Federal-State-Local code requirements, drawing and specification development, cost estimating services, construction scheduling services, development of a construction implementation, and other specialized services as required. This section should include a description of what existing record drawings, services, or equipment will be furnished by the Government for A-E contractor use. Lastly, this section should include a short statement of any services that are not required under this SOW.

3.5.7.2 Part 2 Projects. This section should clearly define all deliverables required from the A-E firm.

a. Final Design Cost Proposal. Provide details regarding hourly rates and total hours per engineering discipline and proposed subcontractors. This section should also require the A-E contractor to acknowledge the furnished requirements, budget, and schedule for completing the task.

b. Final Design Drawings. Provide details of the drawing units, sizes, formats, standards, and software requirements (including BIM requirements). Details should also be provided regarding the specific discipline drawings required, the organization of the drawing package, and any signature or professional stamp requirements.

c. Construction Specifications. Indicate the requirements for specifications to conform to Part 10 of the FAR (e.g., the need to describe equipment salient features to enable equal products) and to be prepared in accordance with the Construction Specifications Institute (CSI) 50 Division three-part 2004 format. Typically, this section offers the A-E firm to use SpecsIntact (i.e., the Unified Facilities Guide Specifications—UFGS—found in the Whole Building Design Guide) or to propose an alternate method

for approval by the NASA Facility Project Team.

d. Final Design Schedule. Provide requirements for a Gantt chart that includes site visits, progress level submissions, design reviews and other important milestones.

e. Construction Schedule. Provide requirements for a conceptual construction schedule in Gantt chart format that includes mobilization, demolition (if required), site preparation, procurement of long-lead items, typical construction activities, commissioning, and activation. This construction schedule also should account for any facility operations and specific Center restrictions that might affect the Performance Period of Construction).

f. Construction Cost Estimate. Provide instructions for the engineering estimate to include all construction discipline labor, materials, supervision, overhead and profit and insurance (bid bond) markups. Subsequently, the A-E should develop the AFPCE by including escalation to the mid-point of construction and specified markups for Supervision, Inspection, and Engineering Services (SIES), construction contingency and other costs. The A-E should also be instructed to develop a base bid work scope and contract options for bid protection purposes.

g. Construction Implementation Plan. Provide requirements for the A-E firm to provide a plan considering all unique site impacts, personnel impacts, construction lay-down area requirements, NASA research ground testing impacts, utility impacts (including tie-in procedures), special permits and forms, confined space concerns and all off-hour work requirements.

h. Final Design Report. Provide instructions on the format requirements for the report including specific sections for technical discipline information and calculations, materials assessment reports, hazardous materials abatement requirements, a list of long-lead materials and equipment and appendices for special studies, back-up data, catalog cut sheets, etc.

3.5.7.3 Part 3 Execution. This section should clearly define major events occurring during the final design process and what is required for those events.

a. Conferences and Meetings. Require the A-E firm to identify all formal meetings including a final design kick-off meeting, fact-finding meetings, milestone review meetings (per Section 3.6 below) and any other specialized meetings. The meeting locations should be specified, and the A-E firm should be responsible for logging meeting minutes and action items.

b. Health and Safety Plan. As applicable, the A-E should submit a site-specific HASP for all employees accessing the site.

c. Design Submittal Requirements & Project Deliverables. See Section 3.6 below.

d. Project Requirements. Attach the Functional Requirements Document (FRD) identified in Section 2.2.6.4.

3.5.8 SOW, Design-Build Projects or Projects with other Delivery Approaches. The primary document used during the acquisition of a design-build contractor is the Performance Specification. In contrast to the functional requirements document that is developed for a design-bid-build project, the functional

requirements document for a design-build acquisition should have baseline (minimum) project success requirements and performance goals that may be evaluated during the acquisition phase and during contract performance. At the conclusion of the design-build contract, the FPM shall ensure that a complete set of as-built drawings and/or a BIM is provided by the A-E contractor.

3.6 Final Design Milestones

3.6.1 Design-Bid-Build Projects. The FPM shall ensure that the design-bid-build final design SOW specifies formal submissions from the A-E firm (and subsequent NASA reviews) at the 30 percent, 60 percent, and 90 percent level of final design completion. For highly technical and/or complicated projects, interim milestones can also be identified in final design SOW as required. These final design stages should include the following minimum elements:

3.6.1.1 30-Percent Final Design Submission. The 30-percent design submission is a critical design milestone for which the project requirements are validated. The SOW should instruct the A-E firm to include the following documents for this submission:

a. For new construction or major modification Facility Projects, civil site plans will be provided including existing utility locations, grading, pavements, and landscape features. The submission should also include basic architectural floor plans and elevations, preliminary structural system drawings, drawings identifying mechanical equipment locations and basic piping and ductwork runs, preliminary piping and instrumentation drawings (P&IDs), electrical equipment locations, one-line diagrams, a preliminary building code summary, and preliminary fire protection, suppression, and protective system drawings.

b. For repair projects, the location and scope of the work will be clearly identified from the existing conditions on site plans, architectural floor plans, and elevations, P&IDs, and electrical one-line drawings (as applicable).

c. A draft construction phasing plan and a preliminary commissioning plan (see http://www.wbdg.org/project/buildingcomm.php).

d. Design analyses and supporting engineering calculations. The analyses should support important assumptions and demonstrate conformance to required codes and standards.

e. An outline of the required construction specifications including section numbers and titles.

f. A preliminary order-of-magnitude engineering cost estimate and AFPCE, in accordance with Section 3.5.7.2.f above.

3.6.1.2 30-Percent PDRI Requirement. The FPM shall engage an independent entity (e.g., third-party Center individual, Agency PDRI team, etc.) to score the project using the PDRI process within two- weeks after receipt of the 30-percent design documents.

a. If the 30-percent final design PDRI score is over 200 out of a possible 1,000 points, the FPM shall immediately notify the assigned FRED CoF Program Officer and the EPM (if applicable). Depending on the magnitude of the score, the FRED may require the Facility CoF Program Manager and the FPM to either specify a higher construction contingency in the AFPCE calculation or recommend a delay in

proceeding with the remainder of the final design. If the recommendation is to delay the final design, the Facility Project Team and all stakeholders will meet to refine the requirements and re-run the PDRI exercise until an acceptable score is achieved. The design will then be allowed to proceed.

b. If the PDRI score is 200 or below, the FPM shall provide the score to the assigned FRED CoF Program Officer and the EPM (if applicable) for information only and proceed with the remainder of the final design activities.

c. The FPM shall record the 30-percent PDRI score on the NF-1509 when requesting construction funding.

3.6.1.3 60-Percent Final Design Submission. This submission will validate that the construction of the facility project is achievable within the NASA-specified budget. If the 60-percent estimate provided by the A-E firm is close to or exceeds the specified budget, the Facility Project Team and the A-E firm should develop a project structure that identifies a base bid work scope that is below the budget and bid option packages that contain work scope items of lesser importance. The base bid work scope needs to result in a project that is functional upon completion (see Chapter 1, Section 1.7.1.2). The A-E firm shall furnish the following deliverables for this submission:

a. A drawing package with a cover sheet including a drawing index, initial versions of drawings and equipment schedules for all required disciplines. Although the drawings will be in varying states of maturity, the set should be complete enough to validate the construction cost estimate. The drawings should reflect adequate M&O clearances around all equipment and systems.

b. First draft of construction specifications including all required sections for each discipline that are edited to reflect the project requirements.

c. Completed design analyses and supporting engineering calculations.

d. A second draft of the construction phasing plan and the commissioning plan.

e. First draft of the construction schedule identifying key milestones and utility tie-in requirements.

f. Identification of any constructability issues.

g. A comprehensive construction engineering estimate and AFPCE in accordance with Section 3.5.7.2.f above.

3.6.1.4 90-Percent Final Design Submission. This submission should be an essentially complete final design package of drawings, specifications, calculations and analysis, schedules, and commissioning plans. The period between 90-percent and 100-percent should be for the A-E firm to address minor spelling corrections, small adjustments to drawings and specifications and for final coordination activities. The A-E firm shall address all of NASA's 90-percent comments prior to receipt of final payment.

3.6.2 Design-Build Projects or Projects with other delivery approaches. The only formal design milestone is at 30-percent. The submission requirements should be comparable to Section 3.6.1.1

above. A PDRI process should be completed upon completion of the Performance Specification and also is required at the time of 30-percent submission.

3.7 Final Design Reviews by NASA

3.7.1 For each of the submission milestones indicated in Section 3.6 above, the FPM shall immediately distribute all materials received from the A-E firm to the Facility Project Team and any other project stakeholders including the FRED CoF Program Officer and the EPM (if applicable), and the Center Institutional Safety Discipline Leads. Depending on the size of the project, NASA will typically have between two and four weeks to review each package and return comments prior to the established submission review meeting. The primary purpose of these reviews for Design-Bid-Build and Design- Build projects is as follows:

a. Ensure A-E conformance to the Final Design SOW.

b. Ensure drawing and specification coordination between engineering disciplines and address any constructability issues.

c. Confirm that environmental and cultural resource issues are addressed according to referenced codes and standards.

d. Review and address project constructability and maintainability issues.

e. Ensure construction safety and health code compliance.

f. Ensure compliance with applicable national consensus building and fire codes, NASA-STD-8719.11, and all other applicable standards through a plan review in accordance with NPR 8715.1, Section 14.4.6.

g. Validate the correction of all nonconformances identified during the plan review in accordance with NPR 8715.1, Section 14.4.6.

h. Ensure that security, IT and other stakeholder requirements are addressed.

3.8 Mission-Critical Technical Facilities

3.8.1 NASA's Mission-Critical Technical Facilities are defined according to NPR 7120.5. These facilities are constructed or significantly modified for ground testing or deployment of space flight hardware and systems. The FPM (per NPR 7120.7 and NPR 7120.8) shall comply with the requirements per NPR 7120.5 and this document. Where compliance to both documents' requirements would duplicate an effort (e.g., a project management plan), only one effort incorporating all required elements from both policies is necessary.

3.8.2 For complex or mission-critical systems, the FPM will ensure that a Failure Mode and Effects Analysis (FMEA) is accomplished in accordance with the NASA-STD-8719.7, Facility System Safety Guidebook.

3.9 Activation Budget

3.9.1 General. The activation budget includes estimated costs associated with all tasks necessary to verify that the facility equipment and systems meet the project requirements, the equipment and systems operate within the design parameters, and the M&O and operating organizations are ready to use and maintain the facility. Facility project activation requirements are identified in Chapter 5 of this document and in Appendix E. As indicated in these references, activation activities can require a combination of CoF project funds, Mission Directorate funds and/or local Center funds. During the Final Design phase, the FPM shall complete the estimate of the activation budget started during the planning process. Upon completion, this plan requires coordination with FRED, the supporting Mission Directorate, and the Center's OCFO.

3.9.2 Outfitting. This budget includes all costs necessary to outfit the facility for personnel move-in and its intended operation. New construction and major modification projects are to include an amount for these items as indicated in Appendix E.

3.9.3 Special Test Equipment. This budget includes all costs for equipment that interface with a ground test facility and the equipment and systems to be tested (usually associated with a Program-Direct CoF Project). These funds are not included in the CoF project budget and are furnished by the supporting Mission Directorate.

3.9.4 Integrated Systems Test (IST). This budget includes all costs for testing the construction of a new or major modification of an existing technical facility (e.g., ground test facility, data center). An IST usually involves installation of a test article or simulated load and subsequent testing of all installed or modified facility systems for the fully integrated operations specified in the design. These funds are not included in the CoF project budget and are furnished by the supporting Mission Directorate.

3.9.5 Full Disclosure of Activation Budget. The FPM shall identify the full activation cost requirements on NF 1509. Activation costs covered under the scope of a CoF project will be included within the engineering budget on the Facility Project Cost Estimate section of the NF 1509 and subsequently be captured in the project AFPCE. All activation costs not covered under a CoF project budget are to be identified in the "Other Related Costs" sections of these documents.



| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | Chapter7 | ApppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | ALL |
 
| NODIS Library | Program Management(8000s) | Search |

DISTRIBUTION:
NODIS


This document does not bind the public, except as authorized by law or as incorporated into a contract. This document is uncontrolled when printed. Check the NASA Online Directives Information System (NODIS) Library to verify that this is the correct version before use: https://nodis3.gsfc.nasa.gov.