SOURCES SOUGHT
A -- MICROWAVE AND COMMUNICATION SYSTEMS BRANCH SURFACE WIRELESS CONCEPTS
- Notice Date
- 9/17/2009
- Notice Type
- Sources Sought
- NAICS
- 334220
— Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
- Contracting Office
- NASA/Goddard Space Flight Center, Code 210.S, Greenbelt, MD 20771
- ZIP Code
- 20771
- Solicitation Number
- NASA-GSFC-RFI-SURFACE-WIRELESS-CONCEPTS
- Response Due
- 11/6/2009
- Archive Date
- 9/17/2010
- Point of Contact
- Bernard L Edwards, Chief Communications Systems Engineer, Phone 301-286-8926, Fax 301-286-1750, Email Bernard.L.Edwards@nasa.gov
- E-Mail Address
-
Bernard L Edwards
(Bernard.L.Edwards@nasa.gov)
- Small Business Set-Aside
- N/A
- Description
- Microwave and Communication Systems BranchSurface Wireless ConceptsRequest for InformationTHIS IS *NOT* A REQUEST FOR PROPOSAL, QUOTATION,OR INVITATION TO BID NOTICE.OverviewNASA is currently developing an architecture and concept of operations for communicationsand tracking on the lunar surface or other small planetary bodies. Under theConstellation Program, there will be vehicles, habitats, science equipment, and EVAcrewmembers on the lunar surface. There is a strong belief that long haulcommunications direct to Earth, or to a lunar relay satellite system, will be traditionalpoint-to-point microwave links at S-Band or Ka-Band, and/or optical communication links. These will be implemented via gateway nodes on the lunar surface, such as a Ka-Band oroptical transmitter on the Altair Lunar Lander. Short range communications betweenvarious entities and the gateway nodes needs to be implemented. Using an internationalstandard, such as something based on the IEEE 802.xx family, appears to be ideal forsurface short range communications. For example, EVA crew members or science packagescould be connected to Altair or a lunar rover via 802.16 or 802.11. Some systems will befixed while others, such as EVA crew members and rovers, will be mobile. The networkwill need to support voice, data / telemetry, and multiple streams of standard and highdefinition video. The Constellation Programs communications architecture is IP basedand that is expected to continue on the lunar surface.Whatever architecture is developed should also be suitable for surface communications atother destinations in the solar system, such as on an asteroid or on a moon of Mars. Withlimited technology development funds, having a destination independent architecture iscritical. Why IEEE 802.xx?NASA would like to use a non-proprietary international standard on the lunar surface. This should help foster communications between NASA provided systems and any commercialor international systems. A robust Media Access Control (MAC) protocol that providesmaximum flexibility would be extremely useful in developing and operating a lunaroutpost.Using a commercial wireless standard should reduce life cycle costs in developing,deploying, and operating lunar surface communication systems. Given the widespreaddeployment of 802.11 networks around the world, it is natural to ask whether 802.11 oranother 802 standard, such as 802.16, could likewise be deployed on the Moon. This isespecially true since NASA doesnt really understand all of the requirements that have tobe met. Starting with a commercial standard forces people to ask if something is reallya requirement if meeting that requirement means moving away from the standard. Thus astandard could also help prevent requirements creep.However, as NASAs concepts mature, it may turn out that it is impossible to meet all ofthe requirements with an off-the-shelf standard. Thus it may be necessary to make minormodifications.Slightly modifying an international standard is perceived to be better,in terms of meeting schedule and reducing life cycle costs, than for NASA to developeverything on its own.An IEEE 802 architecture should also work at other locations in the solar system, such ason a small asteroid or on a moon of Mars. Thus this appears to be a good approach evenif NASAs exploration plans change in the near future.ScenariosThere are two near term scenarios under study:a.Lunar Sortie Scenario:The Lunar Sortie Scenario is very similar to Apollo. This scenario assumes an Altair, anApollo-class rover to provide some mobility, and two simultaneous EVA activities. OneEVA activity will be further away from Altair in the vicinity of the rover and one willbe within the vicinity of Altair. The communication architecture needs to supportmultiple simultaneous links and multi-hopping capability. b.Lunar Outpost Scenario:In the Lunar Outpost Scenario, outpost buildup and science excursions are assumed to begoing on simultaneously. There would be a small habitat zone which would contain a cargohandling unit in addition to a habitat facility and Altair. Multiple small pressurizedrovers would allow the crew to travel further from the habitat zone for scienceexcursion. A surface wireless network would allow the EVA crews to communicate to/throughthe other lunar surface elements. Like before, while not a firm requirement, the EVAProject Office would like direct point to point links between crew members of the EVAteam; in other words, without going through an intermediate node or access point.Requested ResponseThe Microwave and Communication Systems Branch at NASA Goddard Space Flight Centerrequests that interested parties provide inputs and suggestions as to how the IEEE 802.xxfamily could be best used to achieve the communication goals of the ConstellationProgram. Responses may include component or system level concepts including how toimplement IEEE 802 based communication systems in the lunar environment. The branch isinterested in learning of individual component technologies as well as complete systemconcepts. Hardware implementation options need to meet space qualification and radiation exposurerequirements for lunar operations. Discussion should clearly demonstrate capability toimplement design solution in space qualified hardware or define a transition path toqualified hardware and identify associated risks. For lunar operations the proposalshould assume operations over a 10 years period (TBR) and a total exposure of 1.5 kRAD(TBR) of total induced radiation (TID). Discuss how proposed solution mitigates singleevent upset (SEU) effects and provides single event latch-up (SEL) immunity.Cost and schedule are discriminators in the eventual selection of any solution. However,the branch is very interested in learning of potential technology developments that couldbenefit Constellation and the Agency.In addition to the general concept discussed above, the branch requests information onthe following topics. Interested parties do not have to respond all of the followingtopics if they do not apply to their proposed component / technology / system.1.Discuss a minimum cost, minimum risk method of implementing an IEEE 802 wirelessarchitecture on the lunar surface to support Constellation. Discuss the proposed systemand components. Discuss which frequency bands should be used with considerations ofterrain and possible interference from sources on the Earth. Provide Rough Order ofMagnitude (ROM) estimates for Non-Recurring Engineering (NRE) and procurement costs aswell as schedule estimates after receipt of order (ARO). Discuss expected mechanical,thermal, mass and power requirements.2.Discuss a minimum size, weight, and power method of implementing an IEEE 802wireless architecture.Note that this may be different than (1) since the goal here isto minimize SWAP. Provide ROM estimates for NRE and procurement costs as well asschedule estimates ARO.3.Discuss the impact on the total capacity of the 802.xx network if the data ratesof the users differ by more than a factor of 10 among the users. What impact would therebe if some of the users limited signal level adjustments and all the users had more thana factor of 10 data rate needs between the minimum data rates and the maximum data rates?4.Discuss how data can be relayed between an edge user, such as an astronaut on EVAor a small robot with limited communication transmit power, to a larger mobile user andthen the data be relayed back to a central communication node. Discuss the frequency andtiming requirements for all the elements.5.Discuss what modifications could be made to the IEEE 802 family to supportnavigational / tracking needs.This could include making Doppler and range measurements,or being as simple as just providing time of flight measurements. Providing radiometricsto support navigation is not a firm requirement for the lunar surface wirelessarchitecture, but it would be beneficial. Discuss how those modifications would beaccomplished.6.Discuss a method of providing point-to-point ad hoc links without going throughan access point to support the EVA Project Offices desire for crew members to be able tocommunicate with each other without any other infrastructure. While not a firmrequirement, this would be useful in a walk back situation where a team has to walk amaximum of 10 kilometers to get back to Altair or the habitat in case of failure of therover.As an alternative concept, what can be done to support the walk back scenariothat doesnt include custom modifying an 802 protocol?7.How can the IEEE 802 concept be extended to support other NASA missions, notnecessarily on the lunar surface? For example, if NASA developed space qualified IEEE802 radio systems, are there scenarios in space, as opposed to a planetary surface, thatcould make use of the technology?8.Discuss options to incorporate mesh networking or other approaches to extend therange of the network with minimal increases in power or impacts to network reliability.9.Discuss a reconfigurable method of achieving the communication goals of theConstellation Program.The systems should be adaptable and reconfigurable by software /firmware load while on the lunar surface. The branch wishes to consider this option tounderstand the implications of building adaptability to support future technologies thatmay be developed as the program moves forward.This would also be extremely important ifmore than one IEEE 802 protocol is used, such as 802.11 and 802.16. Discuss the proposedarchitecture and components. Provide ROM estimates for NRE and procurement costs as wellas schedule estimates ARO. Discuss expected mechanical, thermal, mass and powerrequirements of this solution.10.Discuss a minimum hardware option that aims to combine the ability to support 802for the lunar surface as well as higher power conventional S-Band microwave links for thedirect to Earth or direct to lunar relay satellite need. There will be platforms, suchas Altair, that will be required to support both functionalities. Discuss the proposedarchitecture and components. Provide ROM estimates for NRE and procurement costs as wellas schedule estimates ARO. Discuss expected mechanical, thermal, mass and powerrequirements of this solution.11.Discuss any other communications and tracking methods, options or technologiesyou believe of benefit to the Constellation Program. Topics of interest include DelayTolerant Networking (DTN) and data routing strategies.Information submitted to GSFC in response to this RFI will be treated as strictlyproprietary unless otherwise indicated. No procurement is planned as a direct result ofthis Request for Information. Information submitted in response to this Request forInformation will be used for Constellation development activities. Parties proposingconcepts of interest to GSFC and Constellation may be invited to submit more detailedinformation or to discuss their concepts further.It is emphasized that this RFI is for planning and information purposes only and is NOTto be construed as a commitment by the Government to enter into a contractual agreement,nor will the Government pay for information solicited.No solicitation exists; therefore, do not request a copy of the solicitation. If asolicitation is released, it will be synopsized in FedBizOpps and on the NASA AcquisitionInternet Service. It is the potential offerors responsibility to monitor these sitesfor the release of any solicitation or synopsis.Technical questions should be directed to: Bernard Edwards at (301) 286-8926 orBernard.L.Edwards@nasa.gov. Interested offerors shall address the requirements of this RFI in written format asdescribed in the previous paragraphs by electronic mail to: Bernard Edwards atBernard.L.Edwards@nasa.gov no later than 5:00 PM EST on November 6, 2009.An ombudsman has been appointed -- See NASA Specific Note "B".The solicitation and any documents related to this procurement will be available over theInternet. These documents will reside on a World Wide Web (WWW) server, which may beaccessed using a WWW browser application. The Internet site, or URL, for the NASA/GSFCBusiness Opportunities home page ishttp://prod.nais.nasa.gov/cgi-bin/eps/bizops.cgi?gr=D&pin=51. It is the offeror'sresponsibility to monitor the Internet cite for the release of the solicitation andamendments (if any). Potential offerors will be responsible for downloading their owncopy of the solicitation and amendments, if any. Any referenced notes may be viewed at the following URLs linked below.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/NASA/GSFC/OPDC20220/NASA-GSFC-RFI-SURFACE-WIRELESS-CONCEPTS/listing.html)
- Record
- SN01960079-W 20090919/090918001355-093f1a2150cf147a88be6e107f8b54de (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |