HPSC_DRFP_Sections_L_and_M.pdf

DRFP NNG11341433R

L.1 SECTION L CLAUSES INCORPORATED BY REFERENCE

52.215-22 LIMITATIONS ON PASS-THROUGH CHARGES—IDENTIFICATION OF

SUBCONTRACT EFFORT (OCT 2009)

1852.233-70 PROTESTS TO NASA (DEC 2015)

L.2 52.215-200 COMMUNICATIONS REGARDING THIS SOLICITATION (JAN 2014)

Any questions or comments regarding this solicitation shall cite the solicitation number and be directed to the following Government representative:

Name: Denise Sydnor

Phone: 301-286-8086

(Collect calls not accepted)

FAX: 301-286-1773

E-Mail: denise.y.sydnor@nasa.gov

*Address: Goddard Space Flight Center

8800 Greenbelt Road

Greenbelt, MD 20771

Attention: Denise Sydnor, *Mail Code 210.8.

*(Note: Must be complete, including Mail Code, on all transmittals.)

The Government will accept relevant and appropriate comments regarding this solicitation, which will be considered in the preparation of the final Request For Proposal (RFP). All Offeror comments should be submitted as soon as possible.

(End of provision)

L.3 GSFC 52.215-201 PROPOSAL PREPARATION—GENERAL INSTRUCTIONS

(FEB 2016)

It is NASA's intent, by providing the instructions set forth below, to solicit information that will demonstrate the Offeror's competence to successfully complete the requirements specified in the

Statement of Work (SOW), Attachment A and in the requirements documents, Attachment A-1.

Generally, the proposal should:

Demonstrate understanding of the overall and specific requirements of the proposed contract.

Convey the company's capabilities for transforming understanding into accomplishment.

Present in detail, the plans and methods for so doing.

Present the costs associated with so doing.

In the event that other organizations are proposed as being involved in conducting this work, their relationships during the effort shall be explained and their proposed contributions shall be identified and integrated into each part of the proposal, as appropriate.

(a) PROPOSAL FORMAT AND ORGANIZATION

(1) Offerors shall submit proposals in four volumes as specified below:

Volume Title Copies

I Offer Volume Original plus 3 Hardcopies and two electronic copies

II Mission Suitability Volume Original plus 10 Hardcopies and two electronic copies

III Cost Volume Original plus 10 Hardcopies, one additional hardcopy for audit support purposes, and two electronic copies

IV Past Performance Volume Original plus 10 Hardcopies and two electronic copies

(2) Prime Offerors and proposed Significant Subcontractors for Cost Volume proposal purposes defined as any subcontract that is likely to exceed 10% of the proposed contract value shall include one (1) additional separately packaged hardcopy of their Cost Volume proposal, marked

NNG16574410R/NASA Proposal Evaluation Material,” which the Government may use for audit support purposes.

(3) All pages of Volumes I, II, III, and IV shall be numbered and identified with the Offeror’s name, RFP number and date. Subsequent revisions, if requested, shall be similarly identified to show revision number and date. A table of contents shall be provided with figures and tables listed separately.

(4) Two electronic copies of the Offeror’s (Prime and proposed Significant Subcontractors) proposal, designating one as “back-up,” shall be submitted (in addition to the hardcopies specified above) in Microsoft Office Word (compatible with Word 2010) or Adobe Portable

Document Format (PDF) (compatible with version X). While the RFP provides the Cost Volume exhibits in PDF format, Offerors shall submit all Cost Volume exhibits in Microsoft Office Excel format (compatible with Excel 2010) and the exhibits shall contain all formulas. Instructions for converting from PDF format to Excel can be found in the Cost Volume Instructions provision.

DO NOT password protect any portion of your electronic submission.

Electronic files of Volumes I, II, III, and IV shall be on virus free CD-ROM (CD-R format) discs with an external label indicating: (1) the name of the Offeror, (2) the RFP number, (3) the format and software versions used, (4) a list of the files contained on the disk and (5) date of the information. The Offeror shall provide written documentation that describes the contents of each

CD-ROM and of each file. In the event of any inconsistency between data provided on electronic media and hardcopies, the hardcopy data will be considered to be correct. The Offeror must certify that the electronic medium is virus free.

(5) The format for each proposal volume shall parallel, to the greatest extent possible, the format of the evaluation factors and subfactors contained in Section L of this solicitation. The proposal content shall provide a basis for evaluation against the requirements of the solicitation. Each volume of the proposal shall specify the relevant evaluation criteria being addressed, if appropriate. The proposal shall include a matrix showing where in the proposal the technical requirements of the SOW and the evaluation criteria of this RFP are satisfied (i.e. SOW element versus Offeror's proposal page numbers). It is intended that this be a simple matrix that should in no way inhibit an innovative approach or burden the Offeror. This offer compliance matrix is excluded from the page limitations contained in paragraph (b)(1) below.

(6) Information shall be precise, factual, detailed and complete. Offerors shall not assume that the evaluation team is aware of company abilities, capabilities, plans, facilities, organization or any other pertinent fact that is important to accomplishment of the work as specified in the SOW.

The evaluation will be based primarily on the information presented in the written proposal. The proposal shall specifically address each listed evaluation factor and subfactor.

(b) PROPOSAL CONTENT AND PAGE LIMITATIONS

(1) The following table contains the page limitations for each portion of the proposal submitted in response to this solicitation. Additional instructions for each component of the proposal are located in the solicitation provision noted under the Reference heading.

Proposal Component Volume Reference Page

Limitations

Offer Volume I L.4 None

Mission Suitability Volume II L.6 Mixed

Technical Approach and Management Approach 60 pages

Requirements Compliance and Verification Matrix * 15 pages

Cover Page, Indices, Offer Compliance Matrix, and Small Business Utilization Subfactor

Excluded

Cost Volume III L.7 Mixed

(a) Cost Exhibits None

(b) Basis of Estimates ** 30 pages

Past Performance Volume IV L.8 Mixed

(a) Information from the Offeror *** 20 Pages

(b) Cover Page, Indices, List of those sent Past

Performance Questionnaires, Small Business

Subcontracting Plan History, Customer

Excluded

Proposal Component Volume Reference Page

Limitations

Evaluations, Termination/Descope information, and List of Acronyms

*Page limits in addition to Mission Suitability Response of 60 pages

**Prime Offeror and all Significant Subcontractors as defined in the cost volume instructions (page limitation is for the total component (Prime and Significant Subcontractors)).

*** Prime Offeror individually and each Significant Subcontractor (as defined in the past performance volume instructions) individually.

(2) A page is defined as one side of a sheet, 8-1/2" x 11", with at least one inch margins on all sides, using not smaller than 12 point type Times New Roman font. Line spacing or the amount of vertical space between lines of text shall not be less than single line (Microsoft Office Word’s default line spacing). Character spacing shall be “Normal”, not “Expanded” or “Condensed.” The margins may contain headers and footers, but shall not contain any proposal content to be evaluated. Foldouts count as an equivalent number of 8-1/2" x 11" pages. The metric standard format most closely approximating the described standard 8-1/2" x 11" size may also be used.

Volumes I, II, III, and IV shall be submitted in separate ringed (or similarly bound) binders. Diagrams, tables, artwork, and photographs may be reduced and, if necessary, run landscape or folded to eliminate oversize pages. Text in Diagrams, schedules, charts, tables, artwork, and photographs shall be no smaller than 10 point. Diagrams, tables, artwork, and photographs shall not be used to circumvent the text size limitations of the proposal.

(3) Title pages, tabs, and tables of contents are excluded from the page counts specified in paragraph (1) of this provision (as well as other documents specified in table (b)(1) above). In addition, the Cost

Volume of your proposal is not page limited except for the page limit for the Basis of Estimate (BOE) section specified in table (b)(1) above. However, this volume is to be strictly limited to cost and price information. Information that can be construed as belonging in one of the other volumes of the proposal will be so construed and counted against that volume's page limitation.

(4) The Government intends to evaluate proposals and award contract(s) without discussions with

Offerors (except clarifications as described in FAR 15.306(a)). Therefore, the Offeror's initial proposal should contain the Offeror's best terms from a cost or price and technical standpoint. The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary. If discussions are held and final proposal revisions are requested, the Government will specify separate page limitations in its request for that submission.

(5) Pages submitted in excess of the limitations specified in this provision will not be evaluated by the

Government and will be returned to the Offeror in accordance with NFS 1815.204-70(b).

L.4 GSFC 52.215-203 OFFER VOLUME (FEB 2016)

This must be a separate volume.

(a) STANDARD FORM (SF) 33, OFFEROR FILL INS AND SECTION K

Blocks 12 through 18 of the SF 33 and the indicated Offeror required fill-ins in Sections B-K must be completed. The signed SF33 and the pages with the required fill-ins must be submitted. Annual representations and certifications shall be completed electronically via the System for Awards

Management (SAM) web site accessed through https://www.acquisition.gov, in accordance with Section

K provision FAR 52.204-8, Annual Representations and Certifications. The balance of the solicitation need not be returned unless the Offeror has made changes to other pages that will constitute part of the contract. Any such changes must be separately identified in the Summary of Exceptions. All SF 33s require original signatures.

(1) It is requested that Offerors indicate, in Block 12 of the SF 33, a proposal validity period of

179 days. However, in accordance with paragraph (d) of FAR provision 52.215-1, “Instructions to Offerors--Competitive Acquisitions,” a different validity period may be proposed by the

Offeror.

(2) Provide the names, phone numbers, and email addresses of persons to be contacted for clarification of questions of a technical nature and business nature. Identify any consultants and/or subcontractors used in writing this proposal (if any) and the extent to which their services will be available in the subsequent performance of this effort.

The contract schedule refers to TBD and TBP. They are defined as follows:

TBD = TO BE DETERMINED BY THE GOVERNMENT

TBP = TO BE PROPOSED BY THE CONTRACTOR

(b) SUMMARY OF EXCEPTIONS

Include a statement of acceptance of the anticipated contract provisions and proposed contract schedule, or list all specific exceptions to the terms, conditions, and requirements of Sections A through J of this solicitation, to the Representations and Certifications (Section K) or to the information requested in

Section L. Include the reason for the exception, new terms, conditions, and/or clauses, including any proposed benefit to the Government. This list must include all exception(s), deviation(s) and/or conditional assumptions taken.

Offerors are cautioned that exceptions or new terms, conditions, or clauses may result in a determination of proposal unacceptability (NFS 1815.305-70), may preclude award to an Offeror if award is made without discussions, or may otherwise affect an Offeror’s competitive standing.

(c) ADDITIONAL INFORMATION TO BE FURNISHED

(1) Business Systems

State whether all business systems, including but not limited to accounting, property control, purchasing, estimating, and employee compensation, which require Government acceptance or approval (as applicable) are currently accepted/approved without condition.

Provide the date of acceptance/approval for each system and the cognizant contract administration office. Explain any existing conditional acceptances/approvals and the compliance status of any systems(s) for which acceptance or approval is currently withheld.

FAR 16.301-3 requires that a contractor's accounting system be adequate for determining costs applicable to the contract prior to the award of a cost-reimbursement contract. The Offeror shall provide evidence of an adequate accounting system as determined by the cognizant administrative office for accumulating and reporting incurred costs. If an Offeror is relying on the accounting system adequacy of a Joint Venture team member, sister company, or any other affiliated company’s accounting system, they must demonstrate a convincing basis for using that system as a basis for determining their own adequacy. An adequate accounting system is not an evaluation criterion. It is a basic contract requirement with a pass/fail determination. A contract may only be awarded to the Offeror(s) who are determined to have an adequate accounting system.

Offerors who do not have an adequate accounting system determination shall provide evidence of any independent audit and system approvals as well as documented system ability to segregate and accrue costs by contract.

(2) Contract Administration

Furnish the information listed below:

a. Cognizant Government audit agency with mailing address, email address, telephone number, and fax number.

b. Cognizant Government inspection agency with mailing address, email address, telephone number, and fax number.

c. Cognizant Government Administrative Contracting Officer by name with mailing address, email address, telephone number, and fax number.

(3) Responsibility Information

Provide information addressing all of the elements under FAR 9.104 to demonstrate responsibility (address the elements under this section that are not addressed in another proposal volume).

(4) Taxpayer Identification Number

Prime Offerors shall provide their Taxpayer Identification Number (TIN) (the number required by the Internal Revenue Service (IRS) to be used by the Offeror in reporting income tax and other returns).

(5) Waiver of Rights to Inventions

This solicitation contains NFS clause 1852.227-70, “New Technology—Other than a Small

Business Firm or Nonprofit Organization” and NFS provision 1852.227-71, “Request for Waiver to Rights to Inventions”. Any petitions for advance (prior to contract execution) waiver of rights to inventions should be included in this volume.

(6) Subcontractor Listing

The Offeror shall provide a summary listing (by name and address) of all subcontractors

(regardless of dollar value) that have been identified throughout the Offeror’s.

(7) Earned Value Management System

In accordance with the Section L NFS provision 1852.234-1, Notice of Earned Value

Management System (Deviation), Offerors shall provide documentation verifying compliance of their proposed Earned Value Management System (EVMS) with the American National

Standards Institute/Electronics Industries Alliance (ANSI/EIA)–748 Standard in this volume. If the Offeror proposes to use a system that has not been determined to be in compliance with

ANSI/EIA–748 Standard, the Offeror shall submit a comprehensive plan for compliance with these EVMS guidelines to the Government for approval. Offerors shall not be eliminated from consideration for contract award because they do not have an EVMS that complies with these guidelines.

(8) Cost Accounting Standards

State whether the Cost Accounting Standards (CAS) Disclosure Statement represented in Section

K FAR provision 52.230-1, Cost Accounting Standards Notices and Certifications, has been approved by the cognizant Administrative Contracting Officer, and provide the date of such approval. If your CAS Disclosure Statement is currently not approved or there are some existing

CAS non-compliance findings, please provide detailed explanation of the CAS non-compliance issues, corrective action status, and any potential impact on this procurement. If the Offeror has not submitted a Disclosure Statement, but would fall under CAS compliance if awarded the resultant contract, then a CAS Disclosure Statement shall be submitted as part of your proposal in this volume. The Government will forward the Disclosure Statement to the cognizant contract administration office with its request for review of the submitted CAS Disclosure Statement.

(9) Organizational Conflicts of Interest

In accordance with the NFS clause 1852.237-72, Access of Sensitive Information, included in this order and NFS 1837.203-70, Providing Contractors Access to Sensitive Information, Offerors shall provide a preliminary analysis of possible organizational conflicts of interest that might flow from the award of this contract. Within 30 days after the contract effective date, the successful contractor shall submit for NASA approval a comprehensive Organizational Conflicts of Interest Avoidance Plan, which will be incorporated into the contract under Clause J.1 as

Attachment C. This comprehensive plan shall incorporate any previous studies performed;

thoroughly analyze all organizational conflicts of interest that might arise because the Contractor has access to other companies' sensitive information; and establish specific methods to control, mitigate, or eliminate all problems identified. The Contracting Officer will review the plan for completeness and identify to the Contractor substantive weaknesses and omissions for necessary correction. Once the Contractor has corrected the substantive weaknesses and omissions, the

Contracting Officer shall incorporate the approved plan into the contract as a compliance document.

(End of Provision)

L.5 52.215-205 PROPOSAL MARKING AND DELIVERY (SEPT 2014)

(Offeror: You MUST comply with these instructions to ensure that the designated receiving office can identify, date and time mark, secure, and deliver your proposal to the Contracting Officer.)

(a) External Marking of Proposal Package(s)

All proposal packages must be closed and sealed.

The proposal package must include the offeror’s name and return mailing address.

The required mailing address and external marking for proposals is as follows:

Goddard Space Flight Center

Greenbelt, MD 20771

Building 35 — Shipping and Receiving Dock

Solicitation Number NNG16574410R

Attn: Denise Sydnor

Building 26, Room 050

“PROPOSAL--DELIVER UNOPENED"

Suggested additional marking if delivery is made by a commercial delivery service:

"COMMERCIAL DELIVERY PERSONNEL: THIS PROPOSAL MUST BE DELIVERED TO

THE DOCK MASTER, BUILDING 35 SHIPPING AND RECEIVING DOCK, NO LATER

THAN 06/07/2016, 3:00 pm).”

(b) Designated Receiving Office

The designated receiving office for proposals is the Shipping and Receiving Dock, Building 35, Goddard Space Flight Center, which must be accessed via the access road off of Good Luck

Road and requires entry via the security guard gate. Proposals must be received at the designated receiving office no later than the date and time stated on the solicitation face page.

The Building 35 Shipping and Receiving dock is open from 7:30 AM to 3:30 PM, Monday through Friday, except Government holidays. Contractor personnel conduct the GSFC receiving function, which includes mailroom operations. Proposals must be marked with the date and time of receipt, subjected to security screening, secured, and delivered unopened to the Contracting

Officer.

There is public access to the Building 35 Shipping and Receiving Dock after entering the

Building 35 security gate. All deliveries are subject to GSFC Security screening.

(c) Methods of Proposal Delivery

There are three suggested methods of delivery to the designated proposal receiving office:

U.S. Postal Service Express Mail

Commercial Delivery Service

Delivery by company employee or other individual agent

It is highly encouraged for all offerors to use U.S. Postal Service Express Mail or

Commercial Delivery Services.

Regardless of the method of delivery chosen, the offeror is responsible for delivery of the proposal to the designated receiving office no later than the date and time stated on the face page of the solicitation.

L.6 GSFC 52.215-210 MISSION SUITABILITY VOLUME INSTRUCTIONS

(COMPETITIVE) (FEB 2016)

Contents of Mission Suitability Volume Instructions

(a) General Instructions

(b) Mission Suitability Volume Format

(c) Mission Suitability Instructions by Subfactor

(a) General Instructions

The Mission Suitability Volume should be specific, detailed, and provide all the information requested by these instructions. The Mission Suitability Volume must demonstrate that the offeror understands the requirements and has the ability to meet the requirements. General statements such as the "requirements are understood" or "standard procedures will be employed" are not adequate. Also, restatement or paraphrasing of the requirements should be avoided. Information previously submitted, if any, will not be considered unless it is resubmitted as part of the Mission Suitability Volume. It must not be incorporated by reference.

Although the Government does not encourage/discourage enhancements to the contract’s technical performance documents (e.g. Statement of Work, Specification, etc.), offerors may choose to propose performance enhancements. In order for the Government to consider a proposed enhancement’s value, the offeror must clearly define the enhancement(s) in Contract Attachment B, “Contractor Proposed

Enhancements,” in performance work statement (PWS) language in accordance with the PWS instructions in Attachment B. In addition, the offeror must describe the associated benefit(s) of the proposed enhancement(s) in their Mission Suitability Volume under the applicable Mission Suitability subfactor(s). The offeror shall include Contract Attachment B as part of the model contract in the

Contract Volume of their proposal. The offeror may receive credit for the proposed enhancement(s) only to the extent of its description in Attachment B, and the associated benefits explained in its

Mission Suitability Volume. Inconsistent statements about any enhancement(s) in an offeror’s proposal may result in a neutral or negative evaluation by the Government. Any enhancement(s) may result in a positive, neutral, or negative evaluation in spite of the Governments right to waive an enhancement(s) during contract performance in accordance with the GSFC 52.211-100, “Contractor Proposed

Enhancements,” clause in Section H of the contract. If the successful offer does not include any proposed enhancements, GSFC clause 52.211-100 and Attachment B will be removed from the resultant contract.

(b) Mission Suitability Volume Format

The Mission Suitability Volume must be divided and presented by each Mission Suitability subfactor as follows:

Subfactor A – Technical Approach

Subfactor B – Management Approach

Subfactor C – Small Business Utilization (SBU)

The Work Breakdown Structure (WBS) contained in the Statement of Work (SOW) of this solicitation shall be used to structure the Mission Suitability Volume for each of the subfactors. This solicitation contains NASA FAR Supplement clause 1852.242-73, "NASA Contractor Financial Management

Reporting." For the purpose of NF 533 reporting under the actual contract, offerors may propose a different WBS more tailored to the way the work is to be performed or to the offeror’s management or reporting systems for consideration by the Government. However, the Mission Suitability Volume and the Cost Volume must follow the provided WBS.

(c) Mission Suitability Instructions by Subfactor

The offeror's technical approach should demonstrate an understanding of the requirements and provide the techniques and procedures that will be used to satisfy the requirements in a timely and cost effective manner. The technical approach shall address the following critical elements of the Statement of Work

