Questions and Answers Batch 4.pdf

Question # Question Government Response

LCRNS.3.0620 – The Lunar Relay Service shall have the ability to provide the messages defined in the LunaNet Interoperability Specification, commensurate with Table 3-11 and Table 3-

12. QUESTION: In Exhibit D this requirement is marked applicable for IOC-A, B, and C. However, LCRNS SRD/LNIS compliance matrix (Table C-1 of the SRD) indicates that Messaging Services (defined in LNIS Section 3.1.3) are not applicable for any of the IOC phases. We respectfully request that NASA amend the RFP to resolve this inconsistency by updating Exhibit D to show these requirements as N/A.

Messaging Services are required in IOC per LNIS Table D-2. LANS / AFS Messages, PNT and Network only Lunar Relay SRD has been updated and posted in the Near Space Network (NSN) Services, elibrary on Sam.gov.

Does the “Lunar Reference System (TBR)” refer to a fixed coordinate locked to the lunar surface or is it defined with respect to the Libration model?

The LRS definitions will be further refined as part of the validation phase. The lunar reference system definitions will potentially include both body fixed, and relative.

The Contractor shall comply with Near Space Network configuration management guidelines (e.g., network freeze) at the time of supporting nominal and critical operational services.”

Where are the “configuration management guidelines” provided?

NSN will communicate the configuration managment guidance in accordance with the need when it occurs during operations. For example, NSN may request a contractor to freeze network configuration for events such as pre-launch testing and launch support.

The Contracting Officer shall unilaterally determine whether the Contractor met the Performance Requirements for each Operational Services Task Order. Upon completion of the task, the Government will descope the remaining unscheduled and/or unused minutes. QUESTION: If the Government descopes any remaining unused minutes, will the contractor still receive payment for scheduled minutes authorized in the Task Order authority to proceed? Please clarify the payment structure in the event of descoped services.

The Government will pay for used minutes under each operational service task order in accordance with the pricing structure defined in the RFP.

The "Rights in Data - Special Works" clause of this contract applies to the following aspects (or items):

Any data requested by the Government for any legitimate government use.

QUESTION: Please clarify if this will apply to data first produced in the performance of this contract, as this is the standard repeated throughout the RFP.

Please confirm this will not apply to technical or operational data and clarify what is meant by “any data requested”.

Clause H.8 "GSFC 52.227 93 APPLICABILITY OF RIGHTS IN DATA – SPECIAL WORKS (MAR 2008)" is revised to replace the words "Any data requested by the Government for any legitimate government use" with "Any data requested by the Government as specified in the Task Order." (See Amendment #2)

The SOW Table of Contents references a NASA Security policy on page 39, yet there is nothing there.

Question: would the Government confirm that a NASA Security Policy will be provided to offerors?

The SOW Table of Contents has been updated to remove the NASA Security Policy from

it. This document is listed as a Reference document in the SOW, NPD 2810.1 NASA Information Security Policy. (See Amendment 2)

Question: May the offeror assume per RFP instruction that an 11x17 size foldout counts as 1 page of the technical volume?

No, as indicated in Provision L.19(b)(2), "Electronic foldout pages count as an equivalent number of 8-1/2" x 11" pages." Since an 11 x 17” page is double the size of an 8.5 x 11” page, it would count as two pages.

Are there any EIRP requirements for the AFS/PFS5 signal at this time? The offeror shall clearly document EIRP assumptions in the proposal. Currently, there are no explicit EIRP requirements for AFS/PFS5 signal.

The SOW table 33 does not mention a surface to surface link but LCRNS.3.0010 mentions compliance is needed with the interfaces in Appendix C. One of these is LNSP-User Surface Interfaces (4.1), which deals with surface-to-surface links. Is it required to have a node on the surface of the Moon?

There is no requirement to have a node on the surface of the moon. Table C-1 in the SRD has been updated. The revised SRD has been posted in the Near Space Network (NSN) Services, elibrary on Sam.gov.