80JSC021SSTIII_DRFP Questions_Answers 1-31-22 - Final.pdf

80JSC021SSTIII - DRFP Questions and Answers

Question # Type Draft RFP Reference Comment or Question Answer

1 General All areas Please add page numbers to make it easier to provide references for questions.

Page numbers have been added to the final RFP.

2 General File: JSC Virtual Tour Information Which labs in this file are relevant to the SST III contract?

The JSC Virtual Reality Lab is relevant to SST III. The other labs included on this file were provided to give Industry an idea of the various facilities located at JSC.

3 General File: JSC Virtual Tour Information Are there any other labs relevant to SST III not included in this list?

Yes, those labs are identified in Section G.3 of the DRFP. This clause will be updated with the final RFP to include additional relevant labs such as the Autonomous Control Spacecraft Software Lab & Gateway Software Verification Laboratory.

4 Section B Section B.5, Section L.23.5 Cost & Price Factor – Vol III

Will the rates for CPFF, required in Table B.5a, be applied to the IDIQ hours provided in Table L.7a? Or should the rates for FFP, required in Table B.5b, be applied to the Table L.7a hours?

The hours identified by the Government in Table L.7a are for total hours estimated to be expended on the SST III contract. However, for proposal purposes, and based on historical data, the hours identified in Table L.7a are associated with cost reimbursable work only. Hence, the rates applied against those hours MUST MATCH the rates proposed in Section B.5, Table B.5a: CPFF Rates per Hour. The Government will further clarify the RFP Section L instructions regarding Table L.7a.

5 Section B Section B.5, Table B.5a

Please confirm that offerors may modify Table B.5a to account for annual, varying rates to be applied to the different types of non-labor costs in accordance with an offeror’s disclosed practices.

Yes, Offerors may modify Table B.5 only in regards to NLR rates. The Offeror is to list all applicable indirect rate(s) associated with any Non- Labor Resources (NLRs) proposed. In addition to identifying the proposed indirect rate(s), Offerors are to identify the applicable base to which each proposed indirect rate is applied. The indirect rate(s) may vary in each Contract Year, but MUST MATCH the Contract Year indirect rates identified in the EPM templates. All indirect rates proposed must be in accordance with an Offeror's disclosed accounting and estimating practices.

6 Section B, H Section B.5, Section H.9

Section B.5 and Section H.9 appear to be in conflict. Please confirm that offerors may apply indirect rates to non-labor (material and ODCs) costs in accordance with their disclosed practices.

Section H.9 clause will be removed in the Final RFP. Offerors are not restricted to applying any indirect rate applicable to any specific non-labor cost in accordance with the Offeror's disclosed accounting and estimating practice, as well as, applicable Disclosure Statement and Cost Accounting Standards.

7 Section B Section B.9

The discussion of the guaranteed minimum states that the values given are based on dollars. Do the dollar values include fee or profit, or is fee or profit to be added to these dollar amounts?

The dollars identified in Section B.9 are total Task Order dollars and thus include fee or profit dollars.

8 Section C Section C - SOW 4.0 System Engineering and Integration

What tools and processes are used to catalog, publish and store system documentation and requirements?

The tools and processes are dependent on the Program being supported.

Project will provide the repository tools as needed. For example, some of the commonly used tools consist of JRIA, Git/GitLab, and DOXYGEN.

9 Section C Section C - SOW 5.2.1 Trick Simulation Environment

What resources (servers, workstations, other infrastructure) are currently maintained in the Trick development network and computer laboratory?

Resources are dependent on customer task orders and change with customer requirements. NASA provides computer assets and infrastructure to meet task order requirements. A typical computer platform for simulation development is a mid-level workstation with 8-processor Intel core and current NVIDIA graphics card.

10 Section C Section C - SOW 6.1 GFE Software Development and Software Verification Labs

What resources (servers, workstations, other infrastructure) are currently maintained in the GFE Software Development and Software Verification Labs?

The resources maintained in the GFE are: Autonomous Control Spacecraft Software Lab (ACSSL) -This facility contains hardware in the loop (HITL) test and evaluation environments and supporting Linux workstations and servers and used for the development of Gateway flight software. The lab consists of four dual string hardware in the loop development rigs with connected workstation. Each rig is two flight computers, two simulation servers, and associated flight like and lab network equipment.

The lab contains 16 workstations. GFE Software Verification Lab (GSVL) - This facility is used to integrate, test, verify, and validate Gateway Government Furnished Equipment (GFE) software prior to formal testing in the GRAIL. Current plans are to have 20 servers and the workstations total by 10/1/2022. The lab is still in development, so the equipment is subject to change as we build out the lab.

11 Section C Section C - SOW 3.0 Scope Please provide information on the target operational platforms for each identified software subsystem.

The target platform for each software is project or program specific and will be identified in the Task Order or project plan. NASA provides all computer resources required for execution of SST III task orders.

12 Section C Section C - SOW 3.0 Scope What is the delivery interface for each software subsystem?

Software will typically be developed on NASA systems and the requirements for delivery will be defined in the associated Task Order. In the event a Contractor-owned system or server is used, the Task Order will define the delivery interface.

13 Section F Section F.3

This paragraph indicates that services are to be performed at JSC, the contractor’s facility, and other locations. We can find no mechanism for proposing separate rates for work performed onsite at JSC and offsite at the contractor’s facility (or another facility). Does the government intend for us to propose separate onsite and offsite rates? Are there separate onsite and offsite rates on the current SST II contract?

No seperate onsite and offsite rates are not required for Section B of this contract. The Excel Pricing Model (EPM) will have a worksheet tab ("OHT") that allows an Offeror to identify and propose various overhead and fringe rates by using multiple "OHT" worksheets. Offerors are free to propose any indirect rate (eg onsite or offsite indirect rates as part of their SLC rate development) that is applicable in accordance with the Offeror's disclosed and established accounting and estimating systems, as well as, in accordance with their Management and Technical approach.The rate structure of the current incumbent contractor will not be disclosed by the Government.

14 Section G Section G.3

Can the government provide a list of hardware inventory managed by SST III in the various facilities (Flight Science Laboratory, Orion Test Dev Lab, xEMU Software Development Laboratory, Autonomous Control Spacecraft Software Lab, etc.)?

The descriptions for the various facilities listed in Section G.3 have been expanded in the final RFP to provide additional clarity. For example, the Autonomous Control Spacecraft Software Lab (ACSSL) contains hardware in the loop (HITL) test and evaluation environments and supporting Linux workstations and servers and used for the development of Gateway flight software. The lab consists of four dual string hardware in the loop development rigs with connected workstation. Each rig is two flight computers, two simulation servers, and associated flight like and lab network equipment. The lab contains 16 workstations.

15 Section G Section G.3, Installation Service Facilities Please identify the labs relevant to SST III in Buildings 15, 46, and 361. (Marked “TBD” in this section).

In the final RFP, Buildings 15 and 361 have been removed from list in Section G.3. Additionally, the Engineering Directorate computational environment (aka- FSL, Flight Science Laboratory) is now listed under Building 46 rather than Building 16.

16 Section J Attachment J-17 - Installation Accountable Government Property List

How many seats will be available for contractor personnel on-site?

There are 140 seats available for Contractor personnel on-site at Johnson Space Center.

17 Section J Attachment J-18 - Proposed Innovations and Efficiencies

Please be more specific with the information required for each innovation and efficiency.

Section L.23.2 TA1 has now been revised in the final RFP to reflect a more specific innovations and efficiencies plan.

18 Section J Attachment J-4 – Standard Labor Category Descriptions (SLC)

In Attachment J-4, SLC the Descriptions and Guidelines are partially displayed. Will NASA provide a table which displays all Job Descriptions and Guidelines?

The complete list of the SLCs is in attachment J-4. A revised list will be included in the final RFP which incorporates one additional SLC, Engineering Assistant.

19 Section L Section L.19 (d)

The file naming convention in this section (Prime Offeror name – solicitation number Cost-Price Volume.xlsx) seems to differ from the file naming convention provided in Section L.23.5(d)2 for the EPM (EPM-Company Name.xls). Please confirm that offerors should use both naming conventions.

The file naming convention in Section L.23.5(d)2 has been modified to match Section L.19(d).

20 Section L Section L.21: Proposal Arrangement, Page Limitations, Copies, and Due Dates, Table L.2

Please be specific regarding what is in or out of page count, and what the page limitations are for each required section of the proposal. For example, are resumes in or out of the 85-page limit for Volume I?

Table L-2 will be updated in the final RFP to identify what is included and not included. Resumes are not included in the page limit.

21 Section L Section L.21: (b)

We believe the 85 page limit for the Mission Suitability volume is too high – it is higher than the recently submitted JETS II volume, which has a value more than 10 times the anticipated value of SST III. We believe a high page limit provides an undue competitive advantage to the incumbent contractor. We recommend the government reduce the page count to 50-60 pages

NASA has significantly reduced the number of pages from the last SST II solicitation. The Government anticipates that the page limit is appropriate for the content of work that needs to be discussed and understood. Therefore, the page count will remain at 85 pages.

22 Section L Section L.21: Proposal Arrangement, Page Limitations, Copies, and Due Dates, Table L.2

The small business utilization portion of Volume I is not specifically excluded from page count. Recommend it be specifically excluded.

Small business utilization is not included in the page count. See Table L.2

23 Section L Section L.21: Proposal Arrangement, Page Limitations, Copies, and Due Dates, Table L.2

Please clarify whether consent letters are required for each priced subcontractor or just those for which we submit past performance contracts.

Consent letters for all entities proposed to work on SST III are required.

24 Section L Section L.21: Proposal Arrangement, Page Limitations, Copies, and Due Dates, Table L.2;

Section L.23.4: Past Performance - Volume II

Recommend past performance consent letters be specifically excluded from page count

Table L.2 will be updated to reflect PP consent letters are excluded from page count.

25 Section L

Section L.21: Proposal Arrangement, Page Limitations, Copies, and Due Dates, Table L.2;

Section L.23.5: Cost and Price Factor - Volume

III

Please identify how each TO should be priced–FFP or CPFF.

Each Sample Task Order (STO) is to be priced as a Cost Reimbursable STO utilizing the appropriate CPFF rates. The STOs in Attachment L-1 and Section L.23.5 will be updated to reflect they are CPFF STOs on the RFP.

26 Section L

Section L.21: Proposal Arrangement, Page Limitations, Copies, and Due Dates, Table L.2;

Section L.23.6: Responsibility Considerations - Vol IV

Recommend no page limit for Volume IV due to the nature of the content contained within this volume.

Volume IV will be updated in the final RFP to include no page limit.

27 Section L Section L.23.4(a)

In subparagraph (a), the instructions for the Past Performance Factor discuss the prime contractor and proposed major subcontractors, but not other subcontractors. However, in subparagraph (h), the instructions address having other subcontractors and other entities submit the past performance questionnaire. Does the government intend to evaluate the past performance of minor subcontractors, or only the prime and major subcontractors?

In accordance with L.23.4(a) and (h), we intend to evalute the prime, major subcontractors, the proposed program manager, and any other organizational entity (parent or affiliated company, division(s), business units, or segments of your company), which is considered to provide meaningful involvement in contract performance.

28 Section L Section L.23.2(c)(4), Table L.4, Cumulative Government Resource Estimate

Please clarify if the Government will provide Total WYE information in this table?

Yes, the Government will be providing WYE information in Table L.4, Cumulative Government Resource Estimate, as part of the Final RFP.

That data will be as follows: TO 1 is 17 WYE, TO 2 is 23 WYE, and TO 3 is

13 WYE.

29 Section L Section L.23.2 - Table L.4

Table L.4, which addresses the Government Resource Estimate for the sample task orders, still shows TBD. Please provide this information as soon as possible so we are able to scope the sample task orders.

See answer to Question 28.

30 Section L Section L.23.4, Past Performance Factor – Volume II

Please clarify number of citations allowed for submission. Include any and all citation with explanatory remarks.

31 Section L Section L.23.4 Please clarify whether we are to submit information on up to three past contracts EACH for the prime and any major subcontractor, or a TOTAL of three past contracts.

A maximum of 3 contract references for offeror and a maximum of 3 contract references for each major subcontractor.

32 Section L Section L.23.5 Cost & Price Factor – Vol III No Cost/Price template or EPM was provided as part of the Draft RFP package. Is that an oversight?

A copy of the EPM will be released with posting of these questions. There will be a training session during the Pre-Proposal conference and an opportunity for comments and questions at that time.

33 Section L Section L.23.5 Cost & Price Factor – Vol III Fixed Fee: May offerors propose more than one fixed fee rate based on element of cost (e.g. Labor vs Non-Labor Material and ODCs)?.

Offerors may propose more than one fee rate based on element of cost.

As a reminder, there are restrictions on fee rates allowed in accordance with FAR 15.404-4(c)(4)(i).

34 Section L Section L.23.5 Cost & Price Factor – Vol III Attachment L-6-Excel Pricing Model (EPM) Workbook is not provided as part of the Draft RFP package. Will NASA provide Attachment L-6 to review for questions?

See Answer to Question 32.

35 Section L Section L.23.5(b)(1) Direct Labor Rates and Indirect Rate Historical Data and Analysis

Will the government consider expanding the exclusion for 3 years of historical direct labor and/or indirect rate data for rates included in a Forward Pricing Rate Proposal (FPRP) submission to DCMA?