(SOW) in enough detail to clearly and fully demonstrate that the offeror understands the requirements and the inherent problems associated with the objectives of this procurement. The offeror shall explain the approach for identifying the optimum skill mix based upon the requirements of the SOW and the approach for matching skill mix to functions.

The offeror shall identify the most significant potential risks under this contract and also describe the risk management techniques that will be used to manage identified risks during contract performance.

Risk factors may be those inherent in the work, unique to the offeror's chosen approach. General areas of possible risk that are of concern to NASA are technical, schedule, cost, export control, and assured integrity. The offeror's discussion of a risk factor should provide the offeror's approach to managing the risk--the probability of the risk, impact and severity, time frame and risk acceptance or mitigation.

The offeror shall provide a work breakdown structure (WBS) covering all HPSC development to at least

4 levels (based on the WBS provided in the Statement of Work). Based on this level 4 WBS, the offeror shall submit a proposed schedule by project phase. The schedule shall identify linkages between tasks, schedule margin and the critical path. This information shall be combined into a single schedule chart.

The technical approach shall provide a chiplet concept and architecture description for the HPSC chiplet, including at a minimum but not limited to:

i. Block diagrams

ii. Listing of the intellectual property (IP) cores to be utilized

iii. Description of how IP cores within the HPSC chiplet are to be interconnected

iv. Description of any custom-designed cores and modifications to existing IP cores

v. Description of chiplet configuration controller

vi. List and description of memory and I/O interfaces provided

vii. Description of the debug and trace capabilities for the HPSC chiplet

viii. Description of power scaling capabilities

ix. Description of hardware implemented fault tolerance capabilities

x. Description of timing and synchronization capabilities

xi. Description of the foundry process and cell libraries proposed for the development of the HPSC chiplet

xii. Expected die size

xiii. Description of the packaging approach

Proposers offering solutions that do not utilize the processor IP shown in architectural block diagram provided in Attachment A-1 shall provide analysis indicating that the proposed design meets or exceeds all of the listed requirements and the rationale for the proposed approach.

The technical approach shall also include a description of the proposed implementation for the HPSC system software, including at a minimum but not limited to:

i. Boot and configuration control software

ii. Operating systems and compilers

iii. Board support packages for operating systems

iv. Trace and debug capabilities

v. Software development environments

vi. Description of software features supporting fault management, power management, and resource allocation

The technical approach shall include a description of the HPSC chiplet operation, including at a minimum but not limited to:

i. Boot process

ii. Chiplet configuration control

iii. Time synchronization

iv. Interrupt handling

v. Fault management, including fault tree and mitigation for each fault type

vi. Time and space partitioning per ARINC-653

vii. Symmetric and asymmetric parallel processing

The technical approach shall include the expected chiplet performance with respect to the requirements

(including minimum requirements and goals) stated in Attachment A-1, including at a minimum but not limited to:

i. Processing throughput

ii. Memory and I/O bandwidth

iii. Power dissipation

iv. Power scalability

v. Radiation tolerance

vi. Fault tolerance

vii. Reliability

viii. Thermal management

Analysis shall be provided to justify the claimed expected performance, and any underlying assumptions shall be stated. For those areas where proposed chiplet performance exceeds contract requirements, address whether or not they are appropriate for inclusion as Contractor Proposed Enhancements

(Attachment B), as described in the general instructions above.

The technical approach shall also provide a description of the HPSC chiplet evaluation board, including at a minimum, but not limited to:

i. Detailed block diagram

ii. Description of I/O interfaces

iii. Concept of operation

The technical approach shall provide a description of the HPSC chiplet emulator, including at a minimum, but not limited to:

i. Development approach

ii. Theory of operations

iii. Expected performance (i.e., effective throughput vs expected chiplet hardware)

iv. Capabilities for hardware architecture evaluation

v. Capabilities for support software development

The technical approach shall provide a description of the development process for the HPSC chiplet, system software, emulator, and evaluation board. Descriptions shall include but not be limited to:

i. Development steps and flow (including interactions with the foundry)

ii. Key tests, analyses and other milestones that gate the development process

iii. Development tool chain used

iv. How assured integrity objectives will be met

The options detailed in the HPSC SOW and requirements document are technical enhancements to the baseline chiplet. The technical approach shall provide a description of how the offeror proposes to implement each of the options. Descriptions shall include, but not be limited to:

i. Block diagrams depicting how options would be integrated with the baseline HPSC chiplet, system software, and evaluation board

ii. Listing of the intellectual property (IP) cores to be utilized (where applicable)

iii. Expected die size increases due to implementation of options

iv. Any expected changes to system software (reference section b above) due to implementation of options

v. Any expected changes to chiplet operation, chiplet performance, evaluation board, and emulator

(reference sections c-f above) due to implementation of options

The technical approach shall include a requirements compliance and verification matrix. The offeror shall describe the extent to which the proposed approach meets or exceeds each of the stated requirements, and how compliance is achieved. For requirements stating threshold and goal, the compliance shall specify whether the proposed approach meets the threshold or the goal. The offeror shall also include the method by which each of the requirements is verified (i.e. test, demonstration, analysis, or inspection).

The offeror's management approach shall include management processes necessary to successfully develop the HPSC in a timely and cost effective manner.

The management plan shall provide a description of interrelationships of technical management, business management, and subcontract management. Include an organizational chart that identifies where this contract fits within the corporate structure and identify all leadership positions by title.

Describe the authority and responsibility of Project Manager and his/her control over essential resources/functions necessary to accomplish the work, including authority and responsibility over subcontract resources. Additionally, describe the process to be followed by the Project Manager in obtaining decisions beyond his/her authority and in resolving priority conflicts for resources/functions not under the Project Manager’s direct control such as personnel, finances, and facilities.

Corporate resources are to be defined in terms of staffing, corporate support, facilities and equipment, including relevance, sufficiency, and availability (either internal and/or external to the contractor) for use on this project. The offeror shall describe the corporate resources available (including significant subcontractors) to enhance technical, operational, and management performance. The offeror shall describe the breadth of the offeror's corporate resource base beyond those of the immediate staff (as applicable to the HPSC project).

The offeror shall describe its strategy for using (or not using) significant subcontractors. The definition of significant subcontractor is provided in the cost volume instructions. However, for this section the offeror shall consider the foundry services provider as a significant subcontractor (even if these services are not acquired via subcontract). If significant subcontractors are proposed, identify their interfaces to your organizational structure and provide: 1) the basis for selection of the subcontractor, 2) the nature and extent of the work to be performed by the subcontractor, including responsibilities and primary functions (note WBS elements) 3) the benefits of these arrangements to the Government, and 4) methods of management and reporting to GSFC of subcontractors' financial and technical plans and performance.

The offeror shall discuss its plans for addressing any problems that arise as a result of the proposed organization structure or poor and/or non-performance of subcontracted portions of the contract.

The offeror shall describe up to 5 most important positions considered critical to meet the requirements of the contract. The descriptions shall include the rationale for identifying these positions as critical.

The descriptions shall also include a list of the qualifications associated with each position. The list shall include the position title, the reporting relationship within the organizational chart, summary of duties and responsibilities, and minimum education and minimum experience qualifications required for the position. The offeror shall also provide the expected level of effort of the identified critical personnel on this contract.

The offeror shall identify the approach for implementing an Earned Value Management (EVM) system consistent with the Statement of Work (SOW) for the Development of the High Performance Spaceflight

Computing (HPSC) Processor Chiplet (reference SOW, section 4.1.3 EVM).

The offeror shall provide a plan for commercialization, making the HPSC broadly available to the US civilian and military aerospace community, and other US industries (where applicable). This plan shall address the productization of the HPSC chiplet and likely distribution channels.

All Offerors, except small businesses, shall complete the portion of the instructions under Small

Business Subcontracting specific to Small Business Subcontracting Plans. Small businesses are not required to submit Small Business Subcontracting Plans; however, small businesses shall indicate the amount of effort proposed to be done by a small business either at the prime level or at the first tier subcontract level.

All Offerors (small businesses and other than small businesses) shall respond to the Commitment to

Small Business Program.

(a) Small Business Subcontracting Plan

(1) This solicitation contains FAR clause 52.219-9 (Deviation)--Alternate II, “Small Business

Subcontracting Plan”. The Plan described and required by the clause, including the associated subcontracting percentage goals and subcontracting dollars, shall be submitted with your proposal.

(2) The Contracting Officer’s assessment of appropriate subcontracting goals for this acquisition, expressed as a percent of the TOTAL CONTRACT VALUE basic and all options combined is as follows:

Small Businesses (SB) 8.0%

Small Disadvantaged Business (SDB) Concerns 5.0%

Women-Owned Small Business (WOSB) Concerns 4.0%

Historically Black Colleges and Universities (HBCU)/

Minority Serving Institutions (MSI)

0.5%

HUBZone Small Business (HBZ) Concerns 0.8

Veteran-Owned Small Business (VOSB) Concerns 3.6

Service-Disabled Veteran-Owned Small Business (SDVOSB)

Concerns

1.7%

(3) The numbers above reflect the Contracting Officer’s assessment of the appropriate subcontracting goals to be achieved at the completion of contract performance. When appropriate, an Offeror may discuss plans to phase-in small business concerns, explaining the rationale for the phase-in schedule. If the Offeror anticipates that it will not meet the proposed small business goals by the time the Offeror submits its first Individual Subcontracting Report (ISR) for this effort as required by FAR clause

52.219-9 (Deviation), Small Business Subcontracting Plan, the Offeror should discuss its approach to include a timeline for meeting these goals and the associated rationale.

(4) Offerors are encouraged to propose goals that are equivalent to or greater than those that the

Contracting Officer has recommended. However, Offerors shall perform their own independent assessments of the small business subcontracting opportunities and are encouraged to propose goals exceeding the recommended goals where practical.

(5) The Plan that the Offeror submits with its proposal shall be incorporated in Section J as Attachment

E in the resulting contract. The requirements in the Plan shall flow down to first tier large business subcontracts expected to exceed $700,000 (or $1,500,000 for construction of a public facility).

Although these first tier large business subcontractors are encouraged to meet or exceed the stated goals, NASA recognizes that the subcontracting opportunities available to these subcontractors may differ from the recommended goals in the solicitation based upon the nature of their respective performance requirements.

(6) Offerors are advised that a proposal will not be rejected solely because the Plan submitted does not meet the NASA recommended goals listed in paragraph (a) (2) above in terms of percent of the TOTAL