No. Three (3) years of historical indirect rate information will be required regardless of the type of rate support being utilized (e.g. an FPRA, FPRR, or FPRP). Moreover, an FPRP rate specifically will not relieve an Offeror from the requirement to provide specific and detailed indirect cost pool and base information for all years covered under an FPRP and for all years not covered by an FPRA or FPRR.

36 Section L Section L.23.5(b)(3) Cost & Price Factor – Vol III

For any indirect rate(s) OR Contractor Fiscal Years (CFYs) not included in a FPRA or FPRR used in this proposal, the Offeror shall complete the Overhead Template (OHT) and the General and Administrative Template (GAT) for those rates and/or CFYs. Does this requirement include rates utilized from FPRAs/FPRRs for pricing beyond the term of the FPRAs/FPRRs?

Yes. Example: If the FPRA/FPRR covers CFY A, B, and C no additional specific and detailed pool or base information is required (although an Offeror is not prohibited from providing such information). However, specific and detailed pool and base information is required for CFYs D thru F -- even if it is the Offeror's standard estimating procedure to straight-line the FPRA/FPRR rate from CFY C to CFYs D thru F.

37 Section L Section L.23.6(g) Table, Column 2 Vol. IV Subcontractor Listing Table: Column 2 header is cut off.

Please update table.

Table will be updated in the final RFP.

38 Section L Attachments Attachment L-1 Does the government intend to publish the Government Resource Estimates for the sample task orders?

See answer to Question 28.

39 Section L Attachments Attachment L-1, Sample Task Order 1 Can NASA provide additional information on the Simplified Wrapper Interface Generator (SWIG) dependency within Trick?

SWIG is an open source tool found at http://swig.org. SWIG is a software development tool that connects programs written in C and C++ with a variety of high-level programming languages. Trick uses SWIG to build the interface code that glues C/C++ math models with our python based input processor. Trick’s input processor reads a python based input file when the simulation is initialized. SWIG generates python variables names which correspond to the C/C++ math model variable names.

SWIG generates the bridge code that connects the python math model variables to the C/C++ math model within the sim.

The Trick development team maintains a set of configuration files to use with SWIG. These configuration files tell SWIG how to handle C and C++ classes and structures, variables, arrays, pointers, class methods and stand alone functions. The Trick development team maintains code that pre-processes header files before the headers are sent through SWIG processing. Some C/C++ code constructs are known to give SWIG difficulty, Trick preprocessor mitigates these situations before they cause errors. Finally the Trick development team maintains code which calls SWIG to process each math model header in a simulation.

40 Section L Attachments Attachment L-1, Sample Task Order 1 What is the function of SWIG? See answer to Question 39.

41 Section L Attachments Attachment L-1, Sample Task Order 1 Please clarify the deliverables and schedules, references, and surveillance plan for STO 1.

Deliverables are detailed in the STO 1 technical requirements. Schedule is the STO 1 period of performance. All reference material is available through the SST III Technical Library. The surveillance plan is not required to demonstrate technical understanding for STO 1.

42 Section L Attachments Attachment L-1, Sample Task Order 2 What software development, configuration management, and other tools are used to develop and maintain the current SST software subsystems?

The offeror can define the tools needed to accomplish Sample Task Order 2.

43 Section L Attachments Attachment L-1, Sample Task Order 2 Please provide documentation on “EA WI-025 and SSET” policies referenced in the Task Definition as required to follow for the class A safety-critical project?

Technical library will be updated to include this information.

44 Section L Attachments Attachment L-1, Sample Task Order 2

Can the government provide documentation on “Core Flight Executive/Core Flight Software (CFE/CFS) architecture” referenced in the Technical Requirements for the Software Development Plan (SDP)?

Reference the Open Source Software section of the Technical Library.

45 Section L Attachments Attachment L-1, Sample Task Order 2 Can the government provide documentation for “EA WI-035 Software Project Management and Development” listed in References?

We provide the EA work instructions for each Task Order. Technical library will be updated to include this information.

46 Technical Library SSTIII Technical Library.pdf Technical Document Links

Can the government provide an updated link or document for “JPR 7150.1 JSC Software Engineering Policy”? Link provided in Technical Library returns error message.

The Technical Library will be updated to reflect the correct link.

47 Technical Library SSTIII Technical Library.pdf Technical Document Links

Can the government provide an updated link or document for “NASA-STD-8739.8 Software Assurance and Software Safety Standard”? Link provided in Technical Library returns “Page not found” message.

The Technical Library will be updated to reflect the correct link.

DRFP Q&A - SST III