CONTRACT VALUE basic and all options combined. NASA will consider the amount of work that the prime contractor plans to perform when determining whether a subcontracting plan is acceptable.

Offerors shall discuss the rationale for any goal proposed that is less than the Contracting Officer’s recommended goal in any category. In addition, the Offeror shall describe the efforts made to establish a goal for that category and what ongoing efforts, if any, the Offeror plans during contract performance to increase participation in that category.

(7) In addition to submitting a Small Business Subcontracting Plan in accordance with the Section I, FAR clause 52.219-9 (Deviation)--Alternate II, Offeror’s shall complete Exhibit 11-C, SMALL

BUSINESS SUBCONTRACTING PLAN GOALS, which provide a breakdown of the offeror’s proposed goals, by small business category, expressed in terms of both a percent of the TOTAL

CONTRACT VALUE and a percent of TOTAL PLANNED SUBCONTRACTS. Offerors shall show the proposed subcontracting goals for the basic contract requirement and each option separately.

(NOTE: FOR PURPOSES OF THE SMALL BUSINESS SUBCONTRACTING PLAN, THE

PROPOSED GOALS SHALL BE STATED AS A PERCENT OF TOTAL SUBCONTRACTS, NOT

AS A PERCENT OF THE TOTAL CONTRACT VALUE, REFER TO THE BELOW EXAMPLE)

Example of Subcontracting Goals as expressed in both the Total Contract Value and Planned

Subcontract Value for a Total Contract value of $100M and planned subcontract value of $50M.

Column A Column B Column C

Category Percent of

Total Contract

Dollar

Value

Percent of

Subcontracting

Value

Small Business (SB) Concerns 25 percent $25,000,000 50 percent

Other than Small Business Concerns N/A $25,000,000 50 percent

Total Dollars to be Subcontracted N/A $50,000,000 100 percent

The following small business subcategories do not necessarily add up to the percentage and dollar amount in the “Small Business Concerns” category above, since some small businesses do not fall into any of the subcategories below, while others will fall into more than one subcategory below.

Small Disadvantaged Business (SBD)

Concerns

5.5 percent $5,500,000 11 percent

Women-Owned Small Business

(WOSB) Concerns

9 percent $9,000,000 18 percent

Historically Black Colleges and

Universities (HBCU)/Minority

Serving Institutions (MSI)

1.5 percent $1,500,000 3 percent

HUBZone (HBZ) Small Business

Concerns

1.5 percent $1,500,000 3 percent

Veteran-Owned Small Business 2.5 percent $2,500,000 5 percent

(VOSB) Concerns

Service-Disabled Veteran-Owned

Small Business (SDVOSB) Concerns

1.5 percent $1,500,000 3 percent

The offeror proposes small business subcontracting goals as a percentage of the Total Contract Value in column A. Then based on the $100 million Total Contract Value, the resulting statement of dollars that the offeror would include in the Subcontracting Plan, as required by paragraph (d)(2) of FAR clause

52.219-9 (Deviation)—Alternate II, would be as indicated in column B.

However, the Small Business Subcontracting Plan shall also express goals as a percent of total planned subcontracts. Assuming total subcontracting of $50M, the resulting percentage goals, expressed as a percent of total subcontract dollars, and which would be stated in the Small Business Subcontracting

Plan as required by paragraph (d)(1) FAR clause 52.219-9 (Deviation)--Alternate II would be recorded in column C.

(b) Commitment to the Small Business Program

(1) All Offerors must briefly describe the work that small businesses will perform to meet the stated requirements. Proposals shall also identify any work to be subcontracted that is considered “High

Technology.” “High Technology” is defined as research and development efforts that are within or advance the state-of-the-art in technology discipline and are performed primarily by professional engineers, scientists, and highly skilled and trained technicians or specialists.

(2) If the subcontractor(s) is known, Offerors shall describe the work that each subcontractor will perform and specify the extent of commitment to use the subcontractor(s) (enforceable vs. non-enforceable commitments). (Small Business Offerors shall provide this information to the extent that subcontracting opportunities exist in their approach to performing the requirement.)

(3) All Offerors shall provide information demonstrating the extent of commitment to utilize small business concerns and to support their development. Information provided shall include a brief description of established or planned procedures and organizational structure for Small Business outreach, assistance, counseling, market research and Small Business identification, and relevant purchasing procedures. (For Other than Small Business Offerors, this information shall conform to applicable portions of your submitted Small Business Subcontracting Plan. Small Business Offerors shall provide this information to the extent subcontracting opportunities exist in their approach to performing the requirement.)

(4) The NASA Mentor-Protégé Program is designed to incentivize NASA large prime contractors to assist a Small Disadvantaged Business, a Women-Owned Small Business, a HUBZone Small Business, a Veteran-Owned or Service-Disabled Veteran-Owned Small Business, or Historically Black College and University/Minority Serving Institution in enhancing their capabilities to perform NASA contracts and subcontracts, foster the establishment of long-term business relationships between these entities and

NASA large prime contractors, and increase the overall number of these entities that receive NASA contract and subcontract awards. Provide a description of the prime’s planned participation in the

NASA Mentor Protégé Program.

L.7 GSFC 52.215-221 COST VOLUME INSTRUCTIONS (MAR 2016)

The Federal Acquisition Regulation (FAR) requires Contracting Officers to purchase supplies and services from responsible sources at fair and reasonable prices. It is expected that adequate price competition will be obtained under this solicitation so that submission of certified cost or pricing data is not required pursuant to FAR 52.215-20, Requirements for Certified Cost or Pricing Data and Data

Other Than Certified Cost or Pricing Data--Alternate IV. The term “data other than certified cost or pricing data” is defined at FAR 2.101.

(a) Instructions

An important prerequisite for the award of the contract is the Prime Offeror must have an accounting system that has been determined adequate by the cognizant administrative office for accumulating and reporting incurred costs prior to contract award. While these proposals are not required to be cost certified, they are to be in sufficient detail to allow direct and indirect rate verification and audit of selected costs. The

Cost Volume proposal should be prepared in a manner consistent with your current accounting system.

The contract resulting from this solicitation is potentially subject to Cost Accounting Standards (CAS) compliance, unless the Offeror qualifies for a CAS exemption. Offerors shall determine CAS applicability (full or modified CAS coverage) for its proposing business unit based on applicability criteria. If full CAS coverage applies to the Offeror and it has not submitted a Disclosure Statement that has been deemed adequate by its cognizant contract administration entity (typically DCMA), then a

Disclosure Statement shall be prepared in support of the Offeror’s proposal. While CAS Disclosure

Statements are not evaluated by NASA, their evaluation must be coordinated between NASA and the cognizant contract administration entity; as such, the CAS Disclosure Statement shall be submitted to

NASA with the proposal in the Offer Volume.

The required format for other than certified cost or pricing data is for evaluation purposes. The cost for any resultant contract will be awarded on the basis of the successful Offeror's normal estimating and/or accounting system or the system set forth in the CAS Disclosure Statement required by Public Law 100-

679, if applicable. If the Offeror's estimating and/or accounting practice differs from the required Cost

Volume proposal format, the costs should be computed in accordance with the Offeror’s normal accounting and estimating procedures and provide your rationale for the format adjustments.

Direct labor must be estimated on the basis of productive effort. Productive effort is the estimated number of hours required to perform the work. Vacations, holidays, sick leave, and any other paid absences shall not be cited as direct labor, but shall be separately identified and priced or included in indirect costs.

Final monetary extensions in the Cost Volume proposal should be expressed as the closest whole dollar amount, with cents omitted.

Duty charges, if any, shall be included in the cost, regardless of whether or not duty free certificates are obtained.

A "subcontract" is any contract, purchase order, material order, interorganizational transfer, etc. that is a direct cost to this acquisition. The Offeror shall provide sufficient detail to support and explain all costs proposed. For the purposes of the Cost Volume, a Significant Subcontractor is defined as a subcontractor expected to exceed 10% of the Prime Offeror’s proposed contract value (Base plus Option Periods). A proposed Significant Subcontractor shall complete and Exhibits 2-A, 3 through 8 and provide the supporting information that is requested from the Prime Offeror. Prospective Significant Subcontractors may submit proprietary cost data, under separate cover, directly to the Government no later than the date and time specified in the instructions for receipt of proposals for this RFP.

The Cost Volume exhibits provided in the RFP are in Portable Document Format (PDF). Prior to completing the Cost Volume exhibits, Offerors shall convert the .PDF file to Microsoft Office Excel either using Adobe Acrobat DC or manually recreate each individual exhibit. (Note: Previous versions of Adobe Acrobat will not properly convert the PDF file to the Excel format.) To convert the exhibits using Adobe Acrobat DC use the following steps:

1) Open the Cost Volume exhibits .PDF file in Adobe Acrobat DC.

2) Click on the Export PDF tool in the right pane.

3) Choose spreadsheet as your export format, and then select Microsoft Excel Workbook.

a. Under the “Save As XLSX Settings” window, ensure that following selections are made:

i. Under Excel Workbook Settings ensure “Create Worksheet for each Page” is selected.

ii. Under Numeric Settings ensure “Detect decimal and thousands separators using regional settings.”

iii. Under Text Recognition Settings ensure “Recognize text if needed” is selected.

1. Ensure “English” is the selected language.

b. Click “OK”

4) Click Export.

5) Name the Excel file and save it in a desired location.

Offerors, including proposed Significant Subcontractors, shall provide one separately packaged copy of their Cost Volume proposal marked “Enter correct RFP number/NASA Proposal Evaluation Material,” which the Government may use for audit support purposes.

All pricing and estimating techniques shall be clearly explained in detail (projections, rates, ratios, percentages, factors, etc.) and shall support the proposed costs in such a manner that audit, computation, and verification can be accomplished. All past actuals shall show the periods of time and costs in detail when used as a basis for estimating the proposed costs.

In order to establish the reasonableness and realism of the proposed costs, and the extent to which costs reflect performance addressed in the Mission Suitability Volume proposal, each Offeror, including proposed Significant Subcontractors, shall submit the other than certified cost or pricing data described in Section (b) below.

(b) Cost Volume Proposal Format

(1) RATE SUBSTANTIATION

The escalation proposed for labor must be stated along with the actual escalation experienced in the last three years. Provide a statement of rationale, including the derivation, for the proposed escalation rates.

If escalation is not proposed, explain why. The Offeror shall also discuss the rationale for any escalation proposed for the other cost elements